Pre-Employment Background Check
A verification of a candidate's history — criminal records, employment history, or other checks required for the role — usually run after a conditional offer.
A pre-employment background check verifies a candidate's history — criminal records, employment history, or other checks specific to a role or industry — typically run after a conditional offer has been extended.
A background check usually runs through a third-party verification service: the employer submits the candidate's consented identity information, the service checks it against relevant records (criminal history, prior employment, education, driving record depending on the role), and returns a report within a defined turnaround time — often a few days to a week. Because it happens after a conditional offer, the check operates against a clock that didn't exist earlier in the funnel: the candidate has already said yes, so any delay in getting the check back directly threatens an already-agreed start date.
The clock that starts after the offer
A candidate accepts a conditional offer with a start date ten days out. A background check is initiated the same day; the verification service typically returns results in 3-5 business days. If the check comes back clean on day 4, there's a comfortable buffer before the start date. If it's delayed to day 9, the start date itself is now at risk — a timing pressure that doesn't exist at earlier funnel stages, where a delay just slows the process rather than threatening a commitment already made.
In staffing & high-volume hiring
Because it usually happens after an offer, a background check sits in a slightly different part of the funnel than the interview stages: the candidate has already said yes, so a delay or a slow-moving check here directly threatens a start date that's already been agreed to. Requirements also vary meaningfully by role and jurisdiction, so what a check covers for one requisition (a driving record for a delivery role, say) can be entirely different from another.
Common mistakes
- Initiating the background check days after the offer is accepted instead of the same day, which eats directly into the buffer before an already-committed start date.
- Applying one blanket check requirement to every role, instead of tailoring what's checked (driving record, specific certifications) to what the role actually requires.
- Not accounting for jurisdiction-specific rules on how and when criminal history can be considered, which varies enough that a one-size-fits-all policy can create real compliance risk.
Related terms & reading
Pre-Employment Background Check FAQ
Is a background check the same everywhere?
No — what's checked and what disqualifies a candidate varies by role, industry regulation, and local law (some jurisdictions restrict how and when criminal history can be considered), so requirements should be set per role rather than applied as one blanket policy.
How long does a background check typically take?
It varies by provider and the depth of the check, but a few business days to about a week is common — which is why initiating it the same day an offer is accepted matters for protecting an already-agreed start date.
What happens if a background check comes back after someone's already started working?
This depends on company policy and applicable law, but it's generally avoided by design — most processes are built to complete the check before an actual start date, precisely to prevent this scenario.
Build a faster, smarter hiring engine.
Start your 30-day free trial — no setup fees, no contracts. Or see ATS Mako in action.
30-day free trial · No setup fees · No long-term contracts