A large cricket program needed to schedule four concurrent competitions, all sharing venues, while enforcing a complex rule that no team could play an opponent for a second time until they had played every other team once.

With multiple teams from the same club sharing a single home venue, scheduling one competition without creating a clash in another was nearly impossible.

The new rule that every team must play each other once before any repeats created a global dependency that broke simple scheduling methods.
A shared venue-capacity layer was created to synchronise all four competitions, ensuring at most one home game per club, per date.
The engine was configured to enforce the completion of the first round-robin phase before scheduling any repeat matchups.
Caps on Home/Away streaks, Home/Away balance, and opponent spacing were all applied on top of the other constraints.
Under the hood, SchedulOpt’s solver used advanced techniques to navigate the massive search space and find a valid, optimised solution.




See how SchedulOpt® can save you time and deliver fairer, more efficient schedules.
