Event Planning

How to Write an Event Run-of-Show That Your Team Will Actually Follow

Aakshat Hariharan · · 8 min read

A run-of-show that lives in someone's email is already dead. Here's how to build one your entire team can access, update, and execute in real time.

What a Run-of-Show Actually Is

A run-of-show (ROS) is the minute-by-minute operational document that drives your event from load-in to load-out. It's not the agenda guests see. It's the internal bible your AV team, catering staff, emcee, and security all work from simultaneously.

Most events fail not because of bad ideas but because of bad coordination between people who are each holding a different version of the plan.

The Problem With Traditional ROS Documents

The classic ROS is a spreadsheet attached to an email sent at 11 PM the night before. By morning it has three versions, two people haven't seen it, and the AV team is working from the one from two weeks ago.

The fix isn't a better spreadsheet. It's a shared live workspace.

The Structure of a Good Run-of-Show

Every ROS needs exactly five columns:

  • Time — specific, not ranges. "7:34 PM" not "7:30–7:45 PM"
  • Duration — how long this item runs
  • Action — what happens (precise verb: "Emcee walks on stage", not "intro segment")
  • Owner — one named person responsible
  • Cue — what triggers the next item

Step 1: Work Backwards From the Hard Stop

Every event has a hard stop — venue curfew, last shuttle, broadcast window. Build your ROS backwards from that time. Everything else is negotiable. The hard stop is not.

Step 2: Build Buffer Into Every Transition

Transitions always run long. If you think it takes 3 minutes to move the keynote speaker from the green room to the stage, plan for 6. Every single time.

A 45-minute keynote that starts 8 minutes late is an embarrassment. A 45-minute keynote with a 6-minute transition buffer that starts 1 minute early is a triumph.

Step 3: Put It Somewhere Everyone Can See

Your ROS does nothing if it's in your inbox. Upload it to your PlanIt event's Files section and post the link in the event chat. Everyone — from the caterer to the AV tech — is in the same chat. No version confusion possible.

Step 4: Assign a Single ROS Owner for the Day

One person calls the cues. Not two. Not "whoever is near the stage." One person with a headset and the authority to say "we're moving on."

The run-of-show isn't a document. It's a communication system. Build it that way.