Skip to main content

Ongoing monitoring & re-checks

Keep every verified credential true after the day you checked it — Oho re-verifies against the register on your schedule and updates the outcome on its own.

Who it's for: Compliance managers responsible for a whole workforce

Availability: Available

What you get​

  • Re-verify every matching credential against its register on a schedule you choose
  • Hear about a suspension, cancellation, or lapse without anyone remembering to look
  • Pick up new expiry dates from the register, so what you see reflects the source rather than what was typed in
  • Keep a history of every check on each worker's profile
  • Feed each change straight into your Compliance Overview and your notifications

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.

How it works​

A one-off check is only true the day it's run — a card can be suspended, expire, or be cancelled the week after you first verified it. 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 and updates each worker's status automatically. Weekly is the default schedule and suits most teams.

→ Ongoing checks — the re-checking loop in the end-to-end journey → Verification Sources — every register Oho can connect to, and what each needs → One-off verification — the first check, which runs either way

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.
  • Most sources need nothing from you. A few need more: portal sign-in details for South Australia, pairing your organisations with the provider's for NDIS Worker Screening, or narrowing which workers are covered for aged-care banning orders. Each source's page notes what it needs.
  • Verification sources are admin-level configuration. If Verification Sources isn't in your menu, ask your Oho administrator.
  • Want an answer now rather than at the next scheduled run? Verify a credential from its own page, or use Verify all on the worker's Credentials tab.
  • Certificates with no register behind them are expiry managed — Oho tracks the date you entered instead of querying a register.
  • A change in outcome is what triggers an alert, so pair this with Set up notifications rather than watching the dashboard.