How to Write NDIS Progress Notes: A Support Worker's Complete Guide with Examples

1. Why Progress Notes Matter

Progress notes are not just admin. They are a legal record of the supports you delivered, evidence that a participant's funded goals are being worked toward, and the primary document an NDIS auditor will scrutinise if your provider is ever reviewed.

Under NDIS Practice Standard Outcome 2.4 — Information Management, registered providers must maintain accurate, timely, and confidential records of all supports delivered to participants. Poorly written, missing, or subjective progress notes are one of the leading causes of non-conformance findings in NDIS audits.

Progress notes serve three distinct purposes that overlap:

• Audit trail. They prove services were delivered as billed. Without contemporaneous notes, an auditor cannot confirm that the hours claimed on an NDIS payment request were actually worked and spent supporting the participant.
• Participant safety. A consistent record allows any support worker — including someone covering a shift for the first time — to quickly understand a participant's current health status, recent behaviours, medication changes, or emerging concerns. Gaps in notes mean gaps in care continuity.
• Funding evidence. When a participant approaches their plan review, the Local Area Coordinator and Planner will look at progress toward their stated goals. Progress notes are the primary mechanism through which goal progress is documented over time. Strong notes at review time directly support better funding outcomes for participants.

2. What NDIS Progress Notes Must Include

Every progress note — regardless of the format you use — must contain six core elements. Think of these as the minimum viable note. If any element is missing, the note is incomplete.

• Date, time, and duration of the shift or session — including start and end times, not just the date.
• Support worker's full name and role — so the record is traceable to an individual.
• Participant's name — never write a note that could apply to an anonymous person; it must be specific to this individual.
• What supports were provided — describe the specific activities, tasks, or interventions that occurred during the shift. Be concrete: "assisted with showering and personal hygiene" rather than "provided personal care."
• Participant's response and presentation — how did the participant engage? Were they alert, fatigued, distressed, communicative? Did they participate willingly, require prompting, or refuse a task? Record observable facts, not your interpretation of their emotional state.
• Link to NDIS goals or support plan outcomes — explicitly connect what happened in the shift to the participant's funded NDIS goals. This is the element most commonly missed, and it is the one that matters most at plan review.

Notes must also be timely. The expectation — consistent with Outcome 2.4 and general health record standards applied across disability services — is that notes are completed within 24 hours of the shift, and ideally at the end of the shift or shortly after. Notes written days later lack reliability and may be questioned in an audit.

3. What to NEVER Write in Progress Notes

Progress notes must be factual and objective. The following types of language are not just unhelpful — they can create compliance problems, damage the participant's dignity, and in some cases expose a provider to legal risk.

Subjective opinions and emotional interpretations

You cannot verify what another person feels. Write only what you observe. "The participant appeared tearful, with red eyes and a quiet voice" is a factual observation. "The participant was sad and upset about her family" is an interpretation — unless the participant told you this directly, in which case you quote them.

• Never write: "John seemed happy today" — Write instead: "John smiled frequently during the activity and stated 'I really enjoy this.'"
• Never write: "She was being difficult" — Write instead: "Participant declined the morning routine three times and stated she did not want to shower. Staff offered a later time and she agreed at 10:15am."
• Never write: "He was aggressive" — Write instead: "Participant raised his voice, used profanity directed at support worker, and knocked a cup off the table. No one was injured. Behaviour support plan was followed."

Assumptions and speculation

Do not speculate about why something happened. If a participant arrives distressed from a family visit, write that they arrived distressed, not that "the family visit upset her." Unless the participant or family told you the cause, you do not know it.

Abbreviations and jargon without explanation

A note must be readable by a person who was not present — including a future worker, a family member with access to records, or an auditor. Unexplained abbreviations introduce ambiguity. If you use a common abbreviation (e.g., ADLs for Activities of Daily Living), that is generally acceptable in the disability sector, but obscure shorthand is not.

Excessive personal commentary or judgement

Notes are not the place to record your personal views about a participant's family, lifestyle, or decisions. Commentary such as "her mother is controlling and interferes with supports" has no place in a progress note. If you have concerns about a third party's conduct, raise them through your organisation's incident or complaint process.

4. The 4 Note Formats: Standard, SOAP, DAP, Brief

There is no single mandated format for NDIS progress notes — the Commission requires that notes be accurate, timely, and complete, but leaves format to providers. In practice, four formats are widely used in Australian disability services. Understanding when to use each will make your documentation faster and more consistent.

Standard Narrative Format

A flowing paragraph or short paragraphs describing the shift chronologically. Most common in residential and SIL settings where shifts are long and varied. Works well for experienced workers who can structure information naturally. Weakest format if the worker has poor written communication skills, because it offers no structure to prompt completeness.

SOAP Notes

Originally from nursing and allied health, SOAP notes are increasingly used in disability services, particularly where behaviour support plans or health conditions are involved. Each letter prompts a specific type of information:

SOAP notes are excellent for complex participants or shifts where health, behaviour, or significant events need to be documented carefully. They take longer to write but produce highly structured, auditable records.

DAP Notes

A simplified version of SOAP that is easier for support workers to use quickly. DAP collapses the format into three sections:

Brief Shift Notes

A condensed format — typically 3 to 5 sentences — used for routine, uneventful shifts where the participant's status is stable and no significant events occurred. Brief does not mean vague. Even a short note must name the supports provided, the participant's presentation, and the relevant goal. Brief notes are appropriate for community access shifts where nothing noteworthy occurred, or drop-in domestic support visits. They are not appropriate if anything out of the ordinary happened.

5. Good vs Bad Progress Note Examples

The following five examples show the same shift documented two ways — the kind of note that creates compliance risk, and the kind that meets NDIS standards. The differences are not about length. They are about specificity, objectivity, and goal linkage.

Example 1: Meal Preparation

Example 2: Community Access

Example 3: Personal Care

Example 4: Medication Support

Example 5: Behaviour of Concern

6. How to Link Notes to NDIS Plan Goals

Goal linkage is the element most commonly absent from progress notes — and the one that matters most when it comes to demonstrating value to the NDIS. Every participant's plan contains stated goals, and every support you provide should be traceable to at least one of them.

Before you start writing a shift note, know the participant's current NDIS goals. These should be in their support plan or service agreement, which your organisation must provide to you. Common goals include phrases like:

• "Increase independence in daily living tasks"
• "Build social connections and community participation"
• "Improve communication skills"
• "Maintain physical health and wellbeing"
• "Develop capacity for self-directed decision-making"

In your note, explicitly name the goal you are working toward. Use the exact language from the plan where possible — this makes it easy for a planner or auditor to cross-reference. Do not just write "participant worked toward goals." Name the goal.

Weak linkage: "Activity supports participant's NDIS goals."
Strong linkage: "This activity directly supports NDIS goal: 'Build capacity to use public transport independently.' Participant successfully purchased a Myki card without assistance for the first time."

Progress notes that consistently link to goals also create a valuable evidence base for plan reviews. A planner reading six months of notes that document incremental skill development can make a much more informed funding decision than one reading notes that describe activities without any reference to outcomes.

7. Incident Reporting vs Progress Notes — the Difference

Support workers often conflate progress notes and incident reports, or assume that writing an incident report means they do not need to document the event in their progress note. Both assumptions are wrong.

Progress notes document what happened during a shift — including any incidents — as a factual narrative. They sit in the participant's ongoing care record.

Incident reports are a separate, formal document required under the NDIS (Incident Management and Reportable Incidents) Rules 2018 whenever a reportable or notifiable event occurs. These reports trigger your organisation's formal incident management process and, for reportable incidents, must be notified to the NDIS Commission within specified timeframes.

Events that require both a progress note entry AND a formal incident report include:

• Falls resulting in injury or that require medical attention
• Medication errors (wrong dose, missed dose, wrong medication)
• Behaviours of concern resulting in harm to the participant or others
• Allegations of abuse, neglect, or exploitation
• Unauthorised use of restrictive practices
• Unexpected serious illness or a medical emergency
• Death of a participant

In your progress note, document what happened factually (what you observed, when, how you responded, outcome). Then complete the incident report separately through your organisation's system. In the progress note, reference the incident report number so the two records can be linked. Never substitute a progress note for an incident report — they serve different functions and go to different people.

8. How Long to Keep NDIS Progress Notes

Under the NDIS Practice Standards and general Australian record-keeping obligations, providers must retain participant records — including progress notes — for a minimum of seven years from the date of the last entry, or until the participant turns 25 years of age if they were a child when services were provided (whichever is longer).

This is not an abstract requirement. The NDIS Commission can conduct audits, compliance investigations, or respond to complaints at any point, and can request records from any point in your registration history. If records cannot be produced, the Commission may draw adverse inferences about whether the services were actually delivered.

Practical implications for providers:

• Progress notes stored only in paper form must be kept securely and be retrievable. Paper degradation, floods, fires, and office moves are genuine risks over a seven-year horizon — consider digitisation.
• Records stored in third-party software platforms (care management systems) must remain accessible even if you change software providers or the platform closes. Maintain regular data exports.
• When a participant exits your service, their records must continue to be retained for the applicable period. Do not delete records on the assumption that the person is no longer a current participant.
• Records must be kept confidential and access-controlled. NDIS participants have rights under the Privacy Act 1988 (Cth) to access their own records.

9. Using AI Tools to Improve Your Progress Notes

AI tools are increasingly being used in Australian disability services to help support workers write better progress notes — and used correctly, they are a legitimate and practical aid to documentation quality.

The most practical use case is note reformatting: a support worker writes rough shift notes — often in point form, informally, or on their phone at the end of a shift — and an AI tool reshapes those notes into professional, NDIS-standard format. This does not mean the AI invents information. The factual content comes entirely from the worker; the AI structures it, removes subjective language, adds appropriate professional phrasing, and prompts for missing elements like goal linkage.

A few principles apply when using AI for progress notes:

• The worker remains responsible. AI-generated or AI-assisted notes must be reviewed and verified by the support worker before they are saved to a participant's file. If the AI misunderstood your input and recorded something inaccurate, that inaccuracy becomes part of the official record.
• Do not enter sensitive identifying information into general-purpose AI tools. Use tools specifically designed for disability service documentation that handle data securely and comply with Australian privacy obligations.
• AI does not replace the observation. The tool can only work with what you give it. You still need to be present, attentive, and aware during the shift. The quality of your rough notes determines the quality of the output.