Why Age-Aware Scheduling Beats a Spreadsheet

A spreadsheet can hold start times. It cannot hold the rules that make those times legal.

Division clocks are not interchangeable

11U and 18U do not share a game length, a rest window, or a reasonable last pitch. When you copy-paste a 90-minute grid across every age group, you either cheat the older kids out of innings or you send 11U home in the dark. Age-aware blocks (duration, rest, and last start) should be inputs, not after-the-fact coloring.

Rest is a constraint, not a courtesy

Back-to-backs, park hops, and “they can eat on the bus” are how you lose a Sunday championship to a tired arm. A solver that refuses illegal rest is slower to build and faster to trust. Spreadsheet conflicts show up as a coach in your ear at 7:40 a.m.

One source of truth for the park

The grid, the public schedule, and the coach link have to be the same object. Exporting to PDF then editing the sheet is how Diamond 3 plays a game that Diamond 4 already finished. Live placement — with conflict checks — is the difference between a command center and a reprint table.

What “good” looks like on Friday night

• Every division has a duration and a last-start rule.
• No team is placed before its rest window.
• Umpire and diamond constraints are visible before you lock the day.
• Coaches can open one link and see only their games.

That is the job Dugout Desk was built to do: treat the schedule as a constraint problem, not a wall of cells.