Offer-stage screening
Collect consent before a client begins employment, education, identity, licence, or criminal background verification.
Use this form before final-stage verification so screening activity is documented, candidates know what is being checked, and recruiters can keep clearance notes attached to the hiring record.
When to use it
This form is most useful when a placement depends on permissioned checks rather than informal email approval. It creates a clear permission trail before any sensitive candidate data is shared.
Collect consent before a client begins employment, education, identity, licence, or criminal background verification.
Confirm the candidate understands start-date conditions before a temporary or contract assignment is released.
Keep the authorization, screening scope, and unresolved questions in one place for later review.
Form fields
The form should be specific about what will be checked, who can access the information, and which candidate details are needed to avoid rejected screening requests.
Start with the information needed to confirm the candidate and capture permission clearly.
Full legal name, preferred name, current address, phone number, and email used for screening updates.
Date of birth or identity details only where the screening provider or local process requires them.
A consent statement explaining that the candidate authorizes role-related background verification.
Candidate signature, date, and acknowledgement that missing information can delay the hiring process.
Make the requested checks understandable before anything is sent to a vendor or client.
Check categories such as employment history, education, licence validation, references, sanctions, or criminal records.
Name of the client, role, recruiter owner, and screening partner receiving the authorized details.
Notes field for country-specific disclosures, expiry rules, or checks that depend on conditional offer status.
Follow-up owner, expected turnaround, and where clearance status will be recorded in the candidate file.
Recruiter workflow
Run the form after the candidate has real interest in the role and before screening partners receive personal information.
Tell the candidate why the check is needed, which areas are included, and how the result affects the hiring step.
Store the signed authorization on the candidate record so recruiters do not rely on a scattered inbox trail.
Connect pending, cleared, or escalated screening status to the relevant job order and placement workflow.
Common mistakes
The biggest risk is treating consent as a quick checkbox instead of a document that explains scope, ownership, and candidate expectations.
A broad phrase like “run checks” leaves candidates unclear about what information may be reviewed.
A healthcare role, finance role, driver role, and junior office role may require different screening depth.
If the form sits outside the ATS or CRM, recruiters may struggle to prove when consent was collected.
ATZ CRM workflow
ATZ CRM helps recruiters keep consent, screening notes, client requirements, and candidate status together instead of splitting the process across spreadsheets and email threads.
FAQ
Quick answers for using the background check authorization form in a live recruiting process.
Send it when the candidate is far enough in the process for verification to be justified and before any screening provider or client receives sensitive candidate details.
The candidate should know which checks are planned, who requested them, how the information will be used, and who to contact if details are incorrect.
Yes. Keeping the signed authorization with the candidate record helps recruiters track consent, screening status, and follow-up decisions in one workflow.