Recommended direction
Design the programme as stations or waves. Each group should know where to go, what they are doing while waiting, and who moves them next.
Planning for 50, 100, 200, or 300+ people is less about choosing the loudest game and more about protecting flow. Use this selector to decide whether you need one rotation, split waves, or a simpler brief before you ask for a quote.
This is a planning aid, not a capacity promise. The final format still depends on the actual venue, vendor availability, weather, food, approvals, facilitator plan, and event date.
You selected 80-150 people, shortlisted venue, sheltered, mixed departments, and 90-150 minutes.
What's driving this: shortlisted venue and 80-150 people.
Design the programme as stations or waves. Each group should know where to go, what they are doing while waiting, and who moves them next.
Keep rounds short and make the next team obvious. The group is large enough that unclear movement will still show.
Ask Cohesion to shape the station or wave plan before the quote is locked.
Large-group format brief Group size: 80-150 people Venue: shortlisted venue Weather: sheltered Group mix: mixed departments Energy: moderate Programme time: 90-150 minutes Food/prizes: simple food or prizes Priority: smooth flow Verdict: Split-wave plan Next action: Ask Cohesion to shape the station or wave plan before the quote is locked.
Send the brief into Event Planner so Cohesion can shape the real station count, facilitator flow, and fallback plan.
Send to Event PlannerIf JavaScript is off, this page still gives you the planning logic: choose the operating shape, protect waiting time, then ask for a simpler brief.
Decide whether the group should move as one crowd, rotate in stations, or split into waves before shortlisting the activity.
For every round, ask who is playing, who is cheering, who is resting, and how the next group moves in.
Check active space, holding space, briefing visibility, toilets, water points, food flow, and sheltered fallback areas.
Arrival, team allocation, meal queues, prize giving, group photos, and dismissal need owners in the run sheet.
Ask vendors for a format that protects flow, participation, weather plan, food timing, and budget before adding extras.
The same activity can feel smooth at 50 people and slow at 200 people. The difference is usually briefing, movement, holding areas, and how many people can join at once.
| Headcount | Safer shape | Biggest risk | Make it easier |
|---|---|---|---|
| 50-80 people | One strong activity or two short blocks. | Do not overload the programme because the group still feels manageable. | Simple team split, short briefing, one clean prize or photo close. |
| 80-150 people | Rotation-friendly activity with visible facilitator control. | Waiting time becomes obvious if only a few people are active at once. | Stations, mixed teams, clear scoring, planned water breaks. |
| 150-250 people | Split-wave or multi-station plan with a real run sheet. | Arrival, food, photos, and dismissal can take over the event. | Pre-assigned teams, multiple facilitators, staggered movement. |
| 250+ people | Festival-style, split-wave, or staged programme. | A single small-group game may leave too many people waiting. | Wave design, holding areas, PA support, simple scoring, senior-owner visibility. |
Use this table when a vendor proposes a format. The question is not only whether the group fits, but whether people stay meaningfully involved.
| Format | Best fit | Watch out for |
|---|---|---|
| One-crowd activity | 50-80 people, simple venue, shorter programme. | Avoid if only a small number can play while the rest wait. |
| Station rotation | 80-200 people, mixed departments, broad participation. | Needs clear station timing, facilitator calls, and movement paths. |
| Split-wave plan | 150-300+ people or venues with limited active space. | Wave B needs a useful role, food window, briefing, or parallel station. |
| Festival-style flow | Very large groups, family days, photo-led energy, or longer windows. | Needs stronger signage, crowd flow, and simple participant instructions. |
Large groups reward simplicity. Keep the pieces that help people move, play, eat, and close cleanly.
| Keep | Cut | Why it matters |
|---|---|---|
| Pre-assigned teams | Sorting 200 people on the spot | Team allocation can quietly consume the first activity block. |
| Simple scoring | Complex rules and hidden tie-breakers | Large groups need fast comprehension and visible progress. |
| Station or wave logic | One bottleneck activity | A queue is not participation unless the waiting role is designed. |
| Weather and holding plan | Outdoor optimism | The fallback must fit the full crowd, not only the equipment. |
| Focused recognition | Long award lists | Short, fair prize moments land better than dragging the close. |
These are signs that the date, venue, format, or scope needs one more pass before you lock the quote.
Large-group planning sits between activity choice, venue fit, weather backup, cost, quote scope, inclusion, and the final run sheet.
Use these answers as starting points, then check the real venue, activity, weather plan, and group profile.
For 100 people, the easier starting point is usually a rotation-friendly activity with simple rules, visible facilitator control, and short waiting periods. Telematch-style formats, stations, and mixed-team challenges are often easier to manage than one activity where only a few people play at once.
For 200 people, plan the event as an operations flow first. Confirm team allocation, station count, facilitator roles, venue movement, food timing, weather branch, prize flow, group photo, and dismissal before asking for a final activity recommendation.
Yes, if the activity structure prevents long inactive periods and the group profile suits that energy. For mixed fitness, senior attendees, or client-facing events, a broad-participation station format may be easier to include.
Very large events often need split waves, festival-style stations, or a staged programme. The right answer depends on venue size, programme time, food windows, weather exposure, and how much waiting time the group can tolerate.
Simplify when the venue is uncertain, the weather branch is weak, the time window is tight, the group is very mixed, or food and recognition layers are being added before the core event flow is stable.