Does your rostering software cover compliance?
Rostering and care-management platforms schedule shifts and store certificates well, but a stored file is not a source-verified credential. Here is the gap and how to close it.
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.
A stored certificate is evidence of upload, not evidence of clearance
Expiry tracking answers "when does this document lapse?" It does not answer "is this person cleared to work right now?" Those are different questions, and only the second one keeps you audit ready.
Verified at source 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 at source" 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 are reviewed rather than verified at source. Police certificates, qualifications, training records and NDIS Worker Screening Clearances are reviewed by a person against the document and supporting detail. They are not currently checked against an issuing-body source. For NDIS Worker Screening, source verification is on the Koora roadmap; today it is reviewed.
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 police certificate issued under 3 years ago, 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, reviewed where not, expiry-tracked, and monitored where Koora tracks the source (ban registers and Working With Children Checks) so those status changes surface, with broader continuous monitoring what Koora is working towards.
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 an expiry threshold is reached, a new review outcome lands, or a ban-register or Working With Children Check status 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, Humanforce, Lumary and AlayaCare are examples of systems Koora can integrate with this way. 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 pre-clears worker credentials: verifying Working With Children Checks and AHPRA registration at source, reviewing police certificates, qualifications, training and NDIS Worker Screening Clearances, and monitoring relevant ban registers so status changes surface rather than waiting for an expiry date that may never move.
Koora pre-clears. The provider keeps the legal obligation to sight evidence and decide who can work. 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.
This is general information, not compliance advice. Always confirm requirements with the relevant regulator, and remember that providers keep the legal responsibility to sight credentials and decide who can work.
We work hard to keep it accurate, but the rules change and we will not always get every detail right. If you think something here needs updating, email us at resources@koora.care. We would genuinely rather know, because we all do better when we help each other get it right.
Bring your compliance into one place
See how Koora keeps your workforce credentials reviewed, current and audit-ready. Start with your first worker free.