Picture a league night with a dozen fixtures. The matches finish, the students head home, and the organiser spends the next morning chasing results through emails, chat messages and screenshots, then working out which of two different scores for the same match is right. Each school that joins adds to the pile. The way through is to stop being the person who gathers every score. Let the teams who played report the result, get their opponent to confirm it, and keep your own time for the results that need a decision.
Who should report the score in a school esports match?
Leave it with the two teams who played. They saw the final screen and have the evidence, so they're best placed to get it right first time. One side submits and the other confirms or disputes. Keep organiser time for missing responses, disagreements and results that need authorised help. When one person collects every score, the whole league moves at the pace of their inbox, and that gets slower with every team you add.
A teacher doesn't have to make every click. Jonathan Jansen from School Esports describes student coordinators as "the champions and passionate students within every school" who teachers can trust with a bit of extra leadership. In his account, permitted jobs include submitting or confirming scores, roster changes and rescheduling. The demo's coordinator guide ties access to an approved teacher's appointment and the event permissions. A proposed reschedule still needs the opponent's acceptance and an updated fixture time. Billing, fee-bearing approvals and school-side disciplinary decisions stay with teachers, subject to the school's own authority rules.
How it works on School Esports
The School Esports demo's match night guide describes submitting head-to-head scores inside the fixture, keeping each result with the right teams and match. The opposing team confirms or disputes the score; you cannot confirm your own team's submission. Revised scores need opposing review, reminders prompt outstanding results, and authorised staff can review unresolved submissions (scores and disputes guide). Check the actions available for your role and event.
What should you decide before the first match?
Settle four things as part of your league setup: who submits, who checks, the reporting deadline for your event, and who takes responsibility for any result still unresolved after it. Put those answers somewhere teams will actually read them, so nobody has to ask on match night. The last one matters more than it might seem. The demo's scores guide says a pending result is not automatically accepted after 24 hours. Confirm the rule for your event, and give someone responsibility for following up unanswered results.
If your event uses School Esports' optional rewards, you could choose to recognise useful participation such as finishing the result workflow. Keep that promise modest. The demo's rewards guide makes eligibility dependent on site settings, and submitting a result doesn't guarantee an immediate award (rewards guide). They sit alongside clear expectations and an easy way to get help.
What should happen when teams disagree on a result?
The disagreement becomes an exception with a clear route to someone authorised to decide it. Raising a ticket doesn't settle anything on its own, so make sure a named person or role owns the outcome. It also helps to sort exceptions by type, because different people should be making different calls:
- Score errors: the submitted result is wrong, for example the teams are in the wrong order or the series score is off. The reviewer checks both against the relevant evidence.
- Disputed defaults: one team says the other didn't turn up. The demo's scores guide directs teams to the opponent-default option rather than inventing a played score. It still needs confirmation or staff review; a disputed default needs staff resolution.
- Conduct concerns: these are about behaviour, whatever the score says. They go to whoever handles conduct for the competition. Authorised competition staff handle sanctions under the event rules, while school-side discipline stays with teachers.
Keep each dispute in one explanation linked to its fixture, with relevant game screenshots. The demo's scores guide says staff review disputes and can correct results. If a score is already final, ask staff rather than submitting a second result. For help during a match, use Request an Admin inside the fixture; for school, roster or attendance questions, contact the teacher; for longer-running problems, open Support (help guide). Include the competition, fixture, time, and what you expected compared with what happened. Leave out personal details that aren't relevant.
Why do late results hold up the rest of the league?
Standings, and in many formats the next draw, are built from those results. Toornament's Swiss rounds explanation gives one example: the first round uses starting seeds, and later pairings use earlier results. A missing or disputed score leaves those pairings working from an incomplete picture. Not every format has to wait for every result, but if yours builds later rounds from the standings, review pending results and open disputes before publishing the pairings that depend on them. Timely, confirmed results keep the whole competition moving, so give your reporting process as much thought as your fixtures.
For the reporting and escalation side, see the NZ Esports league administration case study and moderation, reporting and teacher involvement.
