The public agenda says that the first session starts at nine. It does not tell the sound operator when to open the microphone, the host who introduces the speaker, or the floor lead whether the doors should remain open during the introduction. An agenda tells guests what to expect. A run of show tells the crew how to deliver it.
For a small event, this can be one readable working document. Its value comes from the decisions inside it: the trigger for each transition, the person responsible, and the action to take when the planned sequence cannot proceed. A beautiful timetable with those decisions missing still leaves people improvising.
A hypothetical morning workshop
Imagine Cedar Hall, a fictional team preparing a community business workshop. Ana produces the event, Joel handles sound, and Rosa coordinates the room. Doors open at 8:30. The welcome begins at 9:00, followed by a demonstration at 9:10. These details are demonstration data, not a customer case study.
The speaker plans to arrive at 8:50, but Joel needs to check her microphone before guests enter. Rosa has a room reset scheduled for the same period. The public agenda looks reasonable; the production sequence does not. Ana needs to resolve the preparation window before sharing the final brief.
She moves the technical check earlier after confirming availability. Then she records a fallback: if the demonstration equipment is unavailable, the host opens with questions while Ana decides the next segment. The crew knows who makes that decision.
Connect the timeline to the work around it
Start with the crew’s sequence. Write each segment with its start, duration, location, owner, cue, and required material. Use a concrete cue such as “Rosa confirms the room is ready” when a clock time alone is insufficient. Include setup and teardown; guest arrival is rarely the crew’s first action.
Keep preparation actions separate. “Test the presentation file” is work due before the event. “Start the presentation after the host’s introduction” is an operating cue. Put preparation in assigned Tasks and the sequence in a project Note or Document. The team connects these deliberately through clear names and references.
Use Calendar for the event window. Record the date, location, and relevant participants there. Calendar supplies shared event context; a detailed production document remains useful for cues. Updating the document does not mean every calendar entry or external message changes automatically.
Asana’s run-of-show guidance identifies timing, owners, and transitions as core elements. Eventbrite’s planning checklist also calls for sharing the schedule before the event. Apply those general principles at the level your crew actually needs.
A run-of-show checklist
- Event name, venue, date, and local time zone.
- Working version, last revision, and document owner.
- Crew arrival, setup, and technical checks.
- Start, duration, and location for each segment.
- Named owner and clear cue for every transition.
- Required presentation, equipment, or room arrangement.
- Decision maker and fallback for a delayed segment.
- Breaks, room resets, and handovers.
- Teardown and return responsibilities.
- Where the crew will confirm receipt of a change.
Read the sequence aloud with the people operating it. At each transition, ask who gives the cue and who receives it. If two people wait for each other, resolve the decision in the document. If someone cannot attend the rehearsal, assign a person to brief them before their first responsibility.
Walk through the workshop in Attain OS
Open the workshop project and create a Note called “Workshop run of show — working version.” Add the sequence, Ana’s role, and the fallback decision. Store the presentation and venue plan in Documents, then identify those files in the note. Review access with each participant who needs the material.
Create Tasks for Joel’s sound check and Rosa’s room readiness confirmation, with owners and due dates. If you prepare a task draft from the note, review its wording and checklist before saving. A draft is a starting point; it does not certify that the event is ready.
Add the workshop’s time and location in Calendar. After rehearsal, Ana updates the run of show and records the revision near the top. She explicitly tells the crew where to find it and asks the transition owners to confirm their cues. External collaborators need the appropriate project access; the team should check that access before event morning.
During the event, record meaningful deviations without rewriting history to make the plan look perfect. Afterward, keep one short note about a confusing cue or missing preparation task. That gives the next producer a concrete improvement to make.
