How can I create a run-of-show for a small community event?

Make one shared timeline that answers four questions for every segment: When does it happen? What happens? Who owns it? What tells everyone to move to the next thing?

First, write down the venue access time, guest arrival time, program start, program end, and the time everyone must be out. Mark confirmed times separately from assumptions. Then fit the event between those fixed points. Work backward for setup and forward for cleanup rather than using the full venue window as program time.

For each row, name one lead who is accountable, even if several people help. Add prerequisites in plain language: for example, “welcome table ready after signs are placed.” Finally, add a transition cue, such as “host thanks the speaker and directs guests to refreshments.” That cue makes the handoff visible instead of relying on people to guess.

Here is a sample to adapt. The guest count and times below are illustrative assumptions, not confirmed event details. This version assumes venue access from 4:00 to 7:00, guest arrival at 5:00, and a program from 5:30 to 7:00. Adjust it to your actual booking and activities.

4:00–4:10 | Access and quick team check | Event lead | Confirm room access, identify exits and agreed room limits, and review the plan. 4:10–4:35 | Room setup | Setup lead | Arrange chairs and tables; dependency: room layout agreed with venue contact. 4:20–4:45 | Welcome table and signs | Welcome lead | Place sign-in materials and directional signs; dependency: entrance and table locations confirmed. 4:45–4:55 | Sound and program check | Host | Check the microphone if one is being used; confirm speaker order and pronunciation. 4:55–5:00 | Volunteer positions | Event lead | Each volunteer confirms their station; cue: lead gives a quick verbal “ready” check. 5:00–5:30 | Guest arrival | Welcome lead | Greet guests and direct them to seating; cue: host gives a two-minute warning at 5:28. 5:30–5:35 | Welcome and housekeeping | Host | Explain the program and practical room information; cue: introduce the first speaker. 5:35–6:05 | Main activity or speaker | Program lead | Keep time and give the host a discreet five-minute warning. 6:05–6:15 | Questions or discussion | Host | Take a few questions; cue: host thanks participants and announces the next segment. 6:15–6:35 | Community sharing or activity | Activity lead | Explain the activity before materials are handed out; cue: give a two-minute wrap-up notice. 6:35–6:45 | Closing remarks | Host | Thank contributors and explain what happens next, if anything. 6:45–7:00 | Guest departure and cleanup | Cleanup lead | Collect event materials and leave the room as agreed; dependency: guests have departed and volunteers know what must be packed.

If the venue requires everyone out at 7:00, confirm whether cleanup must finish earlier or whether access extends beyond that time. A timeline is useful only if it fits the actual access window.

For each task, write the prerequisite as something observable, not a vague phrase like “setup done.” For example: “Welcome lead can open the sign-in table once the table is in place and the directional sign is at the entrance.” The person doing the task should be able to tell whether that condition is met.

Use one owner per task and name helpers separately if needed. Then give the owner a way to flag a problem and a backup contact who can make a simple adjustment. A handoff should say both what is being handed over and when: “At 5:25, the welcome lead tells the host whether guests are seated and passes over any program notes.”

Before event day, walk through the sequence aloud with the volunteers. Ask each person to repeat their first task, who they receive information from, and what cue signals the next step. Resolve unclear ownership then, not while guests are waiting.

Agree in advance which parts can flex and who decides. Mark one or two optional elements that can be shortened or skipped without disrupting the main purpose. Avoid quietly pushing every later segment back; the venue end time and any promised closing time may be fixed.

For example, the event lead could decide that if the main activity starts more than five minutes late, the host shortens the discussion by one question and drops an optional announcement. That is a sample rule to confirm with your team, not a universal timing rule. Tell volunteers the cue—such as the event lead showing the host a note—and update the timeline if a change affects their tasks.

Keep a simple live copy with the event lead. When a change is made, say what changed, who needs to know, and whether the next cue or owner changes. The person running the event should not have to remember an unspoken adjustment.

A reusable row for your run-of-show is: “Time | Segment or task | Owner | Helpers | Dependency | Cue or handoff | Flexible?” Keep the shared version readable at a glance, and use actual names or role labels consistently. Before sharing it, check that every segment has an owner, every transition has a cue, and the timeline ends early enough to meet the real venue requirements.