- Applies
- when the month's roster is built
- Enforcement
- Hard: never broken
- Who sets it
- An administrator in your instance
- Family
- Coverage and demand
- Roster style
- no-rotation (day-by-day)
configuredCompiled from the product source on 12 September 2026
Rule catalogue · Coverage and demand
Staff should not be assigned to shifts that are not required
Breaking it puts people on shifts nobody asked for, so the unit pays for cover the manpower requirement never called for.
What coverage and demand rules protect
The demand side of the problem. These rules make sure every required slot is filled and, just as importantly, that people are not assigned to shifts nobody asked for. The second half is easy to forget and expensive: an over-staffed morning is a cost, and it is also a person who could have been resting or covering a genuine gap somewhere else.
Other rules in this family
- Shifts beyond the staffing requirement are still filled
- Every required shift gets someone assigned to it
- Flexible shifts only become types they may convert to
- A flexible shift takes its first-choice conversion target
- Pattern rosters fill the blocks beyond the requirement too
- Substitute staff are not used to fill a pattern roster
- Every block of a pattern roster gets an owner
- Only people actually available go on position