Scheduling Intelligence: The Workforce System That Explains Every Decision It Makes
Optimisation has always been able to move fast. What it has never been able to do is answer for itself. Scheduling Intelligence does both, a fully optimised workforce plan built in seconds, with every assignment inside it accountable to a question.
In a Nutshell
- Explainable Optimisation: Pairs a mathematically exact Optimisation Core with a generative-AI Explanation Layer that only retrieves and translates decisions already made, never invents an answer.
- Speed at Scale: Builds a fully rule-compliant shift plan in seconds for standard scenarios (~50 employees/25 workplaces), and in under a minute even at 200 employees against 200 workplaces.
- Multilingual, Visual Reporting: Renders coverage, rotation balance, and unfilled positions as visual summaries in German, English, Dutch, or Spanish, in whichever language the question was asked.
The Catalyst
A planner opens the shift board and finds the same wall waiting: dozens of workplaces, each with its own requirements, certifications that must be current, roles that can’t be combined, positions needing unbroken coverage across the shift, and hundreds of people to place against all of it, correctly, before the operation can run. None of it is negotiable. All of it has to be resolved before the doors open.
A skilled planner can solve this by hand. What they can’t do is prove it was the best solution available, or explain, with certainty, why one person was chosen over another. Fairness ends up governed by memory rather than data, who worked the harder post last, who’s due a break in rotation, and at scale, memory is not a control system.
This is a workforce problem, wherever shift-based operations run at scale: distribution, retail, manufacturing, facilities. Automated planning tools have existed for years, but most of them optimise for speed alone, delivering a plan without the ability to interrogate it. That trade-off, fast or explainable, has been treated as unavoidable. It isn’t.
The cost of that trade-off isn’t only the planner’s morning. It’s the certified post that sits empty because the one qualified person was already placed elsewhere, discovered only once the shift is already short-handed.
The Method
This is the gap that Primion is closing with Scheduling Intelligence. It is built on one governing idea: every assignment the system makes, it can also account for. Not two products bolted together, one that plans and one that explains, but a single system where the second capability is a direct consequence of the first, built from two components, the Optimisation Core and the Explanation Layer.
The Optimisation Core evaluates every possible pairing of employee to workplace and selects the combination that best satisfies a defined set of priorities, rotation fairness weighted against each employee’s task history, day-to-day variety, alignment to their usual area, and operational priority for the posts that matter most. Hard constraints, qualifications, availability, forbidden combinations, sit outside this and are never breached. Nothing here is probabilistic. A position needing continuous coverage across a shift is split into blocks and rotated automatically, with the sequencing handled by the Core, not assembled by hand afterwards.
Tested across scenario sizes: a standard shift, around fifty employees against twenty-five workplaces, resolves in seconds. A medium scenario, around a hundred employees against fifty workplaces, the same. A large scenario, two hundred employees against two hundred workplaces, completes in under a minute. At production-peak scale, three hundred or more employees against a hundred and fifty or more workplaces, it’s a matter of minutes.
Set the old way against the new. Today, a plan is built by judgement, and judgement is slow to produce and impossible to fully audit. With Scheduling Intelligence, the same request returns a complete, rule-compliant plan in that timeframe, with anything that can’t be filled flagged immediately, ranked by priority, so a gap becomes a decision made in advance rather than a discovery made on the floor.
This is the shift from a plan an organisation has to trust and a plan it can question.
That distinction only holds if the boundary underneath it is absolute, so it’s worth stating as a rule rather than a nuance. The Optimisation Core makes no probabilistic guesses; every assignment is mathematically derivable from the constraints it was given. The Explanation Layer, built on generative AI, never invents an answer; it only ever retrieves and translates a decision the Optimisation Core already made. One side of the system is exact by design. The other is conversational by design. Neither borrows the other’s nature.
The Components
- Optimisation Core
Tested across shift sizes from around fifty employees and twenty-five workplaces up to production-peak scenarios of three hundred or more employees and a hundred and fifty or more workplaces, meeting performance targets at every scale evaluated. Deployable in parallel across multiple sites, with no dependency between runs. - Rotation fairness and variety logic
Computed simultaneously across the entire workforce for every plan generated, replacing what memory and habit could only approximate. - Flexible workplace coverage
Continuous-coverage positions are split into blocks and sequenced automatically across multiple employees within a single optimisation pass. - Explanation layer
In early testing as a conversational interface connected directly to the Optimisation Core’s output. Every response is retrieved from actual assignment data, qualification records, rotation history, availability windows, never generated freely. - Multilingual, plan-aware reporting
Coverage, rotation balance, and unfilled positions render as visual summaries in the language the question was asked in, German, English, Dutch, or Spanish.
Every organisation running shift-based operations at scale eventually asks the same two questions of any automated system: how much time does it actually give back, and can I trust what it decided. Most tools answer one of these convincingly. Few answer both.
The time question has a clear answer. Rotation fairness, area alignment, and variety, weighed simultaneously across an entire workforce, are a computation problem a human planner cannot sustain consistently at scale, no matter how experienced. Removing that ceiling changes what a planning team can be responsible for, not just faster output, but a more defensible one.
The trust question is the one most vendors underestimate. It is the reason automated systems get quietly overridden by the people meant to rely on them. A plan that cannot be questioned does not get trusted, however fast it was built.
Scheduling Intelligence is built for organisations that have stopped accepting that trade-off. Fast enough to plan an entire operation in seconds. Transparent enough, in what it can prove about every decision inside that plan, to be handed real authority rather than cautious tolerance.
The POC
The Optimisation Core has been tested extensively against real operational data, across shift sizes from standard operations to large, multi-area production environments, meeting performance targets at every scale evaluated. The Explanation Layer is earlier in its development, currently in prototype testing to establish how reliably it can answer real planning questions with fully traceable, grounded responses.
What comes next is proving that standard under real operational pressure, wider scenario coverage, harder edge cases, the exact questions a planning team asks on its worst day, not its best one. Every assignment the Optimisation Core makes should be one the Explanation Layer can account for. That is the standard the next phase of testing exists to confirm.
If your organisation is planning shift-based operations at a scale where judgement alone is starting to strain, contact us to learn more.
Let’s talk possibilities!
Every project on this page started with a conversation about a real operational challenge. Bring us yours, and let’s explore what a working prototype could look like.