Skip to main content

Employment verification

Keep every check true after the day it was run — Oho re-verifies against the register on the schedule you set, and tracks the certificates no register can answer for.

Who it's for: Compliance managers responsible for a workforce over time

Availability: Available

What you get​

  • Re-verification of every matching credential against its register, on a schedule you choose
  • A suspension, cancellation, or lapse surfaced without anyone remembering to look
  • New expiry dates read from the register rather than re-typed by hand
  • Expiry tracking for the certificates that have no register behind them
  • An answer now, on demand, when you can't wait for the next scheduled run

Turn it on​

→ Add a verification source — pick the register, set how often Oho re-checks it, and save. From then on every credential of that type verifies on that schedule.

Ongoing verification​

Every capability below is about what happens after the first check. For what gets checked in the first place, see Breadth of verifiables.

Ongoing monitoring and automatic re-checks​

A one-off check is only true the day it's run. Connect the registers you rely on as Verification Sources and Oho re-verifies matching credentials on the schedule you choose, updating each worker's status automatically.

Availability: Available

Expiry-managed credentials​

Certificates with no register behind them — an internal compliance course, a First Aid certificate, a licence, a company induction. Oho tracks the expiry date you entered instead of querying a register, so they still surface as they approach expiry.

Availability: Available

Verify on demand​

When you can't wait for the next scheduled run, re-check a credential from its own page, or every credential on a worker at once from their Credentials tab.

Availability: Available

How it works​

Connecting a register as a Verification Source tells Oho how to reach that authority and how often to look. Oho re-verifies the matching credentials on that schedule, updates each worker's status automatically, and keeps a history of every check on the profile. Credentials with no register behind them are expiry managed instead — Oho tracks the date rather than querying anything.

→ Ongoing checks — the re-checking loop in the end-to-end journey → Verification Sources — every register Oho can connect to, and what each needs → Core Entities — verifiables, outcomes, and how they roll up

For developers

Subscribe to credential.verified and receive each terminal outcome as it lands instead of polling. Deliveries are signed, retried, and replayable.

→ Webhooks & event delivery → Workers & credentials

Good to know​

  • Without a connected source the first check still runs — nothing re-checks it afterwards. See Add a verification source.
  • Every verifiable is first checked the moment it's recorded — see Breadth of verifiables. This pillar is what happens from then on.
  • A change in outcome is what triggers an alert, so pair this with Notifications rather than watching the dashboard.
  • Where those changes roll up is the Compliance Overview — one view per organisation.
  • Some sources need more from you than others: portal sign-in details, provider pairing, or narrowing which workers are covered. Each source's page notes what it needs.