What NDIS Auditors Look for in Progress Notes: The Documentation Checklist

Quality Indicator 2.4: Information Management

Progress notes are assessed by NDIS Commission auditors primarily under Practice Standard Outcome 2.4 — Information Management and secondarily under Outcome 3.2 — Support Delivery. These two outcomes together set the compliance framework for documentation.

Outcome 2.4 requires that providers maintain records that are:

• Accurate and complete
• Contemporaneous (recorded at or near the time of the support)
• Legible and accessible
• Protected from unauthorised access
• Retained for the required period

Outcome 3.2 requires that records of support delivery demonstrate:

• That supports are being delivered consistent with the participant's plan and support agreement
• That the participant's response to supports is recorded
• That any changes in the participant's needs or circumstances are documented
• That incidents and near-misses are recorded and managed

When auditors examine progress notes, they are asking: "Do these records prove that this provider is delivering safe, person-centred, goal-aligned supports?" Every note that fails to answer that question contributes to a non-conformance finding.

What Auditors Actually Check in Progress Notes

Based on the NDIS Commission's Quality Indicators framework and typical certification audit methodology, auditors reviewing progress notes are checking the following elements:

1. Completeness

Are all required elements present? Auditors look for: participant name, date, time of shift, support activities, participant's response, any incidents, next steps/follow-up. A note that is missing any of these elements is incomplete.

2. Goal Alignment

Do the notes reference the participant's NDIS plan goals? Auditors sample the participant's NDIS plan (or a plan summary in the file) and then check whether the shift notes reflect delivery of supports towards those goals. If a participant has a goal to develop cooking independence but three months of notes never mention cooking, auditors will question whether that goal is being actively pursued.

3. Contemporaneity

Were the notes written at or near the time of the support? Notes written weeks after the shift cannot be contemporaneous. Most providers have a 24-hour policy for note completion — auditors look for evidence this policy is followed (e.g., the timestamp on digital notes, or the date of manual entries).

4. Individualisation

Are the notes genuinely about this specific participant? Auditors are trained to spot copy-paste notes, templated entries, and notes that could have been written for any participant. Identical notes across multiple shifts for the same participant are a red flag.

5. Incident Documentation

Are incidents recorded in notes and cross-referenced to the incident management system? Auditors check for consistency between shift notes and the incident register — if notes describe a fall or medication error but there is no corresponding incident report, this is a significant non-conformance.

6. Restrictive Practice Documentation

For providers with participants who have Behaviour Support Plans, auditors check that any use of regulated restrictive practices is documented in both the shift note and the Restrictive Practices Register.

7. Medication Administration

For providers administering medications, auditors cross-reference shift notes with the Medication Administration Record (MAR) to ensure consistency. A shift note that references medication administration must match the MAR entry.

The Most Common Non-Conformances Found

Based on patterns in NDIS Commission audit reports and provider feedback, these are the documentation non-conformances most frequently identified in certification audits:

What 'Contemporaneous Records' Means and Why It Matters

The NDIS Commission requires that records be contemporaneous — meaning written at the time of the support or shortly after, not retrospectively days or weeks later. This requirement serves several important purposes:

• Memory fades — notes written immediately after a shift are more accurate than notes written days later
• Contemporaneous records provide reliable evidence in safeguarding investigations or complaints
• Delayed notes raise questions about whether the support actually occurred as described

Most providers define "contemporaneous" in their Information Management Policy as within 24 hours of the shift. Some high-intensity support settings require notes to be completed before leaving the premises. Auditors assess contemporaneity by examining the timestamp metadata on digital notes or the dates written on paper records.

Record Retention Requirements: The 7-Year Rule

Under the NDIS Commission Rules and the National Disability Insurance Scheme Act 2013, NDIS providers must retain participant records — including progress notes, incident reports, and service agreements — for:

• 7 years from the date of the last entry for adult participants
• 7 years after the participant turns 25 if the participant was a child at the time of service

Note that some states and territories have additional record retention requirements under state legislation (particularly for health-related records). Providers should ensure their retention policy meets the longest applicable requirement.

Records must remain retrievable throughout the retention period. If a participant's supports are discontinued, their files must be archived securely and remain accessible for audit and investigation purposes. This means:

• Digital records must be backed up and recoverable even if the software system is changed or decommissioned
• Paper records must be stored securely against loss, damage, and unauthorised access
• Access controls must restrict who can view participant records to those with a legitimate need

Digital vs Paper Records: What's Acceptable

The NDIS Commission does not mandate either digital or paper records — both are acceptable provided the content requirements are met. However, digital systems offer several compliance advantages:

• Automatic timestamp of note creation (supports contemporaneity evidence)
• Audit trail of who created and modified each note
• Searchability — easily pull all notes for a specific participant or date range for audit review
• Backup and disaster recovery capabilities
• Remote access for team leaders and supervisors

If using digital records, ensure your system:

• Is access-controlled (username and password minimum; MFA recommended)
• Creates a non-editable audit trail of note creation and modification
• Can export notes in a readable format for audit review
• Has a documented data backup and recovery process

Paper records are acceptable but carry higher risks of loss, illegibility, and difficulty retrieval. If using paper, notes must be clearly dated and signed, stored securely, and reproduced accurately for audit review.

How Auditors Sample Records

Auditors do not review every note in your files — they work from a sample. Understanding how they sample helps you prioritise your pre-audit review efforts.

Typical sampling approaches used in NDIS certification audits include:

• Random participant selection: Auditors select a random sample of participants (often 10–20% of active participants or a fixed number, e.g., 5–10 participants) and review their complete file
• Purposive sampling for high-risk: For SIL providers, auditors typically select at least one SIL participant's file and examine overnight shift notes in detail
• Time-based sampling: Auditors may select a specific time period (e.g., the past 3–6 months) and review all notes from that period for the sampled participants
• Incident-triggered sampling: If the provider has had reported incidents or complaints, auditors may select those participants' files specifically

Within the sampled files, auditors typically read 10–30 individual shift notes per participant and cross-reference these against:

• The participant's NDIS plan goals
• The service agreement and support plan
• The incident register (for any incidents during the period)
• The medication administration record (if applicable)
• The restrictive practices register (if applicable)

What this means practically: any shift notes that are in a sampled participant's file may be reviewed. You cannot predict which participants will be selected. This means the standard of your notes must be consistently high across all participants — not just your "best" files.

The Pre-Audit Notes Self-Assessment

Conducting a self-assessment of your progress notes 8–12 weeks before an audit is one of the most valuable preparation steps a provider can take. Here is a practical self-assessment process:

Step 1: Pull a sample of your own notes

Select 3–5 participants at random (not your "best" ones) and pull their last 3 months of shift notes. Include at least one SIL participant if applicable.

Step 2: Check each note against the compliance checklist

• Participant's name is used (not "client" or "patient")
• Date and time of shift are recorded
• Activities and supports provided are described specifically
• Level of assistance/prompting is recorded
• Participant's response or mood is documented
• At least one reference to an NDIS plan goal is present
• Any incidents or changes in condition are flagged
• Note is written in third-person, objective language
• Note is not identical to any other note in the file
• Note was written within 24 hours of the shift (check timestamp)

Step 3: Cross-reference the incident register

For the same 3–5 participants, check whether any incidents referenced in shift notes are in the incident register, and vice versa. Any inconsistency needs to be addressed before the audit.

Step 4: Check the medication records (if applicable)

For participants receiving medication, cross-reference shift notes referencing medication administration with the MAR entries for the same dates. Any discrepancy needs to be investigated and resolved.

Step 5: Identify systemic issues and address them

If you find that a pattern of poor notes is from a specific support worker, address it through supervision and training. If it is systemic across the organisation, implement a notes review process and training programme before the audit.

What Happens When Notes Are Found Non-Conformant

If an auditor identifies a non-conformance in your progress notes, the process is as follows:

1. Finding issued: The auditor documents the non-conformance in their audit report, specifying the Practice Standard outcome that was not met and the evidence (e.g., "5 of 10 sampled shift notes lacked time/date recording, non-conformant with Outcome 2.4")
2. Severity classification: The non-conformance is classified as Major or Minor. Major non-conformances prevent registration approval until resolved. Minor non-conformances require a corrective action plan.
3. Corrective Action Plan (CAP): The provider must submit a CAP documenting what changes will be made, who is responsible, and by when. For documentation non-conformances, this typically involves: staff training on note standards, supervisory review of notes, updated note-writing policy, and a monitoring process.
4. Verification: The auditor or NDIS Commission reviews evidence that the CAP has been implemented before granting registration (for major non-conformances) or as a surveillance audit activity (for minor non-conformances).

Documentation non-conformances are entirely preventable. Unlike equipment failures or clinical incidents, poor notes are a skills and systems problem — and they can be fixed before the audit.

Building a Culture of Good Note-Writing in Your Organisation

The most sustainable solution to documentation quality is not individual note-by-note editing — it is building an organisational culture where good notes are the expected standard, supported by training, supervision, and feedback systems.

Key strategies for building this culture:

1. Set and communicate the standard clearly

Workers cannot write good notes if they don't know what good looks like. Provide training that includes real examples — both non-compliant and compliant — for every support type your organisation delivers. This guide and the related articles in this series provide that resource.

2. Build supervisory review into the workflow

Team leaders or supervisors should review a sample of each worker's notes monthly. Provide specific, constructive feedback — not just "your notes need to be better" but "this note does not reference Maya's goal — here is how you could add that". Positive feedback when notes are good is equally important.

3. Use templates and structure

A structured progress note template reduces the cognitive load of remembering what to include. Templates with prompts ("Goal referenced:", "Prompting level:", "Response:") support consistent documentation. The SIL Rescue Kit's Shift Notes template (Document 36) provides this structure in a format aligned to NDIS Commission requirements.

4. Respond to non-compliant notes quickly and constructively

When a supervisor finds a non-compliant note, address it immediately — not at the next monthly meeting. A quick coaching conversation immediately after the note is written cements learning far more effectively than delayed feedback.

5. Use technology to support quality

Tools like our free NDIS Notes Rewriter can help workers who are struggling to express themselves in a compliance-appropriate way transform their existing language into audit-ready notes. This is particularly valuable for new workers or workers for whom English is not their first language.

6. Celebrate and share good notes

When a worker writes an exceptional note, share it (with appropriate de-identification) as an example of the standard the whole team is aiming for. Recognition drives culture change more effectively than any policy document.