Conference Registration Template

Conference registration is really two forms wearing one URL: an identity form that feeds the badge printer, and a planning form that feeds room allocations and the catering contract. This template splits them across two pages in that exact order, because attention is highest on page one and badge typos are the most expensive mistake to fix on site.

Why these fields. The name field carries a badge-specific hint — "exactly as it should appear" — which cuts the desk-day queue of people asking for reprints. Organization and job title are optional but heavily answered at professional events, because attendees know badges drive hallway conversations; leaving them optional respects the student and independent crowd. Page two starts with ticket type, which gates everything downstream operationally: student verification at the desk, speaker green-room lists, press seating. The track multi-select is capped at two choices deliberately — parallel sessions mean a four-track "I'll attend everything" answer is planning noise, while a forced choice gives you honest room-size predictions. Dinner attendance and the catering note are separated on purpose: one is a headcount your venue bills by, the other is a requirement your caterer cooks by, and merging them into one free-text field loses the countable number.

What we left out. Payment fields — conference fees are settled by invoice or at your existing ticketing checkout, and this form's job is the operational data those checkouts never collect properly. We also left out t-shirt sizes (add one if you actually stock shirts) and hotel questions, which belong with your venue's booking link, not your database.

Who uses this. Single-track community conferences graduating to parallel sessions, internal company summits where badges and dinner counts still matter, academic symposiums, and user conferences run by startups where the organizing team is three people and a spreadsheet.

Make it yours. Rename tracks to your real agenda and add a Logic rule so choosing "Speaker" reveals a talk-title question, or "Press" reveals an outlet field — the Logic panel handles both in minutes. Set the response cap to venue capacity and a close date for when catering numbers lock. Then connect a webhook: badge-printing services and check-in apps can receive each registration the moment it lands, signed, so your desk software is never waiting on a manual export.

One structural note. Keep identity on page one even if you customize heavily. Partial submissions mean a distracted registrant who finished page one is still a recoverable lead — you have their name and email, and a friendly "finish your registration" note usually closes them.