NDIS Incident Notes vs Progress Notes: When to Use Which (And Why Auditors Check Both)

Two Records, Two Jobs: The Core Difference

The confusion between incident notes and progress notes is one of the most common documentation problems in SIL services — and it's understandable, because both are written by the same worker, often minutes apart, about the same person. But they exist to do completely different jobs, and that's the key to knowing which to use.

A progress note is your routine, shift-by-shift record of the support you delivered. It captures the everyday: the personal care you assisted with, the community outing, the medication you supported, what the participant said and chose, and the goals their support worked towards. Most of what you write is progress notes, and most shifts are nothing but progress notes. They prove the funded support was actually delivered.

An incident report (the formal document; "incident note" is the everyday name for it) is triggered by a specific event — something that caused harm, or could have caused harm, to a participant or others. A fall. An injury. A medication error. An allegation of abuse. The use of an unauthorised restrictive practice. A participant going missing. It's a structured document with its own form, its own escalation path, and — for the serious category — its own legal reporting deadlines to the NDIS Quality and Safeguards Commission. It exists so a defined safety event can be captured, escalated, investigated and (where required) reported.

The simplest way to hold the difference in your head:

• A progress note answers: "What support happened on this shift?"
• An incident report answers: "What went wrong, what did we do about it, and who needs to know?"

Routine support → progress note. A harm event → incident report (plus a short progress-note entry — more on that crucial "plus" below).

Side-by-Side Comparison

Keep this table near your workstation for the first month. It settles almost every "which one is this?" question.

The 10-Second Decision Flowchart

When something out of the ordinary happens and you're not sure, walk these four questions in order. The moment you hit a "yes", it's an incident.

The Rule That Trips Workers Up: Incidents Go in BOTH

Here's the single most misunderstood point, and it's the one that creates the most audit findings: when an incident happens, you do not choose between a progress note and an incident report — you write both.

Many workers assume that once they've filled in the incident form, the progress note is redundant. It isn't. The two records do different things and an auditor expects to see both, lining up with each other:

• The incident report holds the full, structured detail: exact time and location, what happened, who was involved and who witnessed it, the participant's reported injury or impact, your immediate response, first aid given, who you notified and when, and the outcome and corrective actions. It feeds the incident register and the reportable-incident process.
• The progress note contains a short, factual entry that the incident occurred — when, what you observed, the response, and that an incident report was completed and the team leader notified. It points to the incident report rather than repeating everything.

Why both? Because the progress note is the continuous timeline of the participant's day and the incident report is the standalone safety record — and an auditor reads them together to confirm they tell the same story. A fall described in a progress note with no matching incident report screams "under-reporting". An incident report with no contemporaneous progress-note entry suggests it was written up after the fact. Consistency between the two is itself the evidence that your incident system works.

Worked Examples: The Same Event in Each Record

These are composites of typical SIL situations — names changed. For each, see how the event lands in the progress note and the incident report, and where the line falls.

Example 1 — A fall in the kitchen (incident → write both)

Example 2 — Declined a shower (NOT an incident → progress note only)

Example 3 — A medication error (incident → write both)

When an Incident Becomes Reportable to the Commission

Not every incident is a "reportable incident". Reportable incidents are the most serious category, and they carry legal notification deadlines to the NDIS Quality and Safeguards Commission. As a worker, you don't make the Commission notification yourself — but you must recognise these and escalate immediately so your provider can meet the deadline. The categories of reportable incidents include:

• The death of a participant.
• Serious injury of a participant.
• Abuse or neglect of a participant.
• Unlawful sexual or physical contact with, or assault of, a participant.
• Sexual misconduct committed against, or in the presence of, a participant.
• The use of a restrictive practice in relation to a participant where it is not authorised, or not used in accordance with an authorisation.

Timeframes matter: certain very serious incidents must be notified to the Commission within 24 hours, while other reportable incidents are notified within 5 business days (with a follow-up report after). These categories and timeframes are set by the Commission and can be updated — always confirm the current detail on the NDIS Commission website and follow your organisation's incident management policy. For the full breakdown, see our guide to NDIS reportable incidents and the incident report guide.

Why Auditors Read Both — And What They're Hunting For

This is the compliance bridge, and it's the reason this distinction is worth getting right. Your documentation isn't busywork — for an auditor, your notes and incident reports are the evidence. When an NDIS approved quality auditor or an NDIS Commission compliance officer reviews your incident management, they don't just read the incident register in isolation. They triangulate it against your progress notes, and against the participant's plan and risk assessments.

Here's the predictable path — and what gets flagged at each step:

1. They sample participants (often the highest-risk, most complex plans) and pull a run of progress notes.
2. They scan the notes for events — falls, injuries, behaviour incidents, medication issues, hospital trips — and then ask: is there a matching incident report for each one? A "Sam had a fall" in the notes with no incident report is the classic under-reporting finding.
3. They run the check in reverse — taking incident reports from the register and confirming each is backed by a contemporaneous progress-note entry. An incident with no same-day note suggests it was written up late.
4. They follow the chain on each incident: Was it escalated? Reported within the required timeframe if reportable? Investigated? Were corrective actions taken and recorded — and do later progress notes show those actions in practice?

The gaps that generate the most findings are almost always consistency failures: events in notes with no incident report, incident reports with no note, contradictory times or facts between the two, and corrective actions that appear on the incident form but never show up in subsequent notes. See the most common SIL audit non-conformities and the audit evidence guide for how this evidence trail is assessed — and incident management for SIL providers for the system that should sit behind it.

Your Incident-vs-Note Self-Check

Run this checklist any time something out of the ordinary happens on a shift. Every box you can't tick is a gap an auditor would find — close it before you sign off, not eighteen months later in an audit interview.

Want to know how your whole documentation and incident system would hold up, not just one event? The free SIL Readiness Scorecard walks you through the records an auditor samples — progress notes, incident reports, the incident register, medication, behaviour support and consent — and shows you the gaps before an auditor does.

The distinction comes down to one habit. When a shift is ordinary, write the progress note. When something causes harm — or could have — write the incident report and a short, matching progress-note entry, then escalate. Keep the two consistent, keep the language factual, and let a tool carry the rewriting load. Do that, and the moment an auditor opens your incident register next to your notes, the two records will tell the same true story — which is the entire point of writing them.