The verification layer the care sector is missing

Every industry that matures grows a layer underneath it that almost nobody talks about: a trust layer. Payments got one. So did communications, identity, and logistics. The visible products sit on top, but the boring plumbing beneath them is what lets a transaction or a message or a delivery be trusted without everyone rebuilding the checks from scratch each time.

Care never grew that layer. And the cost of its absence falls, quietly, on the same people over and over.

The same worker, verified again and again

Picture a support worker who has spent four years across three providers. Along the way she has held a current police certificate, an NDIS Worker Screening Check, a first aid and CPR certificate, mandatory training, and a stack of qualifications. Every one of those has been collected, chased, and filed by an employer at some point.

Now she moves to a fourth provider. What happens? The whole thing starts again. New forms. New uploads. Someone in HR re-reads the same documents a different person read last year. The certificate that was sighted in March is sighted again in November. Nothing about the worker changed. The verification work simply did not travel with her.

Multiply that across a workforce of hundreds of thousands of casual, multi-employer, mobile care workers and you get an enormous, invisible tax. Providers pay it in admin hours. Workers pay it in friction and delay before their first shift. Nobody captures the value, because the work is thrown away and redone the moment the worker walks through a different door.

This is exactly the pattern a trust layer is meant to solve. The check is done once, to a known standard, and then it is portable.

What a trust layer actually does

The useful thing a trust layer does is not magic. It draws a hard line between two questions and answers each one honestly:

• What did we actually check, and how thoroughly?
• Who is allowed to rely on that check, and for what?

If you blur those questions, you get exactly the mess care is in now. A document gets "verified" in one place, "confirmed" in another, "sighted" in a third, and no two parties mean the same thing. So everyone defaults to redoing it, because trusting someone else's vague assurance is riskier than just checking again.

A Career Passport is our attempt at that layer for care. The worker carries their reviewed credentials between employers. Each provider that needs to rely on a credential can see precisely what was done to it, rather than inheriting a fuzzy claim.

The two honest paths

When we talk to providers, the offer comes down to two paths, and we try to be precise about both.

The first path: review the workers you already found. You have hired someone, or you are about to. You hand us their documents and we review them against the requirements for their role and sector, then keep watching for expiries and changes. This is the path most providers start on, because it maps onto how they already hire.

The second path: the worker carries their reviewed credentials with them. The same review work, done once, travels between employers via the worker's Career Passport instead of being repeated by each new one. This is the path that actually retires the re-verification tax, and it is the one that only pays off as more of the sector treats reviewed credentials as portable.

Both paths share the same underlying review. The difference is who initiates it and whether the result is allowed to move.

The precise line between review and verification

Here is the distinction we refuse to fudge, because the whole trust layer depends on it.

For most credentials, what we do is review. A person reads the document, checks it is current, checks it matches the role and sector, and tracks it for expiry. That is genuine, careful work, and it is honest to call it review. A police certificate, a qualification, a training record, an NDIS clearance: these are reviewed.

For a smaller set, we can verify against an authoritative source: AHPRA registration, state working with children check portals, the document verification service for identity, and ban registers. Verification means we confirmed the credential with the body that issued or governs it, not just that we read the paper.

We will not stretch "verify" to cover things we only reviewed. And AHPRA registration is never a substitute for worker screening; it confirms a practitioner is registered, not that they have cleared the screening their role requires. Getting these words right is not pedantry. A trust layer that lies about how much it checked is worse than no trust layer at all.

One more line we hold firmly: Koora pre-clears, the provider keeps the legal duty. We do the review so the provider starts from a clear position, but the obligation to engage a compliant worker stays with the provider. We are the layer beneath the decision, not a replacement for it.

Building it in the open

Some of what a mature trust layer should do is still ahead of us. Portable verified feedback and recognition between providers is on the roadmap, not shipped. Connecting to the rostering and HR systems providers already run happens today through API and webhooks, with direct integrations built on demand as real need appears.

We would rather say that plainly than imply the whole layer already exists. If you are weighing this up, our guide on choosing care sector compliance software lays out the questions worth asking any vendor, including us.

The mission underneath all of it is simple. We're here to uplift care. A workforce that does not have to prove itself from zero at every door has more energy left for the work that actually matters.