What it is and who needs it
A continuous improvement register is a running log of things you have decided to change, why, who is doing it and whether it worked. Registered providers on the certification pathway are expected to show continuous improvement, and most use a register to do it. It also helps providers on the verification pathway show a living system. Our audit checklist places it among the records auditors ask for.
What it provides evidence for
The Core Module outcome on quality management expects a system proportionate to your size that promotes continuous improvement of support delivery. Its indicators call for a documented program of internal audits and for improvement that uses outcomes, risk-related data, evidence-informed practice and feedback from participants and workers. The outcomes for incident management and for feedback and complaints each repeat the point: reviews of incidents and complaints must feed back into practice.
What auditors check
Auditors look for sources, owners and endings. They want to see entries drawn from more than one place, actions that were given an owner and a date, and at least some that are finished with evidence the change happened. They then test it. They may ask a worker whether a recent change reached them, or check that a complaint listed in the register changed a procedure.
Must-include checklist
- A reference number, the date logged and the person who raised the item.
- The source: incident, complaint, near miss, internal audit, participant or worker feedback, risk review or a rule change.
- A short description of the issue or opportunity.
- The action decided, in words someone else could carry out.
- The person responsible and a due date.
- Status, with the date the item was closed.
- Evidence of completion, such as a revised procedure or training record.
- A check that the change worked, with the date it was done.
- The date and meeting at which management reviewed the register.
Common mistakes
- Filled in the week before the audit. Dates bunched together give it away.
- Everything is "ongoing". An action with no end date or outcome shows nothing changed.
- One source only. A register made up entirely of staff suggestions misses what participants and incidents are telling you.
- No proof of effect. Closing an item because the procedure was rewritten is not the same as knowing workers follow it.
- Never discussed. If no meeting minutes mention the register, it is a document, not a system.
How to adapt it to your organisation
Scale the register to the number of people it serves. A sole trader might hold it in a spreadsheet with a monthly review date in their diary. A larger provider may need categories by service line and a named improvement lead. Tie each source to a real process: your complaints procedure should say where a complaint outcome is logged, and your internal audit program should say where audit findings go. Set a review rhythm that you will actually keep, and put it in your calendar and your meeting agenda. Decide how you will gather worker and participant feedback, because the register is only as good as what goes into it. Keep entries factual so the register can be shown to an auditor as it stands.
How the package covers it
The Core Module documents in the package cover continuous improvement and quality management, alongside the incident, complaints and risk systems that feed it. See what is included and pricing. Whatever you start from, the entries must be your own.
This page is general information based on NDIS Commission and government sources at the date shown. It is not legal or professional advice, and the rules can change. Check the NDIS Commission's current requirements and read our disclaimer. The checklists on this page describe good practice, not an official list of requirements, and our documents do not guarantee registration.