Rostering engine
The engine searches for assignments using staffing demand, controller availability, qualifications and configured scheduling rules. You review the result, refine the plan and decide when to publish.
How it works
Demand, available staff and the roster structure shape the first draft. It gives the search a starting point.
The engine explores assignment changes and keeps the best result it finds. You set the search time budget.
More search time can improve the result. It cannot add qualified staff where demand exceeds availability. Test performance with your own roster shape and rules.
Scoring
Hard requirements take priority. A feasible result has no hard violations. If the inputs or search cannot satisfy them, the result can still contain violations.
See which required positions still need someone. Review these gaps alongside hard violations.
Preferences help shape the result: the spread of duties, for example, or staff requests. Compare soft scores using the same inputs and settings.
Rule controls vary: some rules are fixed, some have a fixed priority, and others allow an administrator to set thresholds, weights or hard/soft status. Operational and regulatory requirements should be reflected in the configuration. Explore the rule catalogue.
Evaluation
Each run returns the best roster it found within its search. It does not prove that no better arrangement exists. Another run can produce different assignments and scores.
Use Check Solution to evaluate a roster after generation or manual edits. It identifies applicable rule violations without moving assignments. It does not provide a complete causal explanation for why the search selected each assignment.
Start with a 20-minute discovery call about your staffing constraints, roster patterns and review process. We’ll then arrange a demonstration tailored to your priorities.
