What you promised.
What you delivered.

Standby is event shift contract management software. You build the contracted coverage with your client, capture their sign-off, and finish the event able to show what you actually delivered against it, position by position.

The contract and the schedule usually live in different files, built by different people, for different reasons. That gap is where the arguments come from.

The contract and the schedule are different documents

The contract gets built in a spreadsheet, often by someone who never works the site. The schedule gets built somewhere else, by someone optimizing for who's available. Nobody reconciles them until something goes wrong.

So you find out you're short on a position at 6pm on the day, when the fix is expensive and the client is standing next to you.

Build the coverage with the client in it

Start from blank, upload the client's spreadsheet, or clone last year's event onto new dates. You set the positions and the hours together, and the client reviews the whole plan in a read-only view and signs off on it.

That sign-off is the important part. It becomes the baseline everything afterwards gets measured against, which turns a vague expectation into a specific, dated document you both looked at.

An agreement nobody wrote down is an agreement you'll be relitigating at load-out.

The schedule gets checked against what you sold

Once the plan is signed, scheduling people onto positions happens against that plan rather than beside it. Standby lines the contracted grid up with the schedule, so a position you sold and never staffed surfaces while there's still time to fill it.

Standby doesn't collect availability from your staff. That part stays in whatever you already use. You schedule inside Standby from there, or import a schedule you've already built.

Coverage of record

At the end you get coverage of record: what was contracted, and what was actually covered, position by position, generated from the moves your team made during the event rather than reconstructed afterwards.

Shift reports, staff reports, and after-action reviews come from the same board. When coverage gets questioned, you have the answer ready instead of a defense.

The invoice conversation

A client questions a line on the invoice. Without a record, that's a negotiation, and you usually lose some of it because the whiteboard got wiped days ago.

With coverage of record, it's a document. One contested invoice on a large show can be worth more than the software costs for the year.

Sometimes the question doesn't come from the client at all. A fire marshal can ask a venue to show how many trained crowd managers were on site for its occupant load. Some EMS authorities want a staffing plan filed before the event. The same record answers those too.

Priced per event, from $100

Tiers are sized by staff-hours, meaning the total staffed time across the event, with no per-user fee and no seat minimum. The pricing page shows all three tiers and where an event your size lands.