The run sheet your colleagues will actually read

The run sheet is fourteen pages, neatly formatted, and during the event nobody opens it. The bar staff ask what time the speech is. The technician calls about a microphone that's in appendix B. You spend the whole evening being the search function.

That isn't your colleagues' fault. A fourteen-page document was never designed to be consulted standing up, in a half-dark room, holding a tray.

One timeline, no chapters

A run sheet that works on the floor is a single continuous list by time, from set-up to breakdown. No sections per department — those force everyone to jump between pages to see what's happening at the same moment.

Four things per line: what time, what, who, where. Anything that doesn't fit belongs in an appendix nobody needs during the event.

Write names, not roles

"Technical" is nobody. "Mark" is someone you can go and find. Add phone numbers for the four people who genuinely matter during the event — including the client's contact, because half the questions on the night are about something only they know.

Put in what goes wrong

The part that's usually missing is the part that gets consulted most:

• Who decides if the programme overruns?
• What do we do if it rains, when something is outdoors?
• Who calls the caterer if there are twenty extra guests?
• Where are the spare microphones?

Four lines. They save you ten phone calls during the event.

One page, on a phone

Don't print it as a document — publish it as a list that's readable on a phone screen. Your colleagues have their phones on them, and your paper run sheet is behind the bar.

The test is simple: can someone joining at 17:00 see in thirty seconds what they need to do at 17:30? If not, it's still a document and not a run sheet.