For the host who cannot trust the count
Joke names, throwaway addresses and a list that looks full on Tuesday and half-empty on Thursday. The honest answer is that there is no approval gate, so the filtering happens in the form and in your own tidy-up.
There is no approval step on a webinar registration. A name and an email arrive on the list and are counted, and that is deliberate: an approval queue adds friction for every genuine attendee and would be judged by a human anyway. There is also no bot detection, no captcha and no verification service quietly screening addresses before you see them.
That sounds like bad news until you notice what remains. Nobody can inflate a page without a seat limit, which is enforced and stops the count where you put it. And nothing about the list is automatic in the other direction either: what you control is what the form asks, who can reach it, how big the room is, and what you delete before you export.
Company, job title, or one open field asking what they hope to get out of it. A joke registration answers one word; a real one gives you something you would use in the session.
Turn the page closed and the count drops to people you sent the password to. Crude, but it ends the problem immediately for anything not meant to be public.
Cap the room at what you can genuinely serve. Spam cannot overrun a capped page, and 'full' is a better outcome than a list nobody believes.
Read the list once with intent before you send anything. Obvious junk gets deleted, and the CSV or PDF you take away is the number you can plan against.
Every question you add to catch a fake costs you a real person who could not be bothered. That is the whole tension, and pretending otherwise makes for bad pages. The sensible rule is to add exactly one field you would genuinely read — a job title for a role-specific session, an expectation line for a workshop you are shaping — and stop there. Two thoughtful questions plus a seat limit filters more junk than six questions do, because six questions mostly discourage the people you wanted.
On the wording side, keep the promise real. A registration is not a booking confirmation, and treating the list as ground truth for catering or a room layout is how a host ends up explaining eleven missing people. It is a record of intent, and intent needs a reminder to become attendance.
The first suits an open public page; the second suits a closed session where the count has to be exact.
Name, email, and one field: what would you want to be able to do after this session? Required, one line is enough.
Name, work email, team, and the password sent with the link. Twenty seats, waitlist on, and the list read once before anything goes out.
How it works
An open page draws everything, including the nonsense. If the count has to be exact, close it and take the smaller list of people you meant to invite.
Not three. One field whose answers you would use in the session, which also makes a throwaway registration think about trying harder.
Set the seat limit where the room genuinely is. The page says places left, then says full, and nothing beyond that reaches the list.
Scan the names before the first broadcast, remove what is obviously not a person, and export the CSV or PDF you can plan against.
Questions
No, and the setting that looks like approval is not enforced. A registration lands on the list as soon as the form is submitted. Your filtering happens in the form, the door and the tidy-up, not behind a gate.
There is no captcha, no bot detection and no verification service here. Disposable addresses arrive on the list like any other. Seat limits bound the damage; reading the names yourself is the filter.
No notification goes out when you delete a name, so junk entries disappear quietly. The statuses you maintain — registered, attended, waitlisted, cancelled, no-show — are for your own record.
It can, and it is worth pruning there too. The difference is that a waitlist overflow is not the number you plan the room against, so the pressure on it is lower.
For anything you have to serve, no. A believable count of forty beats an inflated two hundred, and the reminders you send afterwards go to people who were real enough to sign up.
Get Started
One honest question, a door you choose, a cap that matches the room, and a minute of reading before you export. That is the whole method.
