# Building a form

You build a [routing form](/help/routing-forms/overview) in the form editor, which you
open from [**Routing Forms → New Routing Form**](/360/routing?new=1) (or by clicking an
existing form). The editor is organized into tabs:

<Screenshot
  src="/help/screenshots/routing-forms/builder.png"
  alt="The 42min routing-form builder, with tabs for Settings, Fields, Rules, Responses, Customization, and Share; the Settings tab shows the title, URL slug, public description, header toggle, language, and submit-button text"
  caption="The builder's tabs: Settings · Fields · Rules · Responses · Customization · Share."
/>

- **Settings** — the form's **title**, its **URL slug** (the public link is
  `42min.us/routing/<slug>`), a **public description**, whether to **show the header**
  on the public page, the **language**, and the **submit button text**.
- **Fields** — the questions you ask. Add a field, give it a **label**, pick a **type**,
  mark it **required** if needed, and reorder by drag (the order is the order visitors
  see them). Field types:
  - **Dropdown** / **Radio** / **Checkboxes** — choose from a list of options you
    define (checkboxes allow multiple).
  - **Text** / **Textarea** — short or long free text.
  - **Number** — numeric answers.
  - **Email** / **Phone** — typed appropriately.
- **Rules** — the routing logic — see [Routing rules](/help/routing-forms/routing-rules).
- **Responses** — every submission, with the answers given and where the person was
  routed.
- **Customization** — the public page's theme and branding.
- **Share** — the public link and embed options.

## How to do it

1. Open [**Routing Forms → New Routing Form**](/360/routing?new=1).
2. On **Settings**, set the title and slug (and tweak the description / language /
   submit text if you like).
3. On **Fields**, add the questions you need to route correctly — typically one or two
   (e.g. a "Team size" dropdown).
4. On **Rules**, add your [routing rules](/help/routing-forms/routing-rules) and the
   mandatory fallback, each pointing at a [destination](/help/routing-forms/destinations).
5. Save, then test the public link yourself.

<Callout type="tip">
Keep the form short. The fields here exist to *route*, not to gather everything — once
you route someone to an event type, that event type's own
[booking questions](/help/event-types/booking-questions) collect the rest.
</Callout>

## Common pitfalls

- **A field with no good answer for everyone.** A required field with options that
  don't cover every visitor will block some of them — add a catch-all option or make it
  optional.
- **Field referenced by a rule, then deleted.** If you remove a field that a rule's
  condition uses, fix the rule too — otherwise the condition can't match.
- **Slug clash.** Each routing form needs a unique URL slug; the editor flags reuse.