Run-of-Show, Staffing, and Day-of Coordination

What Is a Run-of-Show?

A run-of-show (ROS) document is the single most important operational tool an event coordinator carries on event day. It lists every planned activity in chronological order, typically broken into 15-minute intervals, and tells each team member exactly what should be happening, where, and who is responsible. Think of it as a flight plan: pilots do not improvise takeoff sequences, and neither should event coordinators improvise speaker transitions or meal service timing.

A well-built ROS contains at minimum these columns for every time block:

• Time – start time for the interval (use 24-hour or consistent AM/PM format throughout)
• Location – ballroom, breakout room A, foyer, loading dock, etc.
• Activity – the specific action occurring (e.g., "General session keynote begins")
• Responsible staff – the named person or role accountable for that action
• AV cue – any lighting change, slide advance, microphone switch, or video roll
• Catering action – coffee replenishment, buffet open, plates cleared, bar service begins

Every row must be populated. A blank cell is an unanswered question waiting to become a problem on event day.

Building the Staffing Grid

A staffing grid translates the ROS into a people plan. For a full-day conference with multiple event spaces, you need to know at a glance who is working, where, from when to when, and how to reach them.

A standard staffing grid includes:

• Role title – Registration Lead, Room Monitor, AV Liaison, Catering Runner, etc.
• Shift start and end times – include setup time before doors open and breakdown after the last guest leaves
• Break schedule – staff must receive legally required breaks according to applicable state labor rules; build breaks into the grid so coverage is never dropped
• Radio channel assignment – assign a dedicated channel per zone (e.g., Channel 1 = main stage, Channel 2 = breakout rooms, Channel 3 = back-of-house). This prevents cross-talk and keeps communications clear during high-pressure moments

For eight staff across three spaces, map coverage so that no space is ever unstaffed during open hours. Stagger breaks so at least one qualified person remains in each zone at all times.

Day-of Coordination Principles

Even the best ROS will be tested by real events. Experienced coordinators expect disruption and build decision-making habits before disruption arrives.

Maintain situational awareness. Walk the venue before doors open. Confirm AV is tested, catering is staged, signage is posted, and every staff member has checked in and received their radio.

Communicate through the chain of command. When a problem surfaces, the staff member who discovers it reports to their direct supervisor on the assigned radio channel. The lead coordinator makes the call. Avoid multiple people broadcasting the same problem on multiple channels simultaneously.

Document in real time. Keep an incident log throughout the day. Record the time, the issue, the corrective action taken, and who authorized it. This log protects the organization legally if a dispute arises later, and it feeds your post-event report.

Common day-of scenarios and responses:

• Late speaker: Notify the AV team to hold the title slide. Extend the networking break or shift Q&A earlier. Update the ROS timestamp in your working copy and notify the emcee.
• Wi-Fi outage: Switch presenter to offline slide deck if available. Notify the venue IT contact immediately. Communicate status to attendees calmly and with a realistic time estimate.
• Catering delay: Alert the program team to extend the break or add a short filler segment. Communicate with the catering manager for an updated delivery time. Never announce a delay without an estimated resolution.

Safety Considerations

Day-of coordination involves physical movement through active event spaces. Keep these safety habits in place:

• Slip and trip hazards are common during catering service and AV cable runs. Ensure all cables crossing walkways are taped down or covered with cable ramps before attendee arrival.
• Emergency egress must never be blocked by staging, décor, or equipment. Know the location of all fire exits in every event space and confirm they are clear during your pre-event walk.
• Communication during emergencies follows a separate protocol from routine coordination. Know your venue's emergency action plan and your role in it. Do not use event radio channels for emergency dispatch — use venue phones or 911 directly.
• Staff fatigue is a real risk on long event days. Enforce break schedules. A tired staff member makes communication errors that ripple through the entire event.

Bringing It Together

The ROS and staffing grid are not static documents — they are living tools you update as the day unfolds. Print a working copy and mark changes in real time. At the end of the event, your annotated ROS becomes the foundation of your post-event debrief. Strong day-of coordination is the skill that separates a polished event professional from someone who simply made a plan.