Formiqa/Templates/Event Registration Form Template
Free template · 7 fields included

Event Registration Form Template

Register attendees for conferences, workshops, meetups, and webinars with a clean event registration form. Collect ticket type, dietary requirements, and accessibility needs — all in one place.

No credit cardFree forever planCustomizable fields

An event registration form turns interest into a confirmed headcount. It is the moment a vague "maybe I'll come" becomes a named attendee with a ticket type, a meal preference, and a way to reach them if the venue changes at the last minute. Whether you are filling a 40-seat workshop or a 400-person summit, the registration form is where your logistics either come together or fall apart: it feeds your catering guarantee, your badge print run, your check-in list, and your capacity math all at once. Get it wrong and you are guessing headcounts the week of the event.

A well-built version of this form stays short but captures the fields that downstream logistics actually depend on. This template collects Full Name and Email as required fields, an optional Phone number for day-of contact, Company or Organization for the badge and networking, a Ticket Type dropdown (General Admission, VIP, Student, Speaker), Dietary Requirements as a single-choice list (None, Vegetarian, Vegan, Halal, Kosher, Gluten-free), and a Special Requirements text box for accessibility and other needs. The insight most first-time organizers miss: caterers and venues bill against a guaranteed number submitted days in advance, so a dietary field that maps cleanly to meal counts is worth more than any fancy design. One free-text "food allergies" box that people fill with essays is a nightmare to tally; a fixed radio list you can filter and count is not.

Deploy it by publishing the form to its own link and pasting that link into your event page, email invites, and social posts. Because the ticket type and dietary fields are structured, your Formiqa dashboard becomes a live attendee database you can export the day the caterer needs final numbers, rather than a pile of replies you have to transcribe by hand.

Fields included

7 pre-built fields, ready to customize.

#
Field label
Type
Required
1
Full Namee.g. John Doe
Short text
Yes
2
Email Addresse.g. john@email.com
Email
Yes
3
Phone Numbere.g. (555) 000-0000
Phone
No
4
Company / Organizatione.g. Acme Inc.
Short text
No
5
Ticket Type
Dropdown
Yes
6
Dietary Requirements
Radio (single choice)
No
7
Special Requirementse.g. Any accessibility needs or special requests?
Long text
No

All fields are fully customizable — add, remove, or reorder after opening the template.

Use cases

Who uses this template.

Conference and multi-track summit registration where you need to sort attendees by ticket tier (General, VIP, Student, Speaker) for badge color and access
Paid workshops or training cohorts where you invoice or take payment separately and use the form purely to confirm the seat and collect prep details
Community meetups and user groups that need a fast RSVP count for room booking and pizza orders
Webinars and virtual sessions where you collect the email to send the join link and calendar invite after registration
Gala dinners, awards nights, or any seated event where the dietary field directly drives the catering guarantee and table plan
Speaker and VIP intake, using the Speaker ticket type to route those registrations to a different follow-up (green room details, AV check times)
Best practices

How to get the most from this form.

Make the dietary field a fixed list, not free text

This template uses a radio field with None, Vegetarian, Vegan, Halal, Kosher, and Gluten-free precisely so you can filter and tally meal counts in seconds. Caterers want a clean number per category for the banquet order; a free-text box gives you paragraphs you have to read one by one. Keep None as an explicit option so a blank never means "unknown."

Treat the Special Requirements box as your accessibility channel

Rename or introduce this field clearly so attendees know it is where to flag wheelchair access, a sign-language interpreter, a quiet room, or a plus-one carer. These requests have real lead times, so surface them early and check the field the moment registrations open, not the week of the event.

Use ticket type to drive what happens next, not just pricing

The General/VIP/Student/Speaker dropdown is your segmentation key. Export and filter by it to print the right badge colors, build separate check-in lists, and send tier-specific instructions. Speakers and VIPs usually need different information (arrival times, green room, parking) than general attendees.

Add conditional logic for tier-specific questions

With Formiqa's conditional logic you can show extra fields only when they apply: reveal a "Student ID upload" file field when Ticket Type is Student, or a "Talk title" field when it is Speaker. This keeps the form short for the majority while still capturing what each segment needs, instead of showing everyone every field.

Plan for capacity manually, because there is no auto-cap

Formiqa has no built-in registration limit, so watch your submission count in the dashboard and unpublish the form the moment you hit venue capacity. Set a mental threshold a little below the true max to leave room for VIPs and speakers who register late, and point overflow to a waitlist form.

Send a confirmation email with the details people lose

Enable email notifications so you are alerted on every signup, and configure a confirmation to the attendee with the date, address or join link, start time, and what to bring. Registrations happen weeks ahead; the confirmation email is the artifact people search their inbox for on the morning of the event.

FAQ

Common questions.

What fields should an event registration form actually collect?
Keep required fields to Full Name and Email so the form is fast, then add what your logistics depend on. This template pairs those with an optional Phone (for day-of contact), Company/Organization (for badges and networking), a required Ticket Type, an optional Dietary Requirements list, and a Special Requirements box. Resist adding fields you will not act on; every extra required question lowers your completion rate.
How do I handle payment if my event isn't free?
Formiqa does not process payments, so this form is best for free events or a register-then-invoice flow. Collect the registration and ticket type here, then send a payment link (Stripe, PayPal, bank transfer) in your confirmation email, or take payment through a dedicated ticketing platform and use this form only for the dietary and accessibility details that ticketing tools handle poorly.
Can I cap registrations when the event sells out?
There is no automatic submission cap, so you manage capacity by hand: monitor the running count in your dashboard and unpublish the form once you reach the venue limit. A practical habit is to close registration slightly early and keep a short waitlist form live so you can backfill cancellations without overbooking.
How do I get a clean attendee list for check-in and catering?
On Formiqa Pro, use Export CSV from the submission dashboard to download every registration with timestamps. Because Ticket Type and Dietary Requirements are structured fields, the export sorts and filters cleanly, so you can produce a per-category meal count for the caterer and a check-in sheet grouped by ticket tier without retyping anything.
Can I reuse this form for a recurring or annual event?
Yes. Duplicate the form for each occurrence, rename it with the event date, and publish a fresh link so each edition keeps its own submissions and count. Keeping them separate means last year's registrations never contaminate this year's catering numbers or check-in list.
How should I ask about accessibility needs without making the form clunky?
One well-labeled Special Requirements text field does the job: it invites wheelchair access requests, interpreter needs, dietary allergies beyond the standard list, and language preferences in a single place. Make it optional and phrase the label as an open invitation. For events with predictable needs, you can also use conditional logic to reveal a more specific follow-up field only when someone indicates they have a requirement.
Will attendees automatically get a confirmation and calendar invite?
Formiqa sends you an email notification on every submission, and you can configure a confirmation email to the registrant with all the event details in the body. It does not generate a calendar (.ics) file automatically, so a common approach is to include a "Add to calendar" link or the raw date and time in that confirmation email so attendees can save it themselves.

Use this template for free.

All 7 fields included. Customize and publish in minutes.