Restrictive practices
Recording a restrictive practice is the part everybody does. The part that goes wrong is quieter: an authorisation reaches its review date on a week when the practice leader is on leave, nobody notices, and the practice carries on being used — now unauthorised, and now a reportable incident that nobody has reported.
Chemical, physical, mechanical, environmental and seclusion. Choosing from the Commission's own five means the register can be counted and filtered by kind — which a notes field holding the word “restraint” cannot be, however carefully it was written.
Unauthorised, pending, authorised, expired — with who authorised it and when. Expired being a state the record can actually be in is the whole point: it means a lapse is something the register knows about rather than something a person has to remember to check.
Each practice links to the plan that authorises it, so the question an auditor asks in the room — show me the plan this one sits under — is a click rather than a search through a shared drive.
You cannot record a practice without a review date and the reason it is in place. The register orders by that date, in your organisation's own timezone, and an active practice that has passed it is marked as such without anyone running a report to find out.
A reportable incident carries both of its deadlines from the moment it is recorded: twenty-four hours to notify, and five business days for the detailed report. The five-day figure is counted in the branch's own timezone against its own public-holiday table, so a long weekend moves it rather than quietly eating it.
The part that is hard to copy
An authorisation that has expired, a review date that has passed and an incident deadline that is closing are all conditions the system evaluates, not reminders a person set. The incident clock in particular is moved along by a scan inside the database every hour, which needs nobody to have a browser open or a task still running on an office laptop. That is the difference between a lapse the system will tell you about and a lapse it will merely be able to show you afterwards, once it matters.
Not modules you buy separately. They read the same records, which is why nothing between them ever needs reconciling.
Build a week that already passes the award
Read about it →What the breach costs, before you publish
Read about it →From clock-in to payslip without retyping
Read about it →Bulk claims that match their own remittance
Read about it →Notes tied to the goal they were for
Read about it →Clocks that run whether or not anyone remembers
Read about it →Evidence that accumulates instead of being assembled
Read about it →