Building a volunteer schedule: the method in six steps
Published on September 18, 2026
The schedule is where an organisation either stands up or falls over. It is not hard to build; it is hard to build in the right order.
Step 1: Break the event into positions, not people
Start from what has to be staffed, ignoring entirely who will staff it. A position is a place, a job and a span of hours: "artist welcome, green room, Friday 2pm to 10pm". As long as you think in people, you bend the event around the availability of your regulars, and you discover three days out that a position was never planned at all.
Step 2: Declare the need hour by hour
On each position, say how many people at what time. That is what separates a schedule from a list: it becomes possible to see a gap before it happens. See teams and positions.
Step 3: Collect availability, not intentions
"I'm around all weekend" is not availability, it is an intention. Ask for slots: day and hours. It feels fussy at sign-up and it saves hours afterwards, because every assignment becomes checkable: the tool refuses to assign someone outside what they declared.
Step 4: Assign the constrained positions first
Start with whatever has the fewest possible candidates: positions that need a skill (first aid, cash handling, driving), night slots, the build-up and the take-down. If you start with the easy positions, you fill them with the very people who could have covered the hard ones, and you end up stuck.
Step 5: Check three things before sending
- Overlaps: nobody should be assigned to two places at once. It is the most common mistake in hand-made schedules, and the most visible on the day.
- Travel and breaks: two slots back to back at opposite ends of the site are not back to back.
- Managers: every position needs someone to call. A volunteer who does not know who to ask calls the organiser, and the organiser spends the weekend on the phone.
Step 6: Send each person what concerns them, and nothing else
The full schedule as a PDF, sent to everyone, will be read by nobody. What each volunteer needs is their slot, their location and their contact, with the rest available to whoever wants it. When a change comes along (and it will), you tell the people concerned, not the other two hundred. See emails to volunteers.
Letting volunteers pick their own slots
There is a variant of step 4 that changes the workload: instead of assigning, you publish the slots and the volunteers book their own. It is the right approach when slots are numerous, short and interchangeable: a collection across fifteen stores, a stand to staff at a trade show. It is less so when positions call for skills or for a balance of profiles. See volunteers booking their own shifts.
What a schedule will never fix
A perfect schedule does not make up for a missing briefing. The ten minutes spent explaining a position on the morning itself prevent half of the day's phone calls, and what you wrote in the position sheet will be read if you print it, much less so if it sleeps in an attachment. See documents and mail merge.
Frequently asked questions
How long before the event should the schedule be finished?
A first version two to three weeks out, a version sent to the volunteers one week out. Earlier than that and availability still moves; later and you no longer have time to fill a gap.
Should volunteers get the whole schedule?
Each one needs their own slot, their location and their manager's phone number. The full schedule matters to the team managers, rarely to anyone else.
How do you handle last-minute changes?
By telling only the people concerned, and by having replacements on the critical positions. A schedule that moves is normal; a schedule nobody can read any more because it has been sent out five times is not.