OnePassport Guardian is credentialing infrastructure for a care sector. Workers carry one verified credential between employers. Every provider works to the same standard. The sector can see its own workforce for the first time.
Guardian holds the documents a worker must already have in order to do the job at all. The registration. The qualification. The check. The first aid certificate.
Requiring somebody to hold those is not a new imposition. It is the job. Guardian is simply where they live, in a form that can be verified and carried.
Guardian makes no finding about any person. It records what a worker holds and where they have worked. Nothing more.
Today a credential belongs to whichever employer happens to hold the paperwork. When the worker moves, the proof stops at the door and the next employer starts again.
Guardian moves the credential to the worker and makes it recognisable to every provider in the sector. The proof travels with the person who earned it.
Their qualifications, registration and checks sit in the OnePassport app, verified and current.
One page on the wall at each site, carrying that provider's own code.
A new worker scans on arrival and shows the manager the green connection tick. That scan writes a verified entry to their employment history.
Once a quarter we send the provider its current worker list. One click to confirm, or log in to correct it.
A live view of which providers are current, where credentials are lapsing, and where the workforce is actually moving.
A verified record of where a person has actually worked, built from scans at the door rather than from a claim on a CV.
That record compounds. Every scan makes the next hire easier to check, and gives the sector a picture of its workforce it has never had.
Guardian is operated by OnePassport as sector infrastructure. No employer, network, funder, government body or supplier owns the credential or controls who is recognised by it.
Where a sector or its bodies fund the credential, the worker pays nothing. A support worker or educator on an award wage is never asked to pay for documents their job already requires.
Some professions already fund their own registration and development. A doctor or nurse who buys their credential owns it outright and carries it for as long as they hold it.
Any provider in the sector can verify a credential, whether or not they are a OnePassport customer. The standard is not gated.
What never happens is a worker being charged for a credential their employer has required of them. Who funds it is a decision made at sector level, before anyone is asked to hold it.
A government run credential hits privacy law before it hits anything else. What can be collected, how long it can be held, and what can move between agencies and across state lines are all constrained by legislation written for a different purpose. Those constraints are a large part of why a national credential has never been built.
The credential exists on the worker's consent, not on a statutory power. Nobody is enrolled without agreeing to it.
Because it belongs to the individual, it moves across employers, sectors and state and national borders without a data sharing agreement between agencies.
Consent that cannot be withdrawn is not consent. A worker can disconnect an organisation, or leave entirely, at any time.
Operated by OnePassport under the Australian Privacy Principles, not held in a government database that other agencies can query.
Being precise about this is what makes a sector willing to adopt it.
Guardian runs no check on a person and reaches no conclusion about them. It records what they hold.
It does not replace a registration board or a government register. It sits alongside them and keeps their requirements current.
The worker's record sits with the worker. A provider sees the workers connected to it, and nobody else's.
A worker leaving an employer keeps their credential. It was never the employer's to hold.
Set a credential standard once and have every member work to it, with visibility of who is keeping it current.
Move staff between sites and entities without re-proving the same credentials at each one.
Evidence that a workforce is verified and current, across a whole book rather than one provider at a time.
Hand graduates a credential on day one, so they arrive at their first placement already carrying it.
A workforce movement signal that no register currently produces, without adding administrative load to providers.
Recognise a credential earned elsewhere instead of rebuilding it, and cut weeks out of onboarding.
Which credentials the sector expects every worker to hold. Usually this already exists, written down somewhere nobody enforces.
The set of providers and workers in scope, and a nominated go live date.
Adoption comes from many small pushes in the same direction, not from one mandate. The sector needs a voice willing to call it good practice.
From agreement to launch. Data load, self serve sign up, codes issued, training built, dashboards live.
No. Guardian holds credentials a worker already needs and records verified employment history. It performs no screening and makes no finding about anyone. Screening is a separate, consent based service described under Verifications, and it is never bundled into the credential.
It depends on who funds the credential in that sector. Where a sector or its bodies fund it, the worker pays nothing, and that is the model in aged care, disability support and childcare. In professions where practitioners already fund their own registration and development, such as medicine and nursing, the worker buys the credential and owns it outright. What never happens is a worker being charged for a credential their employer has required of them.
They can still take part. Verifying a Guardian credential is free for any provider in the sector. Comply is the separate paid system for providers who also want to manage their whole compliance operation in one place.
No. A register records who is qualified. Guardian records what a worker currently holds and where they are working, and keeps the register supplied with accurate information instead of competing with it.
Privacy legislation. A government held credential is limited in what it can collect, how long it can hold it, and what can move between agencies and across state lines. A private system built on individual worker opt in avoids those limits, because the record exists on the worker's consent and belongs to the worker rather than to an agency.
The worker, always. A provider sees the workers connected to it. A sector body sees aggregate readiness across providers, not individual files.
About three months from agreement to launch for a defined sector, covering data load, sign up flows, code issue, training material and dashboards.
