How to make a registration form

To make a registration form, write down everything the class or event cannot run without, turn each item into one question, order those questions the way a person thinks about booking (which day, which ticket, who they are, what they agree to), and end on a confirmation screen that says what happens next and when. Keep optional questions few and late, say plainly how payment and places work, and test the finished form on a phone before you share it.

Decide what you need before you build

GOV.UK’s service manual calls the first step a question protocol: a list of every piece of information, made before the form. A question earns its place only if you know that you need it to deliver the service, why you need it, what you will do with it, which people need to give it, how you will check it and how you will keep it up to date and secure.

Run your draft through that list and registration forms shrink. The W3C forms tutorial makes the same point from the other side: people prefer simple, short forms, and asking for irrelevant or excessive information makes them more likely to abandon.

The pottery workshop registration form for a fictional studio passes the test field by field. It asks for a postal address, which looks like overreach for a one day class, until you know the reason: firing takes about three weeks, and the studio posts finished pieces to people who cannot come back for them. The address is optional for exactly that reason. The mobile number is there for one job, reaching people if a class time moves. Every question on the form has an answer to “why is this being asked”, even where the form itself does not print it.

The same thinking separates a registration form from a survey. A registration collects what you will act on; a survey measures opinion. The form against survey note sets out that line if your draft has started to wander into feedback questions.

The field order

GOV.UK advises starting with the questions that tell people whether they can use the service at all, so nobody wastes time. For a class, that is the date and the price. The workshop form opens with who is booking, then moves straight to “Which day, and at what rate”, then the practical questions about the day, and closes on “The two agreements” with a single signature.

Three ordering rules do most of the work.

Choice before commitment. People decide to book on the date and the price. Show those early, while they are still deciding, and leave the terms until they have already chosen.

Optional questions late. “How did you find us?” is useful to the studio and worth nothing to the person booking, so it sits after the practical questions and is never required. Nielsen Norman Group recommends keeping optional fields to one or two and labelling them clearly, which is a fair challenge to any form, this one included.

Agreements last, and separate. The workshop form asks about the cancellation policy and the safety terms as two questions, then photographs as a third with three choices, because agreeing to the safety terms is not agreeing to be photographed.

The first aid course registration form follows the same order with higher stakes. It asks for the unit and the session first, then a Unique Student Identifier, and its welcome screen warns that without a valid identifier no statement of attainment can be issued, even after passing. The blocker is named before the person starts typing.

Payment and capacity

Be straight with people about both, because the form is where their expectations are set.

A registration form built here takes no payment, so the honest pattern is to capture the choice and hand over. The workshop form asks which rate applies from four options and says in its intro that places are held for five days while the deposit clears. The first aid form has a “Who is paying” section with three answers, including an employer who should be invoiced, and a follow up asking for the email that receives the invoice. When payment has to happen straight away, send people to a payment page from the thank-you screen button, or use the redirect add-on.

Capacity works the same way. Nothing on the form closes a class when it fills, so give people somewhere to go when their date is gone. The workshop form’s date question ends with an option to be put on the list for the next class. When a date sells out, remove it from the options and publish again. The event registration fields post covers which fields each kind of event needs, so this post does not repeat that list.

Confirmation

The thank-you screen is the only moment somebody who has just given you their details is paying full attention. Use it to answer three questions: did it work, what happens now, and when.

The workshop form’s thank-you screen says the place is held for five days while the deposit clears, and that the invoice, the address and what to wear are in the inbox. The webinar registration form goes one step further and plans for failure: check the inbox for the joining link, look in spam if it has not arrived in ten minutes, then get in touch.

The screen offers four layouts, a button with its own URL, an automatic redirect after a set number of seconds once that URL is set, and confetti. A registration for a class you have looked forward to can carry confetti. A registration for a compliance course probably should not.

Mobile

Assume the form is opened from a link on a phone. Nielsen Norman Group recommends a single column with labels immediately above the fields for mobile and shorter forms, and warns against placeholder text.

A classic form laid out in flow or paginated mode already falls back to a single column on a narrow screen, so a person on a phone scrolls while a person on a laptop steps through pages. Two things are still worth checking. Turn on the sticky submit button for anything longer than a couple of screens, so the button stays reachable. And keep option lists readable: the swim school registration form puts eight start times in a dropdown rather than eight radio buttons, which is kinder to a thumb.

If the whole registration is short and every question stands alone, a conversational form asks one question per screen on any device. The webinar example does exactly that in eight questions, with the contact details gathered on a single screen by a profile component.

The fields, one by one

The table at the end of this article breaks the workshop form into its fields, the component each uses, whether it is required and why it is there. Use it as a template for your own review. Read down the last column and delete any row where you cannot write a reason. Then read down the required column and ask whether each yes would stop the event running if it were blank.

Common mistakes

Asking for everything at sign up. Dietary needs for a class with no food, a job title nobody prints, a date of birth for an adult workshop. Each is a reason to stop.

Promising an email the form does not send. Email alerts go to one address you set, so the confirmation to the attendee has to come from somewhere else. Say where, and when.

Help text in the wrong place. On a published classic form, a field description only shows for file upload and photo fields. Put a short hint in the sub-label under the field, or a paragraph block above it.

Bundling the terms. One tick for cancellation, safety and photographs records none of them clearly.

Free text for choices. A date typed as “next Saturday” is a phone call waiting to happen. Offer the dates as options.

Build it

The multi step form builder page shows a classic registration form set to paginated, and the tutorial on turning a long classic form into steps walks through switching the layout. The workshop example uses Full Name, Short Text, Address, Radio Buttons, Checkboxes, Long Text and Inline Signing, all from the classic toolkit, which offers 36 of the 41 component types.

Around the form, set the welcome screen’s estimated time, write a thank-you screen that names the next step, and pick from the four add-ons: email alerts to one address, a webhook that posts each registration once with no retry, a redirect after submit, and e-signing when somebody other than the attendee must sign. Publish, copy the public link, and open it on your own phone before anyone else does.