The NDIS Workforce Disruption Plan, and the Emergency Capability List Beside It

Separately, and it's easy to conflate the two: does anyone know, right now, without ringing around, which of your workers currently hold first aid, who's done emergency response training, and who's up to date on infection control? That's a different question, and the Standard asks it as a different requirement.

Two indicators, both Certification-only

Both sit under Emergency and Disaster Management, part of Provider Governance and Operational Management in the Core Module. Both are among the seven requirements Certification adds on top of everything Verification already asks for.

The first, in the Commission's own words:

"Workers with capabilities relevant to responding to an emergency or disaster are identified"

The second:

"Plans are in place to identify, source and induct a workforce if workforce disruption occurs in an emergency or disaster"

The first is about who can respond right now. The second is about where extra people come from if the current workforce can't cover a shift, a house, or a whole service during a disruption. A provider can hold one without the other, and an assessor asks for both by name.

The capability list: who can respond, named against what they hold

The artefact this indicator asks for is a document naming people against capabilities: first aid, contingency planning, infection control. Not a general sense that "the team is trained." A named list.

CORA derives this list rather than storing it. It's assembled from your credential register, first aid tickets, and from completions of two named courses, 1.10 Emergency, Disaster & Incident Response and 2.32 Infection Control & Hygiene. Nothing about the list is typed in separately, which is what keeps it accurate: it can't drift out of step with the register it's built from, because it's read from that register every time, not maintained as a second copy of it.

When nobody currently holds a capability, the list says so in words, rather than showing a blank row that could mean anything from "nobody's covered" to "we haven't filled this in yet."

The disruption plan: named arrangements, filed and ready

The second indicator is satisfied by named arrangements for where extra workers would come from, and how they get screened and inducted quickly. A casual pool, an agency relationship, a neighbouring service's mutual-aid arrangement, whatever the provider's actual plan is, written down and filed where it can be produced on request.

CORA holds this in organisation documents, alongside the position description register and PPE evidence. See what else lives on the organisation side. The indicator is satisfied by the plan existing and being producible, which is what filing it achieves.

The point worth leading with: generic training can't cover your own plan

Here's the part that matters more than it first sounds. An emergency or disaster response is specific to a service. A generic emergency-awareness course can teach the general shape of what to do when something goes wrong. It can't teach a worker your evacuation routes, your on-call chain, or how your own disruption plan actually works, because it was never written with your plan in front of it.

Training built from your own document can. Upload your emergency or disruption plan and CORA builds the course from it, word for word on anything clinical or procedural, so the training a worker completes is about the plan they'll actually be following, not a general script that happens to be about emergencies.

Every claim on this page is written the same way every claim on the site is written: about a named artefact, checkable in a demo. See the standard CORA holds every claim to.