TeamSchedulePro

The season schedule, built in one pass.

Feed it your divisions, teams (with schedule requests!), surfaces, slots, and preferences. Get back a complete, playable season that works for the facility and the teams — without the week of spreadsheet nights.

Sample allocation · 4 nights × 3 surfaces Solved in a single run
Mon
Tue
Wed
Thu
Court 1
A·D
B·E
C·F
U·X
Court 2
G·J
H·K
V·Y
I·L
Rink
M·P
N·Q
O·R
S·T
Hard-locked Preference honored

What it is

Days of work, done before your coffee is cold.

TSPRO (TeamSchedulePro) turns the seasonal headache of building a sports-league schedule from a multi-day spreadsheet ordeal into a job you kick off and walk away from. Feed it your divisions, teams, and available surfaces, and it produces a complete, playable season schedule in one pass — the kind of work that normally eats a coordinator's evenings for a week. It's built for the real world of facility scheduling, where every league has its own quirks: uneven division sizes, teams that can only play certain nights, surfaces that aren't all available at the same times, and the endless small promises made to families and coaches. TSPRO holds all of that at once and still lands a schedule that works both for the facility and for the teams.

The request system

A schedule that speaks two dialects

The heart of it is a request system that speaks two dialects. TSPRO holds both at once — treating the non-negotiables as walls and the preferences as pulls, then finding the arrangement that respects the first and satisfies as much of the second as the calendar allows.

Hard requests

The non-negotiables — a team that genuinely cannot play on a given night. TSPRO treats them as inviolable. Hard constraints are never violated to force a fit; if two of them genuinely collide, you hear about it up front rather than discovering it after publication.

Soft requests

The preferences — the "we'd rather not play late" and "try to keep us on the east rink" asks. TSPRO honors them as fully as the schedule allows, without letting any single preference wreck fairness for everyone else.

?

And before you ask the obvious question — what happens when people ask for too much? — we've already thought of it. TSPRO won't let a single team quietly corner the calendar: if a request would eliminate too large a share of the available slots, it's rejected rather than allowed to distort everyone else's schedule. And when requests pile up to the point that no schedule could possibly satisfy them all, TSPRO doesn't choke or quietly bury a conflict — it works the preferences in priority order, honors what it can, and tells you plainly what it couldn't fit and why, so you're never handed a broken schedule or left guessing.

Best of many, not first that fits

Rather than settling for the first schedule that technically works, the engine generates many candidate schedules and keeps the best one — measured against balance across playing nights, fair distribution of good and bad time slots, and how completely it satisfied everyone's requests. Division-level customization knobs let you tune the rules per division instead of forcing the whole league into one mold, so a competitive adult division and a rec-league kids' division can each get scheduled on their own terms in the same run.

After publication

Reschedules, managed — not a fresh crisis

Then comes the part every scheduler dreads: you publish the season you bled over for days, and within an hour the inbox fills with reschedule requests — a coach with a conflict, a team that needs to swap a night, a surface that just went down for maintenance. By hand, one change ripples into ten, and you're back to rebuilding from scratch. TSPRO makes reschedules a managed operation rather than a fresh crisis: adjustments respect the same hard and soft constraints and the same fairness rules the original run enforced, so a swap doesn't quietly hand one team three late games or stomp on someone's blackout date. The schedule you spent real effort on stays intact around the change instead of unraveling because of it.

The payoff

Time, and trust

Days → minutes

What would take days by hand happens in a single run.

Never tires

Doesn't get tired, miss a blackout date, or shortchange a team to make the grid close.

Defensible

Show the constraints were met and the slots shared fairly — every time.

The payoff across the board is time and trust. What would take days by hand happens in a single run, and unlike a person at hour six of a spreadsheet, TSPRO doesn't get tired, miss a blackout date, or shortchange a team to make the grid close. Every schedule comes out defensible: you can show the constraints were met and the slots shared fairly, which turns the inevitable "why did we get stuck with three late games?" conversation into a two-minute answer instead of an argument.

For a tester

It's worth a run just to watch a season you'd have dreaded building appear in minutes.

For a facility manager

It's the difference between scheduling being a specialized skill one stressed person owns and a repeatable process anyone on staff can drive.

TSPRO · TeamSchedulePro  —  a Boat Dog Customs product