159 Days to Staff One Weekend: A Volunteer Sign-Up Case Study

Every poll in this series so far has been short. The 170-RSVP holiday party was finished in fifteen minutes. The capacity-controlled event took thirteen hours. The Christmas dinner ran eleven days, the matrix registration three weeks, and the potluck we started with — the one we called a long lifecycle at the time — sixty-five days.

This one ran for 159 days.

It’s a volunteer sign-up for a regional youth sports tournament, created on a July evening for an event on a March weekend the following year. Thirty-seven people claimed jobs on it. Two settings were switched on. Nothing else was configured — no deadline, no email collection, no comment fields, no maybe answer, no reminders built into the tool. Five months of organizing a two-day tournament ran through a link and a list.

We picked it because it is the longest-lived poll in our English-language sample, and because a poll that stays useful for five months has to be doing something different from a poll that does its job in an afternoon. It turns out what it does differently is mostly not doing things.

A note on method. The structural numbers in this case study — 37 responses, the 159 days 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 July 2025 by a host in a Central European time zone, for a regional youth sports tournament held the following March. No personal information, identifying details, names, club or event names, or contact data are reproduced. The narrative around the data (typical volunteer behavior, common patterns we see) is composite and representative of many similar polls, not a literal account of any single conversation or helper.

By the numbers

• Template: Assign Tasks
• Theme: Checkbox
• Total responses collected: 37
• Time from creation to last recorded activity: 159 days
• Time from last recorded activity to the event: roughly 10 weeks
• Time zone: Central European
• Let participants add tasks: On
• Participants can see how others have responded: On
• Response deadline: Off
• Participants should provide an email address: Off
• Participants may add a private message: Off
• Participants may answer ‘If necessary’: Off

Two settings on. For comparison, the 13-person Christmas dinner in this series ran on seven, for a third of the people and one evening of activity. The longest, largest-scope poll we’ve looked at is also the most sparsely configured one.

That inversion is the whole story here, so it’s worth stating plainly before we get into it: configuration density tracks the complexity of the question, not the length of the project. This host was asking one very simple question over and over for five months. Simple questions don’t need settings; they need to stay askable.

What the Assign Tasks template actually asks

Assign Tasks is the smallest of Whocan’s nine templates by usage, and it asks a different question from every other poll in this series.

An Invitation poll asks are you coming. A Class Booking poll asks which slot will you take. An Online Poll asks which of these do you prefer. Assign Tasks asks: here is what needs doing — which of it will you take?

The host writes a list of jobs. Each job can be a task with a deadline or a task without one. Participants open the link and tick the jobs they’ll handle; the voter-facing prompt is literally “Please choose the tasks you can handle.” The list then shows, in real time, which jobs have names against them and which are still bare.

For a tournament, that list is long and mundane: setting up, tearing down, running a grill shift, staffing a door, driving something somewhere. None of those jobs is interesting. What’s hard is holding forty of them in one head for five months while people volunteer, drop out, and change their minds.

The host also did something that the description of the poll makes explicit and that we see constantly in volunteer lists: they told people to sign up more than once. Assign Tasks doesn’t cap a person at one job. One helper taking four jobs and another taking one is normal, and the count that matters to the organizer isn’t people, it’s covered slots. Which means the 37 responses on this poll almost certainly represent well over 37 claimed jobs — and that the headline number of a volunteer poll is, unlike an RSVP poll, not a headcount.

Months one and two: the list exists, so people can see the gaps

The poll went up in late July for an event in mid-March. That is an unusually long runway, and it’s a choice, not an accident. A sign-up list published eight months out isn’t trying to fill itself. It’s trying to exist early enough that nobody can claim they didn’t know.

The pattern we see in this phase, on this poll and on the many like it, is a first wave that arrives fast and then stops. The people who sign up in week one are the ones who were always going to help — the committee, the parents who ran it last year, the person who already knew they’d be doing the grill because they do it every year. They claim the jobs they already own. That takes a few days.

Then it goes quiet, and the list sits there half-empty for weeks. This is the phase where a group chat would have failed. In a chat, “we still need people for Saturday setup” scrolls away and has to be re-sent, and each re-send costs the organizer social capital. On a list, the gap is simply visible, permanently, to anyone who opens the link. The organizer doesn’t have to keep saying it. The empty rows say it.

That’s the first thing a five-month poll needs: it has to be a place, not a message.

Months three and four: the plateau, and the setting that mattered

The middle of a long sign-up is where most of the 159 days actually went, and it’s where the host’s second switched-on setting earns its place.

Let participants add tasks was on. This is the Assign Tasks version of participant-added options, and in a volunteer list it does something quite specific. It doesn’t just let people add themselves to the host’s list — it lets them add jobs the host forgot.

That matters more than it sounds. The organizer of a tournament writes the task list from memory, in July, based on last year. The list will be wrong in small ways. Somebody who worked the event last year remembers that someone had to fetch ice twice on Saturday, or that the scoreboard needs a person, or that the second pitch has no bin bags. In a closed list, that knowledge stays in that person’s head until the day of the event, when it becomes a problem. In an open list, they add the row — and usually claim it in the same motion, because the person who remembers a job is nearly always the person willing to do it.

We’d describe the effect as the list getting more correct over time rather than just fuller. That’s a property long-running polls have and short ones don’t. A thirteen-hour poll is only ever as good as the person who wrote it. A five-month poll gets edited by everyone who reads it.

The trade-off is real and worth naming: an open list drifts. Duplicates appear, jobs get worded differently by different people, and somebody eventually adds something that isn’t really a task. The host has to prune it. On a poll that lives this long, that pruning is the actual work of the middle months — and it’s part of why the “updated” timestamp on a poll like this keeps moving even during a period when few new people are signing up.

The setting that did the reminding

The other switched-on setting, Participants can see how others have responded, is easy to skip past. In most polls it’s about social proof — people commit more readily when they can see who else has.

On a volunteer list it does something less flattering and more effective. It makes the distribution of work visible.

Everyone can see that four people have taken eight jobs between them and that eleven rows are still empty. Nobody has to be told that the load is uneven, and — this is the part that matters for an organizer who has to keep asking for five months — nobody has to be told by the organizer. The list makes the ask on the organizer’s behalf, continuously, without any of it reading as nagging.

This is also the closest thing this poll had to a reminder system, because it had no other one. No email addresses were collected. No deadline was set, so there was no deadline to approach. Whatever chasing happened over those five months happened outside Whocan — in the club’s channels, at training, in the chat — and every one of those nudges pointed back at the same link.

We should be honest about the limitation here, since this series tries to be. Whocan did not send those reminders. There is no automated “you have not signed up yet” mail, no escalation, no assignment. A person did the chasing. What the poll removed was the need for that person to also maintain, distribute and reconcile the list they were chasing people against.

Whocan was one tool among several

The poll’s description does something we rarely see stated this explicitly: it tells helpers which things don’t belong in this poll.

Food donations went into the club’s own team system. Receipts and invoices went to the treasurer. The sign-up list handled jobs, and only jobs.

This is worth pulling out, because it cuts against how tool-makers usually talk. The tempting story is that the right tool absorbs the whole workflow. What this organizer actually built was a small piece of a stack: a club management system for membership and catering, a person for money, and a public link for who-does-what. Each of the three is doing the thing it’s least bad at.

We think that’s the correct instinct, and it’s also a reasonable description of where a poll tool’s limits are. Whocan will not track a budget, will not hold your membership data, and will not tell you whether the second grill shift has enough gas. It will hold a list of jobs that anyone can read and edit without an account, for as long as you need it. The organizer of this tournament seems to have understood that boundary better than most, and the poll is short precisely because they weren’t trying to make it do everything.

Why the list stopped ten weeks before the event

Here’s the detail that surprised us, and it’s the one we’d most want a reader to take away.

The last recorded activity on this poll was in early January. The tournament was in mid-March. The list went quiet roughly ten weeks before the thing it existed for.

The suggested arc for a poll this long would be a final push in the last fortnight and a scramble the week before — that’s certainly what the last week of an event feels like. The data doesn’t show it. As far as this poll is concerned, the staffing question was settled in early January and never reopened.

There are two readings, and we can’t distinguish between them from structural data alone, so we’ll give you both. One is that the list genuinely finished: every job had a name, and the remaining coordination moved to phone calls and the day itself. The other is that the last ten weeks of organizing happened somewhere else entirely — in the chat, in the club system, in a spreadsheet — and the poll was simply done being the place where it happened.

Either way, the practical lesson holds. A long-running sign-up isn’t a poll you keep open until the event. It’s a poll you keep open until the question is answered. This one answered its question with ten weeks to spare, and the organizer let it sit rather than closing it, which cost nothing.

For anyone running the same kind of list: that’s the moment to look for. Not the event date — the point where the empty rows stop being empty. If you’re still filling gaps in the final fortnight, the problem isn’t the tool; it’s that the list went up too late for the number of people you were asking.

What this poll got right

1. They published early. Eight months of runway meant the first wave could arrive whenever it wanted, and nobody could plausibly not know.
2. They made the gaps public instead of announcing them. Visible responses turned an unfilled row into a standing, unattributable ask.
3. They let the list get corrected. Participant-added tasks meant the people who remembered last year’s forgotten jobs could add them, usually while claiming them.
4. They invited multiple sign-ups. Volunteer coverage is measured in jobs, not people, and saying so out loud stopped anyone from politely taking exactly one.
5. They didn’t set a deadline they didn’t mean. A deadline five months out is either ignored or arbitrary; the real deadline was the tournament, and everybody knew it.
6. They kept the poll’s scope small. Money went to a person, catering to another system, jobs to the list. Nothing got mixed.
7. They configured almost nothing. Two settings, for a five-month project. The complexity was in the situation, not in the tool.

And the honest limitation: this poll did no reminding, no assigning, and no enforcing. Somebody still had to notice the empty rows and go find a human to fill them. Whocan held the list; it didn’t run the tournament.

When to reach for this setup

If you’re staffing something months out — a tournament, a school fair, a festival, a move, a wedding weekend — the useful question isn’t “how do I collect volunteers.” It’s “where does the list live so that it survives five months of everyone forgetting about it.”

The answer needs three properties, and they’re all visible in this poll: the list has to be readable without an account, the gaps have to be obvious to anyone who opens it, and the people using it have to be able to fix it when it’s wrong.

The Assign Tasks template is what this host started from. If you want the full walkthrough — every setting, tasks with and without deadlines, what participants see when they claim a job, and a live sample you can try — the Assign Tasks guide covers it end to end. If you’re not sure which of Whocan’s nine templates fits your situation, the overview of poll types walks through all of them. And for a much shorter list with a similar shape, the potluck case study that opened this series is the sixty-five-day version of the same idea.

Creating a poll is free and doesn’t need an account. This one outlived two seasons, and its whole configuration was two switches.