NDIS Service Delivery Evidence: Linking Progress Notes to Supports Delivered

Evidence Should Show What Actually Happened

An NDIS progress note should create a clear connection between the support planned, the support delivered, the participant's choices and response, and any next action. Generic entries such as "community access completed" or "supported as per plan" provide little evidence about the service or its value to the participant.

The NDIS Commission does not prescribe one universal progress-note template. Providers need a documentation approach that fits their registration, service agreements, practice requirements, funding arrangements, and the participant's support plan.

What a Service Delivery Note Can Capture

• Date, time, location, and type of support provided.
• The participant's stated choice, priority, or goal for the session.
• Specific assistance, prompting, skill-building, or adjustments provided.
• What the participant did, communicated, or achieved.
• Relevant changes, risks, incidents, or declined activities.
• Follow-up needed and the person responsible for it.

Keep language factual and proportionate. A note should not include unrelated personal information simply to appear detailed.

Example Support Note

"Jordan chose to practise travelling by bus to the local library, consistent with his community-access goal. Before leaving, Jordan used the journey planner with one verbal prompt and identified the correct route. At the interchange he asked to review the platform number and then located it independently. Jordan purchased his own fare and requested support to speak with library staff about membership. He completed the form with assistance reading two questions. Jordan said he felt more confident and wants to practise the return route next Tuesday. Added the requested practice session for coordinator review."

Separate Service Evidence From Marketing Language

Avoid claims such as "excellent progress" unless the note identifies the observable change and the participant's view. Compare current performance with a relevant baseline or previous session without overstating that the provider caused the outcome.

Likewise, a progress note is not an invoice. Service-delivery and claiming records should reconcile, but each must meet its own purpose and controls.

When the Planned Support Changes

Record why the session changed, how the participant was involved, what alternative was agreed, and whether a coordinator or other authorised person needs to review the support arrangement. Do not retrospectively rewrite the goal to match what occurred.

Common Evidence Gaps

• The note names an activity but not the support worker's role.
• No participant choice, response, or outcome is visible.
• Every note repeats identical wording despite different sessions.
• Times, locations, or service types conflict with other records.
• A risk or follow-up is mentioned without an owner.

For a broader record framework, see the NDIS documentation requirements guide. Draft notes can also be reviewed with the NDIS progress note checker.

This article was written by AccuNote's NDIS Documentation Team for general education. Providers should apply current NDIS Commission guidance, registration requirements, service agreements, funding rules, and organisational policies.