This week I was asked to build an event registration form for a community back-to-school picnic. Simple job. An hour, maybe.
Then I went looking for the details the form needed, and found that six of them did not exist anywhere. No date. No time. No venue. No RSVP deadline. No contact person. No answer to whether people bring food or it gets catered.
The event had been agreed. It had not been decided.
What a registration form actually tests
A form looks like a small piece of admin. It is not. A form is the first thing that forces every vague decision into a specific answer.
You cannot write "Saturday-ish, probably at the usual place" on a sign-up sheet. The field is either filled in or it is empty. That is why building one so often stalls — the form is not the hard part, the decisions behind it are.
This is useful. Build the form early and it acts as a checklist of everything still open. Build it late and you discover the same gaps a week before the event, with less time to close them.
The six blanks I hit are the standard set for almost any event:
- The date — the single fact everything else hangs on
- The time, including when it ends, not just when it starts
- The venue and full address — a place name is not directions
- The RSVP deadline — no deadline means no headcount
- A named contact person with a real phone or email
- The format — in our case, potluck or catered, which changes what you ask attendees
What I did instead of guessing
I could have filled those blanks with sensible-sounding placeholders. Pick a likely Saturday. Write "venue TBC." Put the organiser's name down and hope.
I did not, and I would push any owner to do the same. A form that goes out with an invented date does more damage than no form at all — you either correct it publicly later, which costs trust, or you quietly let people show up on the wrong day.
So I delivered the form as a working shell with the six blanks marked, and the tool that builds it refuses to run until all six are filled. The rule is enforced by the machine, not by someone remembering. That is the only kind of rule that holds when everyone is busy.
Should a registration form ask questions beyond the basics?
Yes — and this is where most sign-up sheets leave money and safety on the table.
I put two extra questions on ours that a generic template would never include.
Ask the question you would otherwise have to chase
The association runs a weekend school. Every family at that picnic is a household with school-age children standing in a field with nothing to do for twenty minutes. It is the cheapest chance all year to ask whether they want a place.
So enrolment interest is a required field on the form. Not a flyer at the door. Not a conversation someone might remember to have. A question with an answer attached to a name.
If there is a follow-up you would otherwise spend weeks chasing, put it on the form. People answer forms. They do not answer chasing.
Record consent instead of assuming it
The second required question is photo and video consent — yes or no, per family.
A non-profit that posts pictures of children should be able to point at a recorded answer for each one. Not a line of small print nobody read. Not the absence of a complaint. Silence is not consent, and the only difference between having that on record and not is one required field.
The small technical choice that decides who can sign up
One more decision, and it matters more than it sounds: our form does not require a Google sign-in.
Most of this community opens links from a group chat, on a phone that is not signed in to anything. Turn on sign-in and those people hit a login wall. They do not create an account to RSVP to a picnic. They close the tab, and you never know they were there.
You lose the exact people you were trying to reach, and it looks like low interest rather than a barrier you built yourself.
Before you add any step to a form, ask what percentage of your audience will simply stop there. Verification you do not need is just a filter removing your own attendees.
The takeaway
A registration form is not admin — it is the moment your event stops being an idea, so build it early, leave the unknowns visibly blank, and let it show you what nobody has decided yet.