An incident is the dramatic compliance event. The reportable form, the 24-hour notification, the investigation file. It is also rare — a well-run SIL house records six to twelve reportable events a year.
A handover is the quiet one. Two workers in a kitchen, ninety seconds of "she had a tough morning, meds went down fine, watch the left foot." Then a clipboard signed and a shift starts. Across one house with four shifts a day, that exchange happens 1,460 times a year.
Auditors know which one carries more evidence. That is why, when they ask for a date, they ask for the handover record at every shift change on that date — not the incident form for the quarter.
Why handovers are tested before incidents
The NDIS Practice Standards Core Module sets two outcomes that depend almost entirely on handover quality: continuity of supports and communication. The Commission cannot assess either by reading a single shift note in isolation. They assess it by checking whether the next shift acted on what the previous one flagged.
This is why the audit sample is shaped the way it is. The auditor picks a date, reads the outgoing handover for shift one, then reads the progress notes from shift two. If the outgoing worker flagged "left foot needs rebandaging at lunch" and shift two has no record of either rebandaging or a clinical reason for skipping, the finding is not about wound care — it is about continuity.
That single test — handover flag in, action out — is the cheapest evidence pattern an auditor has. It is run on every Stage 2 SIL audit, often three or four times across different participants and dates.
The four ways handovers fail
A handover record fails an audit one of four ways. Each is common; together they account for most handover-related findings.
No written record at all
Verbal-only handover with no log. The most common failure mode in unregistered SIL houses moving to registration. Workers are talking — often well — but nothing reproduces on demand for the auditor. The Commission's view is unambiguous: if it isn't recorded, it didn't happen.
No acknowledgement timestamp
The outgoing worker writes a handover. The incoming worker never confirms they read it. The auditor cannot prove the information actually reached the next shift, only that it was authored. This is a documentation failure, not a clinical one — but it gets cited identically.
Generic content
"All good." "Quiet shift." "No issues." A handover that contains no participant-specific observation is treated by auditors as a non-handover. It tells the next worker nothing they could not have guessed, and it tells the auditor that the system encourages volume over substance.
Discontinuity
The most expensive failure. Shift one flags a follow-up — a medication change, a wound care task, a behavioural support strategy to try. Shift two's notes show no engagement with the flag, and no clinical reason for skipping it. The audit finding cites the handover, but it usually escalates because it implies a Practice Standards breach in the underlying support.
The volume problem
Handover volume is the reason this gets neglected. A four-shift roster generates eight handover events per house per day — four outgoing, four incoming acknowledgements. Multiply by 365.
That is the audit surface area sitting under one house. Across ten houses, it is just under thirty thousand events. None of them are dramatic. All of them are testable.
"An incident form gets written carefully because everyone knows it will be read. A handover gets written quickly because everyone assumes it won't."
The economics of the problem are obvious once you write them down. A thorough verbal handover — one that hits status, mood, medication notes, and follow-ups — takes 8 to 12 minutes per shift change. Doubled for written documentation, that is roughly 40 minutes a day per house spent on handover. Workers who feel rushed cut content; workers who feel watched cut detail. Neither is the worker's fault.
What an audit-ready handover actually contains
The Commission does not prescribe a handover template — but every assessor we've spoken to is testing the same four fields. A handover that cannot answer these four lines is a handover that will get sampled negatively.
The supervision parallel
Handover failures look very similar to supervision failures: the work is happening, the documentation isn't reproducing on demand, the auditor cites the gap. Both come down to the same operating discipline — capture structured fields at the moment of the event, not retrospectively.
What to fix between now and 1 July 2026
Nine weeks until mandatory SIL registration takes effect. Treat handover as the cheapest pillar to harden — and the one with the highest sampling rate per audit hour.
Aura OS turns handover into four taps and an acknowledgement.
Status, medications, follow-ups, acknowledgement — captured in the app, queryable by participant and date, surfaced in the audit evidence pack. New in April: a Claude-generated AI summary at the top of every handover, plus a one-tap read-aloud for workers driving between houses. The four fields stay mandatory; the time tax drops to about two minutes.
$49 per month AUD, GST inclusive. Seven-day free trial, no card. Australian data.