A weekend tournament schedule is one piece of arithmetic and one set of decisions. The arithmetic is fields × usable hours ÷ slot length, which tells you how many games you can hold. The decisions are pool size, how many advance, and the tiebreaker order — and the tiebreaker order is the one that ruins Sundays when it is left until Sunday.
Here is the whole thing, worked through on a real grid.
How many games can one field hold in a day?
Usable hours divided by your slot length. The slot is game time plus changeover, and the changeover is what directors underestimate.
A slot is:
- Game length — a time limit, an innings cap, or both. Most youth formats run 1h20m to 1h45m.
- Changeover — teams off, teams on, infield drag if you do one. Fifteen minutes is realistic; ten is optimistic.
So a 1h30m game with a 15-minute changeover is a 1h45m slot. In a ten-hour day (8am first pitch, last game starting by 6pm) that is:
10 hours ÷ 1.75 hours = 5.7 → 5 games per field per day
Round down, always. The fractional game is the one that finishes in the dark.
With four fields: 20 games a day. With six fields: 30. That number is the hard ceiling on everything else, and it is worth calculating before you decide how many teams to accept.
How do you size pools to the team count?
Work backwards from the guarantee you have promised.
Pool sizes of four and five are the workhorses. In a pool of four, each team plays three — which conveniently satisfies a three-game guarantee in pool play alone. A pool of five gives four games but takes ten games to complete instead of six.
| Pool size | Games each team plays | Games to complete the pool |
|---|---|---|
| 3 | 2 | 3 |
| 4 | 3 | 6 |
| 5 | 4 | 10 |
| 6 | 5 | 15 |
So for 24 teams: six pools of four, 36 pool games, every team guaranteed three. For 20 teams: four pools of five (40 games, four guaranteed) or five pools of four (30 games, three guaranteed). The choice is a trade between your guarantee and your field capacity.
The rule: pools of four when field time is tight, pools of five when you have capacity and want a stronger guarantee.
A worked 24-team, 4-field, two-day grid
24 teams, four fields, three-game guarantee, 1h45m slots.
Capacity check first. Four fields × 5 games/day × 2 days = 40 games available.
Format: six pools of four = 36 pool games, plus an 8-team single-elimination bracket = 7 games. Total 43. That is three over capacity, so something gives.
The fix: run pool play across Saturday and Sunday morning, bracket Sunday afternoon, and add a fifth field for Sunday only — or drop to a 4-team bracket (3 games) for a total of 39. Taking the second option:
| Field 1 | Field 2 | Field 3 | Field 4 | |
|---|---|---|---|---|
| Sat 8:00 | A1 v A2 | B1 v B2 | C1 v C2 | D1 v D2 |
| Sat 9:45 | A3 v A4 | B3 v B4 | C3 v C4 | D3 v D4 |
| Sat 11:30 | E1 v E2 | F1 v F2 | A1 v A3 | B1 v B3 |
| Sat 13:15 | E3 v E4 | F3 v F4 | A2 v A4 | B2 v B4 |
| Sat 15:00 | C1 v C3 | D1 v D3 | E1 v E3 | F1 v F3 |
| Sun 8:00 | C2 v C4 | D2 v D4 | E2 v E4 | F2 v F4 |
| Sun 9:45 | A1 v A4 | B1 v B4 | C1 v C4 | D1 v D4 |
| Sun 11:30 | E1 v E4 | F1 v F4 | A2 v A3 | B2 v B3 |
| Sun 13:15 | C2 v C3 | D2 v D3 | E2 v E3 | F2 v F3 |
| Sun 15:00 | Semi 1 | Semi 2 | — | — |
| Sun 16:45 | Final | — | — | — |
That is 36 pool games in nine slots plus a four-team bracket, inside capacity, with every team playing three.
What to check on any grid you build:
- No team plays two slots back to back on different fields
- Every team gets at least one slot of rest between games
- Pool play finishes with enough margin to seed the bracket before it starts
- The last game of Saturday is not a team's first game of the weekend
That last one is a courtesy that costs nothing and gets remembered.
How do you seed out of pool play?
Publish the method before entries open, not after the games.
The common approach is pool winners seeded by record, then by tiebreaker, with wildcards filling the remaining bracket slots. The part that needs stating explicitly is what happens when records are equal — which in a four-team pool happens constantly.
What is the tiebreaker order?
Whatever you publish, in a numbered list, before the first pitch. A defensible default:
- Head-to-head — if the tied teams played each other
- Fewest runs allowed — rewards defence and cannot be run up
- Run differential, capped — cap it (commonly at 8 or 10 per game) so a blowout does not decide a bracket
- Runs scored
- Coin flip
The cap in step three is the important one. Without it you have created an incentive to run up the score on a 10U team, which is a bad weekend for everybody and entirely your fault as the director.
Three-way ties need their own sentence: state whether head-to-head applies only when all three played each other, and what you do when it is circular. "If the tie is circular, proceed to the next criterion" is one line and saves an hour.
Where does the schedule fall apart?
Four places, all predictable.
- Games run long. A time limit with no drop-dead means one slow game pushes every game behind it on that field. Publish a drop-dead time — no new inning after X — and hold it.
- The published version is stale. The schedule was edited in a spreadsheet and the version coaches are reading is yesterday's. This is the single most common failure and it is a systems problem, not a scheduling one.
- Results do not reach the bracket. Pool results live in a notebook, so the bracket is seeded from what somebody remembers.
- A change reaches some teams. A field move goes out to a group text that half the coaches have muted.
Three of those four are not scheduling problems at all — they are the same "two records of the same fact" problem that breaks everything else at scale.
Questions directors ask
How long should a youth baseball game slot be?
Game length plus changeover. Most youth formats run 1h20m to 1h45m of game time; add 15 minutes. Build the grid on the slot, never on the game length, or you will be an hour behind by lunch.
Should we do pool play at all?
For a weekend event with a game guarantee, yes — it fills the guarantee and produces seeds. For a one-day event, straight bracket with a consolation round is usually better, because pool play needs completion before the bracket can start.
How many teams advance to the bracket?
A power of two — 4, 8 or 16 — otherwise you are handing out byes, and a bye in a youth bracket is worth arguing about. Size the bracket to your remaining field time, not to how many teams you wish could advance.
What about a drop-dead time?
Publish one. "No new inning after 1h30m" is the standard form, and it is the only thing that stops a single game putting a field behind for the rest of the day.
Can we change the schedule after publishing it?
You will have to — weather, forfeits, a team stuck in traffic. What matters is that the published version is the only version, so a change reaches every affected coach and the bracket reads from the same place. That is the part software actually earns its money on.
Related: how to run a 60-team tournament and the rainout plan for when this grid has to be rebuilt at 6am. We build schedules, brackets and field assignments as part of the back office for tournament organisations.