How to build a volunteer sign-up sheet that fills

A volunteer sign-up sheet has one job: turn “someone should help with that” into a list of named people attached to specific work at specific times. Most sheets fail before anyone sees them, because the person who made the sheet never decided what the jobs were. This guide is about that decision, then about the mechanics of building and filling the sheet in MojoSignUp.

Why paper sheets and group chats stall

The clipboard on the table only works for the people in the room, and the person holding it becomes the only one who knows what is still open. A photo of the clipboard in the group chat is worse: it is out of date the moment it is posted, and three people volunteer for the same slot by replying “I can do that.”

A group chat poll fails for a different reason. It collects a yes or no, not a job. Twelve thumbs-up on “Who can help Saturday?” tells you twelve people are willing. It does not tell you who is doing setup at 7:30 and who is running the gate at 10:00. You still have to assign, and assigning by hand is the work you were trying to avoid.

An online sheet solves both problems only if it enforces capacity and lets people change their own answer. Anything that does not do those two things is a spreadsheet with extra steps. See Online sign-up sheet vs. spreadsheet vs. group chat for the full comparison.

Decide the shape before you touch the tool

There are two kinds of volunteer sheet, and mixing them is the most common way to build something nobody understands.

• A headcount. “Who is coming to the park cleanup?” Everyone does the same thing. The only number that matters is how many. In MojoSignUp this is one instance with a capacity, and no slots.
• A job board. “We need two people on the grill from 11 to 1 and three people on cleanup at 3.” Different people do different things at different times. This is one instance with several slots, each with its own capacity.

If your event has both, build them as two different things. The forty people who are “coming” are an instance headcount. The six adults working the concession are slots. Do not create a slot called “Attending” with capacity 40 next to a slot called “Grill” with capacity 2. Attendees will pick grill because it sounds like a choice, and your grill slot will be full of people who meant “I am coming.” The distinction is covered in Dates versus volunteer slots.

Writing the job list

Each slot needs four things: a name a stranger would understand, a time window, a capacity, and a one-line description of what the person will actually do. Write them on paper first. If you cannot describe the job in one sentence, it is two jobs or it is not a job.

Good slot names are short and specific: “Gate · 8:00–10:00,” “Concession · 10:00–12:00,” “Teardown · 12:00–1:00.” Bad slot names are vague or clever: “Helper,” “Floater,” “Team Awesome.” A floater is a person you assign on the day. They do not need a slot; they need a text message.

Split long shifts. A four-hour gate shift will sit empty while two two-hour gate shifts both fill. People sign up for what they can imagine finishing. The cost of splitting is that you need twice as many names, which is a real cost, so split only where the day is genuinely long.

Put the hard jobs first in the list, and put a sentence in the description about why they are hard. “Field setup 7:30 · you will carry goals and it will be cold” fills faster than a bare “Setup” because the people who would say yes to that are self-selecting, and the people who would have quietly not shown up skip it.

Capacities that match reality

Capacity is how many names a slot accepts before it disappears from the chooser. Set it to the number you need, not the number you would love. If concession needs two people and you set it to four, the slot will look half-empty forever and the two people who did sign up will wonder if it is happening.

If a job needs a backup, make the backup its own slot with capacity 1 and say so in the name: “Gate backup · 8:00–10:00 · only called if someone is sick.” MojoSignUp does not keep a waitlist. When a slot is full it is full, and when someone unregisters it reopens for the next person who loads the page. A named backup slot is the honest way to have a bench. Details are in Capacity limits on dates and slots.

The description people read

The sign-up description is read by people deciding whether to volunteer, not by people who already have. Answer their questions: where to park, which door, whether they can bring a kid, whether there is a job that can be done sitting down. Leave out the history of the event and the thanks to last year’s committee.

Do not put anything on the page you would not put on a bulletin board in a public building. The page is visible to anyone with the link, whether or not you turned public listing on. Gate codes, a family’s home address, and phone numbers belong in the message you send afterward, not on the sheet. Privacy choices for organizers covers what is public.

Filling it: anchors first, then the blast

A sheet posted to a hundred people with every slot empty gets ignored, because nobody wants to be first. Before you send the link widely, ask two or three specific people to take the hardest or earliest slots. Do this by name, in a direct message, with the link. When the blast goes out, the sheet already has names on it and the remaining jobs look like the last few, not the whole thing.

Send the sign-up URL itself, not a screenshot of it. A screenshot is a clipboard photo with better resolution. The URL is always current, and it lets people register and unregister themselves without asking you.

Send it more than once. The first message reaches the people who were already going to help. The second, three or four days later, listing exactly which slots are still open, reaches the people who meant to look and forgot. Naming the open slots matters. “We still need two for teardown” gets teardown filled. “Please sign up!” gets nothing.

Watching it fill

Check the roster at three points: the day after the blast, the middle of the week before, and the morning of. Each check has a different purpose.

• Day after. Are the anchors on it? Is anyone in a slot that makes no sense, like a nine-year-old on the grill? Fix that now, quietly, by removing the row and messaging the parent.
• Midweek. Which slots are still empty? Those are the ones you fill by asking people directly. An empty slot on the live page the day before means you do not have that job covered, and hoping is not a plan.
• Morning of. Anyone who told you last night they cannot make it should already be removed, so the person running the day sees the real list and not a ghost.

The week-of event checklist turns those three checks into a routine.

Day of

Print the roster or keep it open on a phone. The person running the day should be able to answer “who is on gate at ten?” without calling you. If you enabled the SMS reminder, it fires 30 minutes before the instance start, which is useful for the first shift and useless for the afternoon, so plan on a human text for late shifts.

When someone shows up who is not on the sheet, add them to a slot. When someone on the sheet does not show, remove them. The roster after the event should reflect who actually worked, because that is the list you will use to say thank you and the list you will start from next time.

Next time: reuse the structure

If the same jobs recur, save the slot list as a template. Next event, add a new instance and apply the template. Adjust capacities based on what actually happened: if concession was fine with two, leave it, and if setup was chaos with three, make it four. The game-day worked example shows a template reused across a season.

Building it in MojoSignUp, in order

1. Create or open the team that owns the event. Invite the co-organizer now, not after something breaks.
2. Create the sign-up: a title people already use, a short description with the practical facts, public listing off unless strangers should find it.
3. Add one instance for the date with the real start and end times.
4. Add slots to that instance from your paper list: name, time window, capacity, one-line description.
5. Register yourself in a private browser window. Confirm the email arrives and the unregister link works. Then unregister.
6. Send the URL to your anchors. Then send it to everyone.

The first-event tutorial walks through the same steps click by click, and How to run a volunteer event covers the staffing philosophy for larger days.