Half-day shape
Best when the activity is the main experience and food stays simple.
- Arrival and briefing
- Main activity block
- Water break
- Final rounds
- Photo, prizes, refreshments, close
Turn a rough team-building idea into a day-of flow with timing blocks, owners, food windows, transport notes, weather branches, and a clear brief for Event Planner.
The public invite can be short. Your event run sheet needs owners, buffers, food timing, and fallback branches so the day does not depend on memory.
| Time | Block | Owner | Note |
|---|
If the builder does not run, use these as starting points. Adjust the time, owner, and note columns before sending to any vendor or internal approver.
Best when the activity is the main experience and food stays simple.
Best when headcount, food, travel, or leadership moments need more room.
Push the schedule wider or simplify the brief when these stack up.
Use this for a focused department event where the activity carries most of the value.
| Time | Block | Owner | Note |
|---|---|---|---|
| 1:30pm | Arrival and event lead check-in | Event lead | Confirm facilitator, venue contact, water point, food contact, and late-arrival channel. |
| 1:45pm | Welcome and safety briefing | Host / facilitator | Set expectations, team split, phones/photos, attire, and wet-weather note. |
| 2:00pm | Main activity block | Facilitator | Keep rules simple and watch waiting time for large groups. |
| 3:00pm | Water break and reset | Event lead | Use this to fix team balance, check food timing, and brief the next segment. |
| 3:15pm | Final rounds or team challenge | Facilitator | Shorten if the first block ran long. |
| 4:15pm | Prize moment and group photo | Host | Keep recognition inclusive; do the photo before people disperse. |
| 4:30pm | Refreshments or informal debrief | Event lead / caterer | Confirm dietary labels and service window. |
| 5:00pm | Close and dismissal | Event lead | Thank participants and confirm transport or next destination. |
Use this when the event includes larger-group movement, food, recognition, or a more complete offsite flow.
| Time | Block | Owner | Note |
|---|---|---|---|
| 9:15am | Vendor, venue, and event lead arrival | Event lead | Confirm setup, AV, equipment, food windows, and emergency contacts. |
| 9:45am | Participant arrival and registration | Committee | Check attendance, team bands, late arrivals, and accessibility needs. |
| 10:00am | Welcome, objective, and safety briefing | Host / facilitator | State why the day exists and what participants should expect. |
| 10:30am | Activity block one | Facilitator | Start with the simplest rules so the room warms up quickly. |
| 11:45am | Water break and rotation | Event lead | Use buffer to reset teams, confirm lunch readiness, and check weather. |
| 12:15pm | Activity block two | Facilitator | Keep station movement clear for larger groups. |
| 1:15pm | Lunch | Caterer / event lead | Protect the meal window; do not let activity overrun into hot food timing. |
| 2:15pm | Lighter challenge or final rounds | Facilitator | Reduce intensity after lunch and keep the close visible. |
| 3:30pm | Recognition, prizes, or reflection | Host | Name teamwork behaviours, not only the highest scorers. |
| 4:15pm | Group photo and closing | Event lead | Capture leadership, team, and wide-room photos before dismissal. |
| 4:45pm | Buffer and dismissal | Event lead | Handle transport, lost items, vendor teardown, and final venue walk-through. |
A run sheet cannot guarantee weather, permits, food outcomes, or venue behaviour. Its job is to make the decision points visible before the day starts.
The run sheet should not decide the whole event alone. Pair it with quote, venue, weather, and activity-fit checks.
Use these when you need to explain why the timing document matters before the event feels complicated.
Include timing, owner, location, activity block, setup notes, food window, transport note, weather branch, leadership cues, and emergency contacts. Your planning copy can be detailed; participant comms should stay simpler.
For a small indoor half-day event, 10 to 15 minutes between major blocks may be enough. For larger, outdoor, catered, or offsite events, use larger buffers because movement, food, weather, and late arrivals stack quickly.
Yes. Food timing affects energy, queues, dietary checks, and venue clean-up. Treat catered meals as event blocks, not background logistics.
Use the builder to create a rough flow, then send it into Event Planner. Cohesion can adjust the activity format, facilitator flow, food timing, and fallback plan around the real venue and headcount.
A rough run sheet is useful because it exposes missing owners, tight transitions, food risk, weather decisions, and leadership cues. Send the draft into Event Planner and let Cohesion tighten the facilitation flow around the real venue and group.