Running a Village Harvest Festival: Notes From Marcus's Stage
Oliver Hartley
6 min read
Marcus organises a small autumn festival on a school field. This is how a run sheet, a signal plan and a crew list turned a shaky first year into a calm second one.
A call in the middle of the harvest season
Marcus rang us in early autumn with a problem that many festival organisers recognise. His village harvest festival had grown from a single marquee and a borrowed sound system to two stages, a food area and an evening headline slot. The first year had gone well enough for the public, but he described the back of house as a series of shouted conversations.
He wanted to know whether it was worth planning the second year properly or simply hiring more people. I asked him to send me whatever paperwork existed. It was a single page of set times, a list of phone numbers and a photograph of a hand-drawn site plan. That was enough to begin with, and we arranged a visit to the field.
What struck me on that first walk round was how much knowledge lived in one person's head. Marcus knew which cable run crossed the footpath, which band needed a longer changeover and which volunteer could be trusted with the generator. None of that was written anywhere, and none of it would survive a bad cold or a double booking.
Starting with the run sheet
We began with the run sheet because everything else hangs from it. Marcus's single page listed start times, but it said nothing about changeovers, soundchecks, announcements or who had authority to cut a set short if the schedule slipped. We rebuilt it as a minute-by-minute document, with each line naming the stage, the act, the crew member responsible and the cue that moves things on.
The useful discovery was the changeover. Bands in the afternoon were given ten minutes, and in practice they needed twenty. Rather than squeeze people, we shifted the order so that acoustic sets, which need almost no resetting, sat between the louder bands. A small change on paper, but it removed the pressure that had caused most of the shouting the year before.
We also agreed a single copy as the master. Printed versions went to each stage manager, with the time of any revision written at the top, so nobody worked from an outdated list.
- Changeover time written into every line
- One master copy, revisions marked at the top
- A named person for each cue
Mapping the signal and the cable runs
The second job was the signal plan. Marcus had a main stage and a smaller tent stage about eighty metres apart, and a small video screen at the food area showing the main stage. We drew a simple diagram of what left each desk, where it travelled and what it fed, including the feed for the screen and a talkback line between the two stages.
Drawing it out exposed a weakness straight away. The talkback relied on a single long cable laid across a path that would carry the busiest foot traffic of the day. We rerouted it along the field edge and added a cable ramp at the one point where it had to cross.
Labelling mattered as much as routing. Each end of every run received a matching tag, so that a volunteer who had never seen the system could trace a fault without pulling anything out at random.
Planning the crew, not just the kit
Marcus's instinct was that the answer to confusion was more hands. We took the opposite view: fewer people, each with a clear role. We wrote a short crew list showing who covered front of house sound, stage management at each location, power, and a floating pair who could step in wherever things went wrong. Each person received the run sheet and the signal plan before the day.
We also built in breaks. Volunteers who start at seven in the morning and finish near midnight make mistakes in the final hours, so we staggered the shifts and made sure the evening headline slot had a fresh stage manager rather than someone on their thirteenth hour.
A short briefing at the main stage before gates opened covered the plan, the emergency contacts and the one rule everyone agreed to: if in doubt, call the stage manager rather than improvising.
- Fewer roles, each clearly named
- Staggered shifts with real breaks
- A fresh stage manager for the headline slot
How the day actually went
I was not on site for the whole festival, but Marcus rang me during the late afternoon. The schedule had slipped by about fifteen minutes after a delayed band, and for the first time he could see exactly where to recover it. The acoustic slot absorbed the delay, and nobody on the crew needed to be told twice.
A light shower mid-afternoon tested the cable plan. The ramps held, the tags let a volunteer find a wet connector quickly, and the main stage lost less than a minute of sound. The talkback line worked throughout, which meant the two stage managers could settle a late change without anyone walking across the field.
The headline act started on time, and the evening finished a few minutes early. Marcus told me the most noticeable difference was the quiet: the back of house felt calm, and people spoke at normal volume.
What Marcus is changing for next year
Afterwards we sat down with the marked-up run sheet and went through what had worked. Marcus wants to add a short rehearsal block on the evening before, so the two stage managers can walk through the first hour together. He also plans to move the generator further from the tent stage, because the hum was audible during quiet acoustic moments.
None of these ideas are dramatic, and that is the point of a workflow. It is a set of small, written decisions that let a volunteer crew behave like a coordinated one. Marcus keeps the document in a folder, updates it after each event and hands a copy to anyone new.
If you run a festival or party with more than one stage, the same starting point applies: write the run sheet, draw the signal, name the crew.
Marcus's festival did not need more equipment or a larger team. It needed its decisions written down: a run sheet with honest changeover times, a signal plan with labelled cable runs and a crew list in which every person knew their job. Those three documents turned a day of shouted instructions into a calm one. Whatever the size of your event, the same habit applies, and it is worth doing well before the first gate opens.