---
title: Collect responses with forms
description: Build a shareable form, publish its link, and export the responses as CSV.
sidebar:
  badge: Starter+
---

Forms are a workspace-level tool for collecting information from people outside your dashboard: registration interest, team sign-ups, feedback, CFP submissions, anything you'd otherwise chase over email. As the Forms page puts it: *"Build a form, share the link, and collect responses. Forms are not tied to an event and survive teardown."*

Forms are included on **Starter and above**. On Hobby they are read-only: existing forms stop accepting responses and can't be edited, while reading and exporting what you already collected stays available; see [Plans and limits](/organizers/reference/plans-and-limits).

That last part matters. A form belongs to your **workspace**, not to an event, so it outlives any event you run and is reachable from **Forms** in the sidebar's Workspace section.

## Create a form

1. Open **Forms** in the sidebar and click through to **New form**.
2. Give it a **Title**: required, up to 200 characters (for example *Participant registration*).
3. Optionally add a **Description**, shown at the top of the form to everyone who opens it.
4. Click **Create form**.

The form is created as a **Draft** with no questions, and you land in the editor.

## Add questions

Each question is a card headed **Question 1**, **Question 2**, and so on. Every question has a **Question** label (up to 300 characters, required) and an optional **Help text** shown underneath it.

Pick a **Type**:

| Type | What the respondent gets |
|---|---|
| **Short answer** | A single-line text box (the default for a new question) |
| **Paragraph** | A multi-line text box |
| **Email** | A text box validated as an email address |
| **URL** | A text box validated as an `http` or `https` URL |
| **Number** | A numeric input, with optional **Minimum** and **Maximum** |
| **Single choice** | Pick exactly one of your options |
| **Multiple choice** | Pick any number of your options |
| **Checkbox** | A single tick box |
| **Date** | A date picker |

**Single choice** and **Multiple choice** add an **Options** list: new choice questions start with two options, and **Add option** appends more. Each option is a free-text label; you need at least one.

Every question has a **Required** switch, off by default: *"Responders cannot submit without answering."*

The row of icon buttons on each card moves a question up or down, duplicates it, or removes it. A duplicate copies the question's label, help text, type, and options, but counts as a new question; it starts with no responses of its own.

Limits: **60 questions per form**, **40 options per choice question**, and **5,000 characters** per text answer. The **Add question** button disables once you reach the cap.

:::note[Changing a question's type keeps its answers attached]
Switching type preserves the question's label, help text, and required flag, and resets the type-specific parts (options, minimum, maximum). The question keeps its identity, so answers already collected under the old type stay attached to it and get re-rendered under the new formatting. If you want a clean break, remove the question and add a new one.

Removing a question also hides every answer already collected for it, from the responses table, the detail view, **and the CSV export**. Export before you delete a question you care about.
:::

## Set the form's rules

Alongside the questions:

- **Closes at**: an optional deadline. Leave it empty to stay open.
- **Response limit**: an optional cap (minimum 1); leave it blank for unlimited.
- **Related event**: optionally tag the form with one of your events. This is *"Labelling only. The form outlives the event."* Deleting the event doesn't delete the form or its responses.
- **Email respondents a copy of their response**: off by default. Turn it on and each respondent is emailed their own answers back, to the address they typed into one of the form's email questions. Pick which email question under **Send to**. The toggle stays disabled until the form has an email question, because that address is the only one Athena will send to; you can't supply a list of your own, and nothing is sent to you.

:::warning[Re-check the deadline after saving]
You enter **Closes at** in your local time, but when you reopen the form the field redisplays that instant in UTC. If you then save again without correcting it, the deadline shifts by your UTC offset.

If you use a deadline, set it once and avoid re-saving the form afterwards, or close the form by hand when the exact minute matters.
:::

## Publish and share it

Click **Publish**. The button is disabled until the form has at least one question, and a published form can't be saved back down to zero questions.

The editor shows the form's share link: a `/f/…` address with **Copy**, **Open**, and **Rotate** buttons. Alongside it, the **Embeds** page puts the same form on a site you own, either rendered by Athena in a frame or as JSON your own interface draws; see [Embed a form on your site](/organizers/how-to/embed-a-form). Between the link and embeds, that's the whole distribution mechanism: there's no QR code, and no way for the platform to email the form for you.

:::note[Publish before you share]
While a form is a draft its link returns **"Form not found"**; the editor warns you directly: *"Publish the form before sharing this link. It returns “not found” while the form is a draft."* Anyone you sent it to early will need the link again after you publish, though publishing itself doesn't change the address.
:::

**Preview** opens the form exactly as a participant sees it, with every field disabled and a banner reading *"Preview: responses are not recorded"*. If the form is live and you have unsaved edits, save first; the button says so, because **edits to a published form go live the moment you save them**. There's no separate draft-and-publish cycle for content changes.

## What respondents experience

Anyone with the link can fill the form in: **no account and no sign-in**. Athena stores the answers, the submission time, and the browser's user-agent string; no name or email is recorded unless you ask for one as a question.

Forms don't identify respondents or enforce one response per person, and a respondent can't edit or withdraw a submission once sent. If you need identity, ask for it in a question and treat the answer as self-reported.

On success they see **"Response recorded"** and a thank-you naming the form. You aren't notified; checking the responses page is how you find out.

If you turned on **Email respondents a copy of their response**, they're emailed their answers back and the form says so above the submit button, so nobody is mailed without being told first. If the copy can't be delivered (a mistyped address, a mail outage), the response is still recorded; delivery is never allowed to reject a submission.

When a form has closed, whether by status, by passing its deadline, or by hitting its response limit, the link shows the form's title and *"This form is closed and is no longer accepting responses."*

## Read the responses

**Publish** becomes **Close form** once live, and a closed form can be reopened with **Reopen**.

The responses page opens from the editor and shows a **Submitted** column plus one column per question, newest first. Once a form has at least one embed, a **Source** column sits between them, naming the placement a response came from, or *Direct link* for one that arrived through the share link. Two things to know about it:

- It shows the **first six questions** only, noting *"Showing the first 6 questions. Open a row or export the CSV for every answer."*
- It shows the **latest 100 responses**, with no pagination. Past that, the CSV export is the only way to see everything.

Click any row for the full response: every question and answer, the source, any values attached by an embed, and the browser the response came from. That view also carries **Delete response**, which permanently removes that submission.

## Export to CSV

**Export CSV** on the responses page downloads every response, not just the first hundred, and not just the first six questions. The file is named after the form (for example `participant-registration-responses.csv`), UTF-8 with a byte-order mark so spreadsheets open it cleanly.

Columns are **Submitted at**, then **Source** if the form has any embeds, then one column per question in the order the questions appear, then one column for each value an embed records or accepts; see [Embed a form on your site](/organizers/how-to/embed-a-form). A few formatting details worth knowing before you build anything on top of the file:

- **Rows are oldest-first**: the reverse of the on-screen table.
- **Timestamps are full ISO-8601 UTC**, e.g. `2026-07-30T14:03:11.482Z`, not your local time.
- **Checkbox answers export as `Yes` / `No`**, and choice answers export as the option's label.
- **Cells that begin with `=`, `+`, `-`, `@`, or certain whitespace get a leading apostrophe.** This is a deliberate guard so spreadsheets don't execute an answer as a formula, but it does mean a negative number arrives as `'-5`. Strip the apostrophe if you're processing the file programmatically.

## Rotate the share link

**Rotate**, next to **Copy** and **Open**, issues the form a fresh `/f/…` address. Use it when a link reaches people it shouldn't have: the form, its settings, and every response already collected stay exactly as they are; only the address changes.

The old address stops working the moment you confirm, and it returns **"Form not found"** from then on. That applies to everyone holding it, not just whoever it leaked to, so re-send the new link to the people you still want responses from. Rotating can't be undone and the previous address can't be brought back.

Embeds are unaffected. Each one carries its own address, so rotating the share link leaves every embedded copy working. To stop one of those, disable or delete that embed instead.

## Delete a form

**Delete** on the editor removes the form, all its responses, and every embed of it. The confirmation spells out the cost, naming the exact number of responses you're about to destroy, and warns that the share link stops working immediately and the deletion can't be undone. Export first if you need the data.

Deleting is for throwing the data away. To stop a link working while keeping the responses, rotate it, or close the form if you want the address to stay valid and simply refuse new submissions.
