What the Serious Incident Response Scheme covers
The Serious Incident Response Scheme applies to Commonwealth-funded residential aged care and home services, including Support at Home. It requires providers to identify, record, respond to, and report serious incidents involving people receiving care. The incidents covered by SIRS fall into two priority categories based on severity, and the reporting obligations differ between them.
Priority 1 incidents include unreasonable use of force, unlawful sexual contact or inappropriate sexual conduct, psychological or emotional abuse resulting in serious harm, unexpected death, stealing or financial abuse causing significant harm, and neglect resulting in serious injury or illness. These must be reported to the Commission within 24 hours of the provider becoming aware — not 24 hours after the incident, but 24 hours after awareness. Priority 2 incidents cover similar categories at a lower severity threshold and must be reported within 30 days of awareness.
The SIRS framework applies in addition to other incident management obligations under the Aged Care Act 2024 and the strengthened Quality Standards. Standard 7 (Incidents and Complaints) requires providers to identify incidents at the shift level, respond to them, and learn from them — SIRS is the reporting mechanism that operationalises the most serious of these obligations with the Commission.
Why the shift note is the foundation of every SIRS report
The SIRS reporting clock starts from the moment the provider becomes aware of the incident. Awareness, in practice, is established by documentation — specifically, by the shift note that first records the event or observation that should have triggered the SIRS classification. If that note is vague, incomplete, or missing, the awareness timeline becomes contested. A provider that actually became aware on Monday evening but whose Monday evening shift note does not clearly establish awareness may find that an auditor treating Tuesday morning's clearer note as the awareness record — turning a timely 24-hour report into an apparent 36-hour delay.
Beyond the timing question, the shift note is also the evidentiary foundation for the incident report itself. The Commission reviews the incident report alongside the underlying documentation to assess whether the incident was correctly classified, whether the response was appropriate, and whether the follow-up was completed. An incident report that describes a Priority 1 event cannot be supported by a shift note that says "incident occurred, resident appeared distressed" — the report and the underlying record must be consistent and mutually reinforcing.
The elements that make a shift note SIRS-ready
SIRS-ready note checklist
- Specific time reference — when exactly the incident occurred or was observed
- The person's condition before the incident — establishes baseline and context
- A specific description of what happened — sufficient to classify the incident type
- The person's condition immediately after — establishes impact and injury
- Immediate actions taken — who was notified, what treatment or response occurred
- Who else was present or involved — workers, other residents, visitors
- Follow-up initiated — medical review, family notification, management notification
- Clear identification of the worker completing the note and when it was completed
A note that records "resident found on floor at approximately 7pm" does not establish the time with sufficient precision, does not describe the person's condition before or after, does not record what actions were taken, and does not establish who was notified. This note cannot support a SIRS report. A note that records the time to the nearest five minutes, the person's pre-fall condition (ambulant with frame, heading to bathroom), the post-fall condition (seated on floor, reporting left hip pain, GCS 15), the immediate response (nurse notified at 7:02pm, injury assessment conducted, ice applied, documentation completed, family notified at 7:45pm, GP contacted at 8:10pm), and the follow-up initiated — that note supports a complete and timely SIRS response.
NoteGate checks every note for SIRS elements — time reference, condition, action, follow-up — before the note enters the record.
Download the compliance brief →The SIRS documentation failures the Commission flags most often
Missing or ambiguous time references
SIRS awareness is time-specific. A note that records "evening shift" or "approximately" without further precision cannot establish when awareness occurred. For Priority 1 incidents, the difference between 6:50pm and "early evening" can determine whether a 24-hour report is timely or late.
No record of condition before the incident
Without a baseline record, auditors cannot assess the severity of the incident or determine whether the person's condition was a pre-existing or incident-caused state. For falls and injury events in particular, the absence of a pre-incident condition record is a significant gap.
Mismatch between the incident report and the shift note
When the incident report describes events differently from the underlying shift note — different timing, different description, different severity — auditors treat the mismatch as a documentation integrity concern. The shift note and the incident report must be consistent and complement each other.
No follow-up trail in subsequent notes
An incident documented in a Monday note must be traceable through subsequent records. The Commission looks at what happened after the incident was identified. If subsequent notes make no reference to the incident or the person's recovery, auditors infer that follow-up either did not occur or was not documented — neither is acceptable.