Skip to main content

Background screening

Run a screening end to end — ask a candidate or worker for the right set of checks, collect the documents, and settle the results that need a person to decide.

Who it's for: Recruiters and compliance admins who screen people before and as they start

Availability: Available

What you get​

  • Reusable, role-based bundles, so everyone screened for a role is asked for exactly the same thing
  • Candidate self-submission — they supply their own credentials, before you take them on
  • Candidates arriving from the recruitment platform your hiring already runs in
  • Document requirements where the card alone isn't enough
  • One shared queue for the results that can't be settled automatically, with each decision on the audit trail

Turn it on​

→ Send a recruitment check request — pick the credentials you're asking for, send the secure link, and track the response.

Looking for what Oho can check?

The clearances, registrations, and registers themselves are catalogued under Breadth of verifiables. This page is about the workflow you run them through.

Screening workflow​

Recruitment check requests​

A candidate submits their own credentials through a secure form before they're taken on. What they submit is stored against an applicant record and carries across when you promote them to a worker — nothing is re-collected or re-verified.

Availability: Available

Screening packages​

A reusable, named bundle of the checks a role requires. Define it once, then apply it every time you screen someone for that role instead of re-listing the requirements.

Availability: Available

Attachment requirements and review​

Some credentials aren't complete without the document. A credential type can require a scan or photo before a credential of that type can be saved, and a screening package can require an attachment against a specific credential. Attachments that need a person to look land in the Review & Decide queue.

Availability: Available — set per credential type, and per credential within a package

Review & Decide​

Results that can't be settled automatically queue up in one shared place, where an admin confirms or dismisses each one and the decision goes to the audit trail.

Availability: Available

ATS integrations​

Screen candidates from the recruitment platform your hiring already runs in. They arrive as applicants, and where the connector supports it the result goes back to the recruiter automatically.

Availability: Available — JobAdder, SmartRecruiters, LiveHire, and PageUp

How it works​

A screening is a set of requirements sent to a person. A package defines that set; a recruitment check delivers it to a candidate as a secure link, or an ATS connector delivers it from inside your recruitment platform. Whatever comes back is verified against its source like anything entered by hand, and the few results that need a human judgement queue up in Review & Decide rather than quietly changing someone's status.

→ Applicants — how candidates relate to workers, and what happens on hire → Screening Packages — what a package represents → One-off verification — what happens the moment a credential arrives

For developers

Create applicants, send a requirements block for the checks you need, and subscribe to the completion and verification events instead of polling.

→ Screening an applicant → Workers & credentials → Webhooks & event delivery

Good to know​

  • A recruitment check goes to an applicant who hasn't been onboarded yet. To ask an existing worker for a detail you're missing, send a fetch request instead.
  • Screening someone doesn't start the re-check loop on its own — add a verification source for the credential types you hold.
  • Where several credentials are interchangeable, express it as an equivalence set under compliance rules and require the set rather than one card.
  • The wording and branding of the emails a candidate receives is yours to change — see Customise email templates.