Running an inter-school tournament is one of the more satisfying things a school can organise. It’s also one of the more logistically demanding. Dozens of students, multiple schools, fixtures running simultaneously, results to record, parents to communicate with, and usually one or two things that don’t go to plan on the day.
This is a practical guide to the parts that can be planned for.
Six to eight weeks before: programme and invitations
The first decision is format. Round-robin, knockout, group stages followed by knockout, Swiss — each has different implications for how many fixtures you need, how long the day will run, and how you handle odd numbers of teams. For most school tournaments with six to twelve teams, a round-robin within groups followed by finals works well. It guarantees every team plays multiple fixtures regardless of results, which matters when students have travelled a distance to attend.
Once you have a format, you can calculate how many fixtures you need and how long the day will take. Build in more time than you think you need between fixtures. Things run late. Referees need breaks. Students need to get between pitches.
Invitations should go out six to eight weeks in advance for larger tournaments, four to six for smaller ones. Include everything the other school’s coordinator needs to make a decision and plan: date, format, age group, what’s included (food, officials, equipment), whether there’s an entry fee, and a clear deadline to confirm.
Make the confirmation process as simple as possible. The harder it is to confirm, the more chasing you’ll do.
Four weeks before: confirmations and waiting lists
By four weeks out you should know which schools are confirmed and which are still deciding. If you have more interested schools than places, a waiting list becomes important — both to manage fairly and to fill places quickly if a confirmed school drops out.
Be clear about your cancellation policy. If a school drops out a week before, do you fill from the waiting list? What’s the cut-off? Having this written down before it’s relevant means you’re not making decisions under pressure when it happens.
Send a second communication to confirmed schools around this point with more detail: arrival time, parking, what to bring, who to ask for on arrival. The information that seems obvious to you is not obvious to a PE coordinator at another school who is managing their own term.
Two weeks before: fixture schedule and communications
Build the fixture schedule with enough detail that each school can brief their students on what to expect. Which group are they in? What time is their first fixture? Where are they playing?
Send this to school coordinators and ask them to forward it to students and parents. Don’t rely on them to summarise it accurately — send something they can forward as-is.
Think about what parents at your own school need to know: transport arrangements, expected return time, what to bring, whether spectators are welcome and where they should go. This information takes ten minutes to write and prevents thirty minutes of individual queries.
The day before: logistics check
Go through the day in sequence and identify every point where something could go wrong. Pitches marked? Equipment out? Officials confirmed and briefed? Results sheets printed? Someone assigned to manage the scoreboard or results system?
Have a contact number for each participating school’s coordinator. On the day of a tournament, things change — a school is running late, a student has been injured in training, they need to know where to park. Having to find contact details at that point adds unnecessary stress.
Prepare a simple briefing for anyone helping on the day — what their role is, who to escalate to, what to do if a fixture needs to be delayed.
On the day: results and communication
Recording results as fixtures finish is the part that most often gets left until the end and then becomes chaotic. Designate someone specifically for results — not someone who is also refereeing, organising fixtures and answering questions, but someone whose job is results. Every fixture that finishes, they record the score.
If you’re using a digital results system, results can be published as they happen — which means parents and students who aren’t at the venue can follow along. If you’re using paper, someone needs to consolidate at the end and publish.
Communicate with parents during the day if the schedule changes significantly. If the final is running an hour late, anyone planning to pick up a student needs to know.
After the tournament: results and follow-up
Publish final results the same day if possible. Schools that hosted students want to be able to tell them how they finished. A week later, the moment has passed.
A brief email to participating schools — thanking them for coming, sharing final standings, noting anything that will change for next year — takes fifteen minutes and builds the relationships that make future tournaments easier to fill.
Keep notes on what didn’t go to plan. Not as a formal debrief document, just a list. The things you’ll forget by next year are exactly the things that will catch you out again.
The systemic question
If you run tournaments regularly — whether as the host school or as a participating school managing your entries across multiple events — at some point the manual coordination becomes the limiting factor. Tracking which invitations have been responded to, which schools are confirmed, which are on the waiting list, what communications have gone out — doing this across multiple tournaments simultaneously in a spreadsheet is manageable until it suddenly isn’t.
Schools and associations that run tournaments at scale tend to move to a system that handles the administrative layer — invitations, confirmations, waiting lists, fixture schedules, results — so that the people running the tournament can focus on the parts that actually require their attention.
That’s not always necessary. A school running one annual tournament can probably manage with a well-organised folder and a good spreadsheet. But if the volume grows, or if the same coordinator is managing participation across ten external tournaments while also running their own, the administrative overhead becomes the thing that limits what’s possible.