Skip to main content
All articles
NDIS2 min read30 March 2026

What the NDIS Practice Standards actually require from your software

Reviewed 4 October 2026 against current source guidance.

On this page

Find the applicable modules

The NDIS Practice Standards set out outcomes for registered providers. The applicable audit pathway depends on registration groups and the supports delivered. The Commission's provider pack identifies a core module, a verification module and supplementary modules. Confirm which apply before turning a general standards list into software requirements.

Records and access

For participant rights and support delivery, a system can help staff keep current consent, plans, agreements and review records together. Access controls and a record of changes may make it easier to show how information was handled. The Standards describe outcomes; they do not prescribe a particular database design, field layout or reminder feature.

Incident management

Incident management is an obligation for registered providers. A useful workflow records when a concern was received, who assessed it, how the person was supported and whether notification to the Commission was required. Most reportable incidents have a 24-hour notification window, but unauthorised restrictive practice without harm has a five-business-day window. The correct category and reporting steps need human judgment.

Test real work

Supplementary modules can add requirements for particular supports, such as high intensity activities, behaviour support or specialist disability accommodation. New supported independent living Practice Standards started on 1 July 2026. Test a system against the work your staff actually do and the current standards: can they find the plan, show who reviewed it and see what changed? That is more useful than a generic claim that software is 'NDIS compliant'.

Need software that supports complex work?

RedRock builds custom software around people, processes and decisions.

Send an enquiry