Skip to main content

Compliance management

Know where your whole workforce stands right now — and hear about it the moment that changes, instead of finding out at audit.

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

Availability: Available

What you get​

  • A dashboard showing how many people are compliant, at risk, or non-compliant, broken down by organisation
  • Alerts to the right people, through the right channels, when a credential expires soon or a status changes
  • A way to ask a worker directly for a detail you're missing
  • Rules that define what satisfies a requirement, and what each position requires in the first place
  • Requirements satisfied by an exemption counted as met, rather than sitting as a gap

Turn it on​

→ Understand your Compliance Overview — read the dashboard, learn what each result means, and act on flagged workers.

Capabilities​

Compliance dashboards and reporting​

The Compliance Overview shows where you stand at a glance, per organisation rather than as one aggregate number, and the breakdown exports to a spreadsheet you can hand to the manager responsible for each area.

Availability: Available

Notifications and renewal reminders​

Oho tells you when a credential is expiring, when a status changes, and when a worker turns up on a ban register — to your inbox, your team's Teams or Slack channel, and optionally the workers themselves.

Availability: Available

Fetch requests​

Ask an existing worker for a credential detail you don't hold. They fill it in on a secure link with no login, and it lands on their profile, verified where possible.

Availability: Available

Compliance rules​

Define what counts as satisfying a requirement — including equivalence sets, where holding any one member of a set is enough, such as any accepted first aid certificate.

Availability: Available — set up under Compliance Rules in the app

Position-based requirements​

What a position requires, rather than what an individual happens to hold. Set the credentials a position needs and Oho flags anything a worker in that position doesn't hold as a missing credential on their profile. An exemption on file satisfies the matching requirement.

Availability: Available — can also be synced from an HR system that records them

How it works​

Every credential, exemption, and ban check is a verifiable — something Oho can confirm against an official source and then keep confirming. Each check produces a colour-coded outcome, the outcome rolls up into the Compliance Overview per organisation, and a change in outcome is what triggers a notification.

→ How Oho Works — the end-to-end journey, in order → Core Entities — verifiables, outcomes, and how they roll up → Employment verification — the re-checking loop that produces those changes

For developers

Pull compliance state over the REST API, and subscribe to webhook events so your own dashboards and HR systems update the moment a result changes rather than on a nightly poll.

→ Webhooks & event delivery → Pagination, filtering & sorting — for reporting queries across a large workforce

Good to know​

  • Re-checking only happens for credential types whose register you've connected as a Verification Source. The first check runs either way; the ongoing loop needs the source.
  • Who receives which notification depends on their role and the organisations they can see — see Roles & access.
  • The wording and branding of the emails Oho sends is yours to change — see Customise email templates.
  • What each outcome means, including borderline results, is defined once in Core Entities and used consistently across every check type.
  • Bundling the checks a role requires is a screening concern rather than a monitoring one — see Screening packages under Background screening.
  • An exemption is itself a verifiable, so it's catalogued with the rest under Breadth of verifiables; a recorded exemption satisfies the matching requirement here.