Does the rostering engine learn from our data?
No. The engine searches for assignments against defined rules. It does not train a machine-learning model on your rosters or learn new rules from them.
Does it profile individual controllers?
No behavioural profiles are built. The engine uses qualifications, availability and configured preferences. Vacation Score is a separate leave-prioritisation measure, configured by the organisation and visible to staff.
Does it predict fatigue, absence or attrition?
No. Scheduling rules evaluate conditions such as duty duration and rest intervals. The engine does not forecast an individual’s fatigue, future absence or likelihood of leaving.
Will two solves produce the same roster?
Not necessarily. The configuration stays the same, but assignments and scores can differ. Review each result for violations, coverage and operational fit.
Which rules can administrators change?
Depending on the rule, administrators can change activation, thresholds, weights or priority. Some rules are fixed. The catalogue shows the available controls.
What control does the planner retain?
Planners can edit shifts, lock assignments and accept or reject the proposed roster. Locked assignments stay in place during solving; manual choices still need review against the applicable requirements.