Conference registration form template (fields to copy)

What fields does a conference registration form need?

The full template. Copy the rows you need. "Conditional on" means the field only appears when that condition is true.

Twenty-six rows is a large field inventory even when many are conditional. Preview every ticket path, count the fields each buyer sees, and remove any answer without a named user and action.

What is the shortest registration form that still works?

1. First name            [text]      required
2. Last name             [text]      required
3. Email                 [email]     required
4. Organization          [text]      optional if used on badge
5. Dietary requirements  [select: None / Vegetarian / Vegan /
                          Gluten-free / Dairy-free / Halal /
                          Kosher / Other, please specify]  required
6. I have read and accept the code of conduct at [URL]
                         [checkbox]  required

Use this version for a single-day event under about 200 people with no workshops, no international travel and no sponsors receiving lead lists. A 150-person nonprofit summit at $95 does not need a passport field.

If the event has no catering, remove the dietary question. Add job title only if the badge or another defined task needs it.

When do you need the full version?

The four triggers, and what each one costs you if you skip it:

• Workshops with capacity. Without a workshop choice at registration you are running a second signup after purchase, and reconciling two lists.
• International attendees. Visa letters requested by email in the final month, each needing a passport name you then chase.
• Corporate buyers. Some organizations need a purchase order or tax details on their invoice. Make the relevant billing fields available when requested.
• Sponsor lead sharing. Establish the appropriate legal basis before sharing attendee details. If you rely on consent, explain the recipients and purpose and obtain the consent before sharing; registration is one possible collection point.

How do you adapt the template by conference type?

Two adaptation notes that apply to everyone. Keep the field labels identical to what appears on the badge, so the person who prints badges does not have to interpret anything. Use a select for categories the caterer needs to count, with an open-text route for requirements the list does not cover.

What should you not ask?

Three specific traps:

1. Phone numbers without a contact plan. Decide whether your team needs individual calls, an opt-in alert channel or email before collecting a number.
2. Home addresses for a virtual event. If you are shipping something, ask at the point of shipping. If not, do not ask.
3. Open-ended questions with no owner. Ask a specific question where possible, and assign someone to read and act on any open-text responses.

How do you build this form on Checkout Page?

How do you check the form before it goes live?

Five checks to include in the rehearsal:

1. Every required field is genuinely required, and nothing else is.
2. Each conditional field appears when it should and stays hidden when it should not.
3. The confirmation email contains the ticket PDF with a QR code, the date, the venue and the refund policy link.
4. The CSV export column names are understandable to someone who was not in the planning meetings.
5. Attendees can describe dietary requirements the predefined list does not cover.

Once the form is live, resist editing it mid-sale. Changing a field halfway through means half your attendees answered a question the other half never saw, and you will find out in the week you least want to. If you must add a field, make it optional and email the earlier buyers separately.

For the reasoning behind each question rather than the list itself, read conference registration form questions. For what the desk does with these answers on the day, see conference check-in.