If you run a school esports league, people usually ask how many teams signed up. That's just the first step. Registering, getting approved, actually playing, finishing the season and coming back next year are different stages of a school's relationship with your league. Each needs its own count and denominator. Sort out those definitions before the season starts, and your reports can show you where schools fall away.

Why isn't the number of registered teams your participation rate?

Signing up and playing are separate things. A league can have plenty of entries while a fair share of approved teams never get through their fixtures. School Esports' demo team status guide explains that approval doesn't guarantee a published fixture. A team may have a bye. Take care with byes and default wins too: your rules might award points for them, but a bye or default without play doesn't count as actual participation.

What should you count before you calculate anything?

Start by choosing your units, because schools, teams, entries and players tell you different things. These are working definitions for your league to adopt and write down, rather than verified product fields:

  • School: one institution under a stated rule for campuses, mergers and name changes. Count each school once, however many teams it enters.
  • Team: an identified squad under a stated continuity rule. A team name alone doesn't establish whether it's the same squad.
  • Entry: one team registration in one competition, game and season. A team entering two events counts as two entries.
  • Player: one appropriately authorised, deduplicated participant. Count actual appearances separately from roster membership.
  • Fixture: one scheduled head-to-head meeting, however many games it includes. Link recorded reschedules and any replacement fixtures to the original opportunity so you don't count it twice. Measure time-attack and other formats separately.
  • Cohort: a group fixed by a stated rule and date, such as entries approved by registration close. Freeze it, and record late additions, withdrawals and unknown outcomes separately.

Which participation rates should you track?

Three rates cover most of what you need:

  • First-play rate: cohort entries with at least one verified played fixture by a set date, divided by all approved entries in that fixed cohort. A bye or default without play doesn't qualify.
  • Played-fixture rate: verified, actually played head-to-head fixtures divided by scheduled head-to-head fixtures due by the cutoff. Count each fixture once. Due defaults stay in the denominator; byes sit outside it because they have no opponent. A pending or disputed result needs a separate check of whether play occurred. Flag unknown play rather than treating it as confirmed non-play.
  • Season completion: cohort entries meeting a rule declared before analysis, divided by the starting approved-entry cohort. State the required participation through the season; playoff qualification answers a different question.

For the fixture rate, state how you handle cancellations, superseded fixtures and changed due dates. Show those counts so a schedule change can't quietly hide lost play.

Here's a hypothetical example (not School Esports data). Say 20 entries are approved and 15 have played by week two: 15/20 is 75%. The other five might be two bye-only entries, a withdrawal and two still waiting on a fixture. Quietly drop them and you'd report 100%, without an extra game being played. Show those groups separately, and put the raw numbers and date beside every percentage. A zero denominator makes the rate undefined; missing information needs its own label too.

How do you measure whether schools come back?

Count the unique schools in last season's cohort with a qualifying approved entry by the comparable cutoff this season. Divide by all schools in that prior cohort. Be clear whether it means schools that registered, were approved or actually played, and compare the same events and point in the registration cycle.

As a hypothetical, say 12 schools played last season and nine have an approved entry by the next comparable deadline. School re-enrolment is 9/12, or 75%. If the new intake has 15 schools, 9/15, or 60%, is its returning-school share. For an eligible-to-return rate, set eligibility in advance and restrict both numerator and denominator to that eligible group. Show the full-cohort rate, exclusions and reasons alongside it.

Keep school return and player return separate. A school coming back with new students has still returned. For player return, count prior participating players who actually play in the following season against the stated prior player cohort. Graduations and eligibility changes need an explicit policy. Linking student records across seasons needs a clear purpose and proper authorisation.

Jonathan Jansen describes schools moving beyond a "pilot" stage, where scepticism, senior leadership resistance or the perceived admin load may hold them back. In his experience, teachers become ready to invest more and recruit students once they see the "massive social and positive impact". That's his practitioner judgement, rather than a measured retention result. Watching whether pilot schools return is a useful check to include in a business case for a sustainable league.

How should you read student survey results?

Read them as students' own accounts of their experience. The School Students section of NZ Esports' 2025 Gamer Survey infographic reports that 60% said esports made them more confident to be involved in other school activities, and 91% said it helped them socially. These self-reports don't measure actual uptake of other activities or prove esports caused a change. Survey organiser Jonathan Jansen confirms 504 responses overall. That total includes adults and isn't the school-student or question denominator; those counts aren't shown in the infographic.

When breaking results down by game or school, combine or suppress small groups under your school's disclosure policy. Even without a name, a handful of responses can identify a student. Collect only what your question needs and restrict access appropriately.

Why are schools dropping off between entry and play?

Your numbers show where schools drop off. Talking with schools helps you understand why. Possible causes include:

  • approval friction
  • unavailable fixtures
  • fees
  • timetable clashes
  • technical access
  • teacher handover
  • a changed game line-up

Treat each as a hypothesis to check. If a rate moves after you change something, that before-and-after shift doesn't prove your change caused it. Returning schools aren't a random sample of all schools either. No retention target follows from these examples.

Can School Esports produce these reports?

School Esports' demo guides describe approval, fixtures, results and school billing as separate stages. They don't establish an automated retention report for every league. The School Esports homepage advertises analytics; ask the team to demonstrate the fields and reports available for your definitions before relying on a particular cohort dashboard, export or player identifier.