How Oho Works

Oho takes your workforce from "we think everyone's compliant" to "we know — and we'll know the moment that changes." Here's the journey, end to end:

1. Ingest your data — get your people into Oho.
2. Keeping your data in sync — who owns which facts once your system and Oho both hold the same worker.
3. One-off verification — every credential is checked the moment it's added.
4. What a check result means — the one vocabulary every register's answer is translated into, and what each result does to the worker.
5. Ongoing checks — set up Verification Sources so checks keep running on a schedule.
6. How monitoring works — the two moments a check happens, who sets the cadence, and what you see when an answer changes.
7. Review compliance dashboards — see where you stand at a glance.
8. Get notified when issues arise — hear about problems automatically.
9. Fetch credentials from workers — ask workers for the details only they have.
10. Webhooks (for developers) — get a push the moment a check result changes, so your own systems stay in sync.

Three things run alongside the whole journey rather than at a point in it:

• Roles & access — what each person who logs in can see and do, and how you narrow someone's view to the part of the business they look after.
• Where a record came from — the chain behind a credential: what your source system sent, what the register said back.
• The audit trail — the history kept on every record, so you can show what you knew on the day you made a decision.

New to the building blocks behind this? See Core Entities.