Tournament day is an operations center

People who read about the platform behind my wiffle ball tournament sometimes ask what the software actually does on the day. Fair question. Registration and payments happen in the calm months. Tournament Saturday is where the system either holds or it doesn't.

Here's the day it has to survive.

The run of show#

• 11:30 AM - team check-in opens. Forty-ish captains arrive at once, each certain their roster was submitted (it was not always submitted).
• 11:45 - rules recap. Gentleman's pitching. Every player pitches an inning before anyone pitches a second. Five players max.
• 12:00–4:00 - pool play across thirteen fields. Every team is guaranteed four games. Pool play sets seeding only - everybody advances, which keeps the day fun and the stakes honest.
• 2:00–8:00 - Home Run Derby running in parallel, because why have one event when you can have two.
• 4:15 - single-elimination bracket begins, seeded off the pool results that finished fifteen minutes earlier.
• 9:30–10:30 PM - finals, under light towers, on the sponsored showcase field.

Compress that: thirteen fields playing simultaneously, seeding computed in a fifteen-minute window, a parallel derby, and a bracket that has to keep moving until 10:30 at night. That is not a spreadsheet problem. That's an operations problem.

What the software holds up#

Check-in against live rosters. An official pool-play win requires at least three rostered players - which means roster truth matters at noon, not whenever the captain gets around to it. Digital rosters and waivers turn check-in from an argument into a lookup.

Scores from the field, standings in real time. Games are entered from phones at the fields; standings and seeding update as pool play closes. The fifteen-minute gap between "last pool game ends" and "bracket starts" used to be the most stressful quarter-hour of my year.

The bracket advances itself. Win a game, the next matchup populates. Nobody stands at a whiteboard doing playoff math while forty teams watch.

One lesson encoded forever: don't pre-post the pools. One year we published pool assignments early; last-minute team changes made every posted sheet wrong and confused everyone. Now pools go live when they're final, and the system is the single source of truth. That rule exists because we earned it.

What the software doesn't do#

Plenty. The fields get lined by a robot, but somebody still mows. The inflatable outfield fences - this year's big upgrade, replacing a decade of fence-pole archaeology - get inflated by humans. Umpires are recruited, scheduled, and occasionally begged for. The grill does not have an API.

That's the real lesson of running this event: software's job on tournament day is to make the information problems disappear so every human hour goes to physical ones. When the check-in line moves, the scores post themselves, and the bracket runs itself, the committee gets to spend Saturday on hot dogs, beer tickets, and calls at first base - which is the whole point of a wiffle ball tournament.

The 2026 Schott Classic is July 11–12 at William C. Schott Memorial Fields in Cincinnati.