Festival staff schedule: how to plan a multi-day event crew from build to strike

A festival is a run: a build, two to four show days, a strike. Four things change when the same people come back day after day, and each belongs in the schedule, not in the ops manager's head.

• Demand changes by day. Friday opens late, Saturday sells out, Sunday is lighter but runs on tired crews. Headcount and the crowd manager count move with it.
• Fatigue accumulates. An 8-hour shift on day four is not the load it was on day one, especially in heat. Rest between shifts becomes a constraint.
• Hours add up. Daily and weekly overtime, seventh-day rules and day-of-rest laws count across days, so a schedule that looks fine day by day can trigger premiums on the last one.
• Information carries over. No-shows, removed workers, a lost credential, a post that ran short: day one changes the plan for day two, and somebody writes it down that night.

The method builds the schedule in layers: the calendar, the headcount per day, a shift pattern per crew, the people in each slot, then the rules that cross days. Every number comes from one worked example, a three-day music festival, so you can swap in your own figures. For single-day sizing, start with the event staffing plan for large events, which covers posts, span of control, check-in lanes, briefings, breaks and crowd managers for a single day.

Start with a one-line-per-day calendar agreed with the producer. Build and strike days are the ones agencies underprice: smaller crews, different skills (lifting, stocking, bar setup), earlier calls, fewer amenities.

Do not copy Saturday's crew onto Friday and Sunday. Size each day from its own demand drivers: gate lanes from arrivals per minute, bars from drinks per hour, guest services from posts on the site map. The per-post method is the same as for a single large event; what changes is that you run it once per day and then look for the crews that can stay constant.

Two consequences follow. The core crew is the Friday number, about 170 people who work all three show days; Saturday adds about 100 for one day and Sunday keeps about 50 of them, filled by workers who want one or two days. And crowd manager coverage changes daily. Under NFPA 101 the ratio is 1 trained crowd manager per 250 occupants: 48 on Friday, 80 on Saturday, 64 on Sunday if the fire marshal applies the ratio to expected attendance rather than permit capacity. Ask which figure applies, and count trained relievers separately so the number holds during breaks.

Saturday in the example runs from 10 AM (setup and briefings before 12 PM gates) to 1 AM (bar close, cash-out, egress): 15 hours that no single shift should cover. Each crew gets a pattern built around its own peak.

In California the meal must start before the end of the fifth hour, so the day band's meals fall between 11 AM and 3 PM and the evening band's between 5 PM and 9:30 PM. Place them in the schedule, by name, before the first day. The relief crew covers posts that cannot go empty, and the model in the large events guide shows how to size it. The peak shift is 4.5 hours: under California's 5-hour threshold for a meal, but over the 3.5 hours that trigger a 10-minute paid rest.

What breaks most festival schedules is not shift length but the gap between shifts. A worker who closes a bar at 1 AM, gets home at 2 AM and opens at 10 AM has had 8 hours off at best. Repeat for three nights and Sunday's bar crew is the most tired of the run.

NIOSH, in its guidance on long work hours, recommends at least 10 consecutive hours of protected off-duty time per day so workers can get 7 to 8 hours of sleep, and one or two full days of rest after five consecutive 8-hour shifts or four 10-hour shifts. A study of 10,793 US workers (Dembe and colleagues, 2005) found that jobs with overtime schedules carried a 61% higher injury hazard rate, and that working at least 12 hours a day was associated with a 37% higher hazard rate.

Rules that keep turnarounds safe

• Same band all run. Day-band workers stay on days, evening-band workers stay on evenings. It is the simplest way to keep every gap above 10 hours.
• Count the gap from real release time. If bar close and cash-out run to 1:30 AM, the next shift starts no earlier than 11:30 AM. Add the shuttle or the walk to staff parking.
• Never put Sunday's closers on Monday's strike. Sunday's evening band ends at midnight in the example; an 8 AM strike call is 8 hours later. Staff the strike with the day band or with a separate crew.
• Keep build crews off the first show morning. Thursday's build crew worked outdoors all day; give Friday's opening posts to people who start fresh.
• Cap consecutive long days. A worker on a 10-hour band for the build and every show day can reach five or six long days in a row. Rotate a day off into the run, or use two build crews.

Rotation decides who does the hardest posts, and for how long. Your strongest bartender can run the busiest bar for one day; over three days, they burn out by Saturday night.

Heat changes over the run too. OSHA's rule of 20 percent suggests that a worker new to heat spends no more than 20% of a normal shift in the heat on day one, increasing day by day. A festival crew is not on site long enough to fully acclimatize, but the logic still helps: put workers who just arrived from a cooler climate, or who work indoors the rest of the year, on shaded posts first, and move them to exposed posts later in the run. California's outdoor heat standard requires close observation of every worker during a heat wave, and of anyone newly assigned to a high-heat area for their first 14 days, which covers every day of a typical festival. The full heat plan (water, shade, high-heat procedures) is in the large events guide.

Every festival day has three staff peaks, and the schedule shows each one with the headcount required at that hour.

1. Gate opening. Most arrivals come in the first hours. Front-load scanners and line managers, and release part of the gate crew to other posts once the line clears, rather than sending them home early on a short day they were promised.
2. Headliner and the hour before. Bars, restrooms queues and guest services peak together. This is where the peak shift and the overlap between day and evening bands belong.
3. Exit and close. Egress, lost-and-found, bar cash-out, stock counts. It is the least glamorous hour and the one where tired crews leave early. Schedule release times, not "when it is done", and keep a lead on site until the last worker clocks out.

A multi-day schedule needs two kinds of handover. The first happens at each post when the day band hands over to the evening band. The second happens every night, between today's team and tomorrow's plan.

At the post

Overlap the bands at each post (30 minutes leaves room for late arrivals). The outgoing worker covers what is not obvious: low stock, a till problem, a guest issue in progress. They clock out only once the incoming worker is in place, so the post never goes empty and the crowd manager count never drops.

Day to day

The log produces three outputs before anyone goes to bed: the next day's call-time changes, the standby list for the morning, and the confirmation message to everyone working tomorrow. Workers who confirm the night before are the ones you can count on at call time; silence is your early warning for the no-show plan.

No-shows on a festival do not stay flat. Sunburn, a bad night's sleep, a Monday job or simply a better offer can pull people out of the last day more than the first. There is no reliable public figure for this, so use your own: track show-up rate by day of the run, by crew and by worker, and size standby per day from that history rather than from a flat percentage.

• Book the whole run, confirm each day. A worker booked for three days confirms three times: once at booking, and the evening before each day.
• Replace from the run first. A worker on the day band who is willing to extend is faster than a new person who needs a credential and a briefing, as long as the extension respects the 10-hour turnaround and the overtime budget.
• Keep credentials and briefings ready for standby. A standby worker without a credential cannot enter the staff gate. Get standby names on the accreditation list with everyone else.

Credentials are where the schedule meets site security. The Cybersecurity and Infrastructure Security Agency's Public Venue Credentialing Guide describes credentialing as an access control process, separate from tickets, with access areas marked by color, shapes, numbers or letters, and the ability to deactivate a lost or stolen credential. It also recommends collecting temporary credentials at the end, cross-checking what came back and deactivating what did not.

For an agency, the credential list is an export of the schedule: every worker once, with crew, zones and valid days. Added to the schedule means added to the list; removed means the credential is deactivated or collected.

The Fair Labor Standards Act requires overtime after 40 hours in a workweek, a fixed, recurring 168-hour period the employer sets (it need not match the calendar week, but cannot be moved to avoid overtime). Hours the same worker puts in on other jobs for your agency in that workweek count too. Several states add daily rules.

Over three or four days, a storm, a heat wave or high wind is likely to hit at least one. Agree plan B before the run, not in the rain.

• Holds. The National Weather Service rule is to wait 30 minutes after the last lightning or thunder before going back outside. Event control calls the hold; your crews need a shelter location each, a headcount by crew list, and a clear rule on whether hold time is paid and billed (it usually is if workers stay on site).
• Delayed opening. If gates open two hours late, decide whether call times move or crews wait. Moving calls the night before is cheaper than paying a crew to stand in a tent.
• Canceled day. In California, a worker who reports as scheduled and gets less than half the usual day is owed reporting time pay for half the scheduled day, at least 2 and at most 4 hours. Interruptions caused by acts of God or by civil authorities are exceptions, which is exactly where weather cancellations land. Write into the client contract what is billed when a day is canceled, and tell workers in the brief what they are paid.
• Heat days. A forecast heat advisory adds water, shade and rotations, and often a few more people per exposed crew. Decide the trigger with the client in advance, so adding heads on the day is not a negotiation.

Over several days, logistics decide whether people come back: the worker who missed the last shuttle on Saturday is the Sunday no-show. Put each item in the schedule with an owner.

A festival schedule is one table with a row per worker per day. Everything else (call sheets per crew, the credential list, the standby list, the timesheet) is a filtered view of that table.

Two formulas catch most errors: the rest gap (next shift's call time minus this shift's release time, flagged under 10 hours) and the running total of hours per worker in the workweek (flagged at 40, and at 8 per day in California). The free event staff schedule template for Excel and Google Sheets has shifts by event and role, unpaid breaks, hours, confirmations and open slots; add a column per day of the run and the two checks above.

Reconcile hours every night: on day four nobody remembers who left Bar 7 early on day one. The FLSA requires a record of hours worked each workday and each workweek, so the nightly reconciliation is also your compliance record.

Send the client a short daily note (booked against arrived, unfilled posts, incidents) and a full recap within 24 hours of the strike: hours by crew and day matching the invoice, no-shows by day, credential returns and three fixes. Next year's schedule starts from that recap.