TL;DR
A background check process flowchart maps every decision point—from requisition approval to adverse action—so your team executes consistently and stays FCRA-compliant. This guide gives you a step-by-step framework you can convert into a visual flowchart for your ATS, compliance manual, or hiring manager training deck. Use it to reduce time-to-fill, eliminate compliance gaps, and standardize decision-making across every hiring manager and location.
—
Before You Begin
Building an accurate background check process flowchart requires more than mapping vendor turnaround times. You’re documenting a legally sensitive workflow that touches candidate rights, hiring manager behavior, and multi-state compliance obligations simultaneously.
Prerequisites and Preparation
Before you draft a single flowchart box, gather these inputs:
- Your current FCRA disclosure and authorization forms — confirm they’re standalone documents, not bundled into your employment application (a common violation)
- State and local fair-chance law matrix — jurisdictions like California, New York City, Illinois, and Colorado impose sequencing and timing rules that differ from federal FCRA baseline requirements
- Vendor SLA documentation — average turnaround times by check type (criminal, employment verification, education, MVR, credit)
- Your adverse action templates — pre-adverse and final adverse action letters, plus your process for tracking response windows
- Job-relatedness criteria — documented rationale connecting specific criminal history or credit findings to specific job duties, per EEOC guidance
Stakeholders to Involve
Your flowchart isn’t an HR-only artifact. Building it in isolation is the fastest way to create a document nobody follows.
| Stakeholder | Role in the Process |
|---|---|
| Employment counsel | Reviews disclosure language, adverse action timing, and multi-state variations |
| HRIS/ATS administrator | Confirms system triggers, integration points, and data flow between platforms |
| Hiring managers | Provide input on where delays currently occur; need training on what they can and cannot see or ask |
| Talent acquisition leadership | Owns SLA enforcement and escalation paths |
| Background check vendor/account manager | Confirms technical capabilities, API triggers, and reporting turnaround benchmarks |
Information or Access You’ll Need
Request admin-level access to your ATS workflow builder and your background check vendor’s dashboard before mapping the flowchart. You’ll need visibility into how these two systems currently pass data—many compliance gaps originate at integration handoff points, not within either system individually.
—
Step-by-Step Process
Step 1: Trigger Point — Conditional Offer Issued
What to do: Define the exact moment your background check process initiates. In nearly all jurisdictions, this should be after a conditional offer of employment, not during initial screening or interviews.
Why it matters: Ban-the-box and fair-chance laws in over 35 states and dozens of municipalities restrict when you can inquire about or act on criminal history. Initiating checks pre-offer is one of the most common and costly compliance failures.
Common mistake: Sales or operations teams requesting “quick checks” before an offer is extended, bypassing HR’s documented workflow. Lock down system permissions so only authorized users can initiate a check.
Flowchart box language:
> “Conditional Offer Issued → Trigger Background Check Initiation → Route to Compliance Queue”
—
Step 2: Disclosure and Authorization
What to do: Present the candidate with a standalone FCRA disclosure form and obtain written authorization before ordering any consumer report.
Why it matters: FCRA Section 604(b)(2) requires the disclosure to be a clear, conspicuous document consisting solely of the disclosure—no liability waivers, no employment terms, no additional legalese.
Compliance checkpoint: If your state (California, for example) requires additional disclosure elements or a separate authorization for investigative consumer reports, your flowchart needs a branch here, not a footnote.
Common mistake: Embedding the disclosure inside a multi-page onboarding packet. This has driven a significant share of FCRA class-action settlements industry-wide.
—
Step 3: Order Placement and Package Selection
What to do: Route the authorized request to your background check vendor with the correct package based on job classification (e.g., standard criminal + employment verification vs. enhanced package for driving or financial roles).
Why it matters: Over-screening (running credit checks on roles with no financial responsibility) creates unnecessary legal exposure. Under-screening creates negligent hiring risk.
Decision matrix example:
| Job Category | Standard Checks | Enhanced Checks |
|---|---|---|
| General office/admin | Criminal, SSN trace, employment verification | — |
| Driving/logistics | Above + MVR | DOT drug/alcohol if regulated |
| Financial/fiduciary roles | Above + credit check (where legally permitted) | FINRA/registration checks if applicable |
| Healthcare | Above + license verification | OIG/SAM exclusion list check (CMS requirement) |
Common mistake: Using a single one-size-fits-all package for every requisition. This inflates costs and can trigger disparate impact concerns if credit or criminal checks aren’t job-related.
—
Step 4: Vendor Processing and Turnaround Monitoring
What to do: Track check status against your vendor’s committed SLA. Build automated alerts for checks exceeding standard turnaround (typically 2–5 business days for most checks; longer for education/employment verification requiring manual outreach).
Why it matters: Delayed background checks are the number one driver of candidate drop-off between offer and start date. A flowchart with built-in escalation triggers protects your time-to-fill metrics.
Flowchart branch:
> “Check Pending > SLA Threshold → Auto-Escalate to Account Manager → Notify Recruiter of Delay”
—
Step 5: Results Review and Job-Relatedness Assessment
What to do: Route completed reports to a trained reviewer—not the hiring manager—who assesses findings against your documented job-relatedness criteria.
Why it matters: EEOC guidance requires an individualized assessment for criminal history findings, considering the nature of the offense, time elapsed, and relevance to job duties. A blanket “no felonies” policy is not defensible.
Compliance checkpoint: Document the individualized assessment in writing, every time, even when the outcome is “proceed with hire.” This record is your primary defense if the decision is later challenged.
Common mistake: Allowing hiring managers direct, unfiltered access to raw report data. This increases discrimination exposure and inconsistent decision-making across teams.
—
Step 6: Pre-Adverse Action (If Disqualifying Information Is Found)
What to do: If the report may result in a negative hiring decision, send the candidate a pre-adverse action notice including a copy of the report and the FTC’s “Summary of Rights” document. Provide a reasonable waiting period—commonly 5 business days, though some states require longer—before finalizing the decision.
Why it matters: This step exists specifically to let candidates dispute inaccurate information. Skipping it is a standalone FCRA violation regardless of whether the underlying decision was justified.
Flowchart branch:
> “Disqualifying Info Found → Send Pre-Adverse Notice → Hold [X Business Days] → Candidate Response? → Yes: Review Dispute / No: Proceed to Final Adverse Action”
—
Step 7: Final Adverse Action or Clearance
What to do: If the candidate doesn’t dispute the findings or the dispute doesn’t change the outcome, send the final adverse action notice. If the candidate clears, move them into onboarding immediately.
Why it matters: The final notice must include specific required elements: the decision, the reporting agency’s contact information, and a statement of the candidate’s continued FCRA rights.
Common mistake: Failing to track adverse action letters as auditable records. Store timestamps and delivery confirmation for every notice sent—this is standard documentation your legal team will request during any audit or litigation.
—
Step 8: Onboarding Handoff and Record Retention
What to do: Push cleared candidates automatically into your onboarding workflow via ATS/HRIS integration. Set retention schedules for background check records per FCRA (minimum 2 years for adverse action documentation, longer where state law requires).
Why it matters: Manual handoffs between screening and onboarding are a common source of delayed start dates and lost documentation.
—
Pro Tips from Experienced HR Teams
Build conditional logic directly into your ATS, not just your flowchart. Static flowcharts in a shared drive get ignored. Teams that embed decision rules into ATS workflow automation see far higher consistency across recruiters and locations.
Negotiate tiered pricing based on volume commitments, not per-check spot rates. If you’re processing more than 500 checks annually, your vendor should offer volume discounts, dedicated account management, and custom SLA guarantees—ask directly rather than accepting standard rate cards.
Create a separate fast-track flowchart branch for contingent/gig workers if your organization uses them, since state requirements and permissible check types often differ from full-time employee screening.
Use pre-built adverse action automation rather than manually tracking waiting periods in spreadsheets. Missed adverse action windows are among the most common compliance failures HR teams self-report during internal audits.
Map your rescreening cadence (annual MVR checks for drivers, periodic OIG exclusion checks for healthcare) as a recurring loop in your flowchart, not a one-time linear process.
—
Common Mistakes to Avoid
| Mistake | Risk | Fix |
|---|---|---|
| Running checks pre-offer | Violates ban-the-box laws in most states | Lock system permissions to trigger only post-offer |
| Bundling disclosure with other paperwork | Standalone FCRA violation | Separate disclosure into its own document/e-signature step |
| Skipping individualized assessment documentation | EEOC disparate impact exposure | Require written rationale for every adverse decision |
| Inconsistent state law application | Multi-state employers face varying pre-adverse waiting periods | Build state-specific branches into your flowchart, not a single national default |
| No audit trail for adverse action notices | Indefensible position in FCRA litigation | Store timestamped delivery confirmation for every notice |
—
FAQ
Do I need a different flowchart for every state I hire in?
Not necessarily a fully separate flowchart, but you do need conditional branches for jurisdictions with stricter fair-chance timing or disclosure requirements. California, New York City, and Illinois are the most common triggers for state-specific branching.
How long should the pre-adverse action waiting period be?
FCRA doesn’t specify an exact number of days, but 5 business days is the common industry standard. Some states and municipalities mandate longer windows, so confirm requirements for every jurisdiction where you hire.
Can hiring managers see raw background check reports?
Best practice is no. Route reports through a trained compliance reviewer who applies your documented job-relatedness criteria consistently, reducing both discrimination risk and inconsistent decision-making.
What’s the difference between pre-adverse and final adverse action?
Pre-adverse action gives the candidate a chance to dispute inaccurate information before a final decision. Final adverse action confirms the decision after the waiting period has passed and includes the candidate’s ongoing FCRA rights.
How often should we audit our background check flowchart?
Review it at minimum annually, and immediately after any state or local fair-chance law changes take effect. Multi-state employers should also review whenever expanding hiring into a new jurisdiction.
—
Conclusion
A documented background check process flowchart isn’t a nice-to-have compliance artifact—it’s the operational backbone that keeps your hiring team consistent, defensible, and fast. When every recruiter and hiring manager follows the same trigger points, escalation paths, and adverse action sequencing, you reduce both legal exposure and time-to-fill simultaneously.
BackgroundChecker.com helps HR teams run FCRA-compliant background checks with fast turnaround, automated adverse action workflows, and direct ATS/HRIS integration, so your flowchart isn’t just a diagram—it’s how your system actually operates. Whether you’re screening 10 hires or 10,000, our platform scales with transparent per-check pricing and dedicated account management to support your compliance program. Request a demo or start screening today to see how automation can turn this flowchart into your everyday workflow.
—
This article is for informational purposes and does not constitute legal advice. Consult qualified legal counsel for compliance guidance specific to your organization.
