Why a run of show was never a spreadsheet job

Most run of shows start life in a spreadsheet. It makes sense. You have rows, you have a time column, you have a thing that happens at that time, and a spreadsheet is right there. So you open one, you type "08:30 Doors", you drag the corner of the cell down, and for about twenty minutes it feels like the right tool.

Then the client moves the keynote fifteen minutes later.

Now the keynote is at 09:15 instead of 09:00. Which means the panel after it moves. Which means the coffee break moves. Which means the breakout sessions move, the lunch service moves, the afternoon moves, and the gala turnover that was tight to begin with is now fifteen minutes tighter. You have a column of forty start times and every one of them after row nine is now wrong.

If you were clever, you wrote a formula. Start plus duration equals the next start. If you were clever, that formula worked right up until the moment someone, possibly you, hard-typed a value over the top of it because the kitchen needed an extra ten minutes and the formula was fighting you. Now half the column is live and half is hard-coded and you cannot tell which by looking. The spreadsheet has quietly stopped doing math and started lying, and it will not tell you where.

This is the part nobody warns you about. A spreadsheet is a brilliant tool for numbers that sit still. A run of show is a list of numbers that move, constantly, right up until the doors open. Those are different jobs.

The math should follow the change, not the other way around

The core problem with a spreadsheet ROS is that the schedule is the thing that changes, and the spreadsheet treats the schedule as data you maintain by hand.

In 1pm you do not enter end times. You enter a start, a duration, and a title. The end is calculated, always, because an end time you typed by hand is just another number waiting to go stale. When you change a duration, every following item on that day shifts to match. No formula to protect, no column to drag, no hunting for the one cell where the chain broke.

It sounds small. It is the whole thing. The difference between a document you maintain and a document that maintains itself is the difference between a run of show you trust at 4pm and one you stopped trusting at lunchtime.

When something runs late, push it (and everything behind it)

Here is the move a spreadsheet cannot make.

Dinner is running twenty minutes long. On paper, that means the speeches, the band, the cake, and the carriages are all now twenty minutes wrong, and the fix is mental arithmetic performed by a tired person under pressure. In a spreadsheet it is worse, because you have to go and re-type each one, or trust a formula you can no longer see.

In 1pm, when an item starts after the one before it has technically ended, the row offers you a button. Push it, and that single item snaps to start exactly when the previous one finishes. Or push all, and that item plus every later item that day moves forward by the same amount, keeping every gap between them intact. The eight-minute breather you deliberately left before the keynote is still eight minutes after you push. You are not re-spacing the day, you are sliding it.

And because the most common thing a planner does ten seconds after a big change is panic, push all leaves you an undo. One click puts every moved item back where it was. The spreadsheet's version of undo is Ctrl+Z forty times and a prayer.

Reordering should not mean re-typing

Events get re-sequenced. The welcome drinks move before the speeches, the awards swap with the entertainment, the AV demo jumps ahead of the panel. In a spreadsheet, reordering rows means cut, insert, paste, and then fixing every time underneath because the times do not travel with the row in any way that helps you.

In 1pm you grab the handle on the left of a row and drag it where it goes. The times resequence around it automatically. Drop the awards earlier in the night and everything flows to fit. You moved the work, not the clock.

It also knows the difference between a sequence and a stack. Which brings me to the thing spreadsheets are worst at.

Two things at the same time is normal, not an error

A spreadsheet is a ladder. One row, then the next row, then the next. It has no real concept of two things happening at once, so when your 09:00 has three breakout sessions running in parallel, you either fake it with three rows that all say 09:00 and hope nobody reads it as a sequence, or you cram them into one cell and lose the detail.

1pm treats concurrent items as a first-class idea. Items that share a start time are grouped visually, so three things at 09:00 read as three things at 09:00, not as a 27-minute cascade. When you drag within that group, they stay together at the same time instead of being helpfully re-spaced into a queue. Parallel work looks parallel. That alone makes a complex conference ROS readable in a way a spreadsheet never manages.

The run of show should know who is on each item

This is the line a spreadsheet cannot cross, because a spreadsheet does not know your people.

In 1pm every item has a Responsible field, and it is wired to your actual contacts. Start typing and it filters by name as you go, so assigning the AV lead to the keynote is two keystrokes, not a copy-paste from another tab. Filter the whole timeline down to one supplier and something useful happens: every new row you add inherits that supplier automatically. Drill into "Catering", add five items, all five come out tagged to catering. The filter becomes a work area, not just a view.

And once the run of show knows who is on what, it can catch the mistake a spreadsheet physically cannot see. If you put the same person in two places at once, the row flags it. Same crew member, overlapping times, a warning appears, before the day rather than during it. It is smart enough to leave back-to-back items alone (those are fine) and to leave genuine parallel sessions alone (those are deliberate). It only shouts when one human is booked to be in two places, which is the exact error a column of times will never notice.

Stop re-typing the same room name three different ways

Small one, but it compounds. In a spreadsheet, the location column slowly fills with "Ballroom", "ballroom", "Main Ballroom", and "Balroom", and by the end of the day a crew member filtering on their phone for the room they are in finds three of the four because the fourth had a typo.

The Where field in 1pm autocompletes against the locations you have already used on that event. Type "ball" and it offers Ballroom, the exact string you used last time, so the room is spelled one way across forty items. It is the difference between a list you can filter and a list you have to read.

And yes, you can bring the spreadsheet you already have

None of this means the work you have already done is wasted. If your ROS already lives in a sheet, there is a paste-in. Copy the rows, paste them in, and 1pm parses the date, start, duration, and title and drops them into the timeline, resequenced into order. You are not retyping a day's work to switch tools. You are importing it once and never reaching for the spreadsheet again.

A quick note about words

Run of show, ROS, run sheet, "the timeline", the running order: same document, different rooms. Whatever your crew already calls it, the point stands. The thing you are building is a list of times that will not sit still, and the tool you build it in should expect that.

Closing

The spreadsheet was never the enemy. It is genuinely good at what it is for, and for a long time it was the best option in the room. But it was built to hold numbers that stay put, and a run of show is the opposite of that. It is a living estimate that gets corrected forty times between the morning brief and the last encore.

When the client moves the keynote fifteen minutes, you should be able to change one number and watch the rest of the day rearrange itself, correctly, in front of you. Not protect a formula. Not re-drag a column. Not wonder which copy the band has.

That is not a spreadsheet feature. It is a different tool, built for a schedule that moves.

Chris Founder, 1pm.app