Adding a second or third game to a school league feels like a step forward, and it is. It also brings more rulebooks to keep track of and more matches starting on the same evening. A small team can manage that if everyone knows what to share across games and what needs its own approach. Standardise the admin around the games, including checklists, ownership, school contacts and escalation, and give each game its own rules and format. Then plan for your busiest start window, because that's where a small team may run out of hands first.
Why does each new game add so much league admin?
Because every game has its own roster size, match length, rules and support needs, and divisions add to those differences. It's tempting to put everything in one rulebook. A shared admin system can cut duplication without squeezing every game into the same format, so share your processes and ownership, and reuse policy wording where the rule really is the same. Copying a rule that doesn't fit the game is likely to leave you answering more questions than it saves.
Divisions deserve the same care. The demo's draws and standings guide explains that, where an event uses division or tier splits, a team's assigned competition can change, and points and tiebreaks follow the rules for that event (draws and standings guide). Explain both to schools before the season starts so a team moving doesn't come as a surprise.
What should every game have written down before the season starts?
A short checklist for each game, using the same headings, so whoever's on duty can find an answer quickly:
- roster size and eligibility requirements
- a link to the game's current official rules
- the series format, such as best of one or best of three
- how lobbies are prepared, and who's responsible
- the session allowance you're proposing for each match
- a named person who handles escalations for that game
Those checklists are the part of your setup most worth taking into next season, so update them while any problems are still fresh. For the wider league setup, see how to run a school esports league.
Keep the help path consistent across games so students and teachers only have to learn it once. The School Esports demo's help guide sends fixture problems through Request an Admin, school, roster and attendance issues to the teacher, and longer-running account or event problems to Support (getting help guide).
How do you keep things simple for schools entering several games?
Treat each school as one relationship, even if it has teams in three games and two divisions. One main school contact makes teacher communication and billing conversations easier to keep together. The School Esports demo's team management guide describes teachers choosing the tournament and game for each entry, reusing an earlier roster where offered, and submitting several team entries through a bulk-upload template with validation. Eligibility still applies when rosters change (team management guide). For paid events, the demo's billing guide describes school billing for authorised school users where available (school billing guide), so check how fees apply to each event before telling schools what they'll pay.
The tricky clashes are the ones you only spot when you look across games. Three entries from one school might still rely on one teacher, one computer room and the same handful of students. Before fixtures go out, check for students entered in two games on the same night and teachers expected in two rooms at once, and make sure each school has enough devices for all the teams it has entered. Count team entries separately from unique teams, students and schools, too. Each number tells you something different about the load you're taking on.
When does a small esports operations team run out of capacity?
Possibly sooner than you'd think: at match start, when several problems can land together. Registration numbers tell you how big the season is, but they don't show that peak. Picture three games all starting at the same time on a Wednesday. A missing player in one and a lobby that won't open in another can need attention within minutes of each other. A season total that looked manageable doesn't help much in that moment.
The workflow shapes where some of that work lands. The School Esports demo's score guide says opponents confirm or dispute submissions, and a revised pending score needs the opponent's review again. Confirmation reminders go out, and authorised staff can review outstanding submissions and resolve disputes (scores and disputes guide). For no-shows, follow the event's waiting and default rules. The missing opponent guide describes recovery conditions and a time window where it is offered, with no guaranteed replacement. School Esports' Jonathan Jansen says tournament administrators must approve suggested recovery matches before they are locked in.
Spreading games across different nights or start times can ease that peak. Be clear about the trade-off, though. It moves the work around the week without necessarily reducing it, and you may need to staff more evenings while schools commit to more of them as well. Talk with schools before reshaping the calendar, and plan capacity around your busiest start window alongside your registration numbers.
Where School Esports fits: The public demo Division Tournament shows three different games as separate cards in one event. The team management guide describes school-side entries by tournament and game. These are illustrative demo entries and documented workflows, so ask School Esports which games, formats and settings are available for your league.
You can also read about the NZ Esports league administration case study and teams, substitutes and roster changes.
