SendForm.net

Registration Form: What to Ask, What to Skip and a Template to Copy

A registration form collects the minimum details needed to confirm someone's place: usually their name, email address, the session they want and any capacity or access details. This guide covers which fields to ask for and which to skip. It also includes a registration form template you can copy and shows how to close sign-ups when places run out.

Jay HoldenPublished ยท 8 min read
Event check-in desk with a tablet showing a registration form, blank name badges and a row of limited places
Key takeaways The short version, before the details.
  1. Every registration form needs a name, an email address, a session choice and a way to count places.
  2. Only add optional fields that change what you do on the day, such as dietary needs at an event or skill level in a class.
  3. Leave out date of birth, full address, ID numbers and anything you will not act on.
  4. Copy the HTML template below, or build a hosted form with a response limit, a closing date and one response per person.

What is a registration form?

A registration form is how someone claims a place in something with limited room: an event, a class, a club season or a workshop. It has one job: tell you who is coming, to what, and what they need to take part.

That makes it different from a survey or a contact form. Every field should help you confirm the place, plan for the day or reach the person if something changes. If a field does none of those, it slows people down and adds data you then have to protect.

Registration form fields every form needs

Most registration forms get by with these five fields. Start with them and add only what your use case needs.

FieldWhy you need itInput to use
Full nameCheck-in list, name badges, finding the right bookingOne text field with autocomplete set to name
Email addressConfirmation, changes, cancellationsEmail input, required
Session or dateWhich place the person is takingRadio buttons for a few options, a dropdown for many
Number of placesCounting real attendance when people bring guestsNumber input with a minimum and maximum
Access or dietary needsMaking sure the person can actually take partShort free text, or checkboxes with an "Other" option

Use one name field instead of separate first and last name fields unless you print badges sorted by surname. One field works for more naming conventions and is one less box to fill. The autocomplete attribute lets the browser fill the name and email in a single tap.

Which optional fields to add by use case

Optional fields belong on the form only when the answer changes what you do. Here is what usually earns its place, by type of registration.

  • Dietary requirements when food is served, as checkboxes with an "Other" option.
  • Number of guests when people can bring a plus one.
  • Phone number, optional, for last-minute changes on the day.
  • Ticket or session type when you run several tracks or days.
  • Experience level so you can group beginners and regulars.
  • Start date or term when the same class runs more than once.
  • Parent or guardian name and contact for children's classes.
  • Health or mobility notes for physical classes, as optional free text.
  • Membership type such as adult, junior or family.
  • Emergency contact for sports and outdoor clubs.
  • Photo consent as a yes or no question if you publish photos.
  • How they want to help when you rely on volunteers.
  • Experience with the topic so you can pitch the level right.
  • What they want to leave with, as one short text answer.
  • Equipment they will bring, for example a laptop or their own tools.
  • Company or role only for professional workshops where it shapes the content.

What not to ask on a registration form

Every extra field costs you some sign-ups, and every piece of personal data is something you have to store, protect and delete later. Under the GDPR's data minimisation principle, you should only collect what you need for the purpose.

  • Date of birth. If age matters, ask a yes or no question such as "Are you 18 or over?"
  • Full postal address. Ask for it only if you are posting something.
  • Gender, job title, company size. Leave these out unless they change the session.
  • "How did you hear about us?" Keep it only if someone actually reads the answers.
  • A password or account. People should not need an account to take a place.
  • Card details. A form is not a payment page. Take payment through a payment provider instead.

For more on how each field affects completion, see short form vs long form.

Registration form template you can copy

This registration form template is plain HTML and works on any static page. It posts to a SendForm endpoint, so submissions arrive in your dashboard and inbox without a backend. Create a contact form in the dashboard and replace YOUR_FORM_ID with that form's ID.

<form action="https://sendform.net/!YOUR_FORM_ID" method="POST">
  <label for="name">Full name</label>
  <input id="name" name="name" autocomplete="name" required>

  <label for="email">Email address</label>
  <input id="email" type="email" name="email" autocomplete="email" required>

  <fieldset>
    <legend>Which session will you attend?</legend>
    <label><input type="radio" name="session" value="Morning" required> Morning</label>
    <label><input type="radio" name="session" value="Afternoon"> Afternoon</label>
    <label><input type="radio" name="session" value="Both"> Both</label>
  </fieldset>

  <label for="guests">Guests you are bringing</label>
  <input id="guests" type="number" name="guests" min="0" max="10" value="0">

  <label for="message">Access or dietary needs</label>
  <textarea id="message" name="message" required placeholder="Write none if there are none"></textarea>

  <input type="text" name="_hp" tabindex="-1" autocomplete="off" hidden>

  <button type="submit">Register</button>
</form>

A few notes on how it works:

  • The endpoint requires email and message. That is why the needs field is named message and is required.
  • Other named fields, here name, session and guests, are stored as extra fields. A form can send up to 25 of them.
  • _hp is a honeypot field. People never see it, so any submission that fills it in is marked as spam.
  • The radio group sits in a fieldset with a legend so screen readers read the question with each option. The W3C forms tutorial explains why.

This version cannot count places

A static HTML form keeps accepting submissions until you take it down. If you have a fixed number of places, use the hosted form below. It closes itself at your limit or on your closing date.

How to stop registrations when places run out

Overbooking usually happens because the form stays open after the last place has gone. A hosted SendForm form has a Closing section in its Options tab with four controls:

  • Accept responses: switch it off to block new answers right away.
  • After this many responses: the form closes once it has received that many responses.
  • On this date: the form closes at that date and time.
  • Message when closed: what visitors see instead of the form. If you leave it empty, they see "This form is no longer accepting responses."

The server checks the limit and the closing date again on every submission. Someone who opened the page before it closed still cannot get in after the last place has gone.

The limit counts responses, not people. If one response can register three guests, a limit of 50 could mean 150 people. Either set the limit to your capacity divided by the most guests one person can bring, or remove the guests question and ask everyone to register for themselves.

Use the closed message to say what happens next, for example "All places are taken. Reply to your confirmation email to join the waiting list."

How to build a registration form with SendForm

The hosted form builder has an Event registration template that already contains the core fields. Here is how to set it up with a limit, a closing date and one response per person.

  1. In the dashboard, create a new form and set the form type to Hosted form. Enter a form name and a notification email, then click Create form.
  2. On the Builder tab, choose Start from a template, then Event registration. You get Full name, Email address, Phone number, a session question (Morning, Afternoon, Both), Dietary requirements with an Other option, and Number of guests from 0 to 10.
  3. Rename the session options to your real dates, and delete any question you do not need.
  4. Open Options and turn on One response per person. Choose By email, which also makes the email question required.
  5. In Closing, set After this many responses to your capacity and On this date to your registration deadline. Then write a closed message.
  6. On the Share tab, copy the link, or copy the embed code to put the form on your own site.

Responses show up on the Responses tab, and the Summary tab counts how many people picked each session. That makes it easy to see when one session is filling up.

Payment is out of scope. SendForm forms do not take payments. For a paid event, take payment through your payment provider and use the form for the details you need.

Hosted event registration form that closes automatically when places run out
Online form builder

Stop overbooking your next event

Start from the Event registration template, then set a response limit, a closing date and one response per person. Share one link.

Build a registration formNo account needed to answer

Frequently asked questions

At minimum: full name, email address, the session or date the person is registering for, and how many places they need. Add access or dietary needs if they affect the day. Only add other fields if the answer changes what you do, such as experience level for a class or emergency contact for a club.

A registration form reserves a place in something with limited room, such as an event, class or workshop, so it asks about sessions and needs. A sign up form usually creates an account or adds someone to a list, such as a newsletter, and often needs only an email address. People often use the two terms interchangeably.

In a hosted SendForm form, open Options and set "After this many responses" in the Closing section. Once the limit is reached, the form shows your closed message. Remember that the limit counts responses, not people, so allow for guests when you choose the number.

Yes. Turn on "One response per person" in the form's Options. By email blocks a second response from the same email address. By IP address blocks a second response from the same network, so people sharing an office or home network count as one. Both checks run on the server and store only a one-way hash.

Not a SendForm form: SendForm forms do not process payments. For a paid event, take payment through a payment provider. Use the registration form for names, sessions and needs, and never ask people to type card details into a form field.