Build a tournament in this order: agree the event format and policies, stabilize the player list, verify seating, rehearse score collection, then print the player-facing instructions. A seating tool cannot decide your scoring policy, and a beautiful score sheet cannot repair an unclear player list.
This checklist is for the organizer coordinating the room. It is not an official tournament rulebook. Treat the suggested workflow as a planning model and use the rules and event conditions you have actually adopted.
1. Write the event brief before registration opens
Put the date, venue, arrival time, scheduled finish, capacity and intended experience level in one event brief. State what players bring, what the organizer supplies and whether instruction is included. If this is a competitive event rather than guided practice, make that distinction visible in the invitation.
Decide how the event will handle round timing, score submission, ties, corrections, substitutions and an incomplete game. Publish the conditions that apply to your own event instead of assuming that “standard tournament rules” means the same thing to every guest. For a concrete example of an organizer documenting its own movement and scoring conditions, see MahjCon's published tournament rules. Those are that event's rules, not universal instructions to copy into yours.
2. Separate a player's identity from a seat number
Use a stable player ID throughout registration, score records and corrections. A table number can change between rounds; a player ID should not. Keep the mapping from ID to person on the director's list and share only what is needed for seating and results.
Track confirmed, cancelled and standby players separately. Add a version or timestamp to the roster before generating assignments. If someone withdraws, record the change once and regenerate or revise the affected plan according to the tool's actual instructions. Do not leave an old printout at check-in while volunteers work from a newer file.
3. Check the seating plan before players see it
Decide what the seating plan is trying to achieve. Mixing opponents, limiting repeat meetings, accommodating fixed seats and sharing sit-outs are different constraints. Some combinations cannot all be satisfied. Make the priorities explicit instead of promising “perfectly fair seating” for every group size.
A practical seating audit
- Every confirmed player appears in each round or has a documented sit-out.
- No player appears twice within a round.
- The number of active seats matches the venue and chosen format.
- Table labels on the plan match the signs in the room.
- Any fixed-seat or accessibility arrangement is actually reflected.
- Changes and sit-outs are explained to the affected players.
If you use a generator, test the actual player count and round count you intend to run. Read its audit rather than assuming the presence of a “Generate” button guarantees every constraint. If you use a printed rotation chart, check its stated range. A chart and an offline seating application are not interchangeable products.
4. Rehearse one score from the table to the result
Before the event, use a clearly marked fictional test record. Write the player ID, round, table and score under your event's chosen system. Ask one person to collect it and another to enter or verify it. Check how a missing value, an unreadable number and a correction are recorded.
Distinguish not submitted from zero. If your sheet uses zero for a valid result, a blank field should not silently become the same thing. Preserve the original submitted record when correcting an entry and note who checked the correction. Remove test records before live play begins.
Choose a single collection point and a clear hand-in method. The goal is to prevent three volunteers receiving partial information in three different places. A small “scores received” check can be more useful than an elaborate leaderboard that is missing one table's results.
5. Give each event-day job a named owner
| Job | Owns the decision or record |
|---|---|
| Check-in lead | Actual arrivals, missing players and the current roster version. |
| Floor lead | Where players go and how movement instructions are communicated. |
| Score lead | Collection, missing records and entry checks. |
| Director | Rulings and exceptions under the published event conditions. |
Volunteers should know when to send a question to the director instead of improvising an answer. Players should know the same thing. Keep the director's contact point visible, especially if the event uses several rooms.
6. Use the same transition between rounds
A repeatable transition is easier to explain than a new instruction every hour: finish according to the event's time policy, submit the required records, check for missing information, announce the next assignments, then begin when the director calls the start.
Do not rush players to new tables while the score lead is still trying to identify an incomplete slip. If a delay occurs, announce the revised start once through the agreed channel. Multiple unofficial announcements are a recipe for different tables following different schedules.
7. Verify before announcing final standings
Check that every expected record has either arrived or has an explicit director-approved status. Apply the tie procedure you published before play. Allow whatever correction process your event promised, then announce the verified results. Keep personal registration details out of public standings.
Afterward, save the final roster version, seating plan and checked results together. Note the bottleneck worth fixing before the next event: arrival queue, unclear table labels, slow score entry or a policy players did not understand. Improve that one process before adding more paperwork.
Toolkit or seating generator?
The Tournament Kit supports the event's operational paperwork, score tools and director materials. The separate Tournament Seating Generator / Tournament Flow is an offline digital seating tool with a printable companion. Choose for the missing job, inspect the actual listing and limits, and do not assume either product supplies official rules or a policy decision on your behalf.
Original MahjongTableFlow operational guidance. Source example: MahjCon's own published event rules, checked September 23, 2026. For the game materials used in NMJL-style events, consult the National Mah Jongg League. Event policies remain the organizer's responsibility.
