Executive Assistants · Intermediate
Write a run-of-show for an offsite or event
Two days, twenty-four people, a venue ninety minutes from the office, a guest speaker arriving by train, and an outdoor activity in April. The plan is clear in your head. The run-of-show is where you discover that the coach arrives at 09:00 for a 09:00 start and the speaker's train gets in after her slot begins. This guide finds those gaps on paper, a week early.
What AI is for here, and what it isn't
A run-of-show is the event plan turned into a timetable everyone can follow: what happens, when, where, and who makes it happen. Most of the work is already done in your head. Writing it down is where the gaps appear: the ten minutes it takes to walk to the breakout rooms, the coach that can't arrive before registration, the speaker who needs a microphone check.
AI is good at the writing down and at checking the arithmetic. Give it the plan, and it will draft the run-of-show, add up every start time and duration, point out where people have to be in two places at once, and draft the contact sheet and contingency notes. It's patient about re-running the whole schedule when one thing moves.
It doesn't know your vendors, your budget, or how long your executive actually talks when they say "five minutes". It can't negotiate with the venue or make the calls on the day. Those are yours.
Write the plan down roughly
Write the plan as it is in your head, in any order. Don't tidy it. Include:
- Agenda items with rough durations and who leads them.
- Places: each room or location, and how long it takes to get between them on foot.
- Arrivals and departures: coaches, trains, flights, cars, with times and journey lengths.
- Venue facts: access times, when rooms are free, check-in and check-out times, catering times.
- Vendors: who they are, what they do, when they arrive, and who their contact is.
- What could go wrong: weather, late speakers, technical failures. Anything you've been worrying about.
Draft the run-of-show and find the gaps
Turn this event plan into a run-of-show, then check it for timing
problems. Don't change the plan; flag problems for me to decide.
EVENT: [name, dates, number of people]
PLAN: [paste rough plan]
LOCATIONS AND WALKING TIMES: [list]
VENUE FACTS: [access, room availability, catering, check-in]
ARRIVALS AND DEPARTURES: [list with journey times]
PART 1: RUN-OF-SHOW
A table per day with: start, end, duration, item, location, owner,
cues and AV needs, notes. End time = start + duration.
PART 2: TIMING CHECK
List every problem you find, labelled:
- CONFLICT: something can't happen as planned (people in two places,
an arrival after the start, a room not available).
- TIGHT: works only if nothing runs late (less than [n] minutes
between items in different locations, no time for setup).
- MISSING: something the plan implies but doesn't include (setup,
sound checks, luggage storage, transitions, breaks longer than
[n] hours apart).
Give the times and the reason for each.
The timing check is the point of the exercise. A run-of-show with no problems flagged on the first draft is unlikely; if the list is empty, ask again with the walking times and arrival details spelled out.
Fix, then add the contacts and contingencies
Decide how to fix each problem. These are your calls, often with a vendor or your executive. Give the AI the decisions and ask for the revised run-of-show, then the supporting documents.
From the revised run-of-show, draft:
1. CONTACT SHEET: a table of every role with a responsibility on the
day (venue, catering, AV, transport, speakers, our team), with
placeholders for name and mobile number. Group by who to call for
what. I'll add the names and numbers myself.
2. CONTINGENCY NOTES: for each risk below, the trigger (how we'll
know), the decision-maker, and the plan B, in three lines each.
RISKS: [weather for outdoor items, late speaker, AV failure,
transport delay, illness or injury, plus your own]
3. CUE SHEET for [name]: only the items they're responsible for,
with times and locations.
Fill in names and numbers yourself, from your own records. For medical emergencies, confirm the venue's first-aid arrangements and the nearest emergency department with the venue directly; don't rely on an AI tool for either.
Walk it through
Read the run-of-show aloud with one other person, ideally someone who will be there on the day, and follow one attendee through it from leaving home to getting back. Anything that makes either of you hesitate is a gap.
Then send it out in versions: the full run-of-show for your team and the venue, cue sheets for presenters, and a simple agenda for attendees.
Worked example: the leadership offsite
Fictional example. Sam is organizing a two-day leadership offsite for 24 people at a country hotel 90 minutes by coach from the office. Day 1 of the rough plan:
- Coach leaves the office 07:30. Registration and coffee from 08:45; opening session 09:00–10:30 in the Oak Room.
- Guest speaker 10:45–11:45. She's coming by train, arriving 10:42 at a station 20 minutes' drive from the hotel.
- Strategy discussion 11:45–12:30, led by Elena.
- Lunch 12:30–13:15 on the terrace. Breakouts 13:15–15:00 in the barn, a 10-minute walk away.
- Team activity outdoors 17:00–18:30. Coach to the restaurant 19:15.
The timing check comes back with five problems:
- CONFLICT: the coach arrives about 09:00, after registration starts and exactly when the opening begins.
- CONFLICT: the speaker can't reach the hotel before about 11:05 by train and taxi, twenty minutes after her slot begins, with no time for a microphone check.
- TIGHT: breakouts start at 13:15, but the barn is a 10-minute walk from the terrace.
- MISSING: luggage storage. Attendees arrive with overnight bags at 09:00, but rooms aren't ready until 15:00.
- MISSING: a wet-weather plan for the outdoor activity.
Sam's decisions: the coach leaves at 07:00; the strategy discussion moves to 10:45–11:45 and the speaker takes 11:45–12:45, which gives her forty minutes to set up; lunch moves to 12:45–13:30; breakouts run 13:40–15:15, with the walk built in; the venue will store bags in the conference office; and the activity has an indoor alternative in the barn if it rains.
The revised run-of-show goes to the venue the same day. On the day, the speaker's train is twelve minutes late. It doesn't matter.
The run-of-show format
[Event name] — Run-of-show v[number], [date]
Event lead: [name, mobile] Venue contact: [name, mobile]
DAY [n], [date]
Start | End | Item | Location | Owner | Cues and AV | Notes
07:00 | 08:30 | Coach to venue | Office → hotel | [name] | | Bags stored on arrival
...
TIMING CHECK
[Problem] — [decision] — [who decided], [date]
CONTINGENCIES
[Risk]: trigger [ ], decides [ ], plan B [ ]
CONTACTS
See contact sheet v[number] (names and numbers added by hand)
Personal data (dietary, access, medical): sent to [vendor] on [date]
What stays with you: the vendors, the budget, and the calls on the day.