Add a game when you know your format will work and enough schools can actually field teams, ideally after a pilot checked against goals you've agreed beforehand. Pause or retire a game when your own records, reviewed at a set point, show it can't sustain a viable field or is taking capacity away from the rest of your programme. Popularity on its own doesn't settle either decision.

What should you check before adding a new esports game?

Start with publisher permission, because that can rule a game out before demand comes into it. When checked on 7 October 2026, Rocket League's rules hub linked Epic's event licence terms. Selected conditions include no paid participation or viewing gates, an event starting and finishing within 30 days, and players aged at least 13, or older where local requirements say so. An event lasting more than 30 days falls outside those standard conditions unless Epic agrees otherwise in writing. Riot's VALORANT community competition guidelines, dated 18 June 2026, have no fixed duration limit, but require event notification and carry other conditions. Check the full terms for your title, region and event. School approval and ordinary game access don't replace event permission.

Then check whether the schools showing interest can actually play one another. Minecraft's edition explainer confirms that Java and Bedrock players can't play together, and VALORANT keeps console players apart from PC opponents. What looks like a large audience can turn out to be several smaller pools. Check devices and account access with school IT as well. VALORANT's PC requirements include TPM 2.0 and Secure Boot on Windows 11; ask IT to assess the managed devices your schools will use.

The organiser experience shared for this article was specific: Clash Royale reached students through mobile devices, while their Trackmania Time Attack format let students compete without everyone being online at once. That doesn't establish the same experience for every league or Trackmania mode. The official Time Attack qualifier tools document start and end windows with leaderboard scoring, while Track of the Day is labelled as requiring paid access. Those are format and content-access examples, rather than prices or event permissions. Check the intended edition, accounts and track access for your pilot.

Before a pilot, put down in writing what the game is meant to do for your programme. Ask schools what they can confirm: eligible starters and substitutes, an adult contact, and the devices and times they can commit to. Then agree the minimum field your format needs for those schools and the staff time you can give it.

Why aren't registrations enough to judge a game?

Registrations show interest. Actual play and eligible schools and teams returning give you different evidence about participation. During a pilot, keep separate records for each game of:

  • schools expressing interest, registered teams and eligible teams confirmed ready to play, counted separately
  • unique students who actually played, kept separate from rostered players
  • fixtures scheduled, fixtures closed administratively and matches actually played, counted separately
  • defaults, withdrawals, reschedules and recovery matches
  • unresolved disputes and staff support time

Agree what each measure means before comparing games. Byes aren't played matches, and a default can finish a fixture on paper without anyone playing. Count each recovery match actually played once, keep its link to the affected original fixtures, and don't count an unplayed original as played. Flag incomplete data, because a tidy percentage can hide what's missing. Use these records and school feedback to investigate device problems, long sessions, patchy attendance or frequent support requests, even when registrations look healthy.

How does adding a game affect the rest of your league?

Each extra game takes some of your attention and may draw on the same interested schools. If a new title needs the same teachers, players, supervised device time and officials as an existing one, a bigger catalogue can leave you with two thin fields where you had one strong one. Check that overlap before assuming a new game will bring new schools. A smaller field can still earn its place if it's reliable and serves a clear programme goal.

When should you pause or retire a game?

Make the call at a review point you've set before the pilot, with a named person or group responsible for the decision. Look for a pattern: a game that repeatedly can't form the minimum field you agreed, or one whose cost to the wider programme outweighs what it delivers. Continuing with changes, trying a smaller pilot, pausing for a season or retiring it in an orderly way can all make sense.

For school re-enrolment, compare schools eligible to return with those that did. For team return, use a separate cohort of eligible teams and agree how you will identify a returning team if its roster changes. Keep player participation separate again. Record known reasons for not returning, such as students leaving the eligible year group or changes to timetables and devices. Don't assume the game caused every absence, or treat lower attendance as a judgement on a school's students. Use teacher and student feedback alongside the records, without gathering unnecessary personal detail.

A publisher change isn't automatically a reason to retire a game either. When checked on 7 October 2026, Riot's 20 August 2026 notice said it planned to end active development of 2XKO at the end of 2026, while keeping servers online beyond 2026 and allowing community events under the relevant guidelines. That's a stated plan, rather than a promise of permanent availability. Development status, online availability and tournament permission are separate questions.

How do you retire a game without letting schools down?

Give schools the date and reason as early as you can. Settle announced fixtures, prizes and fees under the rules and commitments you've actually made, and offer alternatives where they genuinely exist. Keep appropriate result history for the schools that took part, and follow your privacy and retention policy for rosters and other records. Handled carefully, retiring a weakly supported game can protect the quality of the rest of your programme.

Reviewing your games with School Esports

School Esports, a tournament platform for schools, was built independently with national federation expertise. Its demo guides describe workflows for team rosters, score submission and review and missing opponents. The resulting entry, fixture and result records can be a starting point for your own review. Get in touch for a demonstration, and ask how your chosen titles would be set up and which records and reporting are available for your league. The measures above are for the organiser to assemble; these guides don't establish a dashboard that calculates them all.

You can also read about running multiple games and divisions and measuring participation, retention and re-enrolment.