Formstep

Event registration form template

An event registration form collects who is coming, how to reach them and what they can eat, through one public link or an embed on the event page. A share link per channel tells you where registrations come from, and a response limit closes it when the room is full.

Updated

Use this template

Opens in the editor. No account needed to try it.

The Register for the Event form under a photo of an audience in a darkened hall, with full name, email, phone, organization and dietary requirement questions
What the recipient sees. Swap the photo and logo for your own.

What it asks

Question
Full Name
Email Address
Phone Number
Organization
Dietary Requirements (none, vegetarian, vegan, gluten-free or other)
Please specify your dietary requirements (shown when they pick Other)
Anything else we should know? (optional)

This one is a public form

The request templates here go to one known person. Event registration is the opposite: anyone with the link signs up, so you share it or embed it on the event page instead of sending requests. Logic, translations and integrations work the same way.

How to use it

  1. Select Use this template, and put the event’s name, date and place in the heading and the intro.
  2. Publish it. Make a share link per channel, and give the main one a response limit if seats are limited.
  3. Send each registration to Google Sheets for the attendee list, and to Slack if the team likes to watch them come in.

What to change

  • Dietary requirements. The follow-up question appears only when someone picks Other. Add access needs the same way: a yes-or-no question that reveals a text box.
  • Sessions and tickets. Add a dropdown of sessions or a picture choice of ticket types. For a paid event, add a payment question; it charges through your own Stripe account.
  • Who they are. Organization matters at a conference and not at a workshop. Drop it, or replace it with the team or the course.
  • Several events. Duplicate the form per event, or keep one form and one share link per event, each with its own deadline and limit.

Where the registrations go

Each registration comes back under keys derived from the titles, such as full_name, organization and dietary_requirements, which become the columns of the attendee sheet or the properties of a page in Notion. A choice answer arrives as the option’s key, so a webhook can count vegan without reading a label. The NPS survey or quick feedback template is the form to send afterwards.

When another template fits

  • RSVP when guests are invited by name and may bring others, and you need a yes or a no with a meal choice per guest.
  • Appointment booking when each person picks their own time instead of coming to one.

More templates

Questions about this template

Something else on your mind? The docs cover every setting, and we answer email.

Read the docs

Yes. Give the share link a response limit and it closes by itself at that number, or an expiry date for the registration deadline. Reopen it or raise the limit at any time.

Yes. Make one share link for the newsletter, one for social media and one for partners, and share link analytics compares them. Each link can also have its own deadline and limit.

Turn on the confirmation email and they get one with their answers. Edit the thank-you page for the address, the time and what to bring.

A way to reach the attendee, who they represent if it matters, and what the venue needs to know, usually dietary requirements and access needs. Ask for a session choice only if seats are limited per session.

Collect information from anyone.

Publish a sample form, answer it as your recipient would, and watch the answers come back. No account needed.

Read the docs