Part of Provider Compliance, NDIS and aged care consultants1800 299 452 · info@providercompliance.com.au
Free guide

How to write good NDIS case notes: a practical guide with examples

Last reviewed 21/11/2026 by Provider Compliance against official sources

Case notes are the written memory of every shift. The next worker reads them to know what happened, team leaders use them to spot changes early, and auditors read them to see whether the supports in a person's plan are really being delivered. A good note takes two or three minutes to write. A poor one can leave the next worker guessing, hide a decline in someone's health, or fail to show that a support you claimed for actually happened. This guide sets out what to record, how to keep your language objective and respectful, worked examples of poor and good notes, and the mistakes we see most often when we review participant files.

Why case notes matter

Under the NDIS Practice Standards, registered providers must manage each participant's information so it is accurately recorded, current and confidential, and record it in an accurate and timely manner. The participant must also be told how their information is used and how they can see or correct it. In practice that means your notes do four jobs at once:

Always write as if the person you support will read the note, because they have the right to ask to.

What to record in every note

Keep a simple structure so nothing gets missed. A useful shift note covers:

  1. Date, start and finish times, and who was present.
  2. Supports provided, matched to the service agreement or support plan (for example, meal preparation, community access, personal care).
  3. Goal progress, with a concrete detail, not just a tick.
  4. Health and wellbeing: anything you observed, including medication support if that is part of your role.
  5. What the person said and chose, in their own words where it helps.
  6. Anything unusual, and what you did about it, including who you told.
  7. Follow up needed by the next worker or the team leader.

Leave out gossip, opinions about family members, information about other participants and anything not relevant to the support.

Use objective, person centred language

Objective notes describe what you saw, heard and did. Labels such as aggressive, non-compliant, attention seeking or in a mood are interpretations. They can be wrong, they follow a person around for years, and they tell the next worker nothing useful. Describe the behaviour, what happened before it, and what helped.

Person centred language puts the person first and talks about their choices and strengths as well as their needs. Write Sam chose not to shower this morning and said he would shower after lunch, not Sam refused personal care. Use the name the person prefers, and quote them directly when their exact words matter.

Poor notes vs good notes: examples

Here is what the difference looks like in practice. The names are made up.

Poor noteWhy it falls shortBetter note
Good day. No issues.Says nothing about supports, goals or wellbeing. Nobody can rely on it.9am to 1pm. Supported Ana to catch the 9.40 bus to the library for her reading group. Ana tapped her own card on and chose her seat. She said she wants to try the trip with me sitting further back next week. Ate all of her lunch. No concerns.
Jack was aggressive at dinner.A label, with no detail about what happened, why, or what helped.At about 6.15pm, when the TV was turned off for dinner, Jack shouted and pushed his plate away. I offered to turn the TV back on quietly. Jack sat down within two minutes and ate his meal. No injuries. Recorded for the team leader as the third time this week linked to the TV going off.
Mei seemed unwell, told her to rest.Vague, no observations, no escalation recorded.At 2pm Mei said she felt dizzy and had a headache. She looked pale and ate half her usual lunch. I followed her health support plan, called the on call team leader at 2.10pm and was asked to call her GP, who booked her in for 4pm. Handed over to the evening worker.
Cleaned house. Did shopping.Lists tasks but not the person's involvement or goals.Tom chose the shopping list from his meal plan and paid at the self serve checkout with prompting for the card step only, which is progress on his money handling goal. He vacuumed the lounge; I did the bathroom.

When to write your notes

Write notes during or straight after the shift, while details are fresh. Notes written days later are less accurate and carry less weight if something is ever questioned. If you could not write the note on time, record when you wrote it. Never write a note before a support has happened, and never copy and paste yesterday's note: auditors spot identical notes quickly, and so do participants.

Keep it clear and concise. Plain English, short sentences, no abbreviations your team does not all use, and the 24 hour clock or am and pm used consistently.

Privacy and safe record keeping

Respecting privacy is one of the eight elements of the NDIS Code of Conduct. For case notes that means:

If you make a mistake, correct it using the system's amendment function, or with a single line through the error on paper, initialled and dated. Never delete or overwrite an entry so the original cannot be seen. For incident records, the Commission's incident management guidance says they must be kept for at least 7 years from the date the record is made, and state or territory laws may add to that.

Incidents and changes need more than a note

If something happens that harmed or could have harmed someone, your case note should give a short, factual summary and say that an incident report was completed. The detail belongs in the incident report. Our NDIS incident reporting guide explains what to do on shift and the Commission's timeframes.

What auditors look for, and common mistakes

When an auditor samples participant files, they usually look for notes that match the support plan and service agreement, show the person's goals being worked on, record changes and how they were followed up, and line up with incident records, rosters and invoices. They also notice gaps, such as shifts with no note at all.

The mistakes we see most often are:

Train your team

Our Case Notes for Support Workers course teaches all of this with worked examples and case studies, and NDIS Scenarios and Case Noting gives workers practice writing notes for real situations. Pair them with Privacy and Confidentiality and Incident Reporting:

55 min
Core Compliance

Case Notes for Support Workers

Case notes are the written record of the supports we provide. Good notes keep the team informed, show a participant's progress towards their goals, protect everyone if something goes wrong, and are evidence that supports were delivered as agreed. This course teaches you to write case notes that are objective, factual, timely and person centred. You will learn why notes matter, your privacy and record keeping obligations, what to include and leave out, how to describe what you see and hear rather than your opinions, and how to write respectfully about the people we support. Worked examples and two case studies from real shifts show the difference good notes make. Duration: 55 minutes.

11 lessons · 5 scenarios$55
55 min
Core Compliance

NDIS Scenarios and Case Noting

Case notes are one of the most important things you write as a support worker. They keep the next worker informed, protect the participant's rights and show auditors that supports were delivered safely and as agreed. This course starts with what good case notes look like: objective, factual, timely, respectful and private. We then work through five realistic scenarios covering choice and control, safety and incident response, professional boundaries, medication and cultural safety. For each one you will see the right response, why it matters under the NDIS Code of Conduct and our policies, what to avoid, and a model case note you can learn from. Duration: 55 minutes.

15 lessons · 5 modules$55
50 min
Core Compliance

Privacy and Confidentiality

Every day we are trusted with deeply personal information about the people we support: their health, their homes, their families and their finances. This course explains what privacy and confidentiality mean in disability and aged care support, the laws that protect personal information, including the Privacy Act 1988 and the Australian Privacy Principles, and how the NDIS Code of Conduct and our privacy policy apply to your work. You will learn how to collect, store, share and dispose of information safely, how to handle requests from family and other services, and what to do if information is lost or shared by mistake. Case studies about a lost work phone and a worried sister show these skills in action. Duration: 50 minutes.

8 lessons · 5 scenarios$55
50 min
Core Compliance

Incident Reporting

Incidents happen in every support setting, and how we respond in the first minutes and hours makes a real difference to the people involved. This course explains what an incident is, the different types you may come across, and the immediate steps to take to keep everyone safe. You will learn how to report and document incidents through our internal system, what makes a good incident report, and which incidents are reportable incidents that registered NDIS providers must notify to the NDIS Quality and Safeguards Commission, including the 24 hour and 5 business day timeframes. Case studies about a fall at home and an unreported restrictive practice show how it all fits together. Duration: 50 minutes.

8 lessons · 5 scenarios$55

Enrolling a whole team? Our team purchase page lets you buy seats for any mix of courses with one payment and one tax invoice, and your team dashboard tracks every learner's progress and certificates for your training register.

Frequently asked questions

How do you write a good NDIS case note?

Write it during or straight after the shift. Record the date and times, the supports provided, progress towards the person's goals, their health and wellbeing, what they said and chose, anything unusual and who you told, and any follow up. Describe what you saw and heard rather than giving opinions or labels.

What should not go in a case note?

Opinions, labels, gossip, details about other participants, and anything not relevant to the support. Keep personal views about family members or colleagues out of the record.

Can participants read their case notes?

Yes. Under the NDIS Practice Standards participants must be told how their information is used and when and how they can access or correct it. Write every note as if the person will read it.

How long must NDIS records be kept?

The NDIS Commission's incident management guidance says incident records must be kept for at least 7 years from the date the record is made. State and territory laws may set further requirements, so check your organisation's records policy.

How do I fix a mistake in a case note?

Use your system's amendment function so the original entry is still visible, or on paper draw a single line through the error and initial and date it. Never delete or overwrite a note.

Source: NDIS Quality and Safeguards Commission. Checked 21/11/2026. Provider Compliance is not affiliated with NDIS Quality and Safeguards Commission.