Why you need a live digital run of show

It is 3:50pm on a gala day. The duty manager is holding a printed run of show. It is a good run of show. It was correct at 9am, when it was printed.

Since 9am, the keynote moved fifteen minutes later, the plated mains got pushed because the kitchen is one chafing dish short, and the AV company swapped their access window from 2pm to 1:30. None of this is on the page in the duty manager's hand. The page is a confident, laminated, beautifully formatted snapshot of a morning that no longer exists.

Somewhere in the building there are at least two other printed copies. They disagree with this one, and with each other. Nobody is sure which copy the band has.

This is the printed run sheet in its natural habitat. It is not lying to you on purpose. It just stopped being true around lunchtime and didn't tell anyone.

Here are the reasons a live digital ROS beats the printout, in roughly the order they will ruin your afternoon. A note before we start: 1pm is event management software, and the run of show is one page of it rather than the point of it. That turns out to matter, and I have put the reason at the end.

One. The printout is wrong the moment it prints

A printed ROS is a photograph. A live ROS is a window.

The second you hit print, the document and the event begin to drift apart. Every change after that point lives in someone's head, a text message, or a hurried biro scribble in the margin that only the person who wrote it can read.

A live ROS doesn't drift. You change the keynote time once, on your phone, and every device looking at that ROS shows the new time within seconds. The duty manager, the AV lead, the banquet captain, and the planner are all reading the same line at the same time. No reprint. No "ignore the times on the sheet, I'll tell you the real ones."

Two. There is only ever one copy

The most expensive words at any event are "which version is this?"

Printed run sheets multiply. There is the one from the 9am print run, the one the planner annotated at noon, the one the kitchen has that is actually from last week, and the one nobody can find. Each is a small, plausible, contradictory source of truth.

A live ROS has one copy. Everyone is looking at it. When it changes, it changes for everyone, because it was never really three documents pretending to be one. The argument about which version is correct simply stops happening, because there is only one version and it is the current one.

Three. Nobody has to read the whole thing

A printed ROS gives the florist the entire day. All of it. The keynote, the AV resets, the kitchen timings, the speeches, the strike. The florist needs about four lines of this and has to find them by eye while holding a bucket of peonies.

A live ROS filters. Each crew member opens their link and sees only the items they are actually on, with a one-tap switch to the full picture when they need context. The AV tech sees AV. The photographer sees the moments. The duty manager sees everything, because that is the job.

Less paper to scan means fewer missed cues, which is the entire point of having a run of show in the first place.

Four. It does the time math so you don't have to

Events run late. This is not a flaw in your planning, it is a property of the universe.

On paper, when one thing slips, every following time is now quietly wrong, and the only fix is mental arithmetic performed under pressure by a tired person. "Okay, if dinner is twenty minutes late, then speeches are at, hang on, give me a second."

A live ROS resequences for you. Move an item or stretch a duration and the following times follow automatically. Better still, it shows live countdowns, so instead of doing subtraction in your head you just read "speeches in 12 min" off the screen. The clock does the worrying.

Five. It works on a phone in a loading dock

A run of show is only useful in the places events actually happen, which are rarely near a printer and often near a delivery truck.

The honest objection to going digital is "the venue Wi-Fi is terrible." It is. Everyone's is. A live ROS that assumes a perfect connection is just a worse version of paper.

So a good one caches locally and keeps working when the signal drops. Crew can still see their items, still tap Start and Finish, and everything syncs back up when the bars return. It is built for someone standing in a service corridor holding a phone, not someone sitting at a laptop with fiber.

Six. It tells you what actually happened

When the post-event debrief asks why the dessert service ran twenty minutes long, the printed run sheet has no opinion. It only ever knew the plan, never the reality.

A live ROS records the truth. Crew mark when they actually start and finish, so you get real wall-clock timing instead of best guesses. Every change is logged with who made it and when. Next time you plan a similar event, you are working from what really took forty-five minutes last time, not from the forty you optimistically wrote down.

This is the difference between a document you throw away and a record you learn from.

Seven. You can fix it from the floor

The final indignity of the printout is that fixing it means going back to a computer, editing the file, finding the printer, and physically replacing every copy in the building. Nobody does this mid-event. So the corrections live on sticky notes and shouted updates instead.

A live ROS is edited from wherever you are standing. Spot a clash at the back of the room, fix it on your phone, and it is corrected everywhere before you have walked back to the front. The ROS stays current because keeping it current costs you ten seconds, not a lap of the venue.

Where the run of show actually sits

Everything above is an argument for a live ROS over a printed one. It is not an argument for a run of show app, and that distinction is worth twenty seconds.

A standalone timeline tool gives you a better version of the document. You still type the guest count into it, because the guest count lives in your booking system. You still type the crew in, because your contacts live somewhere else. You still type the access and vacate windows in, because they came off a BEO built in a word processor. You have improved one document and added a ninth place for a detail to go stale.

In 1pm the run of show is one view of an event record that already exists. The event came in as an enquiry on a form, got priced from your item catalog, went out as a quote, came back accepted against a version of your terms, took a deposit through Stripe, and picked up a space, a menu, a pax count, and a crew list on the way. By the time you open the run of show, most of what it needs is already there.

So the times sit next to the BEO the kitchen is cooking from. The crew on an item are the same contacts you chased for insurance certificates through a request. The space carries its own access instructions and will not let you double-book it. The dietary numbers came from the guests themselves. Change the pax and it changes on the BEO, the invoice, and the report, not just on the timeline.

That is the actual argument for a live ROS, and it is a different one from "paper goes stale". Paper goes stale because nobody updates it. A disconnected digital timeline goes stale for exactly the same reason. The only version that stays true is the one that was never a separate document to begin with.

The run of show is the part people notice first, because it is the part standing in the room at 3:50pm. It is genuinely the smaller half of what 1pm does.

A quick note about words

Run of show, ROS, run sheet: same thing, different rooms. Some teams say run sheet, some say ROS, plenty of venues just call it "the timeline." Use whichever your crew already says. The format matters far more than the label, and a live one beats a printed one regardless of what is written at the top.

If you would rather start from something than from an empty page, there is a free run of show builder on this site, with starting points for weddings, conferences and galas. No account, and nothing you type in it leaves your browser.

Closing

The printed run of show is not the enemy. It was the best tool available for a long time, and it is still better than nothing, which is the other common option.

But the printout's whole problem is the thing it cannot do, which is change. Events change constantly, from the morning briefing to the last encore. A document that froze at 9am is always going to lose to a screen that is still listening.

The duty manager at 3:50pm does not need a better printout. They need the page in their hand to be telling the truth, which mostly means they need it connected to everything that decided what the truth is.

Chris Founder, 1pm.app