PoolSolve
Menu
Features Free tools Formats Sports Guides Help

Free tools

Browser-only schedule generators - no account needed; team names you type never leave the device.

Rest time between matches

Fair rest is the difference between a schedule that merely fits the day and one that is actually equitable: a team playing three matches in a row while its opponent rested for an hour is competing at a real disadvantage. This guide covers how much rest teams need, how to enforce it in the schedule, and the trade-offs when rest windows fight against a tight finish time.

How much rest is enough?

Rest needs scale with match length and intensity, not just age. Practical baselines for amateur and youth events:

  • Short matches (under 20 minutes): at least one full slot off between games - play one, sit one. A 20-minute match with a 25-minute slot means a team finishing at 11:25 should not start before 11:55.
  • Standard matches (30-60 minutes): rest at least as long as a match. A 40-minute game should be followed by 40+ minutes before the next kickoff.
  • Full-length matches: two hours minimum, and for most one-day events full-length matches are the reason the format has to change rather than the rest window shrinking.

Cap consecutive matches too. Two in a row is a reasonable ceiling for adults; for younger or shorter-format events, one at a time is better. Daily load matters as well as per-gap rest - three or four short matches per day is plenty for children, five or six for adults. And guard the extremes: no team's first match should be immediately after a long wait such that they play the last three consecutively, and the teams meeting in a semifinal should have had comparable rest since their previous games - a finalist who played 90 minutes ago versus one who played 20 minutes ago is the classic unfair-bracket failure.

Why schedules produce unfair rest by accident

Rest violations are rarely deliberate; they fall out of format arithmetic. With 8 teams and 2 fields, a round robin needs 14 rounds and each team plays 7 matches - so on average each team plays every second round. Any pairing order that clusters a team's games creates a run of three with no gap, while another team's matches happen to spread evenly. Hand-built schedules hide this until someone highlights each team's row.

An odd number of teams is the helpful exception: with 7 teams someone has a bye every round, which gives an automatic rest slot to rotate around. The scheduling an odd number of teams guide shows how the bye distributes. Knockout brackets create the opposite problem - winners return on short turnaround, which is why seeding a tournament and bracket-side rest symmetry matter together.

Enforcing rest in the schedule

The reliable way to enforce rest is to make it a constraint at generation time rather than a fix afterwards. In PoolSolve, rest windows are part of the rules the automatic scheduling engine applies: set a minimum gap in slots or minutes and a maximum run of consecutive matches, and generated schedules honour both - teams simply are not placed in back-to-back slots beyond the cap. The tournament schedule generator lets you test the effect quickly: generate a grid for 8 teams on 2 fields and scan each team's column for adjacent matches.

If you are scheduling by hand, the check that catches problems is a per-team timeline: list each team's matches in order and mark the gap before each. Anything under your floor gets moved to a later round, which is only possible if you left slack - one reason the advice in how long will the tournament take includes a buffer.

The fairness checks beyond the floor

Minimum rest is the floor, not the whole job. Three subtler checks:

  1. Rest parity for shared opponents. If Team A plays Team B in round 10, compare how long each rested since round 9. Parity matters more than the absolute number - 30 minutes each is fairer than 55 versus 25.
  2. Cumulative load. A team whose matches all cluster mid-day plays a harder tournament than one spread evenly, even with identical minimum gaps.
  3. Referee rest. Teams or referees covering matches need recovery too - a refereeing stint straight after playing is the hidden third match. See assigning referees fairly.

When rest fights the clock

Rest rules consume calendar time, so on a tight day something gives. In order of preference: add a field (parallel capacity preserves rest at the same total hours), shorten the changeover rather than the match, reduce the match count by changing format, and only then relax the rest floor - and if you relax it, relax it for everyone and tell coaches. A rest rule that quietly bends for the last three rounds is worse than a lower honest floor, because the teams scheduled late are usually the ones still fighting for qualification.

Multi-day events

Overnight rest resets most of this - a fresh morning makes up for a brutal Saturday. But two rules carry across days: the last matches of day one should not involve the teams opening day two (give the late finishers the late start), and the knockout day should be lighter than the group day, because bracket matches are the ones players remember limping through.

The one-day pattern that works

For the running example - 8 teams, 2 fields, 20-minute matches - the practical target is: play one, rest at least one, never more than two in a row, no team refereeing immediately after playing. That produces a day where every team's 7 matches spread across the 14 rounds with gaps, the day still finishes inside 6 hours of play, and nobody can fairly claim the schedule decided the result.

Generate it now

Try the steps in this guide with a free generator - no account needed, nothing to install.

Open the free generator

Related guides

Put it into practice

Build your first schedule in minutes - every feature is free.

Create a free workspace