For knowing the room before you enter it
Pre-qualifying is not screening people out; nobody is vetted, and the seat limit is the only stopper. It is learning who has taken a seat in time to run the session for them.
Most hosts collect signup answers the way offices collect paper: filed, respected, unread. That is the cost of running without signup questions, and it is paid on the night — the session pitched a level too high for half the room, the example that landed was the one nobody recognised, the follow-up email said company to an audience of volunteers.
The alternative is to ask three questions with the answers already assigned a job. Not a survey; a pre-reading of the room. When Tom runs his quarterly planning session he keeps exactly two custom questions, and each has a named use: one decides which case study opens, the one below decides who the follow-up is written for. That is what pre-qualify means in practice — qualifying your own preparation, not the guest.
Ask which part of the process they use weekly. The answer orders your running examples and quietly reveals who is not actually in the room for the right session.
Ask what they will bring, in one text field: a tool, a spreadsheet, a real case. A workshop's biggest failure mode is an unprepared room, and the form is the cheapest way to prevent it.
Ask a tenure question — new this month, or years in. The two halves of that answer need different courtesies, and the follow-up after the session can carry the same split as a segment.
Say hello to extra questions entirely. The page can sit behind a password, the list is already the audience, and every field is a tax on people you know by name.
Draw the line firmly, because the phrase pre-qualify tempts hosts toward a product they do not have. There is no approval gate: nobody's registration waits on your review, and a completed form is a booked seat up to the limit. If you truly need a vetted room, the honest tools are a cap set small, a password on the page, and invitations you send yourself.
Questions also cannot hold a seat, open a second session, or rescue a bad date. What they can do is make the first ten minutes of the session feel like it was written for this exact list — which is, in the end, the only thing a signup form was ever for.
How it works
Write down two or three things you will decide before the session starts — the opening example, the depth, the follow-up audience. A question is a pipe between the form and one of those decisions.
In the webinar page builder, attach each question as text, select or number. Keep the options in your select short enough that a thumb can read them.
The always-on pair does the delivery work. Mark one custom question required at most, and only if the session genuinely degrades without the answer.
As registrations land, the answers sit beside each name on your list. Ten rows in, you already know how the room reads; adjust the order of chapters accordingly.
Questions
No, and no page should imply it. There is no approval step in registration: every completed form books a seat until the limit is reached. Signup answers prepare you for the room you got; the cap, the password and a personal invitation list decide the room you allow.
Whichever you can read at speed. A number field suits years or count; a three-option select — new, working, doing this weekly — suits judgement. The answer's job is to group the room in one glance, and a glance is not a spreadsheet.
Past three or four custom fields, you are trading list quality for list size, and the trade is invisible until the room is emptier than the cap. Keep the questions whose answers you consulted last session; the rest are habit.
Answers live with each person's row on your attendee list, and the export carries that list as CSV or PDF. Read them on the dashboard before the day; export for whoever is helping you run the room.
Get Started
Two or three questions, each with a job on the night, and the discipline to run without the rest. Build the page, set the limit, and read the rows as they arrive.
