The run of show, and why it comes before the set

Ask most people what went wrong at a bad conference and they will describe a symptom: the queue at registration, a session that overran, lunch that arrived while someone was still speaking. Each of those is the same failure, surfacing at a different hour. Nobody owned the minute.

The run of show is the event

It is not a schedule and it is not an agenda. An agenda says what happens. A run of show says what happens, when, who makes it happen, what has to be true beforehand, and what the room is doing while it does.

It is written before the set is designed, before the film is briefed, before anyone discusses a stage. That order is deliberate and it is the single largest difference between conferences that work and conferences that were expensive.

The set is then designed to fit inside it — which is a real constraint, and a better one than the reverse, where a set is designed first and the day is squeezed into whatever it left room for.

Work backwards from the fixed points

Something is immovable: the keynote the chief executive can attend, the flight the guest speaker is on, the hour the hall reverts to the venue. Find those first and build outward, because everything flexible arranges itself around them and nothing else does.

Then put the slack where it can actually absorb a problem. A session that runs long can eat into a coffee break; it cannot eat into a fixed lunch or a speaker who is leaving for an airport. Slack in the wrong place is not slack, it is a pinch point nobody has noticed yet.

Registration decides the day before it starts

Delegates form their view in the first twenty minutes, at a desk, having travelled. Almost every conference under-resources it.

Staff for the peak rather than the average. It will look over-staffed for an hour either side of the rush, and that is the correct amount of over-staffing. Badges pre-printed and pre-sorted. A separate path for late additions that does not run through the main queue. Somebody senior enough to make a decision standing in the foyer rather than backstage.

None of that appears on a stage, and all of it is what people describe afterwards when they say an event was well organised.

Rehearsal is the highest-return hour, and the first to be cut

Every speaker walks the stage. Every deck opens on the machine it will run from, on the screen it will show on, in the room it will be shown in. Every cue gets called once before it is called for real.

It is the first thing a client offers to drop when the schedule tightens, and it is the last thing that should go. A deck that has never been opened on the actual machine is not a deck, it is a hope — and the failure happens in front of everybody.

What the document actually contains

Not prose. A line per moment, and against each one: the time, what happens, who makes it happen, what has to already be true, and what the room and the screens are doing.

The columns that get skipped are the last two, and they are the ones that catch problems. “Who makes it happen” turns an assumption into a name. “What has to already be true” is where you discover that the panel needs four chairs on stage and the previous session ends with a lectern in the middle of it.

Version it, date it, and make sure the copy in the room is the copy everyone else has.

Plan the gaps, not just the sessions

Most of the value of a conference is in the breaks. It is where the conversations happen, where the sponsor gets their money’s worth, and where people decide whether coming was worth it.

A break too short to get a coffee and return is worse than no break: it damages the session after it, and no amount of production compensates. So the breaks are scheduled first, with the queue for coffee counted, and the sessions fitted around them.

Who is calling it

On the day the document is only as good as the person running it. That should be somebody who built it, standing where they can see the room, with the authority to decide that a session is shortened rather than a break lost.

That is what we mean by holding the timeline — and it is why the same team that designs a corporate event is the team calling it, rather than a coordinator who met the day that morning. The decisions are real, they arrive fast, and they should not be made by whoever happens to be nearest.