How a 62-Person Event Handled Venue Capacity with a Class Booking Poll: A Case Study
Every case study in this series so far has been about a host trying to answer the same question in a different way: who is coming? The potluck host wanted to know who was bringing what. The holiday party host wanted a headcount and a carpool list. The Christmas dinner host wanted a number to hand a restaurant.
This one is about a different question, and it changes the whole shape of the poll. The host of this event didn’t primarily need to know who was coming. They needed to know when to stop.
The poll is a 62-response event sign-up run at a private venue in South America, created one Friday morning and effectively finished the same evening — thirteen hours from creation to last recorded activity. It used three optional settings, no theme, and no deadline. On paper that reads as a poll someone barely bothered to configure. Read against the constraint the host was actually working with — a room with a fixed number of people in it — every one of those choices, including the ones they left switched off, turns out to be deliberate.
A note on method. The structural numbers in this case study — 62 responses, the thirteen-hour span between the poll’s creation and its last recorded activity, which features were turned on or off, the template and theme chosen — come directly from a real Whocan poll created in February 2026 by a host in a South American time zone, for a private event at a small venue. No personal information, identifying details, names, venue or event names, or contact data are reproduced. The narrative around the data (typical participant behavior, common patterns we see) is composite and representative of many similar polls, not a literal account of any single conversation or guest.
By the numbers
- Template: Class Booking
- Theme: No Picture
- Total responses collected: 62
- Time from creation to last recorded activity: 13 hours
- Time zone: South American
- Participants may add a private message: On
- Participants can see how others have responded: On
- Participants may answer ‘If necessary’: On
- Response deadline: Off
- Register people (bring additional guests): Off
Three settings on, two conspicuously off. For comparison, the 13-person Christmas dinner we covered two weeks ago ran on seven. This host used fewer than half as many settings for nearly five times as many people — which is the first hint that headcount and configuration density really don’t correlate, and that what actually drives a poll’s setup is the constraint it exists to manage.
Capacity is not the same question as attendance
The host chose Class Booking, and that choice does most of the work in this poll.
It’s worth being precise about what separates Class Booking from Invitation, because on the surface both are “tell me if you’re coming” tools. The difference is in the unit of the question. An Invitation poll asks about an event: here is one thing happening, are you in. A Class Booking poll asks about slots: here are dated openings, claim one. Its options are dated entries that participants register for with an “I’ll join” action rather than a yes/no tick, participants can’t add their own dates to the list, and each slot can carry a limit on how many people fit in it. The voter-facing prompt is literally “Choose the dates you will attend.”
One honest clarification, since this is the kind of thing that gets overstated: a per-option participant limit isn’t strictly exclusive to Class Booking — the setting exists on some option types in other templates too. What Class Booking does is make claiming a capped spot the entire interaction rather than an add-on. Nothing in the template invites open-ended discussion, participant-proposed dates, or negotiation. It is a door with a counter on it.
That’s why it was the right template for an event the host described, in their own words, as a capacity-control exercise. The venue had a number. The poll’s job was to reach that number and then be visibly, obviously full.
The private message field became a payment ledger
The most interesting thing this host did wasn’t in the template choice. It was a small act of improvisation.
They switched on Participants may add a private message — a free-text note visible only to the host — and then, in the poll’s description, told people what to put in it: confirmation of whether they had already paid, and for which item. The comment column stopped being a comment column and became a payment status ledger, sitting in the same table as the sign-ups.
We see this pattern often enough that it’s worth naming. The private message field is the most reappropriated feature in Whocan. Hosts use it for allergies, for arrival times, for “I’m bringing my sister,” for jersey sizes, for who needs a lift. Here it was money. The field is deliberately unstructured, and unstructured fields get used for whatever the host’s actual bottleneck is.
Two things made it work in this case:
It’s private. Payment status is mildly awkward information. Nobody wants a public column showing who has and hasn’t paid, and plenty of people wouldn’t have answered honestly in one. A note only the host reads gets the truthful answer.
It’s attached to the response. The alternative is a spreadsheet of who paid, maintained separately from the list of who’s coming, which then has to be reconciled — and reconciliation of two lists maintained by one busy person the night before an event is where mistakes live. Here the guest list and the payment ledger were the same list.
And the honest limitation, in keeping with this series: it’s a text field, not an accounting feature. It doesn’t total anything, doesn’t flag mismatches, doesn’t chase anyone, and won’t take a payment. If you need real payment handling, this isn’t it. What it gives you is one list instead of two, and for an event this size that was apparently enough.
Visible responses plus ‘If necessary’ is a waitlist in disguise
The other two settings the host enabled look mundane on their own and turn out to be a matched pair.
Participants can see how others have responded was on. In most polls that setting is about social proof — people are more likely to come when they can see who else is coming. In a capacity-controlled poll it does something more practical: it turns the response list into a live fill gauge. Anyone opening the link can see roughly how full the event already is without asking. For a host managing a hard limit, that setting is the difference between one shared link and thirty individual replies to “is there still room?”
Participants may answer ‘If necessary’ was also on, adding a third answer between yes and no. Class Booking polls often run yes/no only — you either take the spot or you don’t — so switching on a soft middle answer at first looks like it undermines the point of a capacity count. It doesn’t. It sorts the responses into two tiers: firm commitments that consume capacity, and soft ones that don’t yet.
Put those together and you have, functionally, a waitlist — without a waitlist feature. The firm yeses fill the room. The ‘if necessary’ answers are the queue the host works through when someone inevitably drops out the day before. And because responses are visible, the people in that soft tier can see for themselves how close to the front they are.
To be clear about what the tool does and doesn’t do: Whocan will not automatically promote someone from ‘if necessary’ to attending when a spot frees up. The host does that, by hand, by messaging the person. What the poll provides is an ordered, visible list of who to message — which is the part that’s genuinely hard to keep in your head.
No deadline, on purpose
The most counterintuitive decision in this poll is a setting that stayed off.
Response deadline was not set. That sits oddly next to the 170-RSVP holiday party we covered earlier in this series, where a visible deadline was one of the main reasons 170 people responded inside fifteen minutes. Deadlines drive response rates. Every host who has ever sent a reminder knows this.
But a deadline and a capacity limit are two different closing mechanisms, and running both means the tighter one wins while the looser one just confuses people. For this host the capacity was the real constraint. The poll didn’t need to close on a date, because it would close when the room was full — and that could happen in three hours or three weeks. Setting a date on top of that would have created a poll that either shut before it filled, or stayed open with a stale deadline sitting at the top of the page after the last spot was gone.
There’s a second reason, and it’s the one we’d guess mattered more. Capacity management doesn’t end when sign-ups end; it ends when the event does. People drop out. Spots open up on the morning of. A poll with a passed deadline is a poll that can’t absorb a late replacement — and for an event where an empty spot is wasted money and a wasted seat, keeping the door mechanically open until the last moment is worth more than the extra urgency a deadline would have bought.
Thirteen hours
The lifecycle here is unusual for this series. The potluck ran for two months. The matrix Doodle poll ran for three weeks. This one was essentially over in a working day: created in the morning, last activity the same evening.
That’s a distinct pattern, and it has a recognizable signature. A poll that collects 62 responses in thirteen hours was almost certainly shared exactly once, into exactly one place where all 62 people already were — a group chat, a class list, a WhatsApp group. There was no discovery phase, no reminder wave, no second push. One link, one audience, one evening.
It’s worth naming because it changes what “good setup” means. A poll that will live for two months benefits from a theme, a deadline, a friendly description — it has to keep working on people over time. A poll that will be alive for a single day in a chat where everyone is already paying attention doesn’t need any of that. This host skipped the theme entirely and left the poll on No Picture, which for a two-month potluck would be a missed opportunity and here is simply correct. There was nothing to persuade anyone of. The people seeing the link had already decided to come; the only open question was whether there was room.
What this poll got right
- They picked the template that matches the constraint, not the occasion. This was a party, but the problem was capacity, so they used the capacity template rather than the party one.
- They made the fill level self-service. Visible responses meant nobody had to ask the host whether spots were left.
- They built a soft tier before they needed one. The ‘If necessary’ answer turned inevitable drop-outs from a scramble into a list.
- They kept the door open. No deadline meant a spot freed up on the morning of the event could still be filled.
- They bent one field to their actual bottleneck. Payment status went into the private message column, so the guest list and the paid list never diverged.
- They didn’t over-configure a thirteen-hour poll. No theme, no deadline, no extra fields on a poll that lived for one evening among people who were already coming.
And the honest limitation: this setup tracks capacity, it doesn’t enforce anything beyond the per-slot limit, and it doesn’t handle money. The host still had to promote people off the soft tier manually and still had to reconcile what those private notes said against what they’d actually received. What the poll removed was the part that scales badly — 62 people individually asking one person whether there was still room.
When to reach for this setup
If your next event has a number attached to it — a room that holds forty, a class with twelve mats, a bus with a fixed number of seats — the useful question isn’t “how do I collect RSVPs” but “how do I make the limit visible and let people sort themselves against it.” That’s a different tool from an invitation, even when the event is a party.
The Class Booking template is where this host started. If you want the full walkthrough of what it can do — every setting, what participants see when a slot fills, and a live sample you can try — the Class Booking guide covers it end to end. And if you’re not sure which of Whocan’s nine templates fits your situation, the overview of poll types walks through all of them, including where Class Booking stops being the right answer.
Creating a poll is free and doesn’t need an account. This one took its host, by the look of the timestamps, about as long as it takes to write a group message.