Does your rostering software cover compliance?

Most care providers already run a rostering or care-management platform. It builds the roster, tracks availability, often stores worker documents, and sends a reminder when a certificate is about to expire. That is genuinely useful, and for scheduling it is the right tool. The trouble starts when a provider assumes that storing a certificate and tracking its expiry date is the same thing as proving a worker is cleared to work. It is not.

This guide unpacks the difference between document management and compliance assurance, and where a dedicated compliance layer fits alongside the roster you already run.

What rostering software does well

Rostering and care-management platforms (the category that includes scheduling and workforce-management tools used across Aged Care, disability and childcare) are built around the shift. They are strong at:

• Building and publishing rosters, managing availability and filling shifts
• Storing uploaded documents against a worker profile
• Setting an expiry date on a stored document and reminding you before it lapses
• Reporting hours, leave and award interpretation

That covers a real operational need. If your goal is to know who is working when, this is the tool for the job. None of what follows is a criticism of rostering software for doing rostering.

Where the compliance gap opens up

The gap is narrow but important. An uploaded certificate is a stored file. It is a PDF or an image that someone typed an expiry date next to. Storing it proves the worker handed you a document. It does not prove:

• The document is genuine and has not been altered
• The credential is current today, not just on the date it was uploaded
• The worker's clearance or registration has not been suspended, cancelled or subject to a banning order since upload

A printed expiry date is the worst case to rely on, because a clearance can change status long before it lapses. A Working With Children Check can be revoked. A health practitioner's registration can be cancelled or have conditions imposed. A worker can be placed on a government ban register. None of those events moves the expiry date in your roster, so an expiry reminder will never fire. The document still sits there looking valid.

Each of those events reaches you by a different route, and it is worth knowing which. A banning order is caught by nightly screening against the three government ban registers, which is the one source Koora re-checks on a cadence. A revoked or suspended Working With Children Check is not: the issuing scheme notifies the employer linked to that clearance, so the notice goes to whoever is registered against it, and a portal re-check is the other way to find it. An AHPRA cancellation shows on the public register the next time someone looks. Knowing which channel carries which event tells you where your own process still has to do the work.

Verified against the register versus stored on file

This is the distinction that matters. Some credentials can be checked directly against the authoritative source, and that is what "verified against the register" means:

• Working With Children Checks: verified through each state's employer portal, which confirms the number is valid and the clearance is current. A national Working With Children Check reform is also underway to improve consistency across jurisdictions
• AHPRA registration: verified against the AHPRA register of practitioners, which shows current status and any conditions
• Ban registers and the relevant government screening sources: checked against the authoritative listing

Other credentials have no issuing-body source to query. Uploaded National Police Checks (Nationally Coordinated Criminal History Checks), qualifications, training records and NDIS Worker Screening Clearances are checked by the compliance engine against the requirements for the role, and a person reviews the document itself once a worker shares their passport or a provider requests access, or across your own records through the Crew service. For NDIS Worker Screening, source verification is on the Koora roadmap. In-platform National Police Checks, run through an ACIC-accredited body and verified by Koora, are being switched on.

A few sector points worth keeping straight as you map your requirements:

• In disability and NDIS work, police history is bundled into the NDIS Worker Screening Check. You do not list a separate police check alongside it.
• In childcare, police history is bundled into the state Working With Children Check. Again, no separate police check.
• AHPRA registration is never a substitute for worker screening. For Aged Care, screening is a National Police Check issued within the last 3 years, or an NDIS Worker Screening Clearance. Those are the only two options, and an AHPRA registration does not replace either.

Most rostering platforms cannot perform source verification or monitor ban registers, because that is not what they were built to do. They were built to store the file you give them and remind you about the date you typed in.

Two systems, two jobs

The practical answer is not to replace your roster. It is to recognise that scheduling and compliance assurance are two jobs:

• Your rostering or care-management platform owns the shift: who works, when, and for how long.
• A compliance platform owns the credential: is this worker source-verified where possible, checked against the role's requirements where not, expiry-tracked, and screened nightly against the three ban registers so a banning order surfaces. Source verification is point-in-time, so a Working With Children Check is checked against the public state lookup (in Victoria, Queensland, WA, Tasmania and the NT) when it is collected and then tracked to its expiry date. NSW and SA checks are reviewed from the document. Koora is working towards continuous monitoring on more sources.

Compliance status is current-state. It reflects what is true when the report runs, not a reconstructed history of what was true on some past date. That is the right model for an audit question, which is almost always "show me who is cleared now."

How the two systems connect

The two layers do not have to be separate silos. Koora exposes compliance status over API and webhooks, which are available now. That means your rostering or care-management system can read a worker's current compliance state and react to the events Koora emits. When a credential is seven days from expiry, when one has expired, when a review outcome lands, or when a worker's compliance verdict changes, a webhook can notify the roster so the right people see it.

Koora integrates via API and webhooks today, and can build a direct integration for a specific tool on request. Tools such as Deputy, Employment Hero and Humanforce are examples of systems Koora can integrate with this way, and a care management system can be connected the same way once you tell Koora which one you run. To be clear, that means via the API and webhook surface, or a direct integration built on request. It does not mean a pre-built native connector ships today.

Where Koora fits

Koora is the compliance layer that sits alongside the roster you already run. It checks worker credentials: verifying AHPRA registration and Working With Children Checks (where the state publishes a public lookup, in Victoria, Queensland, WA, Tasmania and the NT) at source, checking National Police Checks, qualifications, training and NDIS Worker Screening Clearances against the requirements for the role, and monitoring relevant ban registers so status changes surface rather than waiting for an expiry date that may never move. A person reviews those documents themselves once a worker shares their passport with you, or across your own records through the Crew service.

Your team reviews in Koora, or Crew does it for you. The provider keeps the legal responsibility for who they engage. The goal is not to remove that work, it is to give you a current, trustworthy picture so the sighting and the decision rest on verified status rather than a stored PDF. To go deeper, see worker compliance tracking for providers, care compliance integrations via API and webhooks, and how to choose care sector compliance software.

Frequently asked questions

Does my rostering system verify Working With Children Checks?

Most do not. Rostering and care-management platforms let a worker upload a WWCC document and set an expiry reminder, but the file itself is not checked against the issuing state's register. Source verification happens through each state's employer portal, which confirms the number is valid and the clearance is current.

If I track expiry dates, is that enough for compliance?

Expiry tracking tells you when a stored document lapses, but not whether the credential is genuine or whether status has changed since upload. A clearance can be suspended or a registration cancelled well before its printed expiry. Source verification proves the credential was real and current on the day it was checked, and nightly ban-register screening catches a banning order between checks. The suspension gap stays open: a Working With Children Check suspended part-way through its term reaches you through the scheme notifying you as the linked employer, or through your own portal re-check. Koora is working towards continuous monitoring on more sources.

Can a compliance platform feed status into my roster?

Yes. Koora exposes compliance status over API and webhooks, so your rostering or care-management system can read a worker's current state and react to the events Koora emits: a credential seven days from expiry, a credential that has expired, a review outcome, and a change in a worker's compliance verdict. Koora can also build a direct integration for a specific tool on request. There is no claim of a pre-built native connector.