What NDIS Auditors Look For in Progress Notes (2026 Checklist)

Last updated 2026 · SupportNotes · Made in Australia

What do NDIS auditors actually look for in progress notes?

Here is the short version: an auditor opens your progress notes to answer one question — do these records prove this provider is delivering safe, person-centred, goal-aligned support, every shift? Your notes are the single most-sampled piece of evidence in an NDIS audit, because they are the only record showing what actually happened on the ground, day after day. Policies say what you intend to do. Notes prove whether you did it.

An NDIS Approved Quality Auditor is not reading your notes for nice writing. They are matching each note against the NDIS Practice Standards and their Quality Indicators — the specific statements that describe what an auditor expects to see in operation. If a note cannot answer 'what support was given, how did the person respond, and which goal does this serve?', it becomes a gap. Enough gaps add up to a non-conformance finding, and inadequate progress notes are consistently among the most common documentation findings in NDIS audits.

The good news: auditors are looking for the same handful of things in every note. Once you know what they are, writing audit-ready notes becomes a checklist, not a guessing game.

Which Quality Indicators do progress notes get checked against?

Progress notes are not assessed against one rule — they are evidence for several Quality Indicators at once. For most support providers (and especially SIL providers preparing for certification before the 1 July 2026 mandatory registration date), notes are checked most directly against four Quality Indicators, listed below.

Note: the exact wording and numbering of Practice Standards Quality Indicators is published by the NDIS Quality and Safeguards Commission, and SIL providers are assessed under both the Core Module and applicable specialist modules. Always check your scope of registration — but in practice, if your notes satisfy 2.3, 2.4, 4.1 and 4.3, they will carry you through most documentation questions an auditor asks.

• Quality Indicator 2.3 — Responsive Support Delivery: your notes should show support was delivered in line with the participant's plan and changing needs, not a generic routine.
• Quality Indicator 2.4 — Information Management: records must be accurate, complete, current, stored securely, and retrievable. This is the home of the classic 'incomplete note' finding.
• Quality Indicator 4.1 — Safe Environment: notes should evidence that risks were identified, acted on, and the participant was kept safe during support.
• Quality Indicator 4.3 — Medication Management: for providers who administer medication, notes (and the medication chart) must show what was given, when, the dose and route, who supported it, and the observation afterwards.

The 7 elements an auditor checks in every note

When an auditor samples a progress note, they run their eye down it looking for the same required elements. A note missing any of these is, in audit language, 'incomplete' — and incomplete is a finding waiting to happen.

Two more things auditors quietly check: was the note written close to the time of support (not reconstructed from memory days later), and is it objective? Interpretive words — 'seemed', 'good day', 'refused', 'non-compliant', 'attention-seeking' — record your opinion, not a fact an auditor can verify, and several of them breach the NDIS Code of Conduct by being disrespectful. Replace each one with the behaviour you actually observed.

• Participant name — the correct person, clearly identified.
• Date — the calendar date of the support.
• Exact time — start and finish, or the time of the event you are recording (not 'this afternoon').
• Support activities — what you actually did, in plain, observable language.
• Participant's response — how the person reacted: what they said and did, not how they 'seemed'.
• Risks, incidents or changes — anything unusual, any incident, any change in health or behaviour, and what you did about it.
• Next steps and goal link — what follow-up is needed and which NDIS goal this support serves.

Before and after: rough notes vs audit-ready notes

The fastest way to understand what auditors want is to see the same shift written two ways. The facts are identical — only the detail and the objectivity change.

Example 1 — a community access shift. Rough (a finding waiting to happen): 'Took Sam out. Had a good day. All fine.' Why it fails: no time, no actual activity, 'good day' is an opinion, and there is no link to any goal. An auditor cannot tell what support was delivered or why.

Audit-ready: 'Supported Sam (participant) on 14/02/2026, 10:00am–12:30pm, to catch the bus to the local library and borrow two books, working toward his goal of using public transport independently. Sam read the timetable with one prompt and tapped his Myki without help. No incidents. Next shift: practise the return journey with fewer prompts.'

Example 2 — a medication note. Rough: 'Gave Maria her meds. All good.' Why it fails: no time, no medication name, no dose, no route, no record of how it was supported, and no observation afterwards. In a medication incident review, this single line is indefensible.

Audit-ready: 'At 8:05am administered Maria's morning medication as charted (1 x 500mg paracetamol, oral) and signed the medication chart. Maria took it with water without difficulty. Observed for 15 minutes; no adverse reaction. Chart and note cross-checked.'

Notice that the audit-ready versions are barely longer — they just trade opinions for observable facts, and add the time, the detail, and the goal. That is the whole difference between a pass and a corrective action plan.

How auditors sample your records (so you can't just fix one note)

Auditors do not read every note — they sample. They will pick a handful of participants and pull their notes across a date range, then cross-check those notes against the same participants' service agreements, support plans, goals, incident reports and medication charts. They are testing whether your system is consistent, not whether one note is tidy.

This is why fixing a single note before an audit does not work. If notes for one participant link to goals but another participant's notes are vague, the auditor sees an inconsistent system — and inconsistency is itself a finding. The fix is a repeatable process every worker uses on every shift, so any note pulled at random tells the same complete story.

It is also why the sister checklist on this topic — our deeper guide to documentation audit requirements — is worth reading alongside this one. The two articles cover the same Quality Indicators from different angles, and together they give you the full audit lens on your records.

The 60-second self-audit checklist

Run any note past these eight checks before you sign off. Eight ticks means audit-ready. Anything you cannot tick is a gap an auditor would find — fix it now, not eighteen months later in an audit interview.

If writing this for every participant after a long shift feels like a second job, that is the real reason poor notes happen — time, not laziness. The fix is a better process. Our free Notes Rewriter tool turns rough, phone-typed notes into structured, objective, goal-linked progress notes in seconds, without inventing a single detail. It removes most of the after-shift admin while lifting the quality of the record. Try it on your next shift note and see the difference.

• Right participant, clearly named?
• Date and exact time recorded?
• Specific support activity described (not 'support provided')?
• Participant's response in observable terms (what they said and did)?
• Any risk, incident or change captured — with what you did about it?
• Linked to a goal from the participant's plan?
• Free of opinion words ('seemed', 'good/bad day', 'refused', 'non-compliant')?
• Written at or near the time of support, and signed?

What happens if your notes fail audit?

A documentation non-conformance is a written finding that you have not met one or more requirements of the NDIS Practice Standards. For inadequate progress notes, the auditor issues the finding and requires you to submit a Corrective Action Plan within a set timeframe. Minor findings usually need a documented improvement action; major findings can delay or prevent registration. In serious cases the NDIS Commission can take further compliance action.

The takeaway is simple: notes are not paperwork you do after the 'real' support. They are the real evidence. For SIL providers heading into certification before the 1 July 2026 deadline, getting your notes audit-ready early is one of the highest-return things you can do.

If you also need your underlying policies, procedures and registers in order — not just your notes — the SIL Rescue Kit ($297) gives you the audit-ready document set that sits behind your progress notes, mapped to the same Practice Standards. It pairs naturally with the free Notes Rewriter: the kit fixes your system, the tool fixes your daily records.

Frequently asked questions