Permanent placements
Confirm employment dates, role history, and reference coverage before the client moves to offer.
This page is built for agencies that need a practical verification workflow before final submission, offer confirmation, or contractor start dates without turning background screening into a loose email trail.
Who it helps
The checklist supports recruiters who need to protect clients, candidates, and internal accountability while keeping evidence attached to the hiring record.
Confirm employment dates, role history, and reference coverage before the client moves to offer.
Track compliance-sensitive items before a contractor is cleared for the first shift or assignment.
Separate factual verification from subjective market feedback when stakes and visibility are high.
Checklist
Use the grouped items below as a recruiter-facing control list; adjust requirements for local law, client policy, seniority, and role risk.
Begin by confirming what can be checked and why the check is being requested.
Record written candidate consent before requesting external verification or sharing personal details.
Match screening depth to the role, industry, client policy, and country-specific compliance expectations.
Document which checks are mandatory, optional, client-requested, or dependent on offer stage.
Explain timing to the candidate so delays do not look like recruiter silence.
Validate the claims that affect eligibility, compensation, and client confidence.
Confirm legal name, current location, work authorization, and required identification documents.
Review employment history for date gaps, title mismatches, unexplained overlaps, and missing employer names.
Check licenses, certifications, degree claims, or training records when the role depends on them.
Store verification notes with source, date, owner, and unresolved questions for later audit.
Close the loop with a decision trail that recruiters and clients can understand.
Flag discrepancies as questions first, then ask the candidate for context before escalating.
Separate factual findings from recruiter opinion in the candidate record.
Confirm whether the client, recruiter, or third-party provider owns final clearance.
Update the job pipeline only after the verification outcome and next action are captured.
ATZ CRM workflow
A recruiting CRM should keep the verification trail connected to the candidate, job, client, and placement outcome.
Add verification tasks, notes, and missing documents to the candidate record before contacting outside parties.
Tie screening requirements to the job order so every recruiter understands which checks matter for that client.
Use pipeline updates and activity history to show when the candidate is verified, pending, or blocked.
Common mistakes
Most background-check problems come from unclear ownership, missing consent, or notes scattered outside the recruiting system.
Screening without a documented permission trail creates avoidable trust and compliance risk.
A finance director, nurse, warehouse contractor, and junior marketer should not share one screening depth.
Date or title mismatches may be harmless, but they still need a recruiter-owned explanation.
Helpful next steps
Connect background checks with references, candidate submission quality, onboarding readiness, and compliance controls.
FAQ
Confirm candidate consent, the client-approved screening scope, required documents, the role risk level, the expected turnaround time, and who owns the final clearance decision.
Log the discrepancy, ask the candidate for context, separate facts from assumptions, escalate only when needed, and keep the client-facing update factual and role-related.