The agenda says “team building, 2:00–3:45.” The operating team still needs to know when the room is available, who checks the materials, what releases the group from the previous session and who can approve a change when the schedule slips.

A team-building run of show answers those questions. It connects the participant sequence with the conditions, owners and cues that make the sequence possible. This guide gives you a copyable template and two complete worked examples: a standalone office session and a conference-attached activity block.

Use it after the purpose and delivery scope are sufficiently clear. If you are still choosing the activity's place in a conference, begin with the conference team-building guide. This article handles execution of the selected block rather than design of the entire conference.

What is a team-building run of show?

A team-building run of show is the operational sequence for a session: when each action happens, who owns it, what must be ready and who receives the handoff. It includes setup, briefing, activity transitions, debrief, participant exit and agreed room release, not only the game itself.

A conference-wide run of show may cover production, speakers and several rooms. For a facilitated team-building block, use a focused version with clear boundaries between the host, provider and venue.

A single attendee agenda should not carry private contacts or every operational fallback. Keep it simple for participants, while the working team uses the detailed sheet.

Confirm the delivery brief before you build the timeline

Start with the objective and intended output. If participants will create a working agreement, allow time to discuss and record it. If the event has a hard finish, work backward from the participant release point instead of squeezing everything into the advertised activity duration.

Check the participant planning count, venue layout, meaningful participation options, access window, materials, technology and accepted scope. The team-building RFP template helps gather requirements before selection; the operating sheet should reference the agreed version after appointment.

Write down the boundary of your responsibility. A provider running one activity is not automatically managing catering, conference AV, participant transport or the next speaker. Name the owner receiving the group before and after the activity, and confirm venue-led requirements through the appropriate venue contact.

If the briefing, activity, debrief and transition do not fit, adjust the format or window with the responsible parties. A schedule cannot make an infeasible plan workable by assigning optimistic times to every row.

Copy the team-building run-of-show template

Use one short event header, a compact timing grid and a separate cue/decision record. This is easier to scan than a single table with a dozen crowded columns. Replace role labels with actual names before use and keep personal information out of widely circulated copies.

Complete the control header

The three time boundaries prevent a common mistake: treating a 90-minute facilitated core as if it includes unloading, participant arrival and room reset. Confirm each boundary before sharing a final schedule.

Copy the operating grid

Add rows for the actual approved sequence. Use local clock times and durations, then check that consecutive rows connect without unexplained gaps or overlaps.

Add a cue detail and decision record

“Room ready” is too vague if no one knows who checks it. A better entry is “venue contact and provider lead confirm approved layout, materials and required sound before the host admits participants.” That wording makes the handoff observable.

Use the venue's incident contact and procedures for emergencies. This operating worksheet does not certify safety, replace professional requirements or authorize improvised changes to essential instructions.

Worked example: a standalone office session

Hypothetical schedule: illustrative planning arithmetic, not a FullTilt program duration or staffing commitment. The organizer has planned 105 minutes with participants, a 90-minute facilitated core and 180 minutes of room access. The provider and venue still need to approve the actual format and timings.

The participant window is 09:00–10:45: 105 minutes. The facilitated core is 09:10–10:40: 90 minutes. The access window is 08:15–11:15: 180 minutes. The two activity rounds total 50 minutes; calling all 105 minutes “activity time” would hide arrival, instructions, transition, debrief and exit.

Define the acceptance and release conditions

Before O03, the host needs a positive readiness handoff. Check the approved layout, materials, required technology and participation arrangements with the relevant contacts. If an essential condition is missing, the decision lead resolves it or agrees a changed plan before admitting the group.

Before O08, the facilitator signals the activity finish and brings participants to the debrief arrangement. The sponsor should know whether they are simply listening, helping capture the output or taking over the next-step discussion. Assigning that role in advance avoids an awkward unplanned speech or a missing close.

At O11, venue release means the agreed handback condition is accepted, not simply that participants have left. Confirm who removes materials, restores furniture and checks the room. Those tasks belong to whoever agreed to provide them; the worksheet does not make them automatic supplier inclusions.

Adapt the run of show to a conference agenda

A conference block adds upstream and downstream owners. The host controls when the previous session releases participants, while the activity team needs the promised room access and the next session needs an on-time handover.

Hypothetical conference adaptation: the same 105-minute participant window and 90-minute core move to the afternoon. The venue must actually grant setup access; setup cannot be assumed to happen while a previous session occupies the room.

The participant window is 14:00–15:45; the core is 14:10–15:40; access is 13:15–16:15. A next session starting in the same room before 16:15 conflicts with this sample release plan unless the venue and provider agree another workable arrangement.

Record both people movement and room movement. Participants might leave on time while furniture, materials or sound equipment still block the next use. For a local hotel/conference planning example, see the NYC conference coordination guide.

Assign decisions before anything runs late

Separate protected steps from optional design elements. Necessary instructions, agreed participation arrangements, venue requirements and realistic transitions should not become the default source of time savings. Have the provider identify what can actually be shortened or removed without making the format incoherent.

For a ten-minute late handover, one possible design is to remove an optional ten-minute extension from the second round while retaining the necessary briefing and core debrief. That option must be designed and approved beforehand. It is not a universal instruction to cut ten minutes from any program.

If no approved variant fits, the responsible contacts need a revised scope, another slot or a delay. Do not promise the original experience, full timing and original finish simultaneously when the arithmetic no longer works. Use the cost and quote guide to record changes with commercial consequences.

Rehearse, approve and distribute one current version

Walk through the cues with the people who own them. Ask who releases the room, who admits participants, what the facilitator needs to start, who can change a row and how the next receiver knows the handoff happened. A cue-to-cue review should expose unresolved dependencies without requiring everyone to perform the entire activity.

Nominate a master editor and alternate. Issue a version number and time stamp, provide read-only access for recipients where practical and keep an offline copy. Set the freeze and acknowledgement timing around the actual event rather than assuming one deadline fits every session.

When something changes, log the affected cues, approver and time. Tell each affected receiver what changed and obtain acknowledgement. Replace superseded copies so the venue is not working from one release time while the provider uses another.

For several offices, keep local sheets attached to the shared plan rather than compressing every time zone into one unreadable grid. The multi-city planning guide explains what stays common and what needs local confirmation.

Close the event and improve the next run

Record actual times alongside planned times and note why important deviations occurred. Confirm room release, unfinished actions, any required private follow-up and the owner of the participant output. Keep the factual operating record separate from promotional claims about results.

At the review, ask which handoff was unclear and which assumption should change next time. A recurring five-minute delay might indicate the plan needs a different transition; it is not automatically a reason to pressure participants to move faster.

Connect the operating record back to the complete event planning guide. The run of show should help deliver an agreed plan and improve the next one. It cannot substitute for clear scope, a suitable venue or decisions by accountable people.

Frequently asked questions

‍