Sign-up for an 18+ event
Sign-up with an age check: from the date of birth the graph sends an underage visitor to their own final screen before the form collects any contacts.
Who it is for and when to run it
For bars, clubs, tastings, escape rooms and any event minors cannot attend. You need more than a contact form: you need to turn away under-18s before they leave a phone number.
It is also a worked example of date-based branching. Three date checks send people to different screens, and the canvas shows how it fits together. Open it even if your event has no age limit, just to see how the graph handles dates.
The date-of-birth check relies on the person telling the truth. It does not replace checking ID at the door.
What the template is made of
Every block in the order it sits in the builder. Branching decides which of them a given person actually sees.
- Event registration Text block
The intro screen says «Participants must be 18 or older» up front, so anyone who does not qualify finds out before spending time on the form.
- Date of birth Date
Date of birth is required. It carries a check of «at least 18 years before today», and the graph uses it to decide where to go next.
- Sorry, 18+ only Text block
The «Sorry, 18+ only» screen appears only to people who fail the age check. The survey ends there and no contacts are collected.
- Preferred date to attend Date
Preferred date with a «not before today» check. It catches typos in the year and requests for days that have passed.
- That date has passed Text block
The «That date has passed» screen appears for a past date and ends the form, asking the person to pick a future date.
- Convenient arrival time Date and time
Convenient arrival time (date and time) with a check of «at least two days from today». If the event is sooner, the graph routes to a separate screen.
- Urgent request Text block
The «Urgent request» screen warns that confirmation will be rushed, then the person carries on to the contact fields. It shows a branch that adds a step instead of ending the form.
- First and last name Short answer
Name is required: it is checked against the guest list.
- Phone Phone
Phone is required because a call or messenger is the quickest way to confirm the day before.
- Email Email
Email is optional, for people who prefer written updates.
- Consent to data processing Consent
Consent to data processing is required and comes last, once every check has passed.
How to adapt the template
-
Change the age threshold in the date-of-birth check, for example to 21 if that is your legal drinking age or venue rule. The graph itself does not need rewiring.
-
If arrival time does not matter, delete it along with the «Urgent request» screen and connect the preferred date straight to the contact fields.
-
Replace the two-day urgency window with your own: hours for a restaurant booking, a week for a guided trip.
-
Taking group bookings? Add a party-size question (Number type) after the contacts. For stays across several nights there is the rental booking template.
-
Before publishing, run through the form three times: with an under-18 birth date, with a past date and with tomorrow’s date. You will see all three branches for yourself. The article why surveys need a visual logic editor explains the thinking behind the canvas.
How to read the results
Responses only contain requests that passed the checks: people routed to «18+ only» or «date has passed» never left contacts. If you want those people to go somewhere, add a link to one of your all-ages events on the refusal screens so the refusal is not a dead end.
Filter out requests where the arrival time is less than two days after the submission date. Confirm those first.
The preferred date in the CSV export is your guest list by day. Sort by it, not by submission time.
Common mistakes
- Treating the form check as a substitute for ID. People can enter any birth date.
- Asking for a phone number before the age check. You end up holding contacts of minors you do not need.
- Editing questions on the canvas and not retesting the branches. A deleted screen can leave a branch with nowhere to go.
- Stacking several date checks on one question without knowing which branch wins when more than one applies.
Questions about the «Sign-up for an 18+ event» template
How do I add age verification to a registration form?
Add a date-of-birth question with a check of «at least 18 years before today». On the canvas draw two arrows from it: when the check passes, on to the rest of the form; otherwise to a refusal screen. This template has it wired already; you only change the wording.
What does someone under 18 see when they fill in the form?
After entering their date of birth they land on the «Sorry, 18+ only» screen and the form ends there. They are never asked for a name, phone or email, so you do not collect contacts you should not have.
Can I check other dates the same way?
Yes. The template has two more checks: the preferred date must not be in the past, and the arrival time must be at least two days away. Each leads to its own screen. You can change the threshold, the unit (days or years) and the reference point.
Similar templates
-
Event feedback
Ratings for organisation and speakers, plus willingness to come again.
-
Event registration
Name, contacts, attendance format and track.
-
Feedback form
A smart form with branching: the user picks a reason for getting in touch and gets their own set of questions.
Do not start from an empty canvas
Open the catalog, take the closest template and rewrite the questions for your job. Five minutes instead of an hour.