How to organise a football tournament

Start from the clock, not the format

Most tournament plans fail the same way: someone picks a format they like, then discovers on the Thursday that it needs nine hours and three pitches they do not have. Work the other way round. You know when the first whistle goes, when the last team has to leave, and how many pitches you can put up. Those three numbers decide the format.

The arithmetic is unforgiving. A match slot is the match plus changeover: a 2 × 12-minute format on a single pitch is roughly a 30-minute slot once you count teams walking on and off. Six hours of daylight on two pitches is about 24 slots. That is your entire budget, including finals.

Choosing a format that fits the budget

With twelve teams and 24 slots, three pools of four (18 matches) leaves six slots for a knockout — semi-finals, a final and a third-place match, with room to spare. With twelve teams and 16 slots, you cannot do that, and the answer is fewer matches per team rather than shorter matches: cutting a 12-minute half to 8 to squeeze the bracket in makes every match feel like a warm-up.

• Pools into a knockout. The default, and the right one most of the time. Every team gets three or four guaranteed matches before anyone goes home.
• Straight round-robin. For six teams or fewer. Everyone plays everyone, the table decides it, no bracket needed.
• Pure knockout. Fast and usually a mistake for youth tournaments — half your teams have driven an hour to play one match and lose it.

If your team count is awkward, fix it by changing pool sizes rather than by giving one pool an extra match. Unequal pools mean an unequal number of matches played, which makes the qualification table incomparable — rank on points per match if you cannot avoid it.

What fits in a day

A rough guide, assuming 30-minute slots and every team guaranteed at least three matches. Count your own slots before trusting any of it — a 20-minute slot changes every row.

Twenty teams is a full day and then some. If that is your entry list and you only have six hours, add a third pitch or accept two guaranteed matches per team instead of three.

Pools: seed them, do not draw them blind

A blind draw regularly puts the two strongest teams in the same pool, and one of them is eliminated before lunch. Rank the entries on whatever you know — last year's result, division, the organiser's judgement — and deal them out in snake order: strongest into pool A, second into B, third into C, then back down the line. It takes two minutes and it is the difference between a good final and a good first-round match.

Write the tiebreakers down before the first whistle. Points, then goal difference, then goals scored is the standard ladder. Deciding them at 4pm, when they determine who is in the final, is how tournaments end in an argument in the car park.

The running order

Once the format is set, the schedule is mechanical: assign each match a pitch and a slot, and make sure no team appears twice in the same slot or plays two matches back to back. Give every team at least one slot of rest between matches; two if the format allows it.

Publish the running order with real clock times, not just round numbers. "Pitch 2, 11:30" is something a coach can plan around. "Round 3" is not.

Referees are the constraint you will underestimate

Two pitches running in parallel need two referees, all day, including during the lunch break you forgot to schedule. In practice that means three or four people rotating. Confirm them before you publish the schedule, not after, because losing one referee at 9am halves your throughput and there is no version of the plan that absorbs that.

What goes wrong on the day

• A team does not turn up. Decide the rule in advance: usually a 3–0 walkover, and the pool continues. Improvising it mid-morning is what causes disputes.
• The schedule slips. It always slips. Build one empty slot into the middle of the day; it is the cheapest insurance you can buy.
• Nobody knows the score. The single most common complaint at amateur tournaments is that the standings are on a whiteboard somewhere and nobody can find them.
• Weather. Have the shortened format written down before the day, not improvised in the rain.

Where Tornia fits

Set the tournament up as a season with a pool per group — each pool is its own tournament with its own table. Add every pitch as a named field on the venue, then generate each pool's round-robin as a one-day schedule: give the day, the first and last kick-off and the break, and the matches are placed across your pitches with clock times, no team on two pitches at once and no pitch booked twice across the pools. Assign referees in bulk across a whole round rather than one match at a time.

Rather keep it all in one place? The Groups + Knockout format draws the teams into pools, generates every pool's round-robin and adds the knockout matches after the last pool game, as one running order, with a table per pool. Once the last pool game is approved, the pool finishers move into the bracket on their own, and every knockout winner moves on to the next round; a level knockout match is settled on penalties. Only a place the tables can't settle — a tie no tiebreaker splits, or a group a team dropped out of — is left for you to fill.

On the day, results are entered by whoever you give that permission to — you, the team admins, or the assigned referee — and the pool tables recalculate on approval. Because the competition can be public, every coach and parent watches the standings and the bracket on their own phone from a link, which removes the whiteboard problem entirely. Player names stay off that page unless you publish the rosters deliberately.

One thing worth knowing before the day: the bracket is seeded from the pool tables when the last pool game is approved, and it is frozen as soon as a knockout match has a score entered (pending or approved) or is marked complete. A pool result corrected after that no longer reshuffles the bracket — a knockout match that hasn't been played yet can still get its teams set by hand.

A timeline that works

1. Six weeks out — confirm the pitches and the time window. Everything else depends on these.
2. Four weeks out — close entries. The team count fixes the format.
3. Three weeks out — seed the pools, generate the fixtures, confirm the referees.
4. Two weeks out — publish the running order with clock times and the tiebreaker rules.
5. The week before — confirm every team, and write the walkover and weather rules down.
6. On the day — enter results as they finish, not in a batch at the end.

Running a league instead? How to build a league schedule covers round-robin maths, byes and home-away balance.