Two divisions, one field, and a colour code doing all the work
Day one: a regional primary schools carnival. Eight teams in one age group, six in another, three fields, a tight 10:00–1:30 window. The balance was actually sound — every team got exactly four games. The problem was the middle field, which alternated between the two divisions row by row, with nothing but the shading of a photocopied, fold-creased page to say which game belonged to which age group.
| Time | Field 2 | Division |
|---|---|---|
| 11:00 | Ironbark v Bluegum | Yr 5/6 |
| 11:20 | Ironbark v Melaleuca | Yr 3/4 |
| 11:40 | Banksia v Ironbark | Yr 5/6 |
| 12:00 | Melaleuca v Banksia | Yr 3/4 |
The division column didn't exist on the real sheet — we've added it. On the day, colour was the only label, and the same school names appeared in both divisions.
A referee scoring the 11:20 game against the 11:00 ladder is one smudged photocopy away. The fix costs nothing — one field per division fits comfortably in the same window — but it has to be caught before the sheet is printed, and there's no checker on a whiteboard.
Failure mode: structural — divisions interleaved on a shared field, with formatting as the only guardrail.
37 teams, 74 games — and five teams living on two schedules
Day two: a club carnival for the youngest age group. Thirty-seven teams across four fields, 74 games. Two of the four fields were built beautifully — clean ten-team pools, even rest, no complaints. The other two shared seventeen teams between them, and that's where the day frayed: five teams had games split across both fields, so their families needed two schedules to find one child's day.
| Time | Fixture | Field |
|---|---|---|
| 9:20 | Coolibah v Wattle | D |
| 10:00 | Coolibah v Jacaranda | B |
| 10:40 | Coolibah v Redgum | B |
| 10:40–2:20 | — no games — | |
| 2:20 | Coolibah v Banksia | B |
Three games in the first 80 minutes across two fields, then a three-and-a-half hour wait for the last one. These are six- and seven-year-olds.
Here's the thing: the games themselves were fine. As a desk exercise we re-cut the same 34 games into two self-contained pools — nine teams on one field, eight on the other, every club's teams kept together. Same teams, same number of games, same day length. Every team kept its four games with at least 40 minutes' rest, and the longest wait dropped from 3½ hours to about 2. Nothing about the day needed to change except the split.
Failure mode: allocation — a sound game count undone by how teams were divided across fields. Invisible until you trace one team's whole day.
The best draw we saw all month still couldn't answer one question
Day three: a schools carnival run by an experienced regional body. Forty-three teams, five divisions, eight fields, 86 games — and the draw was excellent. Self-contained pools, complete round robins within them, every team on exactly four games, not a single back-to-back anywhere. This is what a draw looks like when someone who's done it for years builds it. And it still ran into three walls that had nothing to do with the organiser's skill.
| Time | Field 2 | Field 6 |
|---|---|---|
| 10:20 | Redgum v Ironbark | Redgum v Ironbark |
Not a misprint. Two schools each fielded teams in two divisions, and the paired fixtures landed in the same timeslot. Identical words, different children, three fields apart — and the sheet gives a parent no way to tell which is theirs.
Second wall: the draw only made sense next to a separate pools legend — two sheets, cross-referenced by highlighter colour. Third, and biggest: one school had six teams across five divisions, with four of them playing simultaneously at one point. The question every teacher and parent actually has — where do my school's teams need to be, all day? — doesn't exist on any sheet. Everyone builds their own crib notes in the car park.
Failure mode: none, structurally. The ceiling here isn't the organiser — it's that paper can only show one view, and every family needs a different one.
The pattern across all three
Each day failed — or strained — at a different layer. Structure can be fixed with discipline. Allocation can be fixed with care. But the third layer can't be fixed on paper at all, because it's not a drafting problem: a printed draw is one fixed view of a day that every family experiences differently.
- One source of truth. A live draw and ladder at a short link — no photocopies, no versions, no highlighter code.
- A personalised view. Star your team and the day rearranges around you: your next game, your field, pinned to the top.
- Ambiguity removed. Every fixture carries its division — two games with the same names can never be confused.
- Scores where they happen. Referees score at the field; the ladder updates everywhere, instantly.
All of the above is live in Tryda today — it's how the platform already runs gala days, not a roadmap.