Reading the results

The response table

Open a survey from the Surveys list and you land on its responses. Every submission is a row, every question a column, newest first. Answers appear the moment they are submitted — there is nothing to refresh or sync.

• Click any row to open the full response: every answer laid out in order, the language it was answered in, the time it arrived, and the exact survey version it belongs to.
• Uploaded files appear as download links inside the response. They are protected — only signed-in staff can open them, and each download link is short-lived.
• Long surveys produce wide tables. The table scrolls sideways on its own without pushing the page around, and works on a phone.

Correcting, removing and emailing

Members and admins get three actions on every row of the table — viewers read but never change:

• Edit opens the response in the same form the respondent filled in — the exact version they answered, prefilled with their answers. The original survey's rules still apply: required questions stay required, options stay the same list, length limits still count, and uploaded files can be replaced or removed. A replaced file is genuinely deleted from storage on save.
• Delete permanently removes the response, its uploaded files and the contact entry it created. On an invite-only survey the invitation reopens, so the person can answer again. It cannot be undone.
• Email appears on responses that include the respondent's email address. Write a subject and a plain-text message; it is delivered in the workspace's email design, in the language the person answered in, and notes which survey it is about.

To reach more than one person, use Email respondents above the table. Everyone who left an email address starts selected; keep them all, or narrow the list — remove pills, or type to filter and pick specific people. Each recipient gets their own separate copy in the language they answered in, recipients never see each other's addresses, and an address that answered twice is emailed once. If any address can't be delivered to, the result names it and offers to retry exactly those. The recipients come from the contact directory, and one send reaches up to 200 people.

Charts

Switch from the table to the chart view and every question that can be counted is summarised automatically — single choice, multiple choice, yes/no, and rating questions. Free-text answers are not charted, because a chart of unique sentences tells you nothing.

• Each chart can be shown as a donut, pie, bar, horizontal bar, radar, gauge or area — pick whichever reads best for that question.
• Above the charts sit three numbers worth watching: total responses, the number of chartable questions, and the answer rate — how much of the survey people actually fill in. A low answer rate usually means a question is confusing or too personal.
• Charts follow the workspace brand colour, so a screenshot dropped into a report already matches your identity.

Exporting to CSV or Excel

Export from the ⋯ menu on a survey. Two formats are offered and both contain exactly the same data:

• Excel (.xlsx) — a formatted workbook. Choose this for anything a human will read.
• CSV — plain text. Choose this when the file is going into another system or a data tool.

• Columns come from your field names, which is why choosing readable ones in the builder pays off later.
• Files that respondents uploaded are not embedded in the export — the export records the file name, and you download the file itself from the response.
• Every export is logged with who ran it and when, and appears in the Activity log. Response data leaving the platform is worth a record.

Workspace analytics

The Analytics screen zooms out from one survey to all of them. It answers the questions you get asked in a meeting:

• How many responses have we collected in total, and how many this week?
• How are responses trending over the last 30 days?
• Which surveys are pulling their weight, and which are quiet?
• What is the Arabic-to-English split of our audience? (Useful when deciding which language to write first.)