Resources › Checklist
NDIS Practice Standards
Compliance Checklist
The NDIS Practice Standards define the quality and safety requirements for all registered NDIS providers. This checklist covers the core module, which applies to providers delivering higher-risk supports, and restrictive practices, which sit in a supplementary module. It organises the key obligations by the part of the Standards they come from, explains what each requires, and shows how purpose-built software supports compliance.
Based on NDIS Practice Standards (January 2020, as amended). Always verify against the current registered version at ndiscommission.gov.au.
On this page
Rights and Responsibilities
Advocacy and decision support
What’s required
Providers must respect a participant's right to have a support person, advocate, or nominee involved in decisions about their supports.
How software helps
A system can record representatives, nominees and advocacy contacts with access permissions that match their roles.
Participant privacy and information access
What’s required
Participants have the right to access their own records and to know how their personal information is collected, used, and disclosed.
How software helps
Define access by role, keep an access history, and provide a clear process for participant information requests.
Cultural, linguistic, and individual needs
What’s required
Supports must be responsive to each participant's cultural, religious, and linguistic background, as documented in their support plan.
How software helps
Capture communication and cultural preferences where staff need them, with appropriate privacy controls.
Safe and supported environment
What’s required
Participants must be protected from abuse, neglect, exploitation, and unlawful discrimination while receiving supports.
How software helps
A safeguarding workflow could connect intake risks, human review, incident records and staff screening checks. Decide which conditions warn and which prevent a task from proceeding.
Provider Governance and Operational Management
Risk management framework
What’s required
Providers must have a documented risk management system that identifies, assesses, and controls operational and participant-level risks.
How software helps
A risk register can connect assessments to owners, mitigation plans, review dates and approvals.
Financial management and record keeping
What’s required
Accurate financial records must be maintained for all NDIS-funded supports, including claims, receipts, and participant fund usage.
How software helps
Keep an itemised record behind each claim, check it against the current NDIS pricing schedule, and design exports that make reconciliation and review possible.
Human resource management
What’s required
Providers must maintain staff records including qualifications, NDIS Worker Screening Check status, and mandatory training completion.
How software helps
Track required credentials, expiry dates, review owners and the work affected by a missing record.
Skilled and trained workforce
What’s required
Staff delivering supports must have the skills, experience, and qualifications relevant to the participant's needs.
How software helps
Rostering rules can check the credentials relevant to a role before work is assigned, while keeping a human able to review exceptions.
Incident management and notification
What’s required
Providers must have a documented system for recording, investigating, and notifying the NDIS Commission of reportable incidents within prescribed timeframes.
How software helps
An incident workflow can record what happened, assign responsibility, track reviews and make applicable reporting deadlines visible.
Quality improvement system
What’s required
Providers must have processes for monitoring service quality, reviewing adverse events, and making continuous improvements.
How software helps
Bring incidents, complaints and credential gaps into one review view so trends can lead to action.
Continuity of supports
What’s required
Providers must plan for continuity of participant supports in the event of a disruption such as staff unavailability or system outage.
How software helps
Show scheduling conflicts, handovers and coverage gaps early enough for staff to respond.
Participant feedback and complaints system
What’s required
Providers must have a system for receiving, recording, and acting on participant feedback and complaints. Participants must be told how to make a complaint.
How software helps
A complaints register should capture intake, ownership, actions, outcome and follow-up dates.
Documentation standards
What’s required
All case records must be accurate, current, complete, and stored securely with controlled access.
How software helps
Structured records, version history and role-based access can make a later review easier to understand.
Emergency and evacuation procedures
What’s required
Providers operating in shared environments must have documented emergency response and evacuation procedures.
How software helps
Decide which emergency details belong to a participant, a location or the provider, and keep each plan current.
Provision of Supports
Assessment and planning
What’s required
Each participant must have an individual support plan based on a formal assessment of their needs, goals, and circumstances.
How software helps
Link assessments, goals and support plans while preserving earlier versions and review decisions.
Progress monitoring and review
What’s required
Providers must monitor progress toward participant goals, document outcomes, and trigger plan reviews at appropriate intervals.
How software helps
Connect progress notes to goals and make upcoming plan reviews visible to the responsible person.
Written participant agreements
What’s required
Every participant must have a current written service agreement setting out the supports to be delivered, the price, and the participant's rights to choose, refuse, or exit services.
How software helps
Track agreement versions, sign-off and current status alongside the support arrangement.
Transition planning
What’s required
When a participant exits services, providers must manage the transition in a way that protects continuity of support.
How software helps
An exit checklist can bring records, outstanding items and handover responsibilities into one place.
Provision of Supports Environment
Safe physical environments
What’s required
Where services are delivered in a physical setting, the environment must meet safety standards and be appropriate to participant needs.
How software helps
Separate participant home checks from inspections of provider-operated venues; each has a different owner and review cycle.
Infection prevention and control
What’s required
Providers must have infection control protocols appropriate to the services delivered and the vulnerability of participants.
How software helps
Versioned policies and staff acknowledgements can show which protocol was in force and who reviewed it.
Medication and clinical support
What’s required
Where medication administration is part of a support plan, providers must have documented protocols and trained staff.
How software helps
Medication records need clinical oversight. Assess whether a dedicated clinical system is required and how relevant information should be shared safely.
Food safety (where applicable)
What’s required
Providers delivering meal preparation or food handling must comply with applicable food safety standards.
How software helps
A configurable checklist can support provider-specific tasks, ownership and periodic review.
Implementing Behaviour Support Plans
Restrictive practices oversight
What’s required
The use of any regulated restrictive practice requires prior authorisation and must be monitored, reported, and reduced over time.
How software helps
This area needs specialist review. Any system design should distinguish authorisation, implementation, monitoring and reporting records.
Designing a more reliable NDIS workflow?
We can discuss where software might help your team keep responsibilities, records and reviews connected. Your organisation and its advisers remain responsible for interpreting the standards.