Logging it starts the countdown
A reportable incident opens its notification window the moment it is recorded. The deadline becomes a property of the record itself, not a reminder somebody thought to set on their own phone.
Incidents and safeguarding
Every provider knows the reporting windows. Knowing them is not what fails. What fails is the Friday evening when the person who knew is not rostered on — so the clock belongs in the system rather than in somebody's head.
A reportable incident opens its notification window the moment it is recorded. The deadline becomes a property of the record itself, not a reminder somebody thought to set on their own phone.
A reportable incident carries both of its deadlines from the moment it is recorded: twenty-four hours to notify the Commission, and five business days for the detailed report. The five-day one is counted in the branch's own timezone against its own public-holiday table, so a long weekend moves the date rather than quietly eating three days of it.
If a deadline is closing in and nobody has picked it up, the same group is told again, more loudly. After that the people who own the organisation get added. Then it stops — because an alert that repeats forever is one everybody learns to swipe away.
A register of the five regulated restrictive practices, each carrying its authorisation state, the behaviour support plan it sits under, and a review date the register watches — so an authorisation that has quietly expired is something the system knows, not something somebody has to check.
Risk assessments, the complaints register and the feedback register live next to incidents, because an auditor reads all four together and the thing worth seeing is usually the pattern across them.
The part that is hard to copy
A scan runs inside the database itself, on the half hour, every hour, moving incident deadlines along. It needs nobody to have a browser open, a notification switched on, or a scheduled task still alive on an office laptop. That is the difference between a deadline the system is tracking and a deadline the system is merely displaying.
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 →Authorisation that expires on its own
Read about it →Evidence that accumulates instead of being assembled
Read about it →