Responses & insights

Work from the response grid

Answers keep arriving; the question is usually which ones you need in front of you right now. Open a form and choose Responses. The grid loads the newest results first and fetches older pages as you scroll, so large response sets stay usable. Columns come from the current schema plus the 200 most recent stored form versions. Removed fields within that window remain visible; a field that exists only in an older version can fall outside the working column union.

• Search runs on the server across answer values and response source metadata.
• Limit the view by date, source, respondent, or field conditions such as equals, contains, answered, and not answered.
• Use Columns to tune the working view without changing the stored response or CSV schema.
• Open a row to inspect submission context, respondent identity, files, and destination delivery state. The drawer supports previous and next navigation.
• On a form set to hold unverified submissions for review, a Held switch appears whenever unverified submissions are waiting. They are stored but delivered nowhere; release the legitimate ones from that view, or delete them from the drawer.

Filter first, then export

1. 1

   Choose which responses to include

   Set a date range, search term, source, respondent, or one or more field conditions. Filters are URL-backed, so the view can be revisited or shared with another authorized teammate.

2. 2

   Check the result count

   The header count and empty state reflect the active filter. Clear or widen conditions before assuming responses are missing.

3. 3

   Choose CSV

   The export streams every matching response, not only the rows currently loaded in the browser. It preserves the active filters and uses the current schema plus the 200 most recent stored versions for columns. A field that exists only in an older version can be absent from the CSV header even when its raw answer remains stored.

Inspect versions and delivery state

Every response stores the form version it answered for history and analysis. The grid and CSV build a working union from the current schema and up to 200 recent stored versions, with the latest known field definition winning. Raw older answers remain stored, but an older-only field can fall outside that union; historical labels and option wording are not guaranteed to reproduce exactly after schema changes. Sheets and Notion use the current schema when they deliver.

If a webhook, Sheets, or Notion delivery fails, the response view keeps that status next to the stored response. Fix the destination first. Retry failed requeues only failed destinations for the selected responses and keeps the Sheets/Notion commit probe active. The drawer's Re-send deliberately sends one response to every current destination again, so use it only when another downstream copy is intended.

Read insights with the right confidence

Open Insights to see response activity, completion time, where responses came from, completion rates, and answer summaries. Use date and field filters to narrow the results. Select an answer to compare those responses with the full set.

Separate responses from in-progress drafts

Save and resume can count open drafts and show where people stopped. Completed submissions remain in Responses. Pre-submission answers appear in a separate In progress tab only when the form owner explicitly enables that privacy-sensitive setting.

Draft recovery controls, verified identity, one-response-per-person behavior, and project-wide person erasure are documented in Respondents.

Next steps