Run-of-Show Template for Community Events: A Complete Planning Guide
Build a clear, reliable run of show for your next community event. This practical guide includes a reusable template, timing examples, role assignments, contingency planning, day-of checklists, and tips for coordinating registration, communications, check-in, and meaningful attendee networking.
- A run of show turns an event concept into an executable sequence.
- Although the terms are sometimes used interchangeably, an event agenda and a run of show serve different audiences.
- An event checklist confirms whether a task has been completed.
- The following run-of-show template for community events can be copied into Google Sheets, Microsoft Excel, Notion, Airtable, or a shared planning document.
- The strongest templates combine timing with clear ownership.
A run of show turns an event concept into an executable sequence. It shows not only when the welcome, main session, networking break, and closing remarks take place, but also what the delivery team must do before, during, and after each moment.
The following run-of-show template for community events can be copied into Google Sheets, Microsoft Excel, Notion, Airtable, or a shared planning document. Replace the placeholders with your actual times, owners, locations, and event-specific instructions.
The sample below shows how a two-hour community networking event might be managed from organizer arrival through the post-event debrief. It is not a universal schedule; the timing should be adjusted for venue access, audience size, accessibility needs, speaker requirements, and the complexity of the programme.
The schedule begins well before attendees arrive because event delivery depends on work that is invisible to participants. Venue access, equipment checks, volunteer coordination, speaker preparation, and registration testing all need protected time.
A reliable event run sheet template should be built around the event outcome and attendee journey, not just a list of programme items. Start with the result the event is intended to create, then work backward through every action required to deliver it.
Clear ownership prevents the event lead from becoming the default decision-maker for every task. A useful run sheet should show who leads each activity, who supports it, and who needs to be informed when the plan changes.
Title: "Run-of-Show Template for Community Events | MeetWho"
Description: "Use this run-of-show template for community events to plan timing, roles, check-in, speakers, networking, contingencies, and day-of execution."
Run-of-Show Template for Community Events: A Complete Planning Guide
Run-of-Show Template for Community Events, a well-structured event timeline gives your team one reliable source of truth for what happens, when it happens, who owns it, and how to respond when the schedule changes. The template below is designed for community meetups, workshops, panels, networking events, nonprofit gatherings, professional associations, founder communities, and other attendee-focused formats.
A community-event run of show is a minute-by-minute operational document that lists each event activity, its owner, location, required resources, attendee-facing cues, and contingency notes. Unlike a public agenda, it is an internal working plan used by organizers, volunteers, speakers, venue teams, and production staff to coordinate the live event.
What Is a Run of Show for a Community Event?
A run of show turns an event concept into an executable sequence. It shows not only when the welcome, main session, networking break, and closing remarks take place, but also what the delivery team must do before, during, and after each moment.
For a community event, that usually means mapping the complete attendee journey: registration, reminder communications, arrival, check-in, orientation, sessions, breaks, networking, closing, and follow-up. The document should also include backstage responsibilities such as room setup, speaker briefing, equipment checks, volunteer coordination, schedule cues, and fallback actions.
A useful community event run sheet should answer five questions for every important moment:
- What is happening?
- When does it begin and end?
- Who is responsible?
- What does the attendee experience?
- What happens if the plan changes?
The public agenda tells attendees what will happen; the run of show tells the team how it will happen.
Run of Show vs. Event Agenda
Although the terms are sometimes used interchangeably, an event agenda and a run of show serve different audiences.
| Document | Primary audience | Level of detail | Typical content | When it is used |
|---|---|---|---|---|
| Event agenda | Attendees | High-level | Session titles, speakers, breaks, start and end times | Before and during the event |
| Run of show | Organizers and delivery team | Detailed | Owners, cues, equipment, transitions, communications, contingencies | During preparation and live execution |
| Event checklist | Organizers and task owners | Task-based | Setup actions, confirmations, materials, approvals | Before, during, and after the event |
| Project plan | Core planning team | Broad and long-term | Deadlines, budgets, vendors, promotion, logistics | Throughout the planning cycle |
An agenda may say, “6:30 p.m.—Panel Discussion.” The run of show should go further by naming the moderator, confirming when speakers are seated, identifying who starts the presentation, specifying the closing cue, and noting what happens if the session runs late.
Run of Show vs. Event Checklist
An event checklist confirms whether a task has been completed. A run of show places actions in sequence and shows how they affect the live programme.
For example:
- Checklist item: Test presentation equipment.
- Run-of-show item: 5:15 p.m.—AV lead tests slides, microphones, walk-in music, and backup presentation file before the speaker briefing.
Both documents are useful, but they solve different problems. The checklist supports preparation. The run of show supports timing, coordination, and decision-making once the event is in motion.
Copyable Run-of-Show Template for Community Events
The following run-of-show template for community events can be copied into Google Sheets, Microsoft Excel, Notion, Airtable, or a shared planning document. Replace the placeholders with your actual times, owners, locations, and event-specific instructions.
| Time | Duration | Event moment | Attendee experience | Team action | Owner | Location | Equipment or asset | Communication cue | Contingency note | Status |
|---|---|---|---|---|---|---|---|---|---|---|
| [Time] | [Minutes] | Team arrival | No attendee activity | Open venue and confirm access | [Owner] | [Location] | Keys, access codes | Team check-in message | Contact venue backup | Not started |
| [Time] | [Minutes] | Venue walkthrough | No attendee activity | Inspect room, exits, signage, and accessibility | [Owner] | Entire venue | Floor plan | Report issues to event lead | Adjust room plan | Not started |
| [Time] | [Minutes] | Registration setup | No attendee activity | Prepare check-in desk and attendee materials | [Owner] | Entrance | Devices, badges, signage | Confirm desk is ready | Open secondary check-in point | Not started |
| [Time] | [Minutes] | Equipment check | No attendee activity | Test microphones, slides, sound, and internet | [Owner] | Main room | AV equipment, backup files | Send technical approval | Use backup device or offline file | Not started |
| [Time] | [Minutes] | Volunteer briefing | No attendee activity | Review roles, timing, contacts, and escalation process | [Owner] | Staff area | Printed or digital run sheet | Confirm role acceptance | Reassign uncovered tasks | Not started |
| [Time] | [Minutes] | Speaker briefing | Speakers prepare | Review timing, introductions, cues, and questions | [Owner] | Green room or stage | Speaker notes, water | Two-minute warning agreed | Adjust format if speaker is late | Not started |
| [Time] | [Minutes] | Doors open | Attendees arrive and check in | Welcome guests and monitor the queue | [Owner] | Entrance | Check-in devices, badges | Notify host when room is ready | Add queue support | Not started |
| [Time] | [Minutes] | Welcome | Attendees receive orientation | Start programme and explain housekeeping | [Owner] | Main room | Microphone, slides | AV starts welcome slide | Deliver without slides | Not started |
| [Time] | [Minutes] | Main session | Attendees join the core programme | Track time and support speakers | [Owner] | Main room | Slides, microphones | Show timing cues | Shorten Q&A if required | Not started |
| [Time] | [Minutes] | Networking segment | Attendees meet and exchange ideas | Explain format, prompts, and timing | [Owner] | Networking area | Prompt cards, signage | Announce halfway point | Use seated introductions | Not started |
| [Time] | [Minutes] | Closing remarks | Attendees hear next steps | Thank participants and share follow-up actions | [Owner] | Main room | Closing slide | Signal registration team | Send written follow-up if delayed | Not started |
| [Time] | [Minutes] | Breakdown and debrief | Attendees depart | Pack equipment and record lessons | [Owner] | Entire venue | Storage list, notes | Confirm venue handover | Schedule remote debrief | Not started |
Essential Run-of-Show Columns
The strongest templates combine timing with clear ownership. “Time” and “duration” define the schedule, while “event moment” names the activity in plain language.
“Attendee experience” describes what participants see or do. “Team action” records the work happening behind the scenes. “Owner” identifies the single person responsible for making that moment happen.
“Equipment or asset” prevents last-minute searches for files, devices, signs, or presentation materials. “Communication cue” shows what signal triggers the next action. “Contingency note” gives the team an immediate fallback rather than forcing organizers to improvise under pressure.
The “status” field is especially useful during setup. It allows the event lead to see which tasks are complete, delayed, blocked, or still awaiting confirmation.
Completed Run-of-Show Example for a Community Networking Event
The sample below shows how a two-hour community networking event might be managed from organizer arrival through the post-event debrief. It is not a universal schedule; the timing should be adjusted for venue access, audience size, accessibility needs, speaker requirements, and the complexity of the programme.
Sample Event Assumptions
This example is based on a fictional founder-and-operator meetup with:
- 80 registered attendees
- One event host
- Two guest speakers
- Four volunteers
- One venue contact
- QR-based attendee check-in
- A moderated discussion
- A structured networking segment
- Light refreshments
Example Run Sheet
| Time | Duration | Event moment | Attendee experience | Team action | Owner | Cue or dependency | Contingency |
|---|---|---|---|---|---|---|---|
| 4:30 p.m. | 15 min | Organizer arrival | No attendee activity | Access venue, confirm room booking, review exits and facilities | Event lead | Venue contact confirms access | Call venue backup contact |
| 4:45 p.m. | 25 min | Room setup | No attendee activity | Position chairs, tables, signage, refreshments, and networking area | Volunteer lead | Floor plan approved | Simplify room layout |
| 5:10 p.m. | 15 min | Registration setup | No attendee activity | Test QR check-in, prepare name badges, and review walk-in policy | Registration lead | Devices connected and charged | Use manual attendee list |
| 5:25 p.m. | 15 min | Technical check | No attendee activity | Test microphones, slides, music, internet, and backup files | AV lead | Speakers submit final slides | Use offline presentation copy |
| 5:40 p.m. | 10 min | Volunteer briefing | No attendee activity | Review roles, escalation process, accessibility support, and timing | Event lead | All volunteers present | Reassign uncovered duties |
| 5:50 p.m. | 10 min | Speaker briefing | Speakers prepare | Confirm introductions, timing cues, Q&A format, and closing question | Host | Both speakers present | Adjust order if one is delayed |
| 6:00 p.m. | 20 min | Doors open | Attendees check in, collect badges, and enter the room | Welcome guests, manage queue, monitor room capacity | Registration lead | Event lead confirms room ready | Open secondary check-in point |
| 6:20 p.m. | 10 min | Welcome | Attendees hear the event purpose and practical information | Introduce speakers, explain facilities, timing, and networking format | Host | Registration queue is clear | Start while late arrivals check in quietly |
| 6:30 p.m. | 35 min | Moderated discussion | Attendees listen and take part in the main programme | Track speaker time, manage slides, prepare audience microphones | Host | AV confirms microphones live | Move to host-led questions |
| 7:05 p.m. | 15 min | Audience Q&A | Attendees ask questions | Select questions, manage timing, close on a clear final response | Host | Five-minute warning at 7:15 | Reduce final questions |
| 7:20 p.m. | 30 min | Structured networking | Attendees meet people around shared goals and interests | Explain prompts, facilitate introductions, announce halfway point | Networking facilitator | Room reset completed | Use table-based introductions |
| 7:50 p.m. | 10 min | Closing remarks | Attendees hear next steps and follow-up information | Thank participants, mention resources, explain post-event follow-up | Event lead | Two-minute cue from timekeeper | Send missed details by email |
| 8:00 p.m. | 20 min | Informal departure | Attendees finish conversations and leave | Support final questions, monitor venue areas, begin light pack-down | Volunteer lead | Venue permits continued access | Move conversations to approved area |
| 8:20 p.m. | 20 min | Breakdown | No attendee activity | Pack materials, remove signage, check lost property, restore room | Volunteer lead | Attendees have departed | Prioritize venue-critical tasks |
| 8:40 p.m. | 10 min | Team debrief | No attendee activity | Record delays, issues, attendee feedback, and improvements | Event lead | Venue handover complete | Schedule an online debrief |
Why This Example Works
The schedule begins well before attendees arrive because event delivery depends on work that is invisible to participants. Venue access, equipment checks, volunteer coordination, speaker preparation, and registration testing all need protected time.
The example also separates public programme time from operational responsibility. “Doors open” is not simply a start time; it includes queue monitoring, attendee support, room-capacity checks, and a decision about whether the host can begin on schedule.
The networking segment has a defined purpose, owner, set of instructions, and closing cue. This makes it more useful than adding “networking” as an unstructured line between the panel and the final announcement.
How to Build a Community-Event Run of Show
A reliable event run sheet template should be built around the event outcome and attendee journey, not just a list of programme items. Start with the result the event is intended to create, then work backward through every action required to deliver it.
1. Define the Event Outcome
Write one primary outcome before adding times to the schedule. A community event may be designed to support peer learning, member onboarding, professional networking, volunteer recruitment, collaboration, or community retention.
Each major agenda item should contribute to that outcome. When an activity does not support the event goal, improve the attendee experience, or fulfil an operational requirement, reconsider whether it belongs in the programme.
2. Work Backward From Doors Open
Treat doors open as an operational deadline. Calculate how much time is needed for venue access, setup, registration preparation, accessibility checks, speaker arrival, technical rehearsal, and the team briefing.
Add dependencies while planning. The speaker briefing cannot finish until speakers arrive, registration cannot open until the check-in process is tested, and attendees should not enter the main room until the venue and event leads confirm it is ready.
3. Map the Attendee Journey
Document the experience from the first registration action through post-event follow-up. Include confirmation messages, reminders, arrival instructions, check-in, orientation, sessions, breaks, networking, closing, and any resources sent afterward.
MeetWho can support connected parts of this journey by allowing organizers to create an event page, collect registrations, approve applications, manage a waitlist, send announcements and reminders, and share online-event links with registered attendees. These functions support the event workflow, while the run of show remains the team’s live operational timeline.
4. Assign One Owner to Every Event Moment
Every row should have one directly responsible owner. Several people may provide support, but one person should know that the activity will not happen unless they initiate or confirm it.
Useful ownership roles include the event lead, host, registration lead, volunteer coordinator, speaker manager, venue contact, AV lead, accessibility contact, safety lead, and networking facilitator.
5. Add Cues, Dependencies, and Decision Points
A cue is the signal that causes the next action. It might be a timing card shown to a speaker, the end of walk-in music, a message confirming the registration queue is clear, or an AV signal that the next slide is ready.
Decision points should also be visible. For example, identify who decides whether to shorten Q&A, delay the welcome, move networking to another area, or switch to a backup presentation.
6. Build in Buffers and Recovery Time
Avoid scheduling every transition back-to-back. Speaker changes, room resets, audience movement, food service, and technical adjustments often need more time than expected.
Buffers make the schedule more resilient. They also give the event lead space to recover from a small delay without disrupting every later activity.
7. Add Contingency Actions
Critical moments should include a short fallback plan. Prepare for delayed speakers, microphone failure, an internet outage, a growing check-in queue, sessions running over, or a room becoming unavailable.
The fallback should be specific enough to act on immediately. “Use backup laptop” is more useful than “fix technical issue.”
8. Review the Run of Show With the Team
Share the final working version before event day and confirm that every owner understands their arrival time, responsibilities, communication channel, equipment needs, and escalation process.
The team should also know who can approve schedule changes and where the latest version of the document is stored. A detailed plan is only useful when everyone is working from the same version.
Roles and Responsibilities in a Community-Event Run Sheet
Clear ownership prevents the event lead from becoming the default decision-maker for every task. A useful run sheet should show who leads each activity, who supports it, and who needs to be informed when the plan changes.
Even small community events benefit from named responsibilities. One person may hold several roles, but each live event moment should still have a single owner who can confirm that the task is ready, complete, or blocked.
Suggested Event-Team Responsibility Matrix
| Activity | Event lead | Registration lead | Host | AV lead | Volunteer lead | Venue contact |
|---|---|---|---|---|---|---|
| Venue access | Informed | — | — | — | Supports | Leads |
| Registration setup | Approves | Leads | — | Supports | Supports | Informed |
| Speaker arrival | Informed | — | Leads | Supports | Supports | — |
| Technical check | Informed | — | Supports | Leads | — | Supports |
| Doors open | Approves | Leads | Informed | — | Supports | Informed |
| Session timing | Informed | — | Leads | Supports | — | — |
| Networking facilitation | Approves | — | Supports | — | Leads | Informed |
| Emergency response | Leads | Supports | Informed | Supports | Supports | Supports |
| Closing announcement | Approves | — | Leads | Supports | Informed | — |
| Breakdown | Informed | — | — | Supports | Leads | Approves |
Who Can Change the Schedule?
Name one person with final authority to change the live programme. This is usually the event lead, although a host, producer, or venue representative may control specific decisions.
The team should also know how changes will be communicated. Depending on the event, that may be a team chat, radio channel, text group, shared live document, or verbal confirmation through designated team leads.
Planning Registration, Check-In, and Attendee Communications
Registration and communication tasks belong in the community event run sheet, not in a separate administrative plan that the live team never sees. A delayed reminder, unclear arrival instruction, or untested check-in process can affect the entire event timeline.
Add communication deadlines and registration decisions to the same operational view used for event-day preparation. This makes it easier to identify dependencies before they become last-minute problems.
Before the Event
Your timeline should include:
- Registration opening and closing
- Application-review deadlines
- Waitlist release decisions
- Confirmation messages
- Reminder messages
- Venue and arrival instructions
- Accessibility information
- Online-event access details
- Final attendee-count review
MeetWho can support these connected workflows by allowing organizers to create an event page for free, collect registrations, approve applications, manage a waitlist, and send announcements or reminders. For online events, access links can be shared with registered attendees rather than posted publicly.
During Check-In
The run of show should specify when the registration desk opens, who tests the devices, how walk-ins are handled, and who resolves attendee-record issues.
Include practical details such as:
- QR check-in test
- Backup attendee list
- Name correction process
- Queue-management plan
- Badge or wristband distribution
- Accessibility support
- Room-capacity monitoring
- Escalation owner
MeetWho’s QR-based check-in can help organizers manage arrivals, but the operational plan should still include a fallback for device, connectivity, or staffing problems.
For Online and Hybrid Events
Online and hybrid formats need additional timing points. Add host and speaker login times, platform tests, waiting-room setup, chat moderation, backup-host assignment, and a clear link-distribution process.
MeetWho can help control access by sharing online-event links with registered attendees. It should not be presented as the livestreaming or video-conferencing platform unless that capability has been separately verified.
How to Include Networking in the Run of Show
Networking should not appear as a vague thirty-minute block with no owner or instructions. The run of show should define its purpose, format, facilitator, room arrangement, timing cues, and transition into the next event moment.
A well-designed networking segment supports the event’s outcome. For example, a founder meetup may focus on finding collaborators, while an association event may prioritise peer learning or member introductions.
Structured Networking Timeline
A simple networking sequence may look like this:
- The host explains the purpose and participation rules.
- Attendees receive a conversation prompt or matching cue.
- Participants identify relevant people to meet.
- The facilitator announces the halfway point.
- The host gives a two-minute closing cue.
- Attendees save notes or follow-up actions.
- The event transitions into closing remarks.
This structure gives participants enough guidance to begin useful conversations without making the interaction feel overly scripted.
Privacy-First Networking
Organizers should explain whether networking is optional, what attendee information is visible, how consent is handled, and how participants can opt out. Photo policies, recording expectations, follow-up communication, and information-sharing rules should also be clear.
MeetWho follows a consent-based approach. Instead of exposing a public attendee list, it can rank relevant people among participants who have permitted networking, based on professional profiles, event goals, shared interests, what they are working on, and how they may be able to help one another.
Using MeetWho for More Relevant Introductions
MeetWho’s “Know who to meet” approach focuses on meaningful, mutually useful conversations rather than maximizing the number of contacts. Each recommendation can explain why two people may benefit from meeting, how they could help each other, and how to start the conversation.
Participants can send introduction requests and message after a mutual connection. They can also keep private notes, create follow-up reminders, and manage their connection history after the event.
Organizer settings and participant permission remain central. Paid membership does not unlock hidden profiles or private contact details, and MeetWho does not sell attendee lists.
Run-of-Show Contingency Plan
A strong run of show does more than describe the ideal schedule. It also tells the team what to do when a speaker is delayed, the internet fails, a queue forms, or a session runs over.
Every critical event moment should include an immediate action, a decision owner, an attendee-facing message, and a fallback plan.
Common Event Disruptions and Responses
| Disruption | Immediate action | Decision owner | Attendee communication | Backup plan |
|---|---|---|---|---|
| Speaker cancellation | Confirm availability and review programme impact | Event lead | Announce the revised session format | Replace with moderated discussion or extended Q&A |
| Microphone failure | Switch off the faulty device and test backup audio | AV lead | Briefly acknowledge the pause | Use backup microphone or reposition the session |
| Internet outage | Confirm whether core activities can continue offline | Event lead | Explain any affected digital element | Use downloaded files, printed lists, or offline activities |
| Registration backlog | Add staff and separate simple check-ins from complex issues | Registration lead | Reassure attendees and direct the queue | Open a second check-in point |
| Session running late | Decide which later element can be shortened | Event lead | Update the room only when necessary | Reduce Q&A or protect the closing time |
| Low attendance | Adjust room layout and facilitation style | Event lead | Welcome attendees without highlighting turnout | Use smaller-group discussion |
| Capacity issue | Stop new entry and verify venue limits | Venue contact | Give clear waiting instructions | Use an approved overflow area if available |
| Severe weather | Follow venue and local safety guidance | Event lead | Send a direct update through established channels | Delay, relocate, move online, or cancel |
| Medical emergency | Pause nearby activity and follow the venue response plan | Safety lead | Protect privacy and give calm instructions | Resume only when it is safe to do so |
| Catering delay | Reorder the programme where practical | Event lead | Update attendees if the break changes | Serve refreshments later or continue without them |
Safety, accessibility, venue rules, and applicable local guidance always take priority over the published schedule.
Community-Event Run-of-Show Checklist
One Week Before
- Confirm the event outcome.
- Finalize the programme.
- Confirm speakers and facilitators.
- Assign an owner to every activity.
- Verify venue access and room capacity.
- Review accessibility requirements.
- Confirm registration and waitlist decisions.
- Draft attendee reminders.
- Document contingency actions.
- Share the working run of show.
One Day Before
- Lock the latest document version.
- Confirm team arrival times.
- Test links, slides, and backup files.
- Charge check-in and communication devices.
- Prepare signage and attendee materials.
- Review the final registration list.
- Confirm the QR check-in process.
- Reconfirm speakers, vendors, and venue contacts.
- Review emergency and escalation contacts.
- Send the final attendee reminder.
Event Day
- Verify venue access.
- Complete the room walkthrough.
- Test equipment and backup options.
- Brief volunteers and speakers.
- Prepare the registration desk.
- Confirm accessibility arrangements.
- Start the team communication channel.
- Track timing and transition cues.
- Record any schedule changes.
- Conduct a short team debrief.
After the Event
- Thank attendees and speakers.
- Send promised resources.
- Follow up on relevant introductions.
- Review attendance and no-shows.
- Record operational lessons.
- Update the reusable template.
- Save approved event assets.
- Schedule the next community action.
Common Run-of-Show Mistakes
Making the Document Too Vague
“7:00 p.m.—Networking” does not tell the team enough. Add the facilitator, purpose, instructions, room setup, timing cues, transition plan, and fallback format.
Assigning Several Owners Without a Lead
Shared responsibility can leave decisions unowned. Name one lead for each activity, even when several people provide support.
Forgetting Attendee Communications
A schedule change is not fully managed until someone knows whether attendees need an update, which channel should be used, and who will send it.
Planning Without Buffers
A tightly packed schedule becomes fragile when one transition takes longer than expected. Protect important moments with realistic recovery time.
Using Multiple Document Versions
The team should know where the latest run of show is stored and when it was last updated. Archive older versions or clearly mark them as outdated.
Treating Networking as Spare Time
Networking should support the event’s purpose. Give participants a reason to connect, a clear format, and enough information to identify useful conversations.
How MeetWho Fits Into Community-Event Operations
The run of show remains the organizer’s operational timeline. MeetWho supports the connected workflows around event creation, registration, attendee management, check-in, communications, and privacy-first networking.
Organizers can create an event page for free, collect registrations, approve applications, manage a waitlist, send announcements and reminders, share online-event links with registered attendees, use QR-based check-in, and control networking privacy settings.
Participants can create professional profiles, receive a limited number of personalized introductions on the free plan, send introduction requests, message after a mutual connection, save private notes, set follow-up reminders, and manage their connection history. Plus membership can provide more active suggestions, detailed match explanations, personalized conversation starters, AI-supported introduction and follow-up messages, unlimited notes and reminders, calendar integrations, and advanced personal networking tools.
Frequently Asked Questions
What is a run of show for a community event?
A run of show is an internal timeline that explains what happens during the event, when it happens, who owns each activity, what attendees experience, which resources are required, and what the team should do when the plan changes.
What should an event run-of-show template include?
It should include time, duration, activity, attendee experience, team action, owner, location, required equipment, communication cue, contingency note, and status. Larger events may also need dependencies, radio channels, vendor contacts, accessibility notes, and backup owners.
How is a run of show different from an event agenda?
An agenda is written primarily for attendees and summarizes the programme. A run of show is written for the delivery team and includes operational details such as ownership, cues, equipment, transitions, communications, and fallback actions.
How detailed should a run of show be?
It should be detailed enough for the assigned owner to act without guessing. Critical transitions, technical tasks, attendee communications, check-in procedures, and contingency decisions usually require more detail than routine programme items.
Who should create the event run of show?
The event lead typically owns the document, but registration, venue, production, speaker, accessibility, volunteer, and networking leads should contribute to the sections they manage.
When should the run of show be finalized?
The working version should be shared early enough for owners to review it. The final version should be locked after major programme, venue, speaker, and operational details are confirmed, while still allowing clearly controlled event-day updates.
Should attendees receive the full run of show?
Usually not. Attendees generally need the public agenda, arrival instructions, accessibility information, and relevant updates. Internal contacts, technical notes, fallback plans, and backstage instructions should remain with the delivery team.
How do you plan networking in a run of show?
Define the networking goal, facilitator, instructions, timing, room setup, participation rules, prompts, closing cue, and follow-up process. Avoid treating networking as an unstructured break.
Can this template be used for online or hybrid events?
Yes. Add host and speaker login times, platform checks, waiting-room procedures, chat moderation, backup-host responsibilities, online access communications, and internet-failure contingencies.
What tools can help manage registration and check-in?
Event-management platforms can support registration, approvals, waitlists, reminders, and check-in. MeetWho combines these functions with consent-based networking tools designed to help attendees identify the most relevant people to meet.
Plan the Timeline—and the Connections That Matter
A reliable run-of-show template for community events gives every important moment a time, an owner, a cue, and a fallback. It helps the team stay coordinated while creating a calmer, clearer experience for attendees.
Create your next community event with MeetWho for free, manage participants from registration through QR check-in, and help attendees focus on the people most worth meeting.
Create Your Event
