It's 1am. A guard radios in for lunch. You pull someone to cover, then someone to cover them, and now you're at the whiteboard, erasing three names, hoping you don't forget that Post 4 is now standing empty.
Run the site.
Keep the record.
You want to finish the night with every post covered and a record clean enough to hand the client. Standby keeps the contract, the schedule, and the live board in one place so you can. By the time the shift ends, the handoff and the proof have already written themselves.
across one festival
across the run
even agree on a name
by hand, the night before
The radio call is the easy part.
Running a live event means holding three pictures in your head at once: what you promised, who's actually here, and where everyone is right now. They're scattered across emails, spreadsheets, sign-in sheets, and a whiteboard. They never agree, and the person who needs them most can't see them.
Who's here, and what are they holding?
Clock-ins on one sheet, radio handout on a clipboard, breaks tracked in someone's head. The basic questions take a lap of the site to answer.
- Did this agent actually clock in
- What radio and gear do they have
- Did they get their lunch yet
- Is their card still current
Three numbers that should match, and never do.
Contracted, signed up, actually showed, and a callout at 11pm turns into a gap nobody planned for. You find out when a post goes dark.
- What did we contract to cover
- Who actually signed up to work
- What gaps am I carrying tonight
- Who just called out sick
- Who never showed at all
The promise lives where the site can't see it.
The client agreement is buried in emails and a spreadsheet. The site lives on a whiteboard. They drift apart all night, and the shift lead has no line of sight to what was promised.
- Does the ground match the contract
- Can we prove it if asked
Here is the night it costs you. A client asks you to prove a post was covered, and all you've got is a whiteboard that got wiped at 2am.
Falcon goes on lunch.
It's the move that breaks every other tool. Falcon goes on lunch, you pull the nearest body to cover, and that body was holding a post too, so now there's a hole you didn't open on purpose. On a whiteboard you catch it or you don't. On Standby the empty post flags itself the second you create it, floats to the top in red, and the whole relief chain writes itself into the record while you're still keying it in.
Ask anyone who's stood a post what actually goes wrong and you'll hear the same word: forgotten. Left on a position long past the break they were promised, because everyone downstream of the radio lost track.
An empty post should never be able to go dark. That's the one rule the whole board is built to enforce.
If you move people around
a live event, this is for you.
Standby is event security scheduling and operations software, built on site, where an empty post is a real problem. But the scattered-spreadsheets-and-whiteboard dance is the same everywhere there's a roster, a clock, and a client expecting what they paid for.
Call it a post, an aid station, a flagger station, or a section. Same problem underneath: somebody's supposed to be standing there, and right now you can't say for certain they are.
You already know this one. An agent radios in for lunch, you pull the nearest body to cover, and that body was holding a post too. Standby flags the position that just went empty before anyone gets on the radio to tell you.
Crew work a call, and the call has a start time somebody has to hold. Standby tracks who actually turned up against what you booked, group by group, so a short call gets caught at call time instead of at load-out.
Volunteers are enthusiastic part-timers, and a share of them won't turn up. Standby shows which positions are genuinely filled right now, so the people you're holding on standby go where the hole actually is.
Multi-day, multi-stage, hundreds of positions across the grounds, and the plan shifts every morning. Standby holds the whole run on one board, and a gate that empties at 2am surfaces the moment it happens.
Staff get posted to a section and then, in their own word, forgotten. Standby keeps every post visible from the command post. When a fire marshal asks how many trained crowd managers you had on site, the answer's already written down.
Aid stations and roving teams, staffed at the level you agreed to hold. Standby tracks who's on station and whether their certification is current, with the record sitting there when the authority having jurisdiction asks.
Flaggers work a station under a traffic control plan, usually out of sight of everyone else. Standby shows which stations are covered and whose certification is current, without a supervisor driving the lot to find out.
Ushers, ticket takers, and guest services, spread across more sections than any one person can watch. Standby puts every position on one screen, so a section that empties out in the third quarter doesn't stay that way.
Plan it
Build the coverage with your client and get the sign-off.
Run it
Move the site in real time while the open posts watch themselves.
Prove it
Hand the client a record that wrote itself.
Stop running the site from memory.
I've run the night you're running, and I know the 1am math. That's the tool I built, and it's opening to a small group of operators who are done with the spreadsheet shuffle. Request access and I'll walk you through your next event on one board.
Next event, you walk into the trailer with the answer already in hand. Every post covered, the shift handed off in 5 minutes, the report already written.