Festival volunteer coordination is three jobs, not one

Friday afternoon, gates open. Two hundred volunteers across fifteen roles are already in position. The first aid tent has its lead and two assistants, all with current certifications. The merch crew is setting up the tills. The artist hospitality team has their briefings, their backstage credentials, and their early lunch sorted. Recycling, parking, info desk, queue management. Everyone has been assigned, briefed, and credentialled. The weather forecast for Saturday is uncertain, and there’s a contingency plan for it, written down, in the hands of the people who’ll need to enact it.

Most of those volunteers are first-timers, signed up six weeks ago in exchange for a wristband. They were briefed by department heads who’ve done this before. The department heads were recruited and onboarded by a small core of year-round volunteers who’ve been working on this edition of the festival since last October.

None of this happened today. None of it happened in six weeks either, although that’s where most coordinators look. It happened across a year of work that ran at three completely different speeds.

That’s what makes festival volunteer coordination its own particular kind of work. The same coordinator carries three different jobs. The off-season, when a small core keeps the festival alive between editions. The prep season, when department heads return and the festival’s design gets built. And the festival itself, when those plans either survive contact with reality or don’t.

The festival is the only one of the three that’s visible. It’s also the smallest part of the work.

This post is about all three jobs, what software does for each, and what it can’t do for you.

The three modes

Off-season

The festival’s continuity year. From the morning after last year’s teardown to the day prep season starts, the festival exists only as a small group of year-round volunteers and the institutional knowledge they hold. Board, treasurer, programming committee, partnerships lead, marketing chair. Five to fifteen people, depending on the festival’s scale. Often unpaid. Often the same people running the festival’s other ongoing work.

Three things to do, none of them urgent.

Tend the year-round core. These are the people who hold the festival between editions. They are also the people most likely to burn out and quietly drift away in the months when nothing’s happening. The work is staying in light, regular contact: quarterly meetings that don’t run long, occasional social events that aren’t agenda-driven, the visible recognition that year-round work matters even when it doesn’t have an audience. Festivals that lose their core in the off-season find out the cost when prep season starts and there’s nobody left to hold the institutional memory.

Capture last year’s lessons while they’re fresh. The post-festival debrief that gets done within four weeks of teardown is worth ten times the debrief that gets pushed to Christmas. What worked, what didn’t, what nearly went wrong, what numbers came in different from forecast, who’s coming back next year and who isn’t. This becomes the prep season’s starting point. Without it, every year starts from scratch.

Make the framework decisions early. Dates, venue, scope, scale, partnerships, headline programming. The decisions that constrain prep season have to land before prep season begins, not during it. A festival whose dates are confirmed in October has six months of clean prep runway. A festival whose dates are confirmed in March has chaos.

Prep season

Three to six months before the festival. Department heads return or get recruited fresh, the festival’s design gets built, and the recruitment campaign for the surge opens. The pace intensifies week by week. By tech week the prep team is running flat out.

This is also the only rehearsal a festival actually gets. The festival itself doesn’t rehearse. The institution does, every year, when the prep team takes last year’s lessons and applies them to this year’s design. Done well, prep season is where the festival is stress-tested before it has to run in front of an audience.

Four things to do.

Recruit returning department heads first. Last year’s site lead, last year’s first aid lead, last year’s hospitality lead. The institutional memory lives in their heads, not in your records. Bringing them back early, well before you need to recruit a replacement, is the difference between continuity and a year-zero rebuild. Department heads who say yes early also signal commitment to everyone else who’s deciding whether to come back.

Build the recruitment funnel, not the recruitment target. If the festival needs 200 surge volunteers across the weekend, you don’t recruit 200. You recruit between 280 and 320, depending on what you know about your drop-off rate from previous years. People sign up six weeks in advance when enthusiasm is high, then life happens. A meaningful percentage won’t confirm. Of those who confirm, some won’t show up. Knowing your numbers, and recruiting against them, is most of the difference between a smooth festival and a frantic one.

Build the role structure with compliance baked in. A festival isn’t one volunteer job split across time slots. It’s fifteen distinct jobs running simultaneously, each with its own briefings, qualifications, and access requirements. Treating these as a flat list means a coordinator has to manually check every signup against a separate spreadsheet, usually at midnight before gates open. The work is designing the role structure so that compliance is part of the role itself. The signup form does the gating.

Write down the contingency layer. Most festival coordinators build one schedule. The ones who’ve done this more than once build a contingency layer alongside it. Rain on Saturday afternoon means redeploying parking volunteers to covered entry points and pulling recycling teams from the outer field. None of these decisions get made well in real-time on the radio if they haven’t been planned for in advance. The contingency that lives only in the coordinator’s head is the contingency that doesn’t get enacted when the coordinator is also handling something else.

The festival itself

Two to five days. The plan is the plan. There’s no time to make a new one.

Three things to do, all under load.

Execute the plan, don’t redesign it. The temptation under pressure is to start solving the problems the plan didn’t anticipate by changing the plan. Resist this. The plan is what your team is briefed on. Changing it mid-festival multiplies confusion across two hundred people. The right move is to flag the gap, work around it with the contingency layer, and capture it for next year’s debrief.

Communicate in real-time when the plan needs to flex. The contingency layer exists for this. When rain hits and the redeployment plan activates, the message goes to exactly the volunteers affected, immediately, on their phones. Not a bulk email. Not a coordinator manually texting fifteen people. The right notification reaches the right group.

Hold the standards. Compliance gates that hold even when you’re short. Role-fit that doesn’t slip when a department head pushes back. The willingness to say no to a willing volunteer at six pm on opening night, knowing the festival director is listening on the same radio channel. This is the part where coordinators most often crack, because cracking looks like keeping the festival running. It isn’t. The cost of the wrong person behind the bar or at the first aid tent on a Saturday night gets paid by people who didn’t choose to volunteer.

What software does for each mode

Software supports each mode differently and shouldn’t be optimised for one at the expense of the others.

For the off-season, software does little, and that’s the point. A volunteer list accessible from a phone. A way to push a quiet message to the year-round core every few months. A record of who did what last year, who’s been department head before, who’s worth a personal text when next year’s prep season opens. The tool should be unobtrusive. If you’re spending more than twenty minutes a month in it during the off-season, something’s wrong.

For prep season, software earns its place. Custom profile fields hold compliance information for department heads and surge volunteers alike. Groups separate the prep team from the general volunteer pool, and separate roles from each other. Tasks for first aid are visible only to certified volunteers. Tasks for bar are visible only to those over the relevant age. The signup form does the gating. The recruitment funnel (signup, confirmation, show-up) gets captured in records that inform next year’s targets.

For the festival itself, software gives the communication backbone. Push notifications reach exactly the volunteers affected when a stage moves or rain hits. Self-signup that was set up in prep season runs without the coordinator’s intervention. The data captured during the festival becomes the off-season debrief’s raw material.

These are real features doing real work. Worth choosing carefully. Also: a smaller part of the actual coordination than the brochures imply.

What software can’t do

Software can’t tell you what your real drop-off rate is, the first time. That comes from running a festival and watching what happens. Software stores the data so next year’s recruitment plans against numbers, not guesses.

Software can’t transfer the institutional memory that lives in the head of last year’s site lead. That’s walkthroughs, briefings, and yes-actually-write-that-down conversations between the returning lead and whoever’s taking on the role next. Software gives that knowledge a structured place to live: notes attached to roles, debrief documents linked to past festivals, records that survive someone’s departure.

Software can’t have the conversation with the department head who came back this year out of obligation rather than energy and is heading toward burnout by tech week. That conversation is yours to have, often before they’ve recognised it themselves. Software surfaces the patterns that prompt the noticing: response times slowing, hours creeping up, the smaller signs that come before the breakdown.

Software can’t manage the relationship with the festival’s director or producer. The pressure to take on more roles than the volunteer team can absorb. The artistic decisions that land on your roster without consultation. The post-festival debrief that asks for next year’s numbers before you’ve recovered from this year’s. These are conversations the coordinator has, often without backup. Software provides the evidence the coordinator brings to those conversations: volunteer hours, drop-off rates, the cost of last-minute changes. The conversation isn’t “trust me” when the numbers are in front of both of you.

Software can’t replace the off-season community work that holds the festival together when nothing’s visibly happening. The check-in with the treasurer carrying more than she should. The thank-you to the programming committee whose work is invisible until the line-up announcement. The board meeting that doesn’t run two hours over. Software holds the records that make those check-ins easier: who’s been in their role for how many years, who handled what last festival, who hasn’t been visibly thanked recently.

Software can’t read the energy of a surge volunteer team at noon on day three, when everyone is tired and there are six hours of festival left. That’s the coordinator walking the site, talking to team leads, reading faces. Software surfaces what’s visible: task completion rates, gaps in coverage, the data the walking-around eye can be augmented by.

Software can’t make the radio call at the moment of crisis. The medical incident at the main stage. The missing volunteer who hasn’t checked in. The contractor who didn’t arrive. These are coordinator decisions made in seconds, with incomplete information. Software delivers the message instantly once the decision is made: push notifications to exactly the volunteers affected, not the whole list.

This is most of the work. The coordinator who lasts in this role is the one who tends the year-round core in the off-season, recruits returning department heads early in the prep season, builds compliance and contingency into the festival’s design, communicates in real-time when the plan flexes during the festival itself, and captures lessons before they fade. The one who reads the team and adjusts, holds standards when the surge tempts compromise, and looks after themselves in a job that has no recovery time built in.

None of which is a setting you can configure. All of which software can support without replacing. Where the line falls determines whether the festival runs reliably, whether the same team comes back next year, and whether the festival itself runs five years from now.

How to think about choosing tools

Pick something that does its slice well and doesn’t pretend to be the festival.

Calendar-aware matters more than usual. Festivals are dates, not perpetual programmes, and a tool that assumes a steady weekly rhythm will fight you all year. The right tool does almost nothing in the off-season, supports prep season’s intensifying work, runs the festival without breaking under load, and holds the records between editions.

Mobile-first is non-negotiable for the surge. Surge volunteers are signing up from their phones, often on a break at their day job, often at the moment they hear about the festival from a friend. If the signup experience is clunky on mobile, half of them won’t finish.

Push notifications, not email. Email is a day-after channel. Festivals run in minutes. The communication tool needs to be in the volunteer’s pocket, with notifications that reach them immediately when something changes.

Free or close to it is fine. Most festivals are running on tight budgets and shouldn’t be paying for software complexity they don’t need. A tool that holds the volunteer list, runs role-gated signups, sends real-time notifications, and stays out of the way the rest of the year is what’s needed. Nothing more.

Boring is good. The boring tool used the same way for every festival is the tool the volunteers actually use. The clever feature you turn on for the first time during a festival is the feature that breaks at 8pm on Saturday.

Where Zelos fits

A short note, because the post’s whole argument is that the tool isn’t the festival.

Zelos handles the pieces software handles across all three modes. In the off-season, the same workspace holds the year-round core’s records and lets you push occasional messages without spinning up new infrastructure. In prep season, custom profile fields hold compliance information (first aid, licensing, accreditation), groups separate the prep team from the surge volunteers and separate roles from each other, and tasks carry role-specific descriptions and capacity limits. At the festival, push notifications reach exactly the people affected when a stage moves or rain hits, not the whole list. Self-signup means surge volunteers see what’s available and claim what fits. Points and badges support the engagement work that volunteers respond to. All messaging is admin-supervised, by design, which is the right shape when first-time festival volunteers are working alongside a coordination team they’ve just met. The free plan covers unlimited volunteers and 25 active tasks at a time, which is enough for most single-festival deployments without paying anything.

It is not the festival. The festival is what you build with it across the year that runs in three speeds. You can explore the product or start a free account and try it on the next event. The work, either way, is yours.