A 13-Person Christmas Dinner and the Most Feature-Dense Online Poll in Our Database: A Case Study

The case studies in this series so far have been about scale: 170 RSVPs in fifteen minutes, 105 registrations in a matrix grid, a potluck that ran for two months. It would be easy to conclude that a poll tool earns its keep somewhere north of fifty participants, and that below that you might as well use a group chat.

This one is the counterexample. Thirteen people. A team Christmas dinner at a local restaurant in southern Italy. Eleven days from the poll going out to the last response coming in. And — this is the part that made us pull it out of the database — seven optional settings switched on, the densest feature configuration we found in any poll of this type in our twelve-month export, at any size. The host of a thirteen-person dinner used more of the toolbox than hosts organizing events ten times larger.

That inversion is worth taking apart. Because it turns out the features weren’t decoration. Every one of the seven maps to a real constraint of a specific, familiar situation: booking a fixed table at a restaurant for a group that includes families, allergies, and at least one person who will want to propose an alternative. Small events don’t have fewer moving parts than big ones — they have different ones, and this poll is a compact tour of them.

A note on method. The structural numbers in this case study — 13 responses, the eleven-day 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 November 2025 by a host in the Central European time zone, for a team Christmas dinner at a restaurant. No personal information, identifying details, names, restaurant 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

The skeleton first:

• Template: Online Poll
• Theme: Christmas
• Total responses collected: 13
• Days the poll was actively maintained: 11 (from creation in mid-November to the last recorded activity)
• Time zone: Central European
• Register people (bring additional guests): On
• Distinguish between adults and kids: On
• Participants should provide an email address: On
• Participants may add a private message: On
• Allow participants to add options: On
• Participants can see how others have responded: On
• Response deadline: Set and shown

Seven settings, all deliberate, on a poll for thirteen people. For comparison: the 105-person registration we covered two weeks ago ran on three. The 170-RSVP holiday party ran on four. Density of configuration, it turns out, has nothing to do with headcount — it tracks the shape of the event. And a restaurant dinner in December has a very particular shape.

The restaurant booking pattern

Here’s the constraint that explains most of this poll: a restaurant table is a reservation, and a reservation is a number. Not “around fifteen,” not “we’ll see who shows up” — a number, usually promised days in advance, often for a fixed menu, in the busiest month of the restaurant’s year.

That’s what separates a December team dinner from, say, a potluck in someone’s garden. A potluck absorbs uncertainty gracefully: two more people means two more chairs. A restaurant booking does not. The host who created this poll wasn’t really collecting opinions — they were assembling the exact package of information a restaurant asks for when you call to confirm: how many people total, how many of them are children, and is there anything the kitchen needs to know.

Read the seven settings again with that phone call in mind and the configuration stops looking dense and starts looking like a checklist:

• Total headcount → Register people
• Kids’ menus and seating → Distinguish between adults and kids
• Allergies and dietary needs → Participants may add a private message
• A firm number by a firm date → Response deadline
• Reaching everyone if the booking changes → email addresses

This is a pattern we see repeatedly in polls built around a third-party venue. When the event depends on someone outside the group — a restaurant, a caterer, a tour operator — the poll’s settings mirror that party’s requirements, not the host’s preferences. The host is essentially a relay: the restaurant’s questions flow into the poll’s configuration, and the poll’s results flow back as the booking.

Registering people, and counting the kids

Thirteen responses does not mean thirteen diners. With Register people switched on, each respondent can register additional guests — a partner, their children — under a single response. So the actual headcount this poll produced was likely well above thirteen, and that’s precisely why the setting was on. One response per family, not one response per person, is the natural unit for a team dinner where “bring your family” is part of the invitation.

The companion setting, Distinguish between adults and kids, splits every registration into adult and child counts. For most event types this is a nice-to-have. For a restaurant booking it’s close to essential, because the restaurant will ask. Children’s menus are priced differently, high chairs need counting, and a fixed-price Christmas menu almost always has a kids’ variant. A host who collects one undifferentiated number ends up doing a second round of messages — “wait, how many of those twenty are children?” — which is exactly the manual follow-up work the poll was supposed to eliminate.

There’s a quieter benefit, too: asking about kids up front signals that kids are welcome. On a team dinner, that single toggle answers the question half the team was going to ask privately anyway (“is this a family thing or a colleagues thing?”) before anyone has to ask it.

The private message field: where the allergies live

The host also enabled Participants may add a private message — a free-text note that only the host can read, not the other participants.

On small polls this field earns its place the way a good pocket does: you don’t know in advance what goes in it, but something always does. In our composite experience with restaurant-dinner polls, the private notes column collects a very predictable mix — a nut allergy, a vegetarian partner, a gluten-free request, someone arriving late, someone leaving early, one delicate “I’ll come but I’d rather not sit next to the espresso machine.”

The private part matters more than it looks. Dietary needs are mildly personal; plenty of people are reluctant to announce an allergy or an eating pattern to the whole group in a public comment. Give them a channel that only the organizer reads and the information actually arrives — which, for a restaurant booking, it must, because the kitchen needs it in advance. A host who doesn’t collect this in the poll collects it in eleven separate direct messages instead.

Note what this host didn’t do: public comments stayed out of the configuration. For thirteen colleagues who already share an office and a chat group, the poll didn’t need to be a social space — it needed to be an intake form. The public conversation had somewhere else to live; the logistics didn’t.

Participants adding their own options

The most unusual setting on this poll — the one we see least often on this template — is Allow participants to add options. Most hosts keep full control of the option list: here are the choices, pick one. This host handed participants the ability to extend the list themselves.

For a team dinner, that changes the poll’s character. The host’s proposal stops being a final decision and becomes an opening bid. Someone who can’t make the suggested date, or knows the chosen spot can’t seat sixteen, or simply knows a better place, doesn’t have to reply “none of these work for me” and wait — they add their alternative directly to the list, and everyone else can respond to it on equal footing with the host’s original options.

That’s a meaningful trade. The host gives up some control over the outcome and gains something more valuable for a small group: the poll becomes self-correcting. In a thirteen-person team, one blocked date can sink a dinner, and the person who’s blocked is usually also the person with the best alternative in mind. Letting them put it on the ballot collapses what would otherwise be a multi-day back-and-forth — “does the 19th work instead? let me re-ask everyone” — into the poll itself.

It’s also, frankly, a setting that works because the group is small. With 170 participants, an open option list is an invitation to chaos. With thirteen colleagues who trust each other, it’s collaboration. The same toggle is a liability at one scale and the best decision on the poll at another — which is a good illustration of why these are settings and not defaults.

An open participant list, and a deadline

Two more settings round out the seven, and both are the opposite of choices we’ve highlighted in earlier case studies.

Participants can see how others have responded was on. The 170-person holiday party we covered in July hid its guest list, precisely so that people would answer independently. Here the host did the reverse — and at this size, that’s right. On a team dinner, “who’s coming” isn’t noise that biases responses; it is the event. Thirteen colleagues deciding whether to bring their families want to see that others are bringing theirs. Visible responses also apply gentle, entirely legitimate pressure on the last two holdouts, because everyone can see who the group is waiting for. In a small team, transparency does the reminding so the host doesn’t have to.

And the response deadline was set and shown. Eleven days is the visible result: poll out in mid-November, answers in by late November, presumably weeks before the dinner itself. That’s the restaurant constraint again — the booking had to be confirmed while tables in December were still available. A deadline on a thirteen-person poll can feel overly formal, but it converts “whenever you get to it” into a date, and the poll’s own record shows it worked: responses stopped arriving right around when they were supposed to.

The Christmas theme, and why it isn’t fluff

The poll wore Whocan’s Christmas theme — one of the seasonal designs in the theme picker. It would be easy to file this under decoration, but on a poll this small the theme is doing legitimate work.

An invitation’s visual register tells people what kind of event they’re being invited to before they read a word. A plain, unstyled form says scheduling exercise; a Christmas-themed page says this is the team dinner, it will be nice, bring your family. For a host who wants strong turnout from thirteen busy people in the most crowded social month of the year, that framing isn’t cosmetic — it’s part of why people respond at all. The theme is the digital equivalent of putting the invitation on card stock instead of a sticky note.

What this poll got right

Pulling it together, this host made seven configuration decisions and we’d defend every one of them:

1. They collected what the restaurant needed, not what was easy to ask. Headcounts split by adults and kids, dietary notes in private, all by a deadline — the poll’s output was, in effect, a completed booking form.
2. They let one response cover one family. Register people meant nobody had to fill in a form per household member.
3. They gave sensitive information a private channel. Allergies went to the host, not the group.
4. They opened the option list. In a small, high-trust group, participant-added options turned objections into proposals.
5. They kept responses visible. At thirteen people, the guest list is the selling point, and visible responses nudged the stragglers without a single reminder message.
6. They set a real deadline. Restaurants in December don’t hold tables for “probably.”
7. They matched the theme to the occasion. A festive invitation reads as an invitation, not admin.

And one honest limitation, in keeping with this series: a poll like this collects the plan, not the evening. It won’t chase the colleague who said yes and cancels on the day, and it doesn’t talk to the restaurant for you — the host still made that phone call. What it replaced was the part that usually goes wrong: the two weeks of scattered replies, forgotten allergy messages, and recounted headcounts that precede the call.

The small-event case

We opened with the inversion — the smallest poll in this series carrying the heaviest configuration — so let’s close with what it suggests.

Feature-rich tooling isn’t for big events; it’s for constrained ones. A hundred people voting on a meeting time is a large event with almost no constraints, and it ran happily on three settings. Thirteen people committing families to a fixed-menu restaurant booking with a deadline is a small event that is nearly all constraints — and it used seven. The right question when setting up a poll isn’t “how many people?” but “how many promises am I making to someone else, and what do I need from my group to keep them?”

If your next event is closer to the second kind — a dinner, a booking, a small group with real logistics — the Online Poll template is where this host started, and every setting described above is in its options. If you’re not sure which of Whocan’s nine poll templates fits your case, the overview of poll types walks through all of them. And if your Christmas event is the bring-a-dish kind rather than the restaurant kind, there’s a dedicated Christmas potluck sign-up sheet for exactly that.

Creating a poll is free and doesn’t require an account — thirteen people, or a hundred and seventy, the setup takes about the same five minutes.