Build the registration form
Pages, fields, conditions and what happens after someone presses Send — built for a parent on a phone.
Every event has at least one form — one per way in: the public form, an on-behalf form your staff use at a desk, an invitation form, and the import mapping. Each template arrives with these written for its kind of event, so you are editing, not starting blank.
Who fills it in matters. EntryWick assumes a parent, on a phone, registering a whole household at once. The form is split into short pages and never asks the same thing twice for each person.
Step by step
- 1
Open the form and read it as a registrant
Events → your event → Forms → Public registration. Use Preview and go through it as a parent would. Note what is in the wrong order, what is asked and never used, and what you need that is missing. Change the form after that pass, not during it.
One form per way in. Preview before editing. - 2
Arrange pages and fields
A form is pages of fields. Keep each page to one idea: "Who is coming", "Each person", "Permissions", "Review". Field types cover the usual — text, choice, date, phone, email, number — plus the ones events need: signature, file upload (a permission slip, a photo), and consent with the text of what is being agreed to.
- Mark fields per person (asked once for each household member) or per registration (asked once).
- Required fields are refused server-side too, not just in the browser.
Pages keep a phone form short. Per-person fields repeat for each household member. - 3
Add conditions so people only see what applies
Conditional logic shows, hides or requires fields based on earlier answers: a guardian field appears only when a date of birth makes someone under 18; a chaperone question appears only for adults; a bus choice appears only if the person ticked "needs transport".
Logic is re-checked on the server when the form is sent, so a hidden required field can never block a submission and a skipped one can never slip through.
Conditional logic is a Growth-plan feature; Starter forms get validation rules (formats, ranges) without logic. See pricing.
Three conditions typical of a school or community event. - 4
Decide what happens on Send
When a form is sent, EntryWick creates a registration with one attendee per person, in one household. Then the schedules run: a confirmation email at once; tickets a set number of days before the event (or immediately, your choice); a reminder the day before.
The thank-you page says it worked and what happens next. Its text is yours to edit — including a link to the "My registration" page where people fix a typo or say somebody can't come, without emailing you.
One registration, one household, three attendees — and a self-service link. - 5
Test with a real phone, then open it
Register your own household from a phone on mobile data. Check the confirmation arrives, open "My registration", change a name, cancel one person. Then cancel the test registration from the admin (Attendees → person → Cancel) so your counts start at zero.
Finally set the form's open and close dates and share the event link.
Test on a phone, on mobile data — that is where registrations come from.
When you are done
What should be true now
- Every required field is one you will actually use.
- Under-18 attendees cannot be registered without a guardian.
- Your test registration confirmed, self-service worked, and you cancelled it afterwards.
- The form has open and close dates and the link is shared.