Good match-day support for a school esports league starts with a plan before the first match gets under way: who's on hand, which calls each person can make, and where each sort of problem goes. Your platform can give players a clear way to ask for help and suggest ways to rescue a fixture, but someone with the authority to decide still needs to be there to answer. If you're still setting up the league itself, start with how to run a school esports league.

Why does school esports support get busy all at once?

When your school matches start in the same narrow after-school window, support can get busy quickly. When lots of teams log in together, their problems can land together too: an opponent who hasn't appeared, a roster question, a disagreement over a score. Have your people ready for that start, when they're most likely to be needed, and keep them free of other jobs until the first round has settled.

Who should be on hand before the first match starts?

At minimum, you need a named lead who makes the final call, a rules contact for each game you run, and a backup. Share those names with your team before match day so nobody's left guessing who decides whether a late team gets a default. Then publish the help route players and teachers should use, along with the hours you actually plan to staff it. A clear finish time is more useful to a teacher than a vague promise of support all evening. Check that each person has the event access they need, and keep their duties within the responsibility you have assigned.

Where should players and teachers go for help?

It depends on the problem. Agreeing on this beforehand saves a lot of back and forth on the night.

  • Problems in the match itself, like a missing opponent, a score dispute or a rules question, go to your admins or referees.
  • School matters, like the roster, attendance, or a student's behaviour or wellbeing, go to the school's teacher, along with any disciplinary decision.
  • Longer-running account, event or rewards problems go into a support ticket. If a fault is stopping the current fixture, use match-room help too.

Be upfront with schools about where match support stops. A referee looking after a fixture isn't supervising the students in it. An urgent student safety or wellbeing concern needs the school's immediate safeguarding route; don't leave it waiting in a tournament dispute queue. Nothing in your match-day plan replaces the school's own processes.

On School Esports: The demo's get help and troubleshoot guide describes Request an Admin inside the match room, teacher help for roster, school permission and attendance questions, and dashboard Support for longer-running problems. The schoolesports.org homepage also advertises a referee panel for dispute tickets. These are help routes. Who answers, and when, still depends on your league's staffing plan.

What does a referee need to sort out a problem quickly?

A referee needs the fixture, the teams and players involved, and what was said in the match room, all kept together. Otherwise, they have to piece the story back together before making a call. Ask for the competition, fixture, time, what should have happened, what actually happened and any error message. Leave out private details that have nothing to do with the problem. Keep one record per incident so your lead or another referee can pick it up without starting again. If something can't be settled on the night, tell the teams what you know and what happens next. Check any agreed change against the official fixture: a reschedule needs the opponent's acceptance and an updated recorded time. A final score correction belongs with authorised staff, rather than a second result submission.

Some problems can be headed off before play. The head-to-head match night guide takes players through checking their fixture, rules, format and roster first. Those are sensible checks to make before everyone is ready to play.

What happens when a team doesn't turn up?

Your event's waiting and default rules come first, and they should apply the same way to everyone. Where you can, though, it's worth trying to get the team that did turn up a game. In his 6 October 2026 account, Jonathan Jansen from School Esports describes its Smart Match Recovery this way: on game day, it automatically pools teams with an inactive opponent and suggests replacement matches that are valid within the tournament format. A valid match means teams in the same division or within an appropriate Swiss win/loss difference, with no repeat opponents unless the format allows them. The aim is to stop a no-show becoming a bad experience for the school that showed up.

A tournament administrator has to approve each proposed match before it locks in, and can swap or override it. This is where having clear authority matters. In Jansen's words, "simply getting students a game can be more important sometimes than a perfectly strict tournament format", so agree beforehand who approves recoveries and when bending the format is reasonable. A replacement isn't always possible, either. The demo's missing opponents and match recovery guide explains the participant side. When recovery is offered, it has conditions and a time window, and it can end with a changed fixture or with no opponent at all. Check the updated fixture and room before starting to play.

What happens to problems still open when the session ends?

They need a handover. Before supervision finishes, your lead should check for anything unresolved, send each affected team a short note on where things stand, and pass the incident record to whoever picks it up next. Check that the teacher has any student wellbeing concerns and knows the next step. Urgent concerns should already have gone through the school's immediate route, rather than waiting for this handover.

You can also read about moderation, reporting and teacher involvement.