How to run a game for more than 30 people

This guide prevents a large-group game from failing at the control points: thirty-plus people cannot hear the rule, late arrivals have nowhere to go, score reports conflict, and a crowded transition blocks the room. Treat the event as a small operation with a lead host, zone leads, uneven pods, a tested signal, written stop rules, and one channel for decisions.

1. Set the room limit before the game limit

Confirm the venue’s posted capacity, booked areas, fixed exits, accessible routes, toilets, first-aid contact, and emergency procedure with the responsible venue person. Record that person’s name and the exact method for reaching them during the event.

Do not move chairs, tables, signs, or game equipment into an exit or the venue’s accessible route. U.S. Fire Administration guidance calls for clear escape plans and known exit locations, and federal accessibility standards govern accessible routes and facilities in covered settings.¹² Follow the venue plan and applicable local rules rather than inventing a substitute.

If the expected attendance exceeds the confirmed capacity or the venue cannot identify its emergency process, do not start the game.

2. Build a command chain with named decisions

Use a lead host, one score lead, one time lead, and zone leads. Put each name and responsibility on the run sheet. A person may hold two roles in a smaller event, but only one person decides each of these:

• whether a round starts;
• whether a prompt is void;
• whether the score changes;
• whether the game pauses;
• whether the event stops.

Give the lead host stop authority. Give zone leads pause authority in their own zones. If a zone lead raises the pause signal, the time lead freezes the round and the host asks for the issue. Nobody argues across the room.

FEMA’s large-event preparedness material emphasizes planning, public information, operational coordination, and situational assessment.³ This guide scales those functions down to a recreational group; it does not replace a venue or public-safety plan.

3. Divide attendance into uneven pods

Use checked-in attendance, not registration. For 37 players, make six pods of 5, 6, 6, 6, 7, and 7. No one pod size covers more than half the pod family. For 43, use 5, 6, 7, 8, 8, and 9.

Give each pod a letter, number, or color that can be read from the host position. Assign a captain, first responder, recorder, materials lead, and checker. Larger pods add a second responder or checker.

Do not let a 12-person friendship group remain one pod while strangers are split into small groups. Offer linked pods if people want to stay near one another, but keep the operating units within the written size range.

4. Map zones and traffic before check-in

Draw the room with pod positions, host point, score point, materials point, entrance, toilets, and exits. Put pods that request a clearer sightline or shorter route where the venue plan already supports that access. Do not reserve those positions as prizes.

Create one-way collection only if the room permits it without crossing an exit or accessible route. Otherwise, have zone leads bring materials to pods. Mark a late-arrival holding point that does not interrupt the host sightline.

Walk the complete route before admitting players. If two zones must cross to report a score, change the reporting method rather than asking forty people to negotiate the crossing during play.

5. Test the signal in the occupied room

Choose one start signal, one stop signal, and one pause signal. They must be distinct. Show all three before the practice turn.

Test from the farthest pod after most people arrive. Ask that pod’s checker to repeat the instruction. If the response is wrong, move the host, use the venue’s approved sound system, add a visual signal, or have zone leads relay the instruction. Do not assume more volume will fix poor coverage.

Use a spoken instruction plus a visible round number or action card. This follows the practical direction in CAST’s UDL Guidelines to use multiple media for communication and varied methods of response.⁴

6. Lock late arrivals into a join route

Keep check-in open through the practice turn. The check-in person assigns each late arrival to a pod with the fewest people and points out its zone lead. The new player watches the current turn and joins on the next turn.

After scoring begins, add no new pod. If a pod grows beyond the host’s written range, split it only at a round break and give both new recorders a copied score. If the score cannot be copied cleanly, keep the larger pod until the game ends.

Do not stop instructions to welcome individuals by name. Give the same 20 to 35 second join script at the side of the room.

7. Run a full practice turn with no points

The lead host gives one sample prompt. Every pod performs the exact answer, record, check, and report sequence. Zone leads inspect the sequence, not whether the sample answer is clever.

End the practice and ask for only four checks:

1. Did every pod know when to begin?
2. Did every pod create one answer?
3. Did each recorder use the right field?
4. Did the score lead receive one report per pod?

If any answer is no, repair that action and repeat one practice turn. Do not add scoring until all four are yes.

8. Start rounds through a fixed communication loop

Use the same loop every time:

1. time lead displays the round number;
2. host states the action and limit;
3. zone leads show ready;
4. host gives the start signal;
5. time lead gives the stop signal;
6. recorders freeze entries;
7. zone leads submit one result per pod;
8. score lead publishes the accepted totals.

No pod reports directly to the lead host unless its zone lead is unavailable. If reports arrive through two channels, accept the zone-lead report and flag the conflict for the round break.

9. Rotate who acts inside every pod

Print or speak a seat order. The first responder moves one position each turn. The recorder changes after two or three turns, and the captain changes after each full round.

Zone leads watch for three failure signs: one voice supplies two consecutive answers, the recorder edits another person’s answer before submission, or two people have had no named action after three turns. When one appears, the zone lead pauses that pod, names the next responder, and restarts it with the remaining time.

Do not solve unequal participation with bonus points. Change the route into the turn.

10. Publish score and dispute rules before Round 1

Show the scoring unit, deadline, correction window, and tie rule. Use whole points unless the activity genuinely needs another unit. The score lead keeps the only official record.

A pod may dispute through its zone lead during the next round break. The dispute must name the round and requested correction. The score lead either corrects the record or writes “no change.” After the correction window closes, totals stand.

Void a prompt for every pod if the host stated it incorrectly, two defensible answers were not covered, or the reporting channel failed across multiple zones. Do not award guessed compensation points.

11. Use observable stop and shrink rules

Write these rules on the host sheet before play:

• if two zones miss the same signal, pause and repair communication;
• if three score reports conflict in one round, freeze the scoreboard and review that round;
• if a walking route becomes crowded, stop movement and switch to zone-lead collection;
• if two rounds pass with fewer than half the pods completing the action, replace the format with the prepared shorter version;
• if the venue contact or lead host calls stop, end the game without a final round.

The shorter version must already be written. Reduce it to one action, one report, and one finish condition. Do not invent a new game while the room waits.

12. Close the event zone by zone

Announce the final round before it starts. After its reports are accepted, close scoring and state whether a tie stands or uses the published tie rule. Do not improvise repeated tie rounds.

Release cleanup by zone. Materials leads return counted sets; recorders hand in score slips; checkers inspect their pod area. Zone leads tell the host when their areas are clear. Keep normal exits and routes available throughout.

Before people leave, give the venue’s departure instruction and name the lost-property point. The lead host signs off only after every zone lead reports, the score lead stores the official record, and the venue contact accepts the room.

A sample 48-person operating sheet

This is one event design, not a universal staffing formula:

• Pods: seven pods sized 5, 6, 6, 7, 7, 8, and 9.
• Zones: three zones holding 2, 2, and 3 pods.
• Control roles: lead host, score lead, time lead, check-in lead, and three zone leads.
• Join rule: arrivals watch the current turn and join the next one.
• Reporting rule: pod recorder to zone lead, then zone lead to score lead.
• Shrink trigger: fewer than four pods complete the action in each of two consecutive rounds.
• Finish: one announced final round, one correction window, then zone release.

If the room shape, venue plan, or available staff makes this chain unworkable, reduce the event to fewer simultaneous actions. Do not treat headcount as permission to ignore the room.

Run a 42 to 58 minute large-group game from one clock

Say first: “Your pod acts through its named roles. Wait for the start signal, freeze on stop and raise the pause signal if your zone cannot continue. Scores reach the official record through zone leads only. A dispute waits for the round break. The published tie rule is [shared result / one prepared tie prompt]. We stop at [time].”

A pod that finishes early freezes its entry, checks the reporting field and waits for the stop signal. It receives no extra action and sends no early score runner. If a prompt dispute cannot be settled from the prepared key during the round break, void it for every pod. If the score remains tied after the one published tie rule, report the shared result and begin zone release.

Printable large-group game checklist

• The venue’s posted capacity has been confirmed.
• Exits and accessible routes are marked on the room map.
• The venue contact and contact method are written down.
• The venue emergency procedure is known to the lead host.
• Start, pause, and stop authority each have a named owner.
• Attendance will be checked before pods are finalized.
• Pod sizes are uneven and no one size controls most pods.
• Every pod has a captain, responder, recorder, materials lead, and checker.
• Pod and host positions are marked on the room map.
• A late-arrival holding point and join script are ready.
• Start, stop, and pause signals are distinct.
• The farthest occupied pod will test the signals.
• Spoken instructions have a visible companion.
• One complete no-points practice turn is scheduled.
• Score reports use one route through zone leads.
• The official score record has one owner.
• The scoring unit, correction window, and tie rule are published.
• Early pod completion waits for the common stop signal.
• Five observable stop or shrink rules are on the host sheet.
• The shorter fallback has one action, one report, and one finish.
• Cleanup and release happen zone by zone.
• The venue contact has a final room-acceptance step.

Sources