What an NDIS Compliance Dashboard Should Actually Show You
Right now, how many of your active workers have a current clearance, current first aid, and the qualifications required for every shift they are rostered to deliver? If answering that takes more than two minutes, you do not have a compliance dashboard — you have a filing problem.
The question most providers cannot answer quickly
Ask an operations manager at an NDIS provider: "Right now, how many of your active workers have a current NDIS Worker Screening clearance, a current first aid certificate, and all the qualifications required for every support they are currently rostered to deliver?"
Most cannot answer that question without a half-day manual task. Someone has to open the HR system or shared folder for clearances. Someone else opens the qualification spreadsheet. A third person checks the roster to identify which workers are currently assigned to which supports. Then someone compares all three lists manually.
This is not a niche compliance problem. It is the central visibility gap for any NDIS provider trying to run a defensible operation. And it is solvable — but only if those three data layers are held in the same system and queried together.
The three layers a compliance dashboard must cover
Layer 1: Clearance status
Every worker in a risk-assessed role must hold a valid NDIS Worker Screening clearance. "Valid" means current — not expired, not suspended. This layer is the floor.
What a dashboard needs to show:
- Workers with a current clearance (green)
- Workers with a clearance expiring within 30, 60, and 90 days (amber thresholds)
- Workers whose clearance has lapsed or been suspended (red — action required)
- Workers in risk-assessed roles with no clearance on file (critical)
The last category is the most dangerous, and it is the one most providers do not have visibility over because clearance status and role assignment are held in separate systems.
Layer 2: Credential and qualification status
Beyond the clearance, workers may need first aid, CPR, manual handling, medication administration, behaviour support training, or clinical competencies depending on what supports they deliver. Each of these has its own expiry cycle.
What the dashboard needs to show:
- Per-worker qualification status across all required credential types
- Expiry dates and days-until-expiry for each credential
- Workers with any lapsed credential (regardless of whether they are currently rostered)
- Workers with renewals in progress (pending status vs genuinely lapsed)
- Aggregate view: how many workers are fully credentialled vs have one or more gaps
Layer 3: Assignment appropriateness
This is the layer that most compliance tools do not surface — and it is the one that directly drives audit exposure.
A worker might be fully credentialled for their typical support work. But if they are rostered to a shift that requires a qualification they do not hold, that mismatch should be visible before the shift happens — not after.
Assignment appropriateness answers: for every active shift on the roster, is the assigned worker currently qualified to deliver that support?
This requires connecting the booking type (and its required qualifications) to the worker profile (and their current qualifications). Without that connection, you can track credentials all day and still miss the mismatch.
Why these three layers end up in separate systems
The reason most providers cannot answer the compliance question quickly is structural. Clearance records often live in an HR or onboarding system. Qualification certificates live in a shared folder or document management system. Roster assignments live in a scheduling tool or spreadsheet. Nobody built a connection between them — and without a deliberate integration, the data stays siloed.
The practical result: compliance checks require a person to manually bridge the gap between systems. That person's availability — and attention — becomes the single point of failure in the compliance process.
What an effective compliance dashboard surfaces
A compliance dashboard worth the name does not require manual reconciliation. It pulls from all three layers and surfaces:
Expiring records. Workers whose clearance or credentials will expire within a configurable window. The default is typically 30, 60, and 90 days. The alert should go to the worker, their manager, and whoever is responsible for maintaining the register.
Lapsed records. Workers who currently hold an expired credential. This should be a hard flag — not a passive entry on a report that gets reviewed monthly.
Mismatched shifts. Active roster assignments where the worker does not hold the qualifications required for that support type. This is the assignment appropriateness layer.
Upcoming renewal workload. How many renewals are due in the next 90 days? This is useful for planning — if twelve first aid certs expire in the same month, you need to be booking refresher training now.
Workforce-wide compliance rate. What percentage of active workers are fully compliant across all required credential types? This is the executive-level summary that tells you whether the organisation is improving or deteriorating.
Alert logic: who, when, and how
A dashboard without alerts is a report. Alerts are what make compliance proactive rather than reactive.
Who receives alerts: The worker (direct prompt to renew their own credentials), the worker's coordinator or line manager (visibility and ability to follow up), and the compliance or HR function (for register maintenance and escalation).
When alerts fire: The timing thresholds should be configurable. Different credential types have different renewal lead times — booking a first aid refresher course requires two to four weeks' notice; applying for a new Worker Screening clearance can take eight weeks or more. Alerts for clearance expiry should fire earlier than alerts for a one-day online course.
How alerts are delivered: In-platform notification plus email at minimum. SMS for urgent cases (a lapsed credential for a worker with shifts tomorrow) is best practice.
"Compliant at time of service" vs snapshot compliance
A compliance dashboard that tells you the current status of your workforce is useful for operational management. But it does not, by itself, answer the audit question.
Auditors are not only asking "are your workers currently compliant?" They are asking "were your workers compliant at the time each service was delivered?" That requires a point-in-time record — a log that shows what each worker's credential status was on each date they delivered supports.
This is the difference between a snapshot and a ledger. A snapshot tells you today's state. A ledger tells you what the state was on any given historical date.
For audit purposes, you need the ledger. If a worker's first aid certificate lapsed in October and they delivered supports in November before renewing in December, today's snapshot shows a current certificate. The ledger shows the gap.
Gaps in existing tools
Most tools in the market give you layer 1 (clearance tracking) and parts of layer 2 (some qualification tracking). Layer 3 — assignment appropriateness — is almost universally absent. It requires the scheduling engine and the compliance register to be the same system, or to be tightly integrated.
The other common gap is point-in-time reporting. Many platforms track current status but do not maintain the historical record needed for a credible "compliant at time of service" answer at audit.
Teiro's compliance dashboard covers all three layers in a single view — clearance status, credential status, and assignment appropriateness — with expiry alerts, a full compliance history, and audit-ready reporting. Book a demo to see how it works for your workforce size and support types, or sign up to explore it directly.