How to Write a Retreat Run-of-Show That Your Whole Team Can Execute
- 7 days ago
- 4 min read
Updated: 4 days ago
The run-of-show is the document that holds a retreat together on event day. Not the schedule — the schedule is a subset of it. Not the itinerary — that is the guest-facing version. The run-of-show is the operational document that every person with a role in the program is working from: vendor staff, facilitators, your own team.
A weak run-of-show produces a day full of questions: What should we set up in the main room before the 9am session? Who handles the AV if something goes wrong? When is the caterer supposed to have the afternoon snack ready? A strong run-of-show means none of those questions reach you. Everything is already answered.
Here is how to build one.
Planning a wellness retreat? We made something for you. Download the free Wellness Retreat Planning Checklist — a full walkthrough of every step, so nothing falls through the cracks. Get it sent straight to your inbox.
What a Retreat Run-of-Show Is Not
It is not a schedule reformatted as a table. A schedule lists what is happening. A run-of-show documents who is responsible for what, what needs to be in place before each transition, and what happens if something does not go as planned.
It is not a document only the lead planner reads. The run-of-show is a team document. Every vendor, facilitator, and staff member who has a role in the program should have a version of it — either the full document or a role-specific excerpt. A run-of-show that only exists in the planner's hands is a single point of failure.
It is not static. The run-of-show should be updated through the planning process as decisions are finalized, and it should have a version that reflects any last-minute changes made the morning of the event. The version on the table at setup is the operative document — make sure everyone has the same one.
The Sections Every Retreat Run-of-Show Needs
The master contact sheet. Every vendor, facilitator, and staff member: name, role, cell phone number, and the specific circumstances under which they should be contacted on event day. This is the first page. If something goes wrong, no one should be searching for a phone number.
The timeline with owner assignments. Not a schedule — a timeline. Every significant moment in the program day has three fields: the time, what is happening, and who is responsible for it.
"9:00am — Morning session begins — Facilitator" is a schedule entry.
"8:30am — Main room final setup complete, AV checked and running, water and tea stations restocked — Venue operations lead confirmed by planner" is a run-of-show entry.
The transition notes. Between every session, there is a transition. Who clears the room? Who resets the space? What does the next session need that is not currently in place? These transitions are where retreats lose momentum. Documenting them is the operational work that prevents the feeling of a poorly run program.
The contingency tree. For every high-stakes element of the program, there is a contingency: What happens if the lead facilitator is twenty minutes late? What is the protocol if a participant has a medical situation? What do we do if the outdoor session needs to move inside due to weather? The contingency tree does not need to be long — three to five scenarios is usually sufficient. But they need to be written before event day, when there is time to think clearly, not during the event when there is not.
The dietary and accommodation reference. A quick-reference list of participant dietary restrictions, accessibility requirements, and any other needs that affect logistics. This lives in the run-of-show so that anyone managing a meal or a room assignment can answer the question without finding the planner.
How to Distribute the Run-of-Show
The full run-of-show goes to: your core planning team, the venue operations contact, and any senior vendors with broad day-of responsibility. This is the document that tells the whole story.
Role-specific excerpts go to: individual facilitators (their sessions, their transitions, their technical requirements), catering (timing of all food and beverage service), A/V or tech support (all cues and technical requirements), any support staff with specific responsibilities.
People perform better when they have exactly the information they need — not the entire document, which often creates confusion rather than clarity.
Print copies. Always. Cell service fails. Phones die. A printed run-of-show in every key person's hands is not old-fashioned — it is the operational standard for any program that matters.
The Pre-Event Run-of-Show Review
Two to three days before the retreat, walk through the run-of-show with every primary vendor and team member. Not a recap of the schedule — a specific review of owner assignments, contingency protocols, and any open questions.
The questions that surface in a pre-event review are always worth surfacing then rather than on the day. A vendor who is uncertain about their role in a transition will be uncertain on-site. A facilitator who has not confirmed their technical requirements will confirm them during the session setup, which is the wrong time. The pre-event review converts all of that uncertainty into clarity.
On event day, if your team is asking you operational questions that should have been answered by the run-of-show, the document was incomplete. If they are not — if the day unfolds with the people around you knowing exactly what they are doing and when — the run-of-show worked. That is the standard.
Want something you can actually work from? The free Wellness Retreat Planning Checklist breaks down every phase of the process in one tidy download. Pop your email in below and it's yours.
