Compliance dashboards
See where the whole workforce stands at a glance — compliant, at risk, or non-compliant — and work a queue of the people who need chasing.
Who it's for: Compliance managers and operations leads
Availability: Available
What you get
- Read your position from a donut chart and three cards: Compliant, At Risk, Non-Compliant
- Narrow the picture to one team, site, or region instead of one workforce-wide number
- Work the Requires Attention list of workers with expired or expiring credentials
- Act from the queue — drill into a worker, or request updates from several at once
- Export the snapshot as a PDF or CSV for the managers responsible for each area
Turn it on
→ Understand your Compliance Overview — open the dashboard, read what each result means, and act on the workers it flags.
Nothing to switch on — the Compliance Overview is in the left menu under Continuous.
How it works
Every check produces a colour-coded outcome. Those outcomes roll up per organisation into the snapshot at the top of the page, and the workers counted as At Risk or Non-Compliant make up the Requires Attention list below it. Because your people are grouped into organisations — sites, business units, regions — you can read the picture for each group on its own rather than as one aggregate.
→ Review compliance dashboards — where the dashboard sits in the journey → Organisations — how the grouping and roll-up works → Core Entities — the outcomes behind the numbers
For developers
Read compliance state over the REST API and page through it for reporting across a large workforce, and subscribe to credential.verified so your own dashboards update as results land rather than on a nightly poll.
→ Workers & credentials → Pagination, filtering & sorting → Webhooks & event delivery
Good to know
- At Risk is a credential expiring soon; Non-Compliant is one expired or failed. Of the outcomes, May Not Engage and Review Required are the two that need you — the rest either resolve on their own or need nothing.
- A downloaded report reflects whichever Organisation filter you have selected.
- Some results — ban-register matches, police-check decisions, attachment reviews — need an explicit Confirm or Dismiss. Those land in the shared Review & Decide queue, and each resolution is written to the audit trail.
- For a flagged worker you have three routes: send a fetch request, record an exemption, or verify the credential again.
- Who sees which workers depends on their role and the organisations they can see — see Roles & access.
- Rather than opening this page on a schedule, set up notifications and let Oho tell you.