A spreadsheet and a Discord server can get a small school league off the ground. As it grows, though, every team brings more information to keep lined up across separate places, by hand. Jonathan Jansen from School Esports describes the weekly routine of finding the right team to play, pinging players on Discord and waiting for a reply. In his view, a teacher's workload depends almost entirely on the tournament or platform being used, and with spreadsheets and Discord "sometimes you don't even get a game if the other team is unresponsive."
Moving to a dedicated platform works best with a planned handover: decide where each official record will live, re-enter what's current, try out the new process and switch over at one clear point. The current demo guides don't describe a one-click migration, so allow for some careful manual work. If you're still choosing a school esports platform, check that it supports the workflows your league needs before planning the move.
Why do spreadsheets and Discord get harder as a league grows?
One change can leave you updating several places that don't connect. Swapping a player can affect teacher approval, eligibility, match access and billing, and changing the spreadsheet doesn't update the rest. If a reschedule is agreed in chat, the organiser still has to remember which conversation holds the latest agreement. Over time, the league can also come to rely on personal contacts and the informal knowledge of one staff member. Keeping official fixtures, rescheduling and scores in one platform, with proper school and teacher relationships, is meant to reduce those scattered records, provided the move itself is handled well.
What should you move, and what should stay behind?
Move only the current, approved records the new process needs. Start with what you actually use: authorised adult contacts, approved rosters, upcoming fixtures, unresolved results, open support matters and outstanding billing. Give each one an owner and an authoritative version, then decide what needs re-entry and what stays in its existing system. Confirm school authority before moving student information. This inventory is a handover plan, not a list of supported imports.
Old chat messages rarely need to come across. For an unresolved dispute or a school record-keeping obligation, ask authorised staff what needs preserving, who can access it and when it should be reviewed. Keep only relevant evidence in a restricted archive; don't copy personal account packages or whole chat histories by default. Plan where new match communication will happen, too, so schools know which space to use after the switch.
Can you import existing rosters into School Esports?
The demo's team management guide describes bulk entry through a supplied template with validation, and reuse of an earlier roster when that option is offered. Check what's available on your league's site. Neither feature is described as bringing across historical results, chats, billing or organisation settings.
Try a small sample with the actual template first, using synthetic data wherever possible. If real student details are necessary, confirm authority under the registration notice before submitting them. Check identifiers, school and team links, duplicates, eligibility and sign-in matching. Then review the errors and the saved result, because a successful upload doesn't mean every entry is eligible. Teacher registrations also need organisation-administrator review, as the demo's teacher setup guide explains.
How do you test the new process before going live?
Arrange an organiser-approved practice round with permitted test records, following the steps a school will use: an approved teacher signs in, a team finds its correct roster and fixture, someone requests an official reschedule, a result is reviewed and someone contacts support. The demo guides provide checks to confirm on your event's site. A time change needs the official request, the opponent's acceptance and the updated fixture within the displayed event window, so agreeing in chat alone won't move the match. Scores go to the opponent to confirm or dispute, with possible staff review, and billing still needs your usual finance checks.
How do you avoid running two conflicting schedules?
Publish one cutover time and tell every school where official fixtures, changes and results will be recorded from then on. Give each workflow a single authority during the transition. Editing the spreadsheet and the platform independently can produce competing versions. Switch before a new competition phase if you can, keep a fallback contact for anyone who gets stuck, and reconcile open results, support matters and billing before retiring the old process.
What changes for teachers after the move?
In Jonathan's view, once a good platform carries the routine admin, a teacher's workload depends on how developed their club is. They can mainly be a facilitator, enabling students to organise and play and assigning student coordinators, which he describes as becoming very hands-off. Teachers who want to get more involved might run a weekly club, development drills, or esports curriculum built to match learning outcomes. That's his practitioner judgement. The extra involvement is a choice about developing the club, separate from routine league admin. Agree with the organiser which routine tasks students can handle. Keep billing, fee-bearing approvals and disciplinary decisions with teachers, and make adult safeguarding responsibilities clear.
After your first season on the platform, look back at what needed correcting, where schools asked for help and which settings are worth keeping. Conditional roster reuse may help returning teams, though their details and eligibility still need checking again.
Planning a move to School Esports? School Esports was built independently with national federation expertise. Its demo guides describe school and teacher relationships, recorded fixtures, official reschedule requests and opponent score review. The roster guide sets out the bulk entry steps; contact the team to confirm the migration and export scope available for your league.
You can also read about the NZ Esports league administration case study.
