A school esports league brings schools together to compete, so knowing which school each team represents matters to the competition's integrity. An account holder claiming a connection to a school and a team approved for a tournament are two different things. Before a match goes ahead, a responsible adult should have confirmed that school connection through the event's process, and each player should have been checked against the event's rules. Signing in, choosing a school from a dropdown or using an email address that looks like a school one doesn't settle either check on its own. If you're setting up the process, start with school esports registration and teacher onboarding.
Is registering for a school esports event the same as being approved?
No. Registration puts an entry into the system. Approval means it has passed the event's current registration checks. Along the way, an entry can move through several stages:
- account access, where someone can sign in
- an approved teacher role
- a submitted entry for a specific tournament
- any teacher decision the event requires
- the resulting status, such as pending or approved
- a published fixture and a team that's ready to play
Not every event uses every stage. The School Esports demo guides describe teacher validation as an event-specific requirement (getting started, student teams). Paying an entry fee is a separate step, and sorting out billing doesn't confirm anyone's identity. The demo's team status guide explains that duplicate participation, school locks, active restrictions, closed registration or unpaid school billing can block an entry. An approved status therefore doesn't guarantee a fixture or eligibility from then on.
What should organisers publish before school esports registrations open?
Start with the eligibility requirements and the process for corrections and decisions. Explain what the event needs for school, age or division and game identifiers, using the actual rules for that game and event. Then make it clear who decides borderline cases and where participants can ask for a review. Keep the different permissions clear, too. Teacher approval, school permission, parent or caregiver permission, authority to handle student information and game or event eligibility are separate matters. Check the requirements in the school policies, event rules, platform documents and game-publisher terms that apply. The demo's platform terms describe school and operator responsibilities, but an entry's approval status isn't proof of age, account eligibility, publisher permission or legal compliance.
Who approves a school esports team's entry?
It depends on the event, with a teacher or another responsible adult at the centre of the organiser's school process. Where teacher validation is required, it connects an entry to an adult who can confirm the school relationship and support the students. The School Esports demo's teacher setup guide says an organisation administrator reviews teacher registrations. A pending teacher can look through entries, but their approval decisions are held until their own registration is approved. Further organiser review or eligibility restrictions may still apply to the team.
That guide asks reviewers to check the school, event, game, every player's details and eligibility, and authority to submit the information. Check every listed player and substitute, with the right names and game identifiers, in the right tournament for the right school. Approved teacher access and roster editing are separate permissions, so use the team controls available to you or ask the responsible teacher or organiser. The guide doesn't describe employment-document checks or promise a verified identity. Decide what your process actually needs and ask only for that, rather than routinely collecting passports, birth certificates or full school records.
Can student coordinators approve teams?
Sometimes. School Esports founder Jonathan Jansen describes student coordinators as "the champions and passionate students within every school who teachers can trust with some extra leadership responsibilities." The demo's coordinator guide ties access to an approved teacher's appointment, its duration and permitted school events. Within those limits, Jonathan says coordinators can make roster changes, approve teams without billing requirements, help approve or reschedule matches and submit or confirm scores. A reschedule still needs the opposing side to accept the official request and the fixture to show the change (rescheduling guide). Billing data, fee-bearing approvals, school financial commitments and school disciplinary decisions stay with teachers or authorised school adults. Competition administrators retain their own responsibility for sanctions. Coordinator access isn't an organisation-administrator role or permission to override tournament rules.
Can a student play for two schools in the same esports tournament?
The demo's student team guide says no: an approved school team establishes the student's school for that tournament, and they cannot represent another school in the same tournament. That lock belongs to the tournament; it isn't a permanent school assignment across every event. Genuine changes, such as a school transfer or a roster replacement, go through the responsible teacher or organiser and need a decision under the event's rules. Creating a duplicate entry to get around the lock just adds another problem. Record the decision through your usual process instead.
Who should see a student's eligibility information?
Only the authorised people who need it to make the decision. Opponents need confirmation that an entry is eligible, rather than copies of a student's supporting information. The demo's privacy guide describes opponent-facing school rosters as showing first names and in-game usernames, with student emails, last names, student IDs and other private roster fields excluded. It describes access for authorised teachers, team managers and staff as limited by role, school, team, event and organisation. Check your site's notices and permissions. When explaining a decision to the other team, share the outcome and anything they need to do. Reasons that reveal a student's private circumstances stay with the people who need them.
School Esports (schoolesports.org) was built independently with national federation expertise. Its demo guides describe administrator review of teacher registrations, pending and approved entry states, and a school lock within each tournament. Schools and organisers still make the eligibility decisions under their event's process.
You can also read about who can see student information and consent and safeguarding responsibilities.
