Resources › Checklist
NDIS Practice Standards
Compliance Checklist
The NDIS Practice Standards define the quality and safety requirements for all registered NDIS providers. This checklist organises the key obligations by module, 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.
Rights and Responsibilities
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
CoordHub generates compliant service agreements from participant referral data and tracks agreement status across all active participants.
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
Built-in complaints register with timestamped intake, assigned owner, resolution tracking, and automated reminders for overdue items.
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
Participant records include fields for authorised representatives, nominees, and advocacy contacts, with access controls to match.
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
Role-based access controls ensure only authorised staff see participant data. Audit logs record every access event.
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
Participant profiles capture cultural and communication preferences, flagged during scheduling and progress note creation.
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
Risk register with severity and likelihood scoring, mitigation plans, review scheduling, and approval workflows.
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
Per-minute billing engine generates itemised claim records aligned to NDIS price guide line items. All records are exportable for audit.
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
Staff credential tracking module monitors expiry dates for screening checks, first aid, and mandatory training, with automated alerts.
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
Incident reporting module captures incident details at point of occurrence, triggers notification workflows, and tracks Commission reporting deadlines.
Quality improvement system
What’s required
Providers must have processes for monitoring service quality, reviewing adverse events, and making continuous improvements.
How software helps
Compliance dashboard aggregates incident rates, complaint trends, and credential gaps to identify systemic improvement opportunities.
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
Scheduling conflict detection and participant allocation reporting help coordinators identify coverage gaps before they become disruptions.
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
Goal-linked support plans are created during onboarding and can be updated without losing version history.
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
Shift scheduling filters staff by capability and checks credential status before confirming allocation.
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
Progress notes are linked to specific goals. Automated review prompts are triggered when plans approach expiry.
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 are tracked per participant, with administration logs and prescribed staff access controls.
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
Restrictive practices register tracks authorisation status, usage incidents, and reduction plans per participant.
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
Exit workflows ensure records are finalised, outstanding claims reconciled, and referral handover documented.
Safe and supported environment
What’s required
Participants must be protected from abuse, neglect, exploitation, and unlawful discrimination while receiving supports.
How software helps
Safeguarding alerts flag unusual patterns in incident reports. Worker screening verification is enforced before access is granted.
Documentation standards
What’s required
All case records must be accurate, current, complete, and stored securely with controlled access.
How software helps
Role-based document access, immutable progress note records, and structured templates ensure documentation meets audit standards.
Support Provision 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
Venue and location records can be linked to participants and inspections, with maintenance scheduling and compliance notes.
Emergency and evacuation procedures
What’s required
Providers operating in shared environments must have documented emergency response and evacuation procedures.
How software helps
Emergency plan documents are stored per location with review dates tracked and staff acknowledgement recorded.
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
Policy documents with version control and mandatory staff acknowledgement workflows keep IPC protocols current.
Food safety (where applicable)
What’s required
Providers delivering meal preparation or food handling must comply with applicable food safety standards.
How software helps
Custom compliance checklist templates can be configured for food safety obligations and assigned to relevant service types.
See how CoordHub addresses these requirements
CoordHub is purpose-built NDIS practice management software. Every feature maps to a specific compliance obligation so your team spends less time on admin and more time supporting participants.