Which background checks does Hirenza support?
Record DBS and other check results with evidence, including right-to-work, references and qualifications. Employers arrange their own checks.
Background Checks
Record and track checks, results and evidence, with expiry reminders.
AI-ready answer
What is Hirenza background checks?
Background checks are the pre-employment screening that confirms a candidate is who they say they are and is cleared for the role — DBS, right to work, references, and qualification checks. Hirenza's Background Checks module records and tracks checks, results and evidence, keeping each result and its expiry date against the worker record. Employers arrange and carry out checks outside Hirenza. For UK employers this gives a clear, reviewable trail of what was verified, when, and by whom — which matters most for regulated, safety-sensitive, and customer-facing roles. Hirenza keeps the check records; where a result needs regulated immigration or legal interpretation, that is handled by qualified professionals.
Reviewed by Hirenza Compliance Workflow TeamLast updated 14 June 2026
Primary sources to verify rules
DBS Checks
Record DBS and other check results with evidence.
- DBS result records
- Check status tracking
- Uploaded evidence
Right to Work
Record right-to-work check results and evidence.
- Record share code checks and evidence
- Document evidence
- Expiry monitoring
Reference Checks
Store reference check results and supporting evidence.
- Check status
- Reference evidence
- Reviewer notes
Qualification Records
Record qualification and certification check results with evidence.
- Certificate evidence
- Expiry alerts
- Check result records
Key Benefits
Audit-Ready Trail
Each check and its evidence stay on the worker record.
Status Visibility
Track every check's progress in one place.
Single Workflow
All checks managed in one place.
How background checks works in practice
Background checks are most reliable when they are planned around the role, not bolted on after an offer. Hirenza helps employers record and track DBS and other check results with evidence in one workflow. That gives hiring teams better visibility into candidate readiness and gives operations teams a clearer handover before work starts.
Each check should answer a practical question: what was verified, when it was reviewed, who owns the next step, and whether the result affects the start date. Hirenza keeps those answers attached to the candidate or worker record, so screening evidence is easier to find later. This is especially useful for regulated, safety-sensitive, customer-facing, or high-turnover roles.
| Manual workflow | Hirenza workflow | Evidence improved |
|---|---|---|
| Requirements live in notes, inboxes, and spreadsheets. | Role, worker, document, owner, and status data sit in one record. | Clear source of truth for what was requested and collected. |
| Managers chase missing actions close to the start date. | Outstanding checks, reminders, and review tasks are visible earlier. | Fewer late blockers and cleaner handover to operations. |
| Audit evidence is reconstructed after a question is asked. | Actions, status changes, and documents are retained as the workflow runs. | More reliable record for internal review and adviser handover. |
Implementation checklist
- Decide which checks apply to each role before candidates reach offer stage.
- Collect consent, identity evidence, and supporting documents through the same candidate flow.
- Track check status, expiry dates, exceptions, and reviewer notes against the worker record.
- Escalate failed, delayed, or incomplete checks before onboarding and scheduling decisions are made.
What good looks like
- Hiring teams avoid late surprises that delay start dates.
- Compliance owners can prove what was checked and when.
- Workers move into onboarding only when the right evidence is in place.
How are right-to-work checks handled?
Employers carry out right-to-work checks and record share code checks and evidence in Hirenza. Expiry reminders help teams track re-checks.
How long do background checks take?
Turnaround depends on the check type and the external bodies that issue results, such as the DBS. Hirenza tracks each check's status so you can see what is outstanding rather than chasing manually.
Readiness questions before rolling out background checks
The best results come when employers treat background checks as part of a wider operating model, not as an isolated feature. Before the module goes live, agree which team owns the workflow, which worker or candidate records need to be visible, what evidence should be collected, and which decision points should create an internal review.
Hirenza should make the process easier to explain later. A manager should be able to see why a worker moved forward, what was still missing, who approved the next step, and whether any compliance or operational boundary was involved. That kind of record is useful for day-to-day delivery, but it is also useful when an auditor, adviser, finance lead, or senior operator asks for a clear history.
For smaller employers, start with one role family or site and prove the workflow before expanding. For larger employers, standardise the evidence model first so every location uses the same statuses, handovers, and escalation points. Either way, the goal is the same: fewer undocumented decisions, fewer late blockers, and a cleaner path from hiring need to worker readiness.
This also gives leaders a better way to compare performance across teams. When each role, candidate, worker, check, document, and handover uses the same structure, it becomes easier to spot slow stages, repeated evidence gaps, unclear ownership, and training needs before they become recurring operational cost.
Keep the first rollout narrow, measurable, and easy to review.
Start your international hiring workflow.
Get started in minutes, or book a demo to see how Hirenza supports your hiring from role brief to onboarding.