This guide covers everything you need to know: the mandatory fields, the language rules, the most common mistakes, and real before-and-after examples you can use as a reference.

What you'll learn

What to include in an NDIS case note · The language rules auditors check · What good vs bad case notes look like · The step-by-step process · Common mistakes and how to fix them · Answers to frequently asked questions

What is an NDIS case note?

An NDIS case note is a formal written record created after each support session. It serves as evidence that the support was delivered, that it met the participant's needs, and that the worker acted within NDIS guidelines. Under the NDIS Practice Standards, registered providers are required to maintain accurate and complete records of all supports delivered.

Case notes are not just administrative paperwork. They are legal documents that can be requested by the NDIS Quality and Safeguards Commission during an audit, by the participant or their nominee, or in the event of a complaint or incident investigation. A poorly written case note — or a missing one — can put a provider's registration at risk.

What to include in an NDIS case note

A well-structured NDIS case note should contain the following information:

Field Notes
Date of support Required The date the session occurred, not the date you wrote the note.
Start and end time Required Exact times, not approximations. Used to verify billable hours.
Participant's name Required Full name as it appears in their NDIS plan.
Support worker's name Required Your full name. Some systems also require employee ID.
Location of support Required Where the session took place (home, community, day program, etc.).
Support delivered Required What activities, assistance, or services were provided during the session.
Participant's response Required How the participant engaged, responded, or reacted — in objective language.
NDIS goal linkage Required Which goal(s) from the participant's NDIS plan the session addressed.
Any incidents or risks Required if applicable Any incident, near-miss, or risk observed — even if minor.
Follow-up actions Optional Any actions required after the session (referral, medication review, etc.).
Important

NDIS auditors look for specific evidence that supports were delivered as claimed. A case note with only vague descriptions like "Support provided as per plan" will raise red flags and may result in a finding of non-compliance.

The language rules that matter most

The most common reason NDIS case notes fail compliance review is language — specifically, using subjective or interpretive words when objective, factual language is required.

Rule 1: Write in third person

Never use "I" to refer to the participant. Case notes are written about the participant, not by them. Use the participant's name or the word "Participant" where a name is not appropriate.

✗ Avoid this

"I helped the participant get dressed and I made breakfast for them."

"I" here is ambiguous — is this the worker or the participant speaking?

✓ Better approach

"Support worker provided hands-on assistance with morning dressing routine. Participant was then assisted to prepare breakfast independently with verbal prompting."

Rule 2: Use only objective, observable language

Write what you saw and heard — not what you interpreted. Words like "seemed", "appeared", "looked like", "was clearly", and "felt" are subjective and will be flagged in a compliance review.

✗ Avoid this

"Participant seemed upset and appeared to be in pain. He looked like he didn't want to participate."

Three subjective words: "seemed", "appeared", "looked like".

✓ Better approach

"Participant stated he was experiencing pain in his left knee. Participant declined to participate in the scheduled walking activity and requested to remain seated."

Factual. Quotes the participant directly. States what was observed.

Rule 3: Write in past tense

Case notes record what happened, so everything is written in past tense. "Participant attended" not "Participant attends". "Support was provided" not "Support is provided".

Rule 4: Be specific, not vague

Vague case notes are a major audit risk. Specifics matter: name the activity, state the duration, describe the assistance provided, and quote the participant directly where relevant.

✗ Avoid this

"Supported participant with daily activities. Participant was in a good mood. Session went well."

No specifics. "Good mood" is subjective. "Went well" is meaningless to an auditor.

✓ Better approach

"Participant was assisted with showering, dressing, and meal preparation (breakfast) at her home address. Participant initiated conversation and engaged verbally throughout the session. Participant independently selected her clothing with verbal prompting. This session addressed Goal 2 (increasing independence in daily living tasks) in the participant's current NDIS plan."

Step-by-step: how to write an NDIS case note

1

Record the basics immediately after the shift

Note the date, start time, end time, your full name, and the participant's name. Do this while details are fresh — within 24 hours at most. Memory degrades quickly, and inaccurate times can create billing disputes.

2

Write in third person, past tense from the start

Begin your narrative with the participant's name or "Participant". Write everything in past tense. If you catch yourself writing "I" or using present tense, stop and rewrite that sentence.

3

Describe the support delivered — specifically

List every activity or form of assistance provided during the session. Include the approximate time spent on each if the session covered multiple activities. Be specific: "assisted with showering" is better than "personal care".

4

Document the participant's response in objective language

Describe how the participant engaged, responded, or reacted — using only what you directly observed. Quote them directly where useful. Avoid all subjective language.

5

Link the session to NDIS goals

State which goal(s) from the participant's current NDIS plan the session addressed. This is one of the most commonly missing elements and one of the first things auditors check. Under the NDIS Practice Standards, funded supports are required to actively work toward the participant's plan goals — auditors specifically check for this linkage.

6

Record any incidents, risks, or observations

Note anything unusual: a fall, a behavioural incident, a medication issue, a change in the participant's presentation, or a safeguarding concern. Even minor incidents should be documented. If the incident meets the definition of a reportable incident under the NDIS Rules, you must also complete a separate incident report and notify the NDIS Commission within 24 hours.

7

Review for subjective language before saving

Read your note back once. Look for any word that expresses your opinion, interpretation, or assumption. Replace it with what you actually observed. The test: could another person have independently observed and confirmed what you wrote?

Spending 30–60 minutes on case notes after every shift?

Notara generates structured NDIS case note drafts in under 3 minutes. Describe what happened in plain English — Notara handles the formatting, language structure, and goal linkage. You review, adjust as needed, and save.

Try free for 14 days →

A complete case note example

Here is what a well-structured NDIS case note looks like in practice:

Example: well-structured case note

Date: 28 April 2026  |  Time: 09:00–11:30  |  Location: Participant's home, [suburb]
Support Worker: Sarah Mitchell  |  Participant: [Name]


Support worker arrived at 09:00 and conducted handover with night shift. Participant was awake and seated in living room. Participant was assisted with morning personal care routine including showering (with standby assistance due to documented fall risk), dressing (participant selected clothing independently with verbal prompting), and oral hygiene. Participant required full assistance with footwear due to reduced hand dexterity.


Breakfast was prepared (two slices of toast, tea) with participant directing preferences verbally. Participant consumed full meal without difficulty. Participant engaged in conversation throughout the session, discussing plans for the weekend.


At approximately 10:45, participant reported mild pain in right shoulder (rated 3/10 on verbal scale). Support worker documented this and advised participant that a note would be added to the communication book for the coordinator. No further action was required at this time.


This session addressed Goal 1 (maintaining independence in daily living with appropriate support) from the participant's current NDIS plan.


Incidents: Nil reportable. Pain reported as noted above — documented for coordinator review.
Follow-up: Coordinator to be advised of shoulder pain report at next check-in.

Common mistakes that fail an NDIS audit

  • Subjective language — "seemed", "appeared", "looked like", "clearly", "obviously". Replace with observable facts.
  • No goal linkage — Every session must connect to at least one NDIS plan goal. This is the single most commonly missing element.
  • Vague descriptions — "Support provided as per plan" tells an auditor nothing. Name the activities.
  • Copy-paste notes — Writing the same case note for every session. Auditors look for this pattern and it signals non-compliance.
  • Inconsistent timing — Case note times don't match billing records. This creates a billing dispute risk.
  • Missing incidents — Not documenting an incident in the case note, even if you completed a separate incident report.
  • Writing notes days later — The NDIS Practice Standards require records to be accurate. Writing notes a week after the fact from memory is a compliance risk.
  • First-person narrative — "I helped John get dressed." The note should describe what the support worker and participant each did, in third person.
Audit risk

During an NDIS audit, case notes are one of the first documents reviewed. Auditors are specifically trained to identify subjective language, missing goal linkages, and copy-paste documentation. Non-compliant records can result in repayment obligations, conditions on registration, or loss of registration entirely.

What is a reportable incident — and how does it affect your case note?

A reportable incident under the NDIS (Incident Management and Reportable Incidents) Rules 2018 is an incident that must be formally reported to the NDIS Quality and Safeguards Commission within 24 hours. The five categories are:

  1. Death of an NDIS participant
  2. Serious injury of an NDIS participant
  3. Abuse or neglect of an NDIS participant
  4. Unlawful sexual or physical contact with, or assault of, an NDIS participant
  5. Unauthorised use of a restrictive practice

If a reportable incident occurred during a session, it must be documented in the case note and in a separate incident report. The case note should describe factually what happened in sequence. The incident report provides the formal record for the Commission.

If you are unsure whether an incident is reportable, treat it as reportable until you have sought advice from your supervisor or the NDIS Commission.

How long do NDIS case notes need to be kept?

Under the NDIS Practice Standards, registered NDIS providers must retain records for a minimum of 7 years from the date of the record — or 7 years after the participant turns 18, whichever is later. This means a case note written today must be accessible and retrievable until at least 2033.

Unregistered providers are not bound by the same formal obligation, but following the same standard is strongly advisable for your own legal protection.

Frequently asked questions

How long should an NDIS case note be?
There is no mandated word count, but a thorough case note is typically 150–400 words. It should be long enough to fully describe the support session, the participant's response, and any relevant observations — but not padded with filler. Quality matters more than length. A focused 200-word note with clear goal linkage is better than a 600-word note full of vague observations.
Can I use dot points in an NDIS case note?
Some providers use structured formats with dot points for specific fields (date, time, goals addressed). However, the narrative section describing what happened should be written in full sentences. NDIS auditors expect case notes to read as a coherent account of the session, not a checklist. A hybrid format — structured header fields, narrative body — is acceptable and increasingly common.
How soon after a shift do I need to write a case note?
There is no fixed NDIS rule on timing, but best practice is within 24 hours. The NDIS Practice Standards require records to be accurate and complete — writing notes days after the shift increases the risk of errors or omissions. For incidents, documentation should be completed as soon as possible, as the 24-hour reporting window for reportable incidents begins from the time the incident occurred.
What is the difference between a case note and an incident report?
A case note is a routine record of every support session — what happened, what support was provided, how the participant responded. An incident report is a formal document specifically for when something went wrong: a fall, a behavioural incident, a safeguarding concern, or a near-miss. If an incident occurs, it should appear in both the case note for that session (as part of the factual account) and in a separate incident report with full details.
How long do I need to keep NDIS case notes?
Under the NDIS Practice Standards, registered providers must retain records for a minimum of 7 years from the date of the record, or 7 years after a participant turns 18 (whichever is later). Unregistered providers are not bound by the same rules but should follow the same standard for their own protection.
Can I use AI to write NDIS case notes?
Yes — provided the AI tool is built around NDIS documentation standards and you review every document before it is finalised. The support worker retains responsibility for the accuracy and completeness of the case note, regardless of how it was drafted. Tools like Notara are specifically built for NDIS documentation, supporting third-person language, objective tone, and mandatory fields — and flagging content that may warrant incident review, with the worker retaining responsibility for all final decisions.

Summary

A well-structured NDIS case note should: record the date, times, location, support delivered, and participant response; use third-person past tense; avoid all subjective language; link the session to NDIS plan goals; and document any incidents. Writing notes daily, with specific details, in objective language is the single most effective way to protect yourself and your participants during an NDIS audit.

Stop writing case notes by hand

Describe what happened in plain English. Notara generates a structured NDIS case note draft in under 3 minutes — with correct language structure, mandatory fields, goal linkage, and documentation flags for your review. You review, adjust as needed, and save. 14-day free trial, no credit card required.

Start free trial →