NDIS corrective action template: record the change and check it worked

“Policy updated” can be a useful progress note. It is usually an incomplete answer to the question, “Has the problem been addressed?”

Closing a corrective action means making a reasoned decision about the response, supported by evidence. You need to know what changed, whether it was put into practice and what the check of its effectiveness showed. A completed task and a closed finding are not always the same thing.

This article provides a practical closure method for internal quality work. It also explains why your internal status must remain separate from an external auditor's or regulator's decision.

Distinguish three parts of the response

Use these working distinctions to organise the record:

These examples concern document handling. For a live safety issue, the immediate response must fit the actual risk and relevant procedures. Do not delay protective action while preparing a perfect root-cause statement or waiting for a review meeting.

The Core quality-management indicators connect improvement with evidence, outcomes and feedback. The method below is our suggested way to organise that work, not a prescribed closure form. NDIS Commission: quality management.

A seven-field corrective action template

Use this record for one finding and its linked actions. It is a suggested working template, not an official NDIS form. Keep the original finding, evidence references and later review decisions together. Where actions have different owners or dates, give them separate linked entries.

Add the closure decision-maker and date. If the finding belongs to an external process, record that process's outcome separately from your internal status. A blank cell means information is missing; it is not evidence that a step was unnecessary.

Write the finding so it can be checked later

A finding needs an observable problem and a boundary. “Document control is poor” leaves too much open. Try: “On 10 September, two of three checked download locations supplied superseded version 1.0 of form FRM-008, although version 1.1 had been approved for use from 7 September.”

That fictional finding tells you what to test later. It identifies the affected process, the sample and the expected state. It does not claim every document in the organisation is wrong.

Keep the original finding unchanged as the work develops. Add clarification if needed, but do not quietly soften it so the eventual action appears successful. If a wider problem emerges, record the expanded scope and why it changed.

Separate a cause from a plausible explanation

“Staff forgot” may describe what someone thinks happened. It does not explain why the process allowed an obsolete copy to remain available.

Check the evidence for the proposed cause. In the form example, you might find that the release checklist covers the shared drive but omits a saved website download and a printed blank-form folder. That is a specific process gap you can address.

Where the cause remains uncertain, label it as a hypothesis and define what will help test it. Do not turn a brief conversation into a confident finding about a worker's motivation. Listen to the people using the process and consider whether instructions, access, workload or unclear responsibilities contributed.

The aim is a useful explanation, not a particular diagram or a fixed number of “why” questions. Use an investigation proportionate to the concern and within the competence and authority of the people undertaking it.

Define the closure test before doing the work

Agree what evidence will be sufficient and who will review it. This reduces the temptation to declare success using whatever evidence happens to be easiest to collect.

State the expected result, scope, method and review point. For the document example, a test might be: “After the next release, check all three known distribution locations and ask two relevant users to retrieve the approved version. Record each result and any limitation.”

That is a fictional local test, not an NDIS-mandated sample. A different problem may require observation over time, participant feedback, a larger review or appropriately qualified assessment.

If the process has not run again, you may be able to test its design or simulate a step. Label that evidence honestly. A rehearsal is not proof of consistent real-world performance. Keep an effectiveness review open where the required evidence does not yet exist.

A fictional action taken through to closure

Example Supports discovers the obsolete-form problem described above. No real organisation, worker or participant is represented in this example.

Finding CA-018: Two checked locations supplied FRM-008 version 1.0 after version 1.1 became effective.

Immediate response: The document owner replaces the obsolete unused copies at the known locations, verifies that the current links open correctly and informs affected workers which version to use. Existing completed records remain intact.

Cause supported by review: The release checklist lists only the shared drive. There is no assigned step for checking the other two distribution locations.

Corrective action: The owner adds a distribution-location list, assigns a release check and records its result with each approval. A backup owner is identified for absence cover.

Implementation evidence: Revised release checklist version 1.2, its approval record, the location list and a completed check for the replacement copies.

Effectiveness evidence: During the next genuine form release, the reviewer checks all three locations. Each contains the approved version. Two relevant users independently retrieve it using their normal route. The reviewer records the references and notes that the check covers this release only.

Closure decision: “Close CA-018 on the evidence listed. The identified distribution gap has been addressed and the next release check met the agreed criteria. Include release-location checking in the ongoing review routine. Reopen if another superseded blank version is found in current use.”

This decision makes a bounded claim. It does not promise that no document error can ever happen again.

Check implementation and effectiveness separately

Useful implementation evidence might include an approved procedure, a changed system setting, a completed repair, a communication record or a genuine training record. It shows that the planned response occurred.

Effectiveness evidence asks a different question. Did the relevant people use the change? Did it address the issue within the stated scope? Did it introduce a new difficulty? Was the person affected able to explain whether the response helped?

Training attendance alone does not prove competence or sustained practice. An email being sent does not prove its instructions were understood. A new field appearing in a form does not prove that staff record the information accurately. Match the check to the problem you are trying to solve.

Where an action affects participants, decide how their views can appropriately inform the review. Do not seek agreement merely to obtain a favourable closure statement. Record concerns and conflicting evidence as well as positive feedback.

Give the reviewer enough independence to challenge the result

Where practical, use someone other than the action owner to check the evidence. Give them access to the original finding and agreed closure criteria, not only a summary written by the person who made the change.

In a very small service, full role separation may not be possible. Record the actual author and reviewer, and consider an appropriate external or peer review for work beyond your competence or involving significant risk. Do not claim an independent review when you reviewed your own work.

A reviewer should be able to say “partly effective” or “not enough evidence yet.” Those are useful outcomes. They identify the next decision instead of disguising uncertainty as completion.

Keep internal closure separate from external acceptance

If an approved quality auditor raised the non-conformity, follow their required corrective-action and follow-up process. The Commission's guidance describes auditor review of actions and the steps for recording closure of open non-conformities. Your internal “closed” status cannot substitute for that external decision. NDIS Commission: information for quality auditors.

Keep separate fields if necessary: internal implementation status, internal effectiveness decision, evidence submitted externally and external outcome. Retain the actual correspondence and dates. Apply the specific deadline given for the finding; the sample dates in a training article do not extend it.

Likewise, closing an action linked to an incident does not remove incident reporting or other outstanding responsibilities. The Commission describes corrective action as part of incident management, alongside assessment and notification. NDIS Commission: incident management.

Use a final closure checklist

Before closing, check that the record contains:

• The original finding and its scope.
• Immediate measures and any remaining risk.
• The supported cause, with uncertainties identified.
• The action actually implemented, including its owner and date.
• Retrievable evidence of implementation.
• The agreed effectiveness test and actual results.
• Relevant feedback and any conflicting evidence.
• The reviewer's decision, reasoning and limitations.
• Separate status for any external acceptance still required.
• A continuing check or reopening trigger where appropriate.

Take one action currently marked “done” and apply these questions. If implementation is complete but effectiveness has not been checked, change the status to reflect that and assign the review. Accurate progress is more useful than a tidy closed-action count.

To see how a source issue can remain connected with its next action and review, watch the ProviderQMS walkthrough.

Official sources reviewed 13 September 2026. Examples and closure methods are practical suggestions; they do not certify conformity or replace an auditor's or regulator's decision.