Who needs an NDIS risk register?

If you are a registered NDIS provider, a risk register is not optional. The NDIS Practice Standards — the benchmark against which all registered providers are audited — require organisations to implement and maintain systematic approaches to identifying, assessing, and managing risk. A risk register is the core document that gives this requirement its practical form.

This obligation applies across all registration groups, but the depth and rigour expected scales with the complexity of the supports you deliver. Providers of Supported Independent Living (SIL), specialist disability accommodation (SDA), and high-intensity daily personal activities are subject to the most demanding requirements. For these providers, a superficial or incomplete risk register is one of the most common grounds for a non-conformance finding during a certification audit.

Unregistered providers are not subject to the Practice Standards directly, but the NDIS Code of Conduct — which applies to all providers and workers — still requires that supports be delivered safely and competently. In practice, any provider serious about participant safety and continuity of service should maintain some form of risk documentation regardless of registration status.

The regulatory foundation

The NDIS Commission's Practice Standards set out the outcomes providers must achieve. The strengthened framework, which the Commission has been progressively rolling out ahead of the 2026 mandatory registration expansion, has sharpened the governance and operational management standards. Key obligations relevant to risk registers include:

The National Disability Insurance Scheme (Provider Registration and Practice Standards) Rules 2018 (Cth) give the Practice Standards their legal weight. An approved quality auditor assessing your organisation will cross-reference your risk register against these standards.

What must your risk register contain?

The NDIS Commission does not prescribe a single mandatory template, but quality auditors look for a register that demonstrates genuine, systematic risk management rather than a document produced solely for audit purposes. At minimum, a compliant risk register should include the following fields for each identified risk:

  1. Risk ID and description: A unique identifier and a plain-English description of what could go wrong.
  2. Risk category: Common categories for SIL providers include participant safety, workforce, compliance and regulatory, financial, technology, and business continuity.
  3. Likelihood rating: Typically scored on a scale (e.g., rare through to almost certain), using your organisation's defined criteria.
  4. Consequence rating: Scored by the severity of impact on participants, workers, or the organisation (e.g., minor through to catastrophic).
  5. Risk rating: The combined likelihood–consequence score, usually expressed as low, medium, high, or extreme using a risk matrix.
  6. Existing controls: What you are already doing to reduce the risk.
  7. Residual risk rating: The rating after existing controls are applied.
  8. Treatment actions: Further steps planned to reduce residual risk to an acceptable level.
  9. Risk owner: The named role responsible for monitoring and managing this risk.
  10. Review date: When this entry was last reviewed and when the next review is scheduled.
  11. Status: Whether the risk is open, being treated, or closed.

Risks that SIL providers must not overlook

Many SIL providers maintain a register but leave out categories that auditors specifically look for. The following risk areas are particularly scrutinised in SIL and disability accommodation contexts:

How often must you review your risk register?

The Practice Standards do not specify a single mandatory review frequency, but the expectation embedded in governance requirements is that reviews are conducted at regular intervals and in response to triggering events. Best practice — and the pattern auditors look for — is:

Evidence of regular review — meeting minutes, version control on the document, or a review log attached to the register — is what distinguishes a live risk management system from a document created for audit and then forgotten.

Consequences of not having a risk register

During a certification or verification audit, an absent or inadequate risk register is one of the clearest pathways to a non-conformance finding. Depending on severity, this can result in:

Beyond audit consequences, a provider without a functioning risk register is genuinely more likely to experience preventable incidents — with direct costs to participants, workers, and the organisation.

Practical steps to build or strengthen your risk register

  1. Adopt a risk matrix your whole team can use. Choose likelihood and consequence scales and define them clearly so that ratings are consistent regardless of who completes the entry.
  2. Conduct a risk identification workshop. Involve frontline workers, coordinators, and managers. Frontline staff often identify risks that management documentation misses.
  3. Map your register to the Practice Standards. Work through each standard that applies to your registration groups and ask: what could prevent us from meeting this outcome? Each answer is a candidate risk.
  4. Link the register to your incident data. Review your incident register quarterly and ask whether recurring incident types represent an unaddressed or under-controlled risk.
  5. Assign ownership at role level, not individual name. When a staff member leaves, the risk does not disappear. Ownership should sit with a role title so accountability transfers automatically.
  6. Version-control the document. Date every revision and keep prior versions. Auditors want to see a history of genuine engagement with the document, not a freshly minted register.
  7. Review at every board or management meeting. Include a standing agenda item for risks rated high or extreme. Record in your minutes that it was discussed.

Template excerpt: what an entry looks like

Risk ID Description Category Likelihood Consequence Risk Rating Controls Owner Next Review
R-014 Participant receiving high-intensity support experiences medication error due to worker unfamiliarity with complex medication regime Participant Safety Possible Major High Medication management plan in place; high-intensity worker competency verified on induction; monthly supervisor spot-checks; incident reporting obligation communicated to all staff Service Delivery Manager Quarterly or following any medication incident

Providers working through the 2026 mandatory registration changes and building their governance documentation from scratch may find it useful to work from an audit-ready template set. The ndiscompliant.com.au 74-document SIL compliance kit includes a pre-structured risk register template mapped to the current Practice Standards, alongside the full suite of policies, procedures, and forms auditors look for — a practical starting point rather than a blank page.

Important: This article provides general guidance about NDIS compliance requirements. It is not legal or professional advice. Requirements may change as the NDIS Commission updates its policies and Practice Standards. Always verify current requirements with the NDIS Quality and Safeguards Commission or a registered NDIS consultant before making compliance decisions.