How to manage volunteers for an event: roles and responsibilities

Most festival volunteer problems aren’t volunteer problems. They’re coordination problems.

A volunteer who doesn’t show up was usually never given a clear shift confirmation. A volunteer who can’t answer questions wasn’t briefed on the schedule. A volunteer who quits mid-event wasn’t given water or relief. Volunteers come ready to help. The question is whether your operation lets them.

If you’re coordinating volunteers at a festival, your real job isn’t recruiting. It’s making sure that once they show up, they can actually do the thing they signed up for. This guide is built around that: what each role needs from you to work, and the operational habits that separate festivals where volunteers come back from ones where they don’t.

Six operating principles

These hold across every role.

1. Let volunteers pick their own shifts, but design the menu carefully. Self-signup beats top-down assignment for retention. People know their own capabilities better than a spreadsheet does. But if you open every shift to everyone equally, backstage fills in three minutes and Sunday morning cleanup stays empty. Self-signup is a tool for matching volunteers to work they’ll do well; it’s not a tool for letting unpleasant work go undone. The next section covers how to design the menu so the unpopular shifts also fill.

2. Cap active shifts at four hours. Anything longer in a customer-facing role produces mistakes. Setup and teardown can run longer with proper breaks and meals, but anyone working a gate, a bar, or an info booth should hand off by the four-hour mark.

3. Build 15-minute handovers between shifts. This is where information lives or dies. The outgoing volunteer tells the incoming one what’s happened that morning, who the difficult attendees were, what changed on the schedule, where the spare wristbands are. Skip the handover and the next shift starts from zero.

4. One source of truth for schedule changes. The most common in-event failure is the schedule shifting and only half the volunteers finding out. Decide before the event where the schedule lives (a shared document, a chat channel, a posted board) and make sure every volunteer knows where to check it. Push every change there first, before announcing it anywhere else.

5. Make the escalation chain explicit. Every volunteer should know two things by heart: who their team lead is, and what to do if their team lead isn’t reachable. Write it on the back of their lanyard if you have to. The default failure mode is a volunteer who hits a problem they can’t solve and stands there waiting for someone to notice.

6. Reach volunteers on their phones, with notifications tied to specific work. Festival days are too busy for volunteers to check email or scroll a group chat looking for updates. The channel that works pushes the right information to the right people automatically. When the gate procedure changes at 11am, the gate crew sees it on their phones immediately, and the rest of the team isn’t distracted by an update that doesn’t affect them.

These principles are why coordination tools matter, and why we built Zelos around task-based signup with built-in messaging tied to each shift. The principles work in any tool. The tool just has to support them.

How to fill the less popular shifts

Some festival shifts are easy to fill: backstage hospitality, the photo pit, the after-party clean. Some are hard: Sunday morning teardown, the porta-loo rotation, the 6am setup crew, the overnight security walkaround. Pretend they’re equal and you’ll end the weekend with a full backstage crew and unsupervised toilets.

A few coordination patterns that actually work:

Gate the popular shifts. Don’t open everything to everyone. Restrict the most attractive shifts to returning volunteers, or require a less popular shift first (“one teardown shift unlocks backstage hospitality”). The reciprocity is honest. Popular shifts are the reward, not the default.
Tier the perks toward the unpopular shifts. A teardown volunteer should get more than a backstage volunteer: extra meal vouchers, priority signup for next year, a different lanyard, named recognition in the closing thank-yous. The work is harder, so the compensation should be too.
Cap the attractive zones. When backstage hospitality reaches its needed headcount, lock it. New signups have to pick from what’s actually short-staffed. This is just supply and demand. If you don’t cap, the queue won’t redirect on its own.
Bundle. Offer “festival pass plus two shifts” packages where one shift is glamour and the other is grunt. Volunteers know what they’re agreeing to and self-select around their tolerance.
Pay for the worst shifts when you have to. Some festivals can’t get volunteer coverage for toilet servicing or overnight security at any price of free t-shirt. If the role is hard enough, contract it out or pay an hourly rate to a small crew. Nobody should feel like they ended up on the bad shift because they were the only one who didn’t know better.
Recognise loudly. The teardown crew gets named in the after-event email. The cleanup volunteers get the first round at the volunteer party. The coordinator personally thanks them at handover. Status is a real currency for repeat volunteers, and you choose where it flows.

The underlying point: self-signup is how you match volunteers to work they’ll do well. The coordinator still owns the outcome of which shifts fill. They just stop pretending the spreadsheet does the matching.

What follows is what each volunteer role actually needs from you, before and during their shift. Treat it as a reference. Most festivals won’t run all of these roles, but the structure (before, during, shift mechanics, common failure) holds across every one.

Setup and breakdown crew

This is the team that determines whether your festival opens on time. They arrive a day or two before gates and stay until the site is built. After the event, they pull it all down.

Before shift: A site map showing where every structure goes, a build order so the right things go up first, and a working inventory of tools and materials per zone.
During shift: Meals on a schedule, not whenever someone remembers. Water at every station. A designated lead for each zone who can answer build questions without radioing the main coordinator for every nail.
Shift mechanics: 6 to 8 hours with two breaks and one full meal. Don’t push 10-hour build days unless the volunteer is paid or experienced.
Most common failure: Underestimating teardown. Volunteers are tired by the end and many have already left. Recruit your teardown crew separately, on a different signup, with their own perks. Don’t assume the build crew will stay.

Entry, registration, and ticketing

This is the most public-facing role at your festival. Gate volunteers set the tone for everyone who walks through.

Before shift: Today’s gate procedure (paid vs comp tickets, will-call vs on-site sales, wristband colours by access tier), and a one-page laminated decision tree for edge cases: lost wristband, comp pass missing from the system, child without a ticket.
During shift: A working ticket scanner already paired with the right account. A cash float if you sell at the gate. A radio or chat channel to call a supervisor without leaving their post. Someone to bring them water.
Shift mechanics: 3 to 4 hours with 15-minute handovers. Always staff two volunteers per gate. One scans, one answers questions. Never put a first-timer alone on a gate.
Most common failure: A volunteer hits an edge case they don’t know how to handle and the queue stacks up while they look for a supervisor. Solve it before the event with that decision tree.

Crowd direction and information

These volunteers move attendees around the site. They direct parking, manage flow at stage exits, run the info booth, handle lost and found.

Before shift: A site map memorised. Today’s schedule, including any morning-of changes. A short script for the five questions they’ll get asked most: toilets, water, first aid, food, the running order.
During shift: The same source of truth for schedule changes as everyone else, plus a way to check it without abandoning their post. If you’re running an info booth, give the volunteer there a printed schedule that gets reprinted whenever it changes.
Shift mechanics: 4 to 6 hours. Rotate positions every couple of hours. Standing at a parking entrance for six straight hours destroys morale.
Most common failure: A stage time shifts and the info booth tells attendees the old time for the next two hours. Attendees lose trust in everything the volunteers say. Fix the comms loop, not the volunteer.

Food, drink, and merchandise

Volunteer-run bars and merch tables are common at community festivals. Volunteers serve drinks, check IDs, run the till, restock supplies.

Before shift: Pricing list visible at the till. The day’s drink menu if it changes. The local ID policy in writing: which IDs you accept, what to do with a fake. A 5-minute walkthrough of the POS or cash drawer.
During shift: A designated cash lead for reconciliation between shifts. Restock runners so volunteers aren’t abandoning the till to fetch beer. A clear line on what to do if someone’s already drunk.
Shift mechanics: 3 to 4 hours. Pair an experienced volunteer with a newer one. Cash handling is where festivals get burned by inexperience.
Most common failure: Cash gets miscounted between shifts and nobody knows where the gap came from. Solve it with a handover sheet signed by both volunteers and a designated cash supervisor checking each handover.

Backstage and artist liaison

Backstage is one of the most requested volunteer assignments, but the work is logistics. Volunteers manage artist arrivals, set up dressing rooms, coordinate transport, keep the running order on schedule. Because it’s a glamour shift, it should be gated. See the section above.

Before shift: A runsheet with every artist arrival, sound check, set time, and departure. Dressing room assignments. Rider summaries: what each artist wants in the room.
During shift: A stage manager or production coordinator they can radio directly. Explicit permission to say “I’ll check and get back to you” instead of making up answers. Snacks and water in the volunteer area, because artists will eat anything left in the green room.
Shift mechanics: 4 to 5 hours, often split around the show schedule. Don’t assign superfans of the headliner to that headliner’s hospitality. Spread bias-prone assignments around.
Most common failure: A volunteer makes a promise to an artist or their team that production can’t keep. Brief volunteers explicitly on what they can and can’t commit to. Anything outside the rider, defer up.

Security support

Don’t lean on volunteers for actual security. Professional staff handle de-escalation, ejections, serious incidents. Volunteers play a supporting role: visible presence, bag checks at low-risk entry points, enforcing no-smoking or no-alcohol zones, reporting anything that needs a professional response.

Before shift: A written list of what they’re authorised to do and what they must escalate. The radio channel for security professionals. A script for de-escalation up to the point where they hand off.
During shift: Visibility: high-vis vests or distinctive shirts so attendees know they’re staff. A radio or phone with a direct line to professional security.
Shift mechanics: 3 to 4 hours. Vigilance drops after that, especially overnight.
Most common failure: A volunteer steps into a situation they’re not trained for, either because they didn’t know to escalate or because they couldn’t reach anyone who could. Make the handoff trivially easy.

First aid support

Same logic as security. Most events should contract a first aid provider or have qualified medics on site. Volunteers support by guiding people to the medical tent, fetching supplies, and calming a crowd around an incident.

Before shift: The location of every medical post and emergency exit. The protocol for what they’re authorised to do, which is almost certainly nothing beyond escort and call. The phone number for the lead medic.
During shift: A radio or phone. Water. Access to the medical tent for breaks.
Most common failure: A well-meaning volunteer with first aid training does more than their event protocol authorises. Spell out the limits in writing.

Volunteer photographers are a bonus, not your primary coverage. Hire a professional for the shots you actually need. A volunteer dedicated to social media during the event is genuinely useful: they can pull the best attendee posts, share live updates, and monitor mentions.

Before shift: A shot list for photographers, a content brief for social. Login credentials for whichever channels they’re posting to. The hashtag.
During shift: Wi-Fi or cell coverage strong enough to upload. A way to clear borderline posts with you before they go live.
Most common failure: Photographers shoot 3,000 photos of the headliner and nothing of the volunteer crew, the food vendors, or the families enjoying the kids’ area. Brief them on what the festival actually wants to remember.

Team leads and supervisors

For anything beyond a small event, you’ll need volunteers who supervise other volunteers. Team leads handle their crew’s check-ins, breaks, handovers, and on-the-spot problems. They report to the main coordinator.

Before shift: The full picture, not just their crew’s tasks but how those tasks connect to the rest of the festival. A direct line to the main coordinator. Authority to make small decisions without checking up.
During shift: A way to call a 5-minute huddle with their crew. Coffee.
Shift mechanics: Often longer than their crew’s shifts, closer to a half-day. Stagger team lead shifts so there’s always someone with context on duty.
Most common failure: Team leads get pulled into doing crew work because they’re the most experienced person in the area, and nobody’s actually supervising. Protect their supervisory time.

Runners and floaters

Runners move between areas, transporting items, covering quick breaks, and handling small errands. Floaters are similar but assigned more loosely. They go wherever the bottleneck is.

Before shift: A working knowledge of the site. The radio channel for the main coordinator. A list of where every team is stationed.
During shift: A bike or cart if the site is big. Water.
Shift mechanics: 3 to 4 hours. This is also a good role for new volunteers. They see different parts of the operation before specialising next time.
Most common failure: Floaters end up plugged into one understaffed zone for their entire shift and the actual floating function disappears. Keep at least two floaters available at all times, even if it means accepting that one zone runs slightly thin.

Family programming and accessibility

If your festival has children’s areas, workshops, pet zones, or accessibility services, each needs its own volunteers. Children’s areas in particular have safeguarding requirements (usually background checks and adult-to-child ratios), so plan recruitment well in advance.

Before shift: Safeguarding briefing. Background check on file. The rules for the area: drop-off vs supervised, age limits, what to do about a lost child.
During shift: Two adults minimum on duty at all times. A radio to security and a radio to first aid.
Most common failure: Staffing the kids’ area like any other zone and discovering at 2pm that you’re below ratio because one volunteer left for lunch.

How many volunteers does a festival need?

Rough benchmarks for planning, not rules:

Under 1,000 attendees: 20 to 40 volunteers across all roles.
1,000 to 10,000 attendees: 75 to 200 volunteers.
10,000+ attendees: 300+ volunteers, plus paid leads.

One volunteer per 50 to 100 attendees is a baseline. Adjust upward for events with complex ticketing, family programming, multiple stages, or anything mission-critical you’re not contracting out. Adjust downward if you’ve hired professionals for security, food, and waste management.

Shift length per role, summarised: 3 to 4 hours for active customer-facing roles, 4 to 6 hours for site management and crowd direction, 6 to 8 hours for setup and teardown with proper breaks. Anything over 4 hours in a public-facing role produces avoidable mistakes.

What volunteers expect in return

Volunteers aren’t free labour. They’re paid in non-cash. Standard perks across most festivals:

Free entry to the festival outside their shift
Meals during shifts, or a meal voucher
A volunteer t-shirt that identifies them
Sometimes a credit toward next year’s ticket, or priority signup for next year

For longer commitments (full weekends or multi-day events), camping spots and travel reimbursement are common. The most reliable retention tool isn’t the t-shirt. It’s treating volunteers like they’re part of the festival, not running it from outside: invite them to the after-party, name them in the thank-yous, and remember their names next year.

Where to find festival volunteers

The best volunteer pool is the one you already have: last year’s volunteers, attendees who signed up for your mailing list, supporters of whatever your festival benefits. Past volunteers convert at several times the rate of cold recruits, so contact them first and offer priority signup.

Beyond that, the channels that consistently work:

Local universities and schools, especially programmes with service-hour requirements
Community groups tied to your festival’s theme: music, culture, food, cause
Volunteer-matching platforms relevant to your region
Partner organisations that share your audience

Avoid relying on social media alone for recruitment. It surfaces interest but doesn’t convert reliably. Use it to drive people to a proper signup form with role descriptions.

Briefing volunteers before the event

Volunteers can’t perform a role they weren’t briefed on. The morning-of briefing is the most common single point of failure: too much information delivered too fast to people who haven’t had coffee yet.

Two briefings work better than one.

A pre-event briefing, ideally 1 to 2 weeks out, covering the festival’s layout, the schedule, the policies that affect them, and their specific role. A 30-minute video call works for distributed teams. A printed handbook works for people who’d rather read.
A morning-of briefing, no more than 15 minutes, covering today’s specifics: what changed since the pre-brief, who’s where, weather, the radio channel, the escalation chain.

Then keep briefing during the event. Push updates to the relevant teams as things change. Brief incoming shifts at the handover, not just at the start of the day.

Frequently asked questions

How many volunteers do I need for a festival?

A baseline is one volunteer per 50 to 100 attendees, adjusted upward for complex ticketing, family programming, or extensive staging. Under 1,000 attendees typically needs 20 to 40 volunteers; 1,000 to 10,000 needs 75 to 200; 10,000+ needs 300 or more, with paid leads on top.

How long should festival volunteer shifts be?

Three to four hours for active, public-facing roles. Six to eight hours is acceptable for setup and teardown with proper breaks and meals. Shifts longer than four hours in customer-facing roles produce more mistakes and lower-quality interactions.

Can volunteers handle security and first aid?

Only in a supporting role. Professional staff should handle anything serious. Volunteers can provide visible presence, do bag checks at low-risk entry points, and direct people to the medical tent, but they shouldn’t be your primary line for either.

How do I fill the unpopular shifts?

Gate the popular shifts behind eligibility (returning volunteers only, or “complete one less popular shift first”). Tier the perks so harder shifts get better compensation: extra meal vouchers, priority signup next year, public recognition. Cap the attractive zones once they’re full so new signups redirect to what’s short-staffed. For the genuinely worst shifts, pay a small contracted crew rather than relying on goodwill.

How do I keep festival volunteers from quitting mid-event?

Cap shift length, build in handovers, feed them on schedule, give them water, and make sure they know who to escalate to when something goes wrong. Most mid-event quits come from volunteers being given a job they can’t actually do: bad brief, missing tools, no relief.

What’s the most common festival coordination failure?

A schedule changes and only half the volunteers find out. Fix it with one source of truth for the schedule (usually a chat channel or shared document) and a discipline of pushing every change there first, before announcing it anywhere else.

Let them sign up, but design the signup. Pure self-selection without scarcity management leaves the unpleasant shifts empty. Combine self-signup with eligibility gates on the popular shifts, caps on the attractive zones, and tiered perks for the harder shifts.

What do festival volunteers get in return?

Free entry to the festival outside their shift, meals during shifts, a volunteer t-shirt, and sometimes a credit toward next year. Multi-day events often include camping spots and travel reimbursement.

How Zelos helps with festival volunteer coordination

Zelos Team Management is a task and shift signup app with built-in messaging. You post shifts, volunteers claim the ones that fit them, and every shift carries its own chat channel, by design, so when the gate procedure changes at 11am, only the gate crew gets pinged.

The free plan covers unlimited volunteers and works for small to mid-size festivals. The Pro plan adds CSV bulk upload and full history at $99/month. Never per volunteer, no matter how many you bring on for the weekend.

Start a free project or book a demo to see how it works for your event.