Airbnb won on trust. Care hiring will too.

There were always spare rooms. Before Airbnb, every city was full of empty apartments, sofa beds, and people who would happily have rented them out for a weekend. The supply existed. What did not exist was a reason for a stranger to hand over their house keys, or for a traveller to wire money to someone they had never met. The thing that was missing was not inventory. It was trust.

This is the part of the marketplace story that gets skipped. We remember the listings, the photos, the slick app. We forget that the hard problem was never finding accommodation. The hard problem was making two strangers comfortable enough to transact: verified identity, reviews that carried real weight, a payment flow that held funds, and recourse when something went wrong. Airbnb did not win by listing more apartments. It won by building the trust layer that let the apartments already sitting empty become something a stranger would book.

Care hiring has the same shape

Care has never had a candidate shortage in the way the sector talks about it. There are Aged Care workers, disability support workers, and early childhood educators across Australia who are qualified, screened, and looking for work. Job boards are full. Agencies have rosters. Care marketplaces like Mable and HireUp already do the matching layer well. The classifieds problem, the problem of putting more names in front of more providers, was solved a long time ago.

What is not solved is the bit in the middle. A provider cannot tell, from a name on a list, whether this person holds a current NDIS Worker Screening Check, whether their working with children check is the right state and still valid, whether their qualifications hold up, or whether they appear on a ban register. So the provider does the only thing they can: they re-collect everything, chase documents over email, and rebuild the same picture every worker has already built a dozen times for a dozen other employers. The supply is there. The trust is not portable.

That is the gap: a layer that lets a provider look at a worker and know what has been reviewed and what has been verified, without starting from a blank page every time.

What a trust layer actually does

In the Airbnb case, the trust layer was a bundle of boring, unglamorous components: identity confirmed once, a reputation that travelled with you, and a clear record of state. None of it was the product people thought they were buying. All of it was the reason the product worked.

A Career Passport is the care-sector version of that idea. The worker's credentials, screening, and qualifications live in one place that the worker owns and carries between jobs. A provider granted access sees the current state of those credentials rather than a folder of PDFs of unknown vintage. The screening that was checked for one employer does not have to be re-collected by the next. The trust becomes portable, which is exactly the property the spare rooms were missing.

The care-specific twist

Here is where the analogy stops being clever and starts being serious. When Airbnb's trust layer fails, someone has a bad weekend. When a care provider's trust layer fails, the stakes are safeguarding: a vulnerable person, a regulator, a banning order. Care credentials are not a five-star rating. They are regulated, time-bound, and legally consequential.

That changes the design in two ways. First, the difference between review and verify matters and cannot be blurred. Koora verifies a narrow set against authoritative sources: public state working with children check lookups (VIC, QLD, WA, TAS and the NT), AHPRA, and ban registers. For everything else, like police checks and qualifications, the compliance engine checks the document against what the role requires, and a person reviews the document itself once a worker shares their passport or an organisation adds the Crew service. AHPRA registration confirms a practitioner is registered. It is not a screening check and never stands in for one. Conflating these would be the care-sector equivalent of a fake review, and the whole value of the layer collapses if it lies.

Second, the legal duty does not transfer. Koora checks each credential against the role and verifies what it can at source, so a provider starts from a worker whose records are already in place rather than from zero. But the provider keeps the obligation to make the final hiring decision and meet their own regulatory requirements. A good trust layer makes the provider's job faster and better evidenced. It does not pretend to take the responsibility off their desk. Anything that erases the work also reads as if it lowers the rigour, and rigour is the entire point.

Building the layer, not the listings

Practically, this means the work is not about aggregating more candidates. It is about the connective tissue: a worker record that updates as credentials change, provider-side visibility into who is compliant and who is lapsing, and clean ways to plug that into the rostering and HR systems providers already run, through API and webhooks now, with direct integrations on demand. Portable verified feedback and recognition ship today, and travel with the worker when they share their Passport.

The supply was there all along, in spare apartments then and in qualified care workers now. The problem is that trust does not travel, so everyone rebuilds it from scratch, every time. Build the layer that lets it travel, with the rigour the sector demands, and the supply that was always there finally becomes something a provider can act on with confidence.

We're here to uplift care.