Rule catalogue · Data integrity

Assignments already worked cannot be rewritten

Breaking it changes a position allocation that has already happened, so the record stops matching the day as worked.

Applies: when positions are allocated on the day
Enforcement: Hard or soft, set per organisation
Who sets it: An administrator in your instance
Family: Data integrity
Roster style: tactical (quarter-hour position allocation)

configuredCompiled from the product source on 12 September 2026

What data integrity rules protect

Not every rule is about people. This family holds the structural invariants: an assignment cannot exist in two places at once, history cannot be rewritten, a swap has to be aligned on both sides. They are mostly fixed in code rather than configurable, because they are not policy choices. They are the difference between a roster and a spreadsheet that looks like one.

Other rules in this family

Externally owned assignments cannot be reassigned
Assignments already worked cannot be reassigned
A locked assignment stays with the person it names
A replacement assignment stays with its replacement
A swapped shift stays with the person who took it
Externally owned pattern blocks cannot be reassigned
Pattern blocks already worked cannot be reassigned
A locked pattern block stays with the person it names

Back to the full catalogue →