LEF MARKETING / INSIGHTS

How detailed should a corporate event run sheet be?

Willem van Vugt • 28 Oct 2026

A corporate event run sheet should be detailed enough that any team member could pick it up and run the event without needing to ask questions. For most B2B tech events, that means timing intervals of 15 minutes or less during active programme periods, named owners for every task, and enough context that a last-minute substitute understands what needs to happen and why.

The right level of detail depends on event complexity, team size, and how many external suppliers are involved. A 60-person executive roundtable needs a different run sheet than a 2,000-person partner conference. Below, the most common questions about corporate event run sheets are answered directly.

What sections should every corporate event run sheet include?

Every corporate event run sheet should include a timeline of activities with named owners, supplier and venue contact details, AV and technical cues, speaker and session logistics, catering timings, and contingency notes. These core sections ensure every team member and supplier knows what is happening, when, and who is responsible.

In practice, a well-structured run sheet for a B2B tech event typically covers:

Event overview: Date, venue, key contacts, and a brief summary of the day
Pre-event setup schedule: Venue access times, AV checks, registration desk setup, signage placement
Programme timeline: Every session, break, and transition with start and end times
Speaker logistics: Arrival times, briefing slots, presentation handover procedures
Supplier cue sheet: Catering service times, AV operator cues, security handovers
Contact directory: Mobile numbers for every key person on site, including the venue coordinator and AV lead
Contingency notes: What happens if a speaker is late, a session runs long, or a technical issue occurs

For large-scale events with multiple breakout rooms or exhibition floors, each zone may need its own sub-schedule within the master run sheet.

How far in advance should a run sheet be finalised?

A corporate event run sheet should be finalised at least five to seven working days before the event. This allows enough time to share it with all suppliers and team members, incorporate their feedback, and issue a final confirmed version before anyone travels to the venue.

A working draft should exist much earlier. For a large conference or trade show, the run sheet framework is often built six to eight weeks out, with sessions, speakers, and supplier timings added progressively as they are confirmed. The document evolves through several versions before reaching its final state.

The key discipline is locking the run sheet at least 48 hours before the event day. Changes after that point should be tracked in a separate amendments log, not edited directly into the master document, to avoid confusion on site.

Who needs a copy of the event run sheet?

Everyone with an operational role on the day needs a copy of the event run sheet. This includes the event manager, all onsite team members, AV and production crew, catering manager, venue coordinator, security lead, and any agency or supplier with timed responsibilities. Speakers typically receive a simplified version covering their own session logistics.

Sharing a 30-page master document with every supplier creates noise. The practical approach is to issue role-specific extracts: the AV team receives the technical cue sheet, catering receives the service timings, and registration staff receive the arrival and check-in schedule. The full master run sheet stays with the event manager and deputy.

For internal stakeholders such as marketing directors or sales leads attending the event, a clean event programme is more appropriate than the operational run sheet itself.

How granular should the timing intervals be on a run sheet?

Timing intervals on a corporate event run sheet should be no longer than 15 minutes during active programme periods, and as short as 2 to 5 minutes for technical transitions, speaker changeovers, or AV cues. The more complex the transition, the more granular the timing needs to be.

A general rule of thumb: if something can go wrong in that window, it deserves its own line on the run sheet. A keynote changeover that involves a presenter clicker handoff, a video playback, and a stage lighting change is not a single 5-minute transition. It is three separate cues that each need a named owner and a precise time.

During lower-intensity periods such as networking breaks or lunch, 15 to 30-minute intervals are usually sufficient. The level of granularity should reflect operational risk, not just personal preference for neat schedules.

What’s the difference between a run sheet and an event programme?

A run sheet is an internal operational document used by the event team and suppliers to manage every logistical detail of the day. An event programme is a guest-facing document that outlines the agenda, speakers, and session descriptions. They cover the same time period but serve entirely different audiences and purposes.

The event programme tells attendees what to expect and when. The run sheet tells the team what to do and when. A programme might list “Keynote: 09:30” as a single line. The corresponding run sheet entry covers the speaker arriving backstage at 09:10, the AV check at 09:20, the introduction by the MC at 09:28, the slide advance handover at 09:29, and the Q&A moderator moving to position at 09:55.

Confusing the two creates problems in both directions. A run sheet that reads like a programme leaves the team without the operational detail they need. A programme that reads like a run sheet overwhelms and confuses attendees.

How should a run sheet handle unexpected changes on the day?

A run sheet should include a built-in contingency buffer and a clear escalation process so that unexpected changes can be absorbed without derailing the entire schedule. The event manager should be the single point of decision-making for any deviation from the plan, with pre-agreed fallback options already documented in the run sheet itself.

Practical ways to build resilience into a run sheet include:

Buffer time: Build 5 to 10 minutes of flex into session transitions, particularly before keynotes or panel discussions
Contingency notes per section: Document what happens if a speaker is late, a session overruns, or a technical failure occurs
Version control: If changes are made on the day, issue a timestamped amendment to all team leads immediately
Named decision-maker: Every run sheet should state clearly who has authority to make real-time changes and how team members should communicate issues

The goal is not to plan for every possible scenario but to ensure the team has enough structure to make fast, confident decisions when things do not go to plan. A run sheet that only works when everything goes perfectly is not a run sheet. It is a wish list.

How LEF Marketing and Events supports your event execution

LEF marketing & events is a full-service event management agency specialising exclusively in B2B tech and IT events. When it comes to operational documents like run sheets, the team does not just fill in a template. Every run sheet is built around the specific complexity of your event, your venue, your suppliers, and your programme.

Here is what working with LEF on event execution looks like in practice:

One point of contact who owns the master run sheet and coordinates every supplier and team member
Complete logistical support from pre-event planning through to post-event reporting, including run sheet creation and version management
Experienced onsite teams who know how to manage real-time changes without disrupting the attendee experience
Transparent project management so your internal stakeholders always know where things stand
Coverage for events from 50 to 10,000 attendees, across conferences, trade shows, partner events, and executive meetings

If you are planning a B2B tech event and want a team that handles every operational detail, get in touch with LEF or explore what the team does to find out how they can support your next event.

LET'S MAKE IT HAPPEN