Plan
Use a clan-based Telematch rotation with one central timing and scoring path.
360-person Telematch case study
TADM 360-Person Telematch Case Study
A large Telematch is not just a bigger set of games. The useful pattern is the control system: clans, arenas, team units, timing, scoring, movement, and one visible event rhythm.
360participants6arenas5clans12people per team unit
Based on a past Cohesion Telematch event.
Event at a glance
Event Snapshot
Use this snapshot to review the client, group size, venue, arena plan, and team structure before adapting a similar large-group Telematch.
| Client | Tripartite Alliance for Dispute Management |
|---|---|
| Short name used here | TADM |
| Event date | 6 March 2023 |
| Group size | 360 participants |
| Venue | MOM Services Centre, 1500 Bendemeer Road |
| Format | Telematch |
| Arena plan | 6 arenas |
| Clan structure | 5 clans |
| Team unit | Each arena split into 5 teams of 12 |
| Planning reference | Past Cohesion Telematch event |
Planning tool
360-Person Rotation Planner
Use this planner to turn the example into a starting brief. Share your date, venue, weather exposure, food plans, approvals, facilitator needs, budget, and event timing so Cohesion can shape the format around the real event.
Recommended direction
Rotation-ready with controls
Recommended next action
Send the rotation assumptions into the Event Planner so Cohesion can check venue footprint, timing, and facilitator coverage.
Check before confirming
Adjust if needed
Transfer pattern
What the TADM format makes easier to decide
Use this pattern when the brief is large, mixed, and rotation-led. The exact arena count still depends on venue, timing, facilitators, weather plan, food, and approvals.
Choose the clan unit first
The clan is the scoreboard identity. It helps a 360-person event feel like one shared programme instead of six separate corners.
Keep arena teams small enough
Teams of 12 per arena are easier to brief, move, and score than one large crowd waiting around each game.
Centralise timing and scoring
Large Telematch days need a single timing rhythm and a clear score path from each arena back to the main result.
Protect holding and movement space
The format is only as strong as the movement plan between briefing, arenas, water breaks, food, and closing.
Copy or adapt
Adapt The Example
This case study is useful as a planning reference. The right activity mix still depends on your group size, venue, timing, weather plan, and how active your team wants to be.
| Keep | Adjust | Reason |
|---|---|---|
| Clan-based scoring | Publicly tracking every micro-result | A clan result is easier to explain at 360 people. |
| Pre-assigned teams | Sorting everyone on event day | Late team sorting can consume the schedule before games start. |
| One rotation rhythm | Each arena deciding its own timing | Independent timing creates crowding and uneven waiting time. |
| Facilitator control points | Free-flow movement between arenas | Large groups need clear movement ownership. |
Make the example fit your event
Start from the useful structure, then tune the activity mix around your current team. A repeatable event is not about copying every detail; it is about keeping the pacing, briefing, and movement clean for the group in front of you.
Details that help us recommend the format
- A current group-size range and arrival pattern.
- Venue areas for active stations, waiting groups, water points, and closing.
- Indoor, outdoor, or wet-weather preferences.
- Food, transport, leadership segments, and timing windows.
Related planning paths
Turn this example into your own event brief
Use these guides if you are still deciding on activity fit, headcount, budget, venue, weather plan, quote details, participation comfort, or event-day timing.
Telematch
See the rotation-friendly format used in this example
Archery Tag
Compare an active arena format for mixed large groups
DBS case study
Compare a repeat finance example across changing group sizes
Events Club case study
Compare a 500-person multi-arena active event
Event Planner
Turn the closest example into your own event brief
Case Studies
Compare more Cohesion planning examples
Large Group Selector
Choose a format for 50, 100, 200, or 300+ people
Run Sheet Builder
Turn the format into event-day timing
Inclusive Planner
Check access, comfort, food, and participation risk
Quote Checklist
Ask for the scope details that protect the event
Cost Calculator
Keep venue, food, prizes, and logistics visible
Venue Chooser
Check active space, holding areas, and movement flow
Weather-Safe Planner
Protect outdoor or sheltered branches
Activities
Compare Telematch, Laser Tag, Archery Tag, Bubble Soccer, and more
Contact
Talk through your current brief with Cohesion
TADM 360-Person Telematch Case Study questions
What does the TADM case study show?
It shows a 360-person Telematch structure using 6 arenas, 5 clans, and smaller team units so scoring and movement could be managed at scale.
How should another 360-person event use this example?
Use the 6-arena structure as a starting reference, then tune the arena count around venue footprint, game selection, timing, facilitator coverage, weather plan, and the wider schedule.
Why are clans useful for large Telematch events?
Clans give participants a simple shared identity and make the closing score easier to understand than a long list of individual station results.
What should you check before copying this format?
Check venue space, holding areas, facilitator coverage, movement routes, weather branch, food timing, and how scores will be tabulated.
What should we share to plan something similar?
Share the group-size forecast, venue layout, available time, preferred energy level, food timing, weather exposure, and whether teams or clans can be assigned before event day.
Plan from this example
Bring Your Brief Into The Event Planner
Use this case study as a starting point. Your event still needs its own fit check around people, space, activity intensity, weather, food, movement, and approvals.