What a spreadsheet cannot do

The spreadsheet is not the problem

Excel is a remarkable tool. It structures data, applies formulas, and renders tables. Most planners have been using it for years, sometimes with sophisticated macros and finely tuned conditional formatting.

The problem is not Excel. The problem is that employee scheduling is a combinatorial problem, and a spreadsheet is not a combinatorial solver. This is not a flaw in the tool; it is a design boundary. You do not blame a screwdriver for not being a drill.

The planner who uses Excel is not at fault. They are doing expert work with a general-purpose tool. But beyond a certain complexity threshold, human expertise alone cannot guarantee an optimal result, and that threshold is reached much earlier than most people think.

The combinatorial ceiling

Consider a typical case: 150 employees, 30 days, 50 shift types. That amounts to 150 × 30 × 50 = 225,000 possible combinations. Each combination must simultaneously satisfy dozens of constraints: qualifications, legal rest periods, contract types, coverage requirements, workload fairness.

A human planner does not evaluate 225,000 combinations. They work by approximation: fill the critical slots first, then adjust the rest. It is an effective heuristic, but it is sequential. It does not see the schedule as a whole.

The solver, by contrast, explores the entire solution space. It uses constraint propagation to eliminate impossible branches before even exploring them, then refines the search through intelligent backtracking. In minutes, it either proves its solution is optimal, or returns the best solution found within the allotted time.

This is not a question of planner competence. It is a question of volume: beyond a few dozen agents, no manual verification can be exhaustive.

The cascade effect

Every planner knows this scenario: you fix a conflict on one agent's row, and the fix creates another elsewhere. You move a shift to respect a rest period, and suddenly a slot is left uncovered. You fill the slot with another agent, and their contractual hours are exceeded.

This is the cascade effect. In a spreadsheet, every change is local: the planner sees the cell they are editing, but not the full set of repercussions across the rest of the schedule. Conditional formatting can flag some conflicts, but not all, and never exhaustively.

The CP-SAT solver does not suffer from this effect. It considers all constraints simultaneously. It does not "fix" an existing schedule: it builds a solution that satisfies every rule from the start. There is no cascade, because there is no sequence.

The hidden cost of time

Manual scheduling typically takes 3 to 5 days per month. That is time spent exclusively on building the schedule, not counting mid-month adjustments for unplanned absences or activity programme changes.

Over a year, that represents 36 to 60 working days, the equivalent of 2 to 3 months of a planner's activity. This time is incompressible with a spreadsheet: the complexity of the problem demands a volume of manual checks that cannot be reduced.

Beyond the direct cost in hours, there is operational stress. A planner who knows their schedule potentially contains undetected violations works under constant pressure. Every call, every last-minute absence can collapse a fragile balance.

A constraint solver generates a schedule in minutes. The planner spends their time analysing, adjusting, and improving, not building cell by cell. The job shifts from execution to supervision.

What the solver resolves structurally

A constraint solver is not an improvement on Excel. It is a fundamentally different tool for a fundamentally different problem.

• Exhaustiveness: the solver explores the complete solution space. It does not miss a combination. If an optimal solution exists, it finds it
• Simultaneity: all constraints are evaluated at the same time, not sequentially. No cascade effect
• Guarantee: a schedule returned as OPTIMAL is mathematically proven. It is not an estimate; it is a certainty
• Reproducibility: same input data, same output schedule. No variation from one planner to another, no dependency on individual experience
• Traceability: the optimisation score breaks down every penalty. The planner knows exactly why the solver made each choice

The planner remains indispensable. They define the rules, validate the result, and manage exceptions. But they do so with a tool that matches the complexity of the problem, not with a spreadsheet designed for a different purpose.

To understand in detail how mathematical modelling works behind Planopti, or how regulatory compliance is guaranteed automatically, see our other articles.

Getting started

Moving from Excel to a solver does not mean abandoning your processes. Planopti works alongside your existing workflow: import your current Excel files, define your constraints, generate a first optimised schedule, and compare it with your manual version. The result speaks for itself.