An NDIS Worker Screening Check has an expiry date, and so does almost everything else that qualifies a worker for a shift: first aid, CPR currency, medication competency, a driver licence for shifts with transport. Most providers file these in an HR folder and check them at audit time.
The problem is that a lapse does not bite in the HR folder. It bites on a Tuesday shift, delivering a risk-assessed support, with a worker whose clearance quietly ended the week before. Expiry is a rostering constraint, and it belongs in the rostering system.
Two kinds of consequence
Not every expiring document means the same thing. A lapsed worker screening check makes certain work unlawful to deliver — that is a hard stop, and a roster should refuse to publish the shift. A first aid certificate expiring next month is different: a prompt to book the refresher, not a reason to pull tonight's shift.
A good register distinguishes blocking constraints from advisory ones, because a system that treats everything as a hard stop teaches people to override it.
The most predictable compliance event you have
Almost every compliance failure involves surprise. Document expiry involves none — the date is printed on the document, often years in advance. That makes it the easiest class of failure to engineer away: warn early, warn again as the date approaches, and block at the point where the shift would be non-compliant.
The warning has to reach the people who can act: the worker who needs to renew, and the rosterer who needs to plan around a gap if they do not.
What the register needs to hold
Whether it lives in software or a spreadsheet, the register is only useful if it answers four questions without research:
- Each document's type, expiry date, and which supports or duties it gates
- Whether a lapse blocks rostering or raises a warning
- Who was notified, and when — so the trail exists if the renewal never comes
- Sighting records: who verified the document, and on what date
How this works in Nexrosta
Nexrosta treats worker documents as rostering data. Documents warn before they expire, and a lapsed worker screening check blocks the shift outright — it is one of the fourteen conflict checks that run before any shift saves. The warnings and the block are written to the append-only audit log, which is the difference between telling an auditor you have a process and showing them one.