PoolSolve
Menu
Features Free tools Formats Sports Guides Help

Automatic scheduling that respects every constraint

Stop juggling spreadsheets. Tell PoolSolve who plays, where and when - the solver places every match into a conflict-free schedule.

The PoolSolve schedule board: match cards placed across fields and time slots
Every match placed across pools and time slots - one dense day of a 56-team cup

Constraint solving, not templates

Google's OR-Tools CP-SAT engine assigns slots to all matches at once - field capacity, opening hours, referee availability and rest windows are hard rules, not hopes.

Coach and referee aware

Coaches leading multiple teams and referees with limited availability are modeled directly, so generated schedules avoid personal conflicts.

Repair, do not restart

Fix the matches you like and re-solve the rest. The solver rebuilds around your pinned games instead of starting over.

Violations you control

Every remaining conflict is listed with its reason - accept it explicitly or send it back to the solver. Nothing is silently wrong.

How it works, step by step

1

Describe your constraints

Teams, fields, referees, rest windows and time preferences go in once - nothing else is needed to start.

2

Solve the whole slate at once

The CP-SAT solver assigns every match a slot and venue simultaneously, so conflicts are impossible by construction.

3

Review violations honestly

Anything it could not place is listed with the reason - accept it or relax a constraint and solve again.

4

Pin and repair anytime

Lock the matches you like; the solver rebuilds around them when a team drops out or a field closes.

Why spreadsheets lose to a solver

Manual scheduling feels safe because every cell is under your control, but control is exactly the problem. A forty-team weekend produces hundreds of matches, and each placement depends on every other: move one game to satisfy a coach and you may break a rest window, free a field too early, or leave a referee stranded between courts. Spreadsheets cannot see those ripples - they only record your last edit, so every manual fix quietly creates the next problem to find and someone has to check the whole grid again by eye. A constraint solver works the opposite way. It reasons about the entire slate at once, testing combinations a person would never have time to check, and either returns a schedule where every hard rule holds or proves that none exists. That proof matters as much as the schedule: instead of discovering on Saturday morning that two teams were double-booked, you learn which constraints clash and see the exact matches, fields and rule groups involved - the decision to relax something becomes yours and deliberate, not an accident.

A match card open on the schedule board, ready to move or edit
Open a match card to move it, lock it or fix a conflict on the spot

Fairness you can actually enforce

A fair schedule is not a vague promise, it is a list of measurable rules you can hold the result against. PoolSolve lets you set a minimum rest window between a team's games, cap how many consecutive matches anyone plays, and spread early and late slots so the same squad does not always open the venue or close it. Referee fairness works the same way: officials are assigned from eligible pools, workload is balanced across the day so nobody covers six matches while a colleague covers one, and senior-qualification quotas keep finals staffed at the right level. Even field fairness is expressible - no team should spend the whole day on the farthest pitch while the favourites play every game on the show court. Because each fairness rule can run as a hard constraint or a weighted soft one, you decide what fairness means for your event and how firmly it holds, instead of hoping a manual grid happens to produce it by luck. Every rule also reports its own violations, so fairness stays auditable.

The constraint setup: rest time, referee and field rules for the solver
Rest windows, referee coverage and per-division rules the solver must honor

Paint availability once, reschedule calmly

Every schedule starts from painted availability. Venues carry opening hours, fields get slots assigned to the categories that will use them, and teams and referees declare when they can actually be there - unavailable mornings, late arrivals and shared coaches marked once instead of remembered forever. Per-match time windows and matchday bindings then pin specific games where they belong. This model pays off the moment reality intervenes: rain closes a field on Sunday morning, a team drops out on Friday night, a referee calls in sick. In a spreadsheet that means a weekend of manual surgery, hunting every cell the change touches and still missing one. Here you update the availability that changed and re-run, and the solver re-places only what the new information invalidates - the rest of the day stays exactly where participants already saw it. Painted availability also doubles as documentation: instead of tribal knowledge about who cannot play early, the constraints live in the workspace, apply automatically to every future event you run, and stay editable when next season's ground rules differ.

The venue canvas painting fields and categories across tournament days
Paint pool availability per day and watch the capacity meter keep score

Questions, answered

What scheduling engine does PoolSolve use?

A two-phase constraint solver built on Google's OR-Tools CP-SAT engine. Phase one assigns every match a field and time slot under the hard rules; phase two staffs referees and resources against those fixed placements.

Which constraints does the solver respect?

Field capacity and opening hours, painted team and referee availability, rest windows between games, coaches shared across teams, medal-match spacing, per-match time windows and matchday bindings. Each tunable rule runs in hard, soft or off mode, and soft rules carry adjustable weights.

What happens when no valid schedule exists?

The solver proves the model infeasible and explains why in plain language - the conflicting rule groups plus the specific fields, teams, matches or pinned games involved - so you know exactly what to relax before rerunning.

Can I keep part of a schedule and re-solve the rest?

Yes. Pin the matches you want to keep and repair re-places everything else around them - played games and locked staff are never moved.

How long does generation take?

Generation runs as a background job: a first complete schedule typically appears within seconds and keeps improving within a time budget you choose - Quick, Standard or Thorough. Watch improvements land live on the board or stop early to keep the best.

Does the solver assign referees too?

Yes - a dedicated staffing phase assigns referees and resources against eligibility, availability, senior-qualification quotas and workload balance, and reports any coverage shortfall instead of silently leaving gaps.

Also see

Keep exploring

Try it on your next season or tournament

Create a free workspace