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

# Questions at check-in

> See how custom questions marked shown when scanning appear to your scanners

Some things you ask at registration only matter at the door. A meal choice is useless in a spreadsheet at the entrance — it needs to be in front of the person scanning, at the moment they scan.

That's what **shown when scanning** does.

***

## How it works

<Steps>
  <Step title="You add a custom question to the registration form">
    On the event wizard's registration step, click `Add Custom Form` and write your question — for example `What food type would you want?` with options `Chicken`, `Veg`, `Fish`.
  </Step>

  <Step title="You scope it to the right ticket categories">
    Use `Applied to:` so only the relevant buyers are asked. A meal question might apply to `VIP` only.
  </Step>

  <Step title="You turn on Shown when scanning">
    The saved question then summarizes as something like *Dropdown • Required • Shown when scanning*.
  </Step>

  <Step title="The attendee answers at checkout">
    Their answer is stored on their order.
  </Step>

  <Step title="Your scanner sees it at the door">
    When the ticket is scanned, the answer appears alongside the check-in result.
  </Step>
</Steps>

Full setup detail: [Registration form and custom questions](/events/registration-form).

***

## What to use it for

Turn it on for anything a staff member **acts on at the door**:

* Meal or dietary choice, so catering gets the right count at the right table.
* Drink package or bar tier, so the bar knows what's included.
* Session or track, so people are pointed the right way.
* Accessibility requirements, so someone can help immediately.
* Merchandise or swag size, so the right item is handed over.

Leave it off for anything you only analyze afterwards — how they heard about the event, marketing consent, general feedback. Those belong in the [attendee export](/attendees/export-attendees), not on the door team's screen.

<Tip>
  Every extra answer on the scan screen is one more thing to read while a queue builds. Two or three at most; beyond that the door slows down and staff start ignoring them.
</Tip>

***

## Answers you didn't mark

An answer to a question that is *not* marked shown when scanning is still collected and still available afterwards — it simply doesn't appear at the door. See [Export attendees](/attendees/export-attendees).