The Run-of-Show Is Not the Plan. The Contingency Column Is.

Most run-of-show documents look finished long before they are useful. Times down the left, cues across the top, names in every cell. It reads well in a production meeting. It also assumes the day goes exactly the way the document says it will, and no day does.

The version we build for our own events has one more column, and it is the one we spend the most time on.

What the contingency column actually holds

For every line that can fail, we write down what happens when it does. Not a philosophy, a decision.

• Keynote runs eleven minutes long: pull the sponsor video, hold the break at ten minutes, tell catering by radio before we tell the room.
• Generator two drops: which circuits die, which vendor is on it, who tells the stage manager, and how long we ride the house PA before we announce anything.
• Shuttle loop is late by twenty minutes: hold doors or open bar early, and who owns that call.

The point is not to predict every failure. The point is that when something breaks, nobody is inventing a plan in front of a client with a headset on.

Why teams skip it

It is uncomfortable. Writing down the failure states of your own event feels like admitting the plan is fragile. It is also more work, because a real contingency line requires a phone call to the vendor to confirm they can actually do the thing you are writing down.

The teams that skip it are usually the ones who describe their events as "mostly smooth" afterward. Mostly is the tell.

Where the decisions come from

The column is only as good as the conversations behind it. We build ours in three passes.

1. Walk the timeline with the venue. Every transition, ask what the building cannot do quickly. Doors that lock on a schedule, freight elevators with a service window, a loading dock shared with the restaurant next door.
2. Walk it with every vendor who has a call time. Ask what breaks their day. AV wants to know when they lose the room. Catering wants the real dinner time, not the printed one.
3. Walk it with the client and ask which moments are non-negotiable. Everything else is what you trade when time runs short.

The version the room sees

The client does not need the contingency column. They need to trust that it exists. We keep a clean, printed run-of-show for the client and a working copy for the operations team, and we never confuse the two.

When we moved this into the Kewl platform, the working copy became the one that updates in real time for every radio holder, while the client version stays clean. That was the whole reason we built it. The document was never the problem. The gap between the document and the people executing it was.

Start with three lines

If your next event has a run-of-show with no failure states written in, pick the three moments that would hurt the most and write the decision for each. Confirm it with the vendor who owns the fix. Then hand it to whoever is on the radio.

That is the plan. Everything else is the schedule.