Runsheet

Guide

Corporate Event Run of Show: Anatomy, Example, and How to Run It Live

Corporate general sessions carry the biggest crews and the least room for a late finish. Here's what makes their run of show different, a fully populated example, and how to run it live across a room full of departments.

Last updated July 22, 2026

What's different about a corporate event run of show

A corporate event run of show carries more moving parts than a single-speaker show or a simple panel discussion. A general session usually stacks a keynote, a panel, an awards moment, and breakout tracks into one day, each with its own AV requirements, and each handed to a different owner. On top of that, corporate shows almost always run against a real constraint: a CEO or executive with a flight to catch, a room booked by the hour, a livestream with a fixed end card. The rundown has to hold multiple departments (AV, stage management, front of house, breakout track leads) to the same clock, and it has to protect a hard end time that isn't negotiable.

That combination, more segment types, more departments, and a strict finish, is what separates a corporate event run of show from a generic one. The columns are the same (start, duration, item, owner, notes), but the crew reading it is bigger, and more of those rows have a cue attached that another department is waiting on.

The anatomy of a corporate event rundown

These segment types recur across most corporate general sessions:

  • Registration / walk-in. Badge pickup, sponsor booths, house music, usually the least strict timing in the whole day but still needs an owner.
  • Opening video or cold open.A pre-produced piece that sets the tone before anyone's on stage, tightly cued to house lights and audio.
  • Executive welcome. CEO or host walk-on, mic handoff, usually a fixed short slot.
  • Keynote. The anchor segment, longest single block, usually a hard stop because everything after it depends on it ending on time.
  • Panel or fireside chat.Multiple mics, a moderator, and a Q&A runner if the audience gets to ask questions.
  • Breakout sessions. The agenda splits into concurrent tracks, each effectively its own mini rundown running in parallel to the main stage.
  • Awards or recognition moment. Needs its own cue list, walk-up spotlight, name-card teleprompter script, trophy handoff.
  • Sponsor moments. Logo reveals, thank-yous, sometimes a sponsor speaker slot, small on paper but easy to forget under pressure.
  • Breaks / buffer blocks. Deliberate slack the rest of the day can borrow from when something upstream runs long.
  • Changeovers. Stage resets between segment types, chairs to podium, podium to panel, easy to underestimate and a common source of drift.
  • Close. Credits, thank-yous, and the hard-out constraint the whole day is built backward from.

Example: a corporate general session run of show

StartDurItemDept/OwnerNotes/Cues
7:30 AM0:30Registration / badge pickupFront of houseBadge printers live, coffee station open, sponsor banners lit
8:00 AM0:20Doors open / walk-inAV + FOHWalk-in playlist, house lights 70%, agenda on side screens
8:20 AM0:05Countdown to startStage manager60-sec countdown on confidence monitor, house lights begin fade
8:25 AM0:03Opening videoAV / VideoPlay cue from video server, house lights to 10%, no mic needed
8:28 AM0:07CEO walk-on + welcomeHost / CEOWireless handheld + lav backup, walk-on music cut on cue
8:35 AM0:25CEO keynoteAVConfidence monitor + teleprompter, lav mic, hard stop into video
9:00 AM0:05Sponsor video packageAV / VideoPre-roll from video server, house lights stay down
9:05 AM0:35Executive panel: state of the businessAV + Moderator4 lavs + 1 handheld for Q&A runner, moderator holds timer card
9:40 AM0:15Networking breakFront of houseBuffer block, absorb overrun here, sponsor booths open
9:55 AM0:05Changeover to breakoutsStage + AVReset main stage for awards backdrop, breakout rooms mic-check separately
10:00 AM0:45Breakout sessions (3 concurrent tracks)Track leadsEach room has its own runner + confidence timer, main stage dark
10:45 AM0:15Reconvene / reseatFront of houseWalk-in music resumes, house lights back to 70%
11:00 AM0:20Awards presentationAV + StageTrophy table preset, name-card teleprompter script, spotlight on walk-up
11:20 AM0:10Sponsor thank-you + closing remarksHostSponsor logos on screen, thank-you script on teleprompter
11:30 AM0:10Closing video + creditsAV / VideoPlay cue from video server, house lights fade up during credits
11:40 AM0:05Hard outAllRoom clear by 11:45, next vendor load-in at noon

Two rows are doing more work than the rest: the 9:40 networking break is the buffer the whole morning borrows from if the keynote or panel runs long, and the 11:40 hard out is the constraint everything above it is built backward from. Neither is filler.

Running it live across a multi-person crew

Corporate general sessions carry the biggest crews of any event type this guide covers: AV lead calling cues, a stage manager, front-of-house staff, a video operator, one runner per breakout track, sometimes a separate sponsor liaison. Every one of those people needs to know, in real time, whether the show is on schedule, running behind, or about to move to the next segment, and they can't all be crowded around the same laptop to see it.

That's the part a static document can't do. On paper, when the keynote runs 10 minutes over, the AV lead has to manually tell the stage manager, who tells front of house, who tells the breakout track leads, all while also doing their own job during a live show. In a run of show tool where start times are computed from durations, one edit reflows every following start time automatically, and separate control, crew, and stage screens all update to the same live state at once, no one has to relay the change by radio or by running across the room.

Deciding what to do about the slip, cut a segment, eat into the buffer, hold the hard out, is still the show caller's call, not the software's. How to call a show covers those decisions. The run of show template guide covers the columns this example builds on, and the software comparison covers what to run it in if a spreadsheet has already let you down once.

Runsheet is built for exactly this: build the rundown, then run it live with synced control, crew, and stage screens that reflow together when the schedule slips.

FAQ

What is a corporate event run of show?
A corporate event run of show is the minute-by-minute schedule a general session, conference, or company event runs on: every segment, its start time and duration, who owns it, and the AV/production cues attached to it. It's built for a crew to execute live, not just for attendees to read.
What should a conference run of show include?
At minimum: registration/walk-in, the opening (video or host welcome), each keynote or panel with mic and monitor cues, breakout sessions if the agenda splits, sponsor moments, buffer blocks between segments, and a hard-out time. Every row needs a dept/owner so no cue is nobody's job.
How detailed should AV cues be?
Detailed enough that whoever's on that cue doesn't have to ask a follow-up question live. Mic type and count, what triggers a video or lighting change, monitor/teleprompter notes, and whether a segment is a hard stop or has flex. Put cues in the notes column next to the segment they belong to, not in a separate cue sheet.
What software do corporate event producers use?
It ranges from spreadsheets to dedicated tools. RundownStudio and Lasso (formerly Shoflo) both market directly to corporate event teams; Overture is built specifically for producers running general sessions; OnTime is a free, self-hosted option teams run themselves. Most of these share the same core idea: computed start times that reflow when a segment runs long, plus synced views for the crew.
How do you keep a corporate show on time?
Build buffer blocks into the agenda on purpose, not by accident, give the show caller a hard-out everything works backward from, and make sure the person running the room can see the live schedule update the moment something slips, rather than finding out secondhand. The schedule has to reflow automatically or someone ends up retyping start times live while also doing their actual job.

Build the rundown. Run the show. Every screen in sync.

Runsheet is the hosted place to build a run of show and then run it live, no setup, share links for control, crew, and stage screens. Free for 1 rundown, 3 connected screens.

Start free

Runsheet is a hosted tool for building a run of show and then running it live: synced countdowns and current-item view on every screen, times reflow when the schedule slips.

More guides