Conference registration form questions: what to ask

What should a conference registration form ask?

The form is the last thing between a person who wants to attend and your bank account. Organizers add fields because someone in a planning meeting asked for them, and nobody ever removes them.

Before a field goes on the form, name two things: the person who will read the answers, and the action they will take. If you cannot name both, cut the field.

Form friction can be expensive, but this site has no measured abandonment benchmark. Track starts, completions and field-level errors in your own checkout before attributing lost registrations to form length.

Which fields are required on a conference registration form?

Split first and last name into two fields. Single "full name" fields produce badges reading "dr. james okoro-smith" in lower case and make check-in lists harder to sort.

Validate the email and show the buyer what they typed before payment. A mistyped address can prevent ticket delivery and may not be discovered until the conference is close.

Per-attendee or per-order: which details go where?

Check how your ticketing tool scopes custom questions before you design the form. Some ask once per order, some repeat per ticket, and some let you choose per field.

If your tool asks per order and you sell group tickets to companies, you have two workable options:

The second option can reduce checkout work when an office manager does not yet know who will attend. It also creates a follow-up task and incomplete-record risk, so compare completion rates and administrative effort before adopting it.

What do you need on the form to print badges?

"Name as it should appear on your badge" is worth its own field. It lets Katherine print as Kate, keeps honorifics off the badge for people who do not want them, and stops you printing an all-caps passport name across the front.

As a rule of thumb, keep the badge name line to about 20 characters so the type stays readable from six feet away. Say so in the field's help text rather than hard-limiting the input.

Organization is the second line and the field sponsors care about most. Job title is the third line and is the one to cut first if your badge template is tight.

Make pronouns optional and free text, never a dropdown that misses options.

How should you ask about dietary requirements and accessibility?

Your caterer needs counts by category by a date, not a wall of prose. A select list with vegetarian, vegan, gluten-free, dairy-free, halal, kosher, nut allergy and other gives you that straight from the export.

For accessibility, ask something like: "Is there anything we can do to make the conference work better for you? For example step-free access, a reserved seat near the front, captions, or a quiet room." Route those answers to one named person who replies individually. An unanswered accessibility request is worse than not asking.

Both categories are sensitive. Restrict who can export them, and delete the file after the event rather than leaving it in a shared drive.

How do you let attendees choose sessions or tracks with limited capacity?

A registration question records a preference. It does not stop 180 people picking a room that seats 60, which is how free workshops attached to a paid pass go wrong.

The two mechanisms, and when each fits:

Add-ons also let you charge. A $75 pre-conference workshop attached to a $499 pass is the cleanest way to raise revenue per attendee, as covered in workshop add-ons and multi-day passes.

What consent and photo release wording belongs on the form?

Sample wording to adapt, not legal advice:

[ ] I accept the ticket terms and the refund policy. (required)
[ ] I understand that photography and filming take place at this event
    and may be used in future marketing. Tell us at the registration
    desk if you prefer not to appear. (required acknowledgement)
[ ] Email me about future events from Example Conference. (optional,
    unticked by default)
[ ] Share my name, organization and email with event sponsors.
    (optional, unticked by default)

Link the refund policy before payment and keep a record of the version the buyer accepted. Clear pre-purchase notice supports informed agreement, but visibility or a checkbox does not by itself make an unlawful or unfair term enforceable.

The sponsor checkbox is the one organizers get wrong. Pre-ticking it, or hiding sharing inside the general terms, is what generates complaints when the first sponsor email lands.

Where do discount codes, invitation codes and invoice details go?

A custom "promo code" text field is a trap. It records the code, charges full price, and leaves you issuing partial refunds by hand.

For invitation-only tiers such as alumni or past speakers, two patterns work. If your tool supports unlisted ticket types, share one by direct link so the price stays off the public page. Otherwise use a coupon code with a usage limit, which fits when the tier is a discount rather than a separate product.

For buyers who request an invoice, a conditional block can collect legal company name, billing address, tax or VAT number, purchase-order reference and an accounts-payable email. Checkout Page can use Stripe Tax to calculate tax for configured registrations and transaction data, but the organizer remains responsible for deciding where it must register and configuring the tax treatment. Scale can record payments taken manually outside card checkout; that is not the same as an integrated invoicing or bank-transfer workflow.

When should you use conditional logic and multi-step forms?

Conditional logic examples that pay for themselves:

• Show "Which workshop are you attending?" only if the buyer selected a workshop pass.
• Show a free-text allergy box only if the dietary answer is "other".
• Show company, billing address and tax ID only if "I need an invoice" is ticked.
• Show passport name and nationality only if the attendee ticks "I need a visa invitation letter".

A sensible step order to test is ticket selection, attendee details, extras and add-ons, then payment. Do not assume an abandoned form leaves a usable lead: retention and follow-up depend on what the platform records, whether an email was supplied and what contact permission applies. It also keeps multiple ticket tiers on their own screen.

Field-by-field: what to ask and why

Copy the ready-made version from the conference registration form template, then delete the rows you cannot act on. Once the form is live, read the check-in guide to make sure the answers you collected reach the right people on event day.