How to run a volunteer event

A volunteer event is not an RSVP. People are choosing a job in a time window. If you only collect “I can help Saturday,” you will still be assigning work at 7:55 a.m. Build the board first, then fill it.

Write the jobs on paper before you open the product

List every role and every window. Concession 9–11, concession 11–1, gate 9–11, cleanup 1–2. Count how many humans each window needs. That number is slot capacity. If you cannot fill a grid on paper, the software will not invent one.

Collapse jobs that are actually the same. “Float” and “wherever needed” become a dumping ground. Either give that slot a real task or delete it.

One instance per day, slots per job

Saturday is one instance. Each row on your paper grid is a slot: title, optional start and end time, capacity. Do not create one sign-up per job. That produces six URLs and six rosters. Do not create one instance per shift if they share a location and a day; that is what slots are for. See dates versus slots.

If the same grid repeats every Saturday, save it as a slot template and apply the template when you add the next instance. Changing the template later does not rewrite Saturdays you already published.

Share like a coordinator, not like a marketer

For a closed volunteer corps, leave public listing off and send the event URL in the channel they already use. For a community day you want new people to find, turn listing on and share the team page. Do both and you will get strangers in roles that needed training.

Tell people to pick a slot, not to reply to the email with “I can do either morning.” Replies outside the page are how double-booking starts.

Fill the hard jobs first

Ask specific people for grill, money, and cleanup before you blast the whole list. Those slots have small capacities and high cost if empty. Easy jobs (set up chairs, bring ice) fill themselves. If a critical slot is still empty 48 hours out, assign it in conversation and then enter the name, or remove the slot and change the plan. Empty capacity on the page is a promise you might not keep.

The 48 hours before

Open the roster and read it as if you do not know anyone. Missing last names, two people on the same slot who cannot work together, a 9 a.m. shift with one name when capacity is three. Message those people yourself. Organizers can enable email and SMS reminders in account notification settings, including an optional text 30 minutes before an instance. That is a reminder, not a staffing plan. It will not recruit a missing cashier.

Print or screenshot the roster if your site has bad cell service. That printout is a copy. Updates still happen in the product when someone unregisters.

During the event

Check people in against the roster. If a walk-up wants to help, add them to an open slot or raise that slot’s capacity by one and add them. If someone no-shows, remove the entry so the count is honest for the next window. Do not run a second list on a legal pad unless you will type it back before the next shift starts.

After

Leave the sign-up in place. Next month, add another instance and apply the template. Do not delete the event to “start clean” if you will want last month’s pattern. If a job was useless, take it off the template before the next date.

A concrete Saturday grid is in the game-day worked example. Churches and nonprofits use the same pattern with different slot names.