Volunteer management system for festivals: how to get shifts, staffing and communication under control

Published 2 September 2026 · Consitus

Most festivals start with a spreadsheet, and it works for a surprisingly long time — until there are fifteen departments, three shift layers a day and a pile of last-minute cancellations. At that point the work is no longer about planning, but about knowing which version of the plan is the real one.

This guide walks through how volunteer planning usually works in practice, what a volunteer management system has to do in order to remove work rather than add it, and how to choose a system based on your own workflow.

Why spreadsheets and email become fragile

A spreadsheet has no roles, no history and no way to notify a volunteer. Coordination therefore moves into email, text messages and phone calls — and the plan is only correct as long as one person keeps track of every channel.

• Several people edit the same staffing plan without seeing each other's changes.
• Cancellations land in an inbox instead of in the shift plan.
• Volunteers do not know their own shift unless somebody sends it again.
• Contact details exist in several versions of the same sheet.
• Nobody can say exactly how many people are missing right now.
• Last year's experience disappears when the sheet is never tidied up.

The spreadsheet itself is rarely the problem. The problem is that coordination depends on memory and manual messages — and the exposure is greatest during the days when the festival is actually running.

Start with the festival's workflow — not with the system

The most common misstep is to begin with the question “which system should we buy?”. The right first step is to describe what actually happens from A to B in your organisation. For a festival the sequence usually looks like this:

• A volunteer signs up and creates a profile with contact details.
• The volunteer is attached to one or more departments.
• Preferences are recorded, or the volunteer picks from open shifts.
• A department lead approves and allocates the shifts.
• Communication goes out to the department, the team or a single shift.
• Attendance is recorded while the festival runs.
• Changes and cancellations are handled on the fly.
• History and setup are kept and reused next year.

Once the sequence is written down, the real problems become visible: where you switch systems, where the same thing is typed twice, where a status is missing, and who actually owns each step. That description should drive the system choice.

Which system should we choose?

Choose based on workflows and responsibility, not on the longest feature list. A system with a hundred features is no better if the twelve you use every day do not match the way the festival is organised.

Questions that decide the choice

• Can department leads work independently without access to everything?
• Does the system's idea of a shift match your shift types, teams and changeover times?
• Can the plan be changed during the event without losing the overview?
• Can volunteers understand their own plan without instructions?
• Do you keep the specialist systems that work — ticketing, accounting, messaging?

The system should fit the workflow, not force the organisation into a standard flow. If the festival is pushed into a fixed flow, coordination drifts back to email and spreadsheets, because that is faster than fighting the system. For us the foundation is Consitus Intranet with modules assembled afterwards — but the principle holds whichever supplier you choose.

Roles and access for department leads

A festival is not one organisation but many small ones. Bar, stage, entrance, kitchen and clean-up each have a lead who knows their own people best. The system should reflect that: the lead plans, approves and communicates within their own department, while the coordinator sees the whole picture.

Without role separation, all the work collects with one person — and the system becomes a new bottleneck instead of relief.

Open shifts, staffing gaps and cancellations

The core of a volunteer system is that the staffing plan always shows reality. That takes three things: open shifts must be visible, gaps must be marked, and a cancellation must make a shift available again.

• Open shifts can be seen and claimed by the volunteers allowed to take them.
• Staffing gaps are shown clearly, so prioritising is easy.
• Cancellations inside a deadline are handled by the volunteer.
• Cancellations after the deadline go to the lead, who can refill the shift.
• Changes are logged, so nobody is unsure what was agreed.

Targeted communication instead of mailing lists

Manual mailing lists go out of date the moment a shift plan changes. When communication is sent from the plan instead — to a department, a team, a shift or a day — the message always reaches the right people and there is no list to maintain.

It also makes follow-up simple: a reminder the day before, a note about a changed meeting point, or a thank-you afterwards can go to exactly the group concerned.

Mobile access during the festival

During the event nobody is sitting at a computer. Volunteers and leads have a phone in hand, and the system has to work that way: see your shift, see who is arriving, record attendance, send a message, find a phone number.

Reuse from year to year and history

A festival repeats itself. Departments, shift types, time slots and task descriptions are largely the same, and the volunteers are often the same people. If last year's setup can be copied, planning goes from weeks to days.

History is worth more than the time saved: you can see who has helped before and where, which shifts are usually hard to fill, and how many cancellations to plan for.

Possible extensions when the need is real

Once shifts and staffing run smoothly, there is usually an appetite to bring more of the work into the same place. That can make good sense — but only when the need is concrete:

• Documents and checklists per department, so instructions sit with the shift.
• Meetings and minutes for coordinators and department leads.
• A simple budget and visitor-economy overview for internal management.
• Public display of selected information, such as open shifts or the programme.

One important boundary: a volunteer system is not an accounting system. Figures can be recorded and displayed for management and follow-up, but bookkeeping, VAT and annual accounts stay in the accounting system, which the solution can exchange data with instead.

Signs the festival has outgrown spreadsheets

• Several people edit the plan and nobody is sure which version applies.
• Cancellations arrive through four different channels.
• Volunteers ask again about their shift because they cannot find it.
• Department leads wait for the coordinator to update the sheet.
• Staffing gaps are discovered on the day.
• Contact details have to be cleaned up every year.
• Planning restarts from scratch because last year's sheet is unusable.

Pitfalls when choosing and implementing a system

• Choosing a system before the workflows are described.
• Adopting everything in year one instead of shifts and staffing first.
• Requiring duplicate entry because the spreadsheet stays alongside.
• Giving everyone access to everything, so nobody dares change anything.
• Choosing a solution volunteers cannot use on a phone.
• Forgetting who owns the setup once the festival is over.

Next steps

Start by describing one department's workflow and counting the system switches and duplicate entries. Then read more about volunteer management for festivals and how a digital workplace connects the systems you already use.