Responses

The first tab on this page is Dashboard — charts and headline numbers for the whole form, with the individual responses one tab over.

Responses lists every submission, newest first, across all versions of the form. A leading # column numbers the rows, and each has its own Actions — a quick view, and (for anyone with export access) a menu to download just that one response. Open a row to see its answers laid out against the questions of the version it was filed against — so a response from before you reworded a question still reads correctly.

An answer whose question no longer exists is still shown, marked as removed, rather than dropped. Silently hiding submitted data is worse than an unfamiliar label.

Beside the tab bar sits a Table / Excel view switch. Table is the everyday view above; Excel view turns the same responses into something closer to Excel — every question gets its own column, however many questions the form has, and the first couple of columns stay put while you scroll sideways through the rest. It carries the same leading row-number column as the table.

Click and drag across a block of cells, then press Ctrl+C (or ⌘+C) to copy exactly that block — paste it straight into a real spreadsheet. Click a column's header to sort by it. Excel view is for looking and copying only: nothing you do there can change a response, and there is nothing to accidentally save.

Export the whole set as CSV or Excel from the toolbar. One row per response, one column per question, using labels as headers. Multi-select answers become a delimited list; uploaded files become a reference. For a single response, use its own row-level Actions menu instead of exporting everything.

When a form is part of an app, its responses also appear on the record they were filed against. The record's timeline shows every response in order, and opening one shows that response in place, with previous and next to step through the rest — so reviewing everything collected about one school does not mean visiting each form's response list in turn.

Deleting a response is a soft delete. It leaves the list and the exports; it is not immediately destroyed. Deleting the form does not delete its responses — the form goes to Trash and the data stays with it, which is why restoring a form restores everything collected through it.

Responses never cross organizations. Every read is scoped to the workspace you are in, checked on the server rather than filtered in the browser.

A deleted form's responses travel with it into Trash and come back with it too. And for an app with many steps and thousands of records, exporting form by form stops being practical — a single background job can pull everything at once.

Which form version does a response belong to?

Each response records the exact published version it was filled on, so edits made later never change how it reads.