Nine days.
One board.

Standby is festival shift tracking software for multi-day, multi-stage events. Hundreds of positions across the grounds, a roster that turns over between days, and a plan that shifts every morning, all held on one board.

A one-night show and a nine-day festival break in completely different ways. This page is about the second kind.

The plan changes every morning

Day 3 is not day 2. Gates move, a stage runs long, weather rearranges the grounds, and the coverage you built in February stopped describing reality sometime around load-in.

Standby holds multiple areas, shifts, and days in one event, so changing tomorrow doesn't mean rebuilding the week. What you actually staffed on each day stays recorded separately, which matters when someone asks about day 6 specifically.

Hundreds of positions, tracked one at a time

A position in Standby is always a single assignment. Six people working the same gate means six lines, tracked separately, so each one can be covered and reported on by itself. That's what makes "the gate is staffed" a checkable statement instead of a hopeful one.

At festival scale that distinction stops being pedantic. A gate that's supposed to hold 6 and is holding 4 reads as covered on a spreadsheet.

The gate that empties at 2am

Late at night, deep into a multi-day run, somebody covers a break and pulls a person off another position. Nobody's fresh, the radio's busy, and the position that just emptied is at the far end of the grounds.

Standby flags it the moment the move is made and floats it to the top of the board. Long-shift and missed-break warnings surface too, which is the kind of thing that matters more on day 7 than on day 1.

On a nine-day run, the mistakes don't come from not knowing the job. They come from hour 60.

It works where the grounds don't

Festival sites are large and reception is uneven. The live board works offline, and moves save on the device and sync when the signal comes back, so the far corner of the site stays on the same board as the command post.

Next year starts from this year

Clone a past event onto new dates and the structure comes with it: the areas, the positions, the shift patterns you worked out the hard way. Or import a schedule you've already built elsewhere.

Standby doesn't collect availability from your crew. That stays wherever you do it now. From there you schedule inside Standby or bring the schedule in.

What you can prove at load-out

Coverage of record, position by position, across every day of the run, measured against what your client signed off on before the gates opened. Shift reports, staff reports, and after-action reviews come out of the moves you already made.

On a festival that's often the difference between a renewal conversation and an invoice dispute.

Priced per event, from $100

Tiers are sized by staff-hours, the total staffed time across the whole run, so a festival lands in the Festival tier at $2,500 rather than being billed per person per month for a roster that existed for nine days. See the pricing page for where your event lands.

For the general version of this, without the multi-day scale, see event shift tracking.