> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orriven.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Surveys

> Ask attendees after the event: build questions, publish and open the survey, collect answers from the entry pass, and read the results.

A survey collects feedback after registration — follow-ups the registration form was too early to ask. It uses the same question builder as the registration form. Attendees answer from their [entry pass](/en/events/hosted-pages). Surveys are listed under **Surveys** in **Marketing**.

## Create a survey

<Steps>
  <Step title="Name it">
    Choose **Create survey** and enter a name, such as "Post-event feedback". Questions, publishing, and opening happen on the survey's own page. A new survey is a **Draft**: invisible to attendees.
  </Step>

  <Step title="Build the questions">
    Choose **Add question** and build the survey the way a [registration form](/en/ticketing/registration-form) is built — short answer, paragraph answer, single choice, multiple choice, dropdown, plus layout items that ask nothing. Reorder, duplicate, or remove questions from each card. **Save draft** keeps the work. Attendees see none of it yet.
  </Step>

  <Step title="Publish">
    Choose **Publish** and confirm. Publishing snapshots the questions on screen into what attendees will see — unsaved edits are saved first. Publishing does not open the survey.
  </Step>

  <Step title="Open">
    Choose **Open** to start collection. Only then does the survey appear on entry passes. **Close** stops collection. **Open** again resumes it.
  </Step>
</Steps>

Publishing and opening are separate: publishing decides *what* is asked, opening decides *whether* it is being asked. A survey can be published weeks ahead and opened on the closing day.

The page shows the current state: **Not published** while there is no published version; "published but not open" while the fill page still answers "not found"; and "the draft differs from what attendees see" after editing a published survey — publish again to update it.

## Lifecycle

| Status       | Meaning                                                                    |
| ------------ | -------------------------------------------------------------------------- |
| **Draft**    | Being built. Nothing is visible to attendees.                              |
| **Open**     | Collecting. Confirmed attendees see it on their entry pass and can answer. |
| **Closed**   | Not collecting. The fill page answers "not found". Can be reopened.        |
| **Archived** | Retired. Invisible to attendees, read-only in the console.                 |

* **Archive** is available from any state. **Restore** lands on **Closed**, never Open.
* Surveys are **never deleted** — answers point at them.

## Where attendees answer

The entry pass has a **Surveys** section listing the event's open surveys, each marked **Open** or **Answered**. Opening one shows the published questions. **Submit** saves the answers. A person who has already answered sees their answers and can **Edit my answers** while the survey stays open — saving again replaces the earlier set.

Only a **confirmed** registration can answer. A pending, waitlisted, or cancelled registration sees no surveys. To let someone answer, confirm their registration.

<Note>
  There is no public or anonymous survey. Every response belongs to one registration, which is what makes "one response per person" and the confirmed-only audience possible.
</Note>

## Read the results

**View responses** — from the list or the survey page — opens the results:

* **One card per question.** Choice questions show a bar chart of how often each option was picked. Text questions show the latest answers. Each card states how many of the respondents answered it.
* **All responses** — a table with one row per respondent (name and email, submission time) and one column per question, searchable and exportable as CSV.

A question removed from the draft still appears in the results as long as anyone answered it. The response is a snapshot of what was asked at the time.

## Automations

The trigger **Survey response submitted** fires when a person submits a survey for the **first time**. Editing and resubmitting does not fire it again. Use it with a thank-you email — see [Automations](/en/marketing/automations).

## Rules to know

* **Draft is invisible; published and open are separate.** Attendees see nothing until the survey is published *and* open.
* **One response per person**, replaced on resubmission, never duplicated.
* **Confirmed attendees only.** The registration's status is the only switch.
* **Closed answers "not found"** to the outside, the same as a draft or an archived survey.
* **Editing a published survey changes nothing live until it is published again.**
* **Restore lands on Closed.**
* Surveys are not part of the Developer API.

## Related

<CardGroup cols={2}>
  <Card title="Registration forms" icon="list-checks" href="/en/ticketing/registration-form">
    The same builder, asked at registration time.
  </Card>

  <Card title="Hosted pages" icon="panel-top" href="/en/events/hosted-pages">
    The entry pass, where open surveys are listed.
  </Card>

  <Card title="Automations" icon="workflow" href="/en/marketing/automations">
    Thank respondents on the survey-submitted trigger.
  </Card>

  <Card title="Email templates" icon="mail" href="/en/marketing/email-templates">
    Send the entry pass link to invite responses.
  </Card>
</CardGroup>