ISSUE · WORKFORCE & CONTRACTORS
Verify once. Rely many times.
Every hire triggers the same ritual: documents produced, copied, filed, and forgotten — then produced again for the next employer, the next client, the next site pass. The regulatory ground has already moved: since 2022 the UK's Right-to-Work and DBS regime has recognised REUSABLE identity checks through certified providers. The enabling move was not technology. It was a regulator saying a check, once done well, may be relied on again.
The onboarding pile, before and after
What happens today
HR collects a passport photo, a proof of address, a reference letter and a qualification certificate — into a personnel file that must now be guarded for years. The contractor does this four times a year, once per client, and every client holds the whole pile.
What happens with a reusable check
The check is done once, properly, and signed. The employee or contractor carries the proof — "right to work verified", "background check passed on this date" — and each relying party checks the signature instead of rebuilding the file. Nobody new holds the documents, because nobody new ever received them.
Leavers are the hard part, and the design says so
A workforce credential is only as trustworthy as its revocation. The platform's specification targets directory-scale issuance — an employer connects the corporate directory, credentials issue at directory scale, and a deactivated account revokes its credential within five minutes. That five-minute figure is the specification's design target for planned work, not a measured production number, and this page will not dress it up as one. What is live today is the revocation rail itself: a signed status list any verifier can fetch.
What an employer would actually be adopting today.
No employer issues on this platform today, and directory integration is planned work, not shipped work. Issuance for a tenant is operator-run — an organization cannot yet self-serve its own credential types. The rows below are the measured state of the pieces a workforce programme would stand on.
- PLANNED A wallet a person installs from an app store. wallet-native You cannot hold a credential on a phone you own. Everything a person would do with a proof waits behind this.
The register holds 17 live · 2 partial · 2 planned · 5 not yet.
4 of the 5 capabilities this page depends on have no row in the register yet, so this page will not print a state for them. They are named rather than dropped, because a slice that silently shortens itself is the same defect as a claim with no receipt.
- vc-issuance
- selective-disclosure
- partner-certification
- self-service-onboarding
The register route serves, but it carries no row for these yet. List what it does carry:
curl -s https://id.orbis.id/api/site/register | jq -r '.entries[].slug'