A miniature burgundy stage with an ochre curtain and a pale-blue cue strip passing ivory blocks on a navy base.
Original AI-generated editorial illustration; not a real account, product sale or completed job. View full-size image.

An event run sheet tells the delivery team what happens next, who gives the cue and what must be ready before a transition begins. Build it around arrivals, changes of activity and clearing the room. Include a fallback for delays, then test the sequence with the people responsible for carrying it out.

The example below is an invented neighbourhood history evening. It is a planning exercise, not a report of a real event or a claim about attendance. Venue permissions, staffing and safety arrangements must be confirmed for the actual event; this proposed document cannot supply those decisions.

1. Define the part of the event you control

Start with the organiser's purpose and the practical boundaries of the assignment. In the fictional evening, the room opens for arrivals, a host introduces a speaker, a discussion follows, and the team clears the space. The planner is preparing the running order, not deciding building capacity or approving emergency arrangements.

Identify the person who can authorise a change on the day. A speaker, venue contact and volunteer may each have useful information, but conflicting instructions need one agreed decision route. Record an alternative contact if the main organiser is unavailable.

Keep the run sheet separate from the public invitation. An invitation tells a visitor what to expect. The team needs additional information about handovers and preparation. For collecting the initial scope and access arrangements, use the client onboarding handover guide.

2. Write transitions as actions with an owner

Use one row for an action that someone can start or confirm. Include the planned time or relative position, the action, its owner and the condition that permits it to begin. Avoid a wide table that becomes unreadable on a phone; a compact action card can hold the detail under each cue.

A practice transition card could say:

  • Cue: move from arrivals to the host's welcome.
  • Ready condition: the organiser confirms the room is ready and the speaker can begin.
  • Owner: the host gives the welcome; the door volunteer follows the agreed late-arrival instruction.
  • Delay response: the organiser decides whether to extend arrivals or shorten a later optional segment.

These are invented roles, not a tested staffing plan. The important part is making the dependency visible. Writing “speaker begins” without a cue owner leaves everyone waiting for someone else to make the decision.

3. Put access needs into the running order

W3C's guidance on accessible events recommends providing accessible materials in advance and in adaptable formats. It also covers document structure and alternatives for visual information. Applying that guidance takes preparation; it is not an accessibility certification for a venue or event.

Ask the organiser how access requirements will be gathered and handled appropriately. Put agreed preparation tasks into the run sheet, such as making the approved materials available before a presentation. Don't reduce access planning to a note saying “check on arrival” when the task requires work beforehand.

Keep personal details out of the general team sheet. The team needs the instruction relevant to their role, with a route to the responsible organiser for questions. Confirm the actual arrangement rather than assuming that a generic planning template meets every attendee's needs.

4. Decide what happens when the timing changes

A run sheet needs a decision rule for delay. List which segments have a firm dependency and which can change with the organiser's approval. Don't automatically remove a break, rush a room change or extend beyond the venue's agreed access period to recover lost time.

In the fictional evening, suppose the speaker hasn't arrived when the host is ready to begin. The sheet should direct the host to the organiser, who chooses an approved fallback. It should not ask a volunteer to invent a replacement presentation or announce an arrival time nobody has confirmed.

Use a simple change note: what changed, who approved it and which cue is affected. Update the team through the agreed channel. The project change log guide explains how to preserve the reason and authority behind a change without confusing a suggestion with a decision.

5. Describe visual cues in words

A coloured mark on a room sketch may mean something to its creator and nothing to the next volunteer. W3C's guidance on complex images explains that a complex visual may need a short identification and a longer description of its essential information. Use that principle when a diagram carries instructions the team must understand.

For the practice room sketch, write a plain-language explanation of the sequence shown by the arrows. Identify the cue by name instead of relying only on a colour. Check the explanation with the organiser and venue contact; a drawn route is not evidence that the route is suitable or authorised.

6. Rehearse the handovers rather than reading silently

Walk through the running order with the role owners. Ask each person what information they receive, what they do and whom they notify next. A missing cue is easier to find when someone has to describe the action in their own words.

Try a late-arrival scenario and a delayed-start scenario using the organiser's approved options. Record unanswered questions instead of improvising around them. The rehearsal is a document check, not proof that every live condition has been covered.

Check the version the team will carry. A revised schedule in the planner's folder won't help someone using an earlier printout. Mark the current version and withdraw superseded team copies through the agreed process. The meeting coordination guide covers invitations and scheduling that happen before this delivery stage.

7. Close the room and the record

Include the final handover: who confirms the agreed clearing tasks, who returns borrowed items and who tells the organiser that the team's work is complete. Leave venue-specific requirements to the responsible venue representative. Don't imply that a checked box proves a room inspection has been performed when nobody with that responsibility was present.

After the fictional exercise, ask another person to use the sheet to explain the arrival-to-welcome transition. They should find the owner, ready condition and delay decision route without guessing. Revise the sheet around whatever they couldn't locate. For an activity-specific preparation pack, see the separate craft workshop guide.