How to Write NDIS Progress Notes That Pass an Audit

What Auditors Actually Look For

When NDIS auditors review your progress notes, they're not checking whether you're a good support worker. They're checking whether your documentation proves that quality support was delivered. Here are the five things they examine most closely.

1. Evidence of Goal-Linked Support

Every note must clearly connect the support provided to at least one of the participant's NDIS goals. Generic statements like "assisted participant with daily tasks" won't pass. Instead, write: "Supported Sarah to independently prepare lunch (Goal 2: Increase daily living skills), providing verbal prompts only."

:::tip Always reference the specific NDIS goal number or description in every progress note. This is the single most important audit requirement. :::

2. Person-Centred Language

Auditors look for language that centres the participant's experience, choices, and autonomy. Avoid clinical or controlling language.

  • Don't write: "Client was non-compliant with medication schedule"
  • Do write: "Sarah chose to take her medication after breakfast rather than before. Discussed timing preferences and noted her choice in the support plan."

3. Objective, Measurable Observations

Your notes need to describe what you observed, not your opinion. Use the STAR method: Situation, Task, Action, Result.

  • Don't write: "Had a good day"
  • Do write: "Sarah completed her morning routine independently in 25 minutes (compared to 40 minutes last week), requiring only one verbal prompt to brush teeth."

4. Safety and Risk Documentation

Every shift should include a brief safety note. Auditors will flag notes that never mention safety, wellbeing, or environmental checks.

:::warning If a safety concern is identified during a shift and not documented, this is a serious compliance failure that can result in sanctions. :::

5. Timeliness and Consistency

Notes should be written as close to the shift as possible — ideally within 24 hours. Auditors can see timestamps and will flag patterns of late documentation.

What NOT to Write

  • Personal opinions about the participant's behaviour
  • Abbreviations that aren't universally understood
  • Information about other participants (privacy breach)
  • Vague statements with no measurable detail
  • Copy-pasted notes from previous shifts

NDIS Practice Standards Reference

These requirements come from the NDIS Practice Standards — Core Module: Support Provision, which states that providers must "maintain accurate and up-to-date records of supports delivered to each participant."

https://www.ndisnotes.com.au/blog/how-to-write-ndis-progress-notes