TL;DR / Key Takeaway
An employee arrest notification policy requires employees to disclose arrests, citations, or criminal charges within a defined window (typically 24-72 hours) as a condition of continued employment. Unlike conviction-based screening, arrest data carries heightened legal risk under EEOC guidance and state fair-chance laws, making a well-drafted, consistently enforced policy essential to protecting your organization from disparate impact claims while maintaining legitimate safety and compliance oversight.
What HR Teams Need to Know
An arrest is not a conviction. That distinction sits at the center of every legal challenge to workplace arrest policies, and it’s why so many organizations get this wrong.
Your background check program likely already addresses pre-employment criminal history. But post-hire arrest notification is a different animal entirely. It requires employees to proactively report law enforcement contact that occurs during employment — often before any court has determined guilt or innocence.
This matters because arrests, standing alone, are not reliable evidence of conduct. The EEOC has stated for decades that an arrest record by itself does not establish that criminal conduct occurred. Yet many employers — particularly in regulated industries like healthcare, transportation, financial services, and education — have legitimate operational reasons to know when an employee has been arrested, especially for offenses connected to job duties.
The compliance tension is real: you need visibility into events that could affect licensure, safety, insurability, or fitness for duty, but you cannot treat an arrest as equivalent to a conviction without exposing your organization to discrimination liability.
This topic sits at the intersection of your conduct policy, your background check program, and your adverse action process. Getting the notification mechanism right — and the response protocol right — is what separates a defensible policy from a liability magnet.
Detailed Analysis
Why Employers Implement Arrest Notification Policies
Organizations adopt these policies for several defensible business reasons:
- Regulatory obligations — FINRA-registered firms, DOT-regulated drivers, healthcare workers under CMS oversight, and childcare/education employees often have licensing bodies that require prompt disclosure of arrests for certain offenses.
- Duty-of-care exposure — If an employee with client-facing or safety-sensitive duties is arrested for a violent offense, you need the ability to assess risk before the criminal case resolves.
- Bonding and insurance requirements — Fidelity bonds and certain liability policies may require disclosure of employee arrests tied to financial crimes.
- Contractual flow-down requirements — Government contractors and subcontractors frequently must certify that they monitor and report employee arrests related to security clearances or contract eligibility.
The Arrest vs. Conviction Framework
Your policy — and every manager who enforces it — must operate from a clear internal framework. Confusing these categories is the single most common source of legal exposure.
| Factor | Arrest | Conviction |
|---|---|---|
| Legal weight | No adjudication of guilt | Judicial finding of guilt or plea |
| EEOC treatment | Cannot be used alone as basis for adverse action | May be used with individualized assessment |
| Employer action | Investigate; do not automatically discipline | May proceed to adverse action per policy |
| Disclosure trigger | Policy-defined (often job-relevant charges only) | Typically broader disclosure requirement |
| Retention practice | Should not appear in permanent personnel file absent findings | Documented per conduct policy |
Designing the Notification Trigger
Not every arrest warrants disclosure, and demanding blanket reporting of all law enforcement contact — including minor traffic stops or matters wholly unrelated to job function — invites both privacy pushback and disparate impact risk.
Best-practice policies narrow the trigger to:
1. Arrests or charges for felonies
2. Arrests or charges for misdemeanors substantially related to job duties (e.g., theft charges for an employee with cash-handling responsibilities, DUI for a commercial driver)
3. Any charge that would affect a required license, certification, or clearance
4. Charges involving violence, if the role involves vulnerable populations or workplace access
Avoid vague catch-all language like “any interaction with law enforcement,” which courts and plaintiffs’ attorneys will characterize as overbroad and unrelated to legitimate business need.
Notification Timeframes and Enforcement
Most defensible policies require disclosure within 24 to 72 hours of the arrest or charge, or by the next scheduled workday if the employee is out on leave. Building in a grace period tied to business days (rather than calendar days) reduces disputes over technical noncompliance.
Enforcement of the notification requirement itself — as distinct from the underlying arrest — is where you have the most legal footing. An employee who fails to disclose a qualifying arrest per policy can generally be subject to discipline for the policy violation, separate from any conclusions about the arrest’s merits.
Compliance Considerations
EEOC Guidance and Title VII Exposure
The EEOC’s longstanding position, reinforced in its Enforcement Guidance on the Consideration of Arrest and Conviction Records, is that arrest records alone cannot justify an adverse employment action because arrest data has a disproportionate impact on certain racial and ethnic groups and does not establish actual conduct.
If you take action based on an arrest, you must be prepared to show:
- The conduct underlying the arrest was independently investigated (not simply assumed from the charge).
- The decision was based on the nature of the conduct, its relationship to the job, and time elapsed, consistent with the Green factors framework courts apply.
- Similarly situated employees have been treated consistently, regardless of protected class.
State Fair-Chance and Ban-the-Box Interactions
A growing number of states extend fair-chance protections beyond hiring into the employment relationship, restricting how employers can use arrest and conviction data even for current employees. Examples include:
- California — Labor Code Section 432.7 generally prohibits employers from using arrest records that did not result in conviction in any employment decision, with narrow exceptions for pending criminal charges.
- New York — Article 23-A requires individualized assessment before taking adverse action based on criminal history, and case law has extended similar reasoning to current-employee discipline.
- Illinois — The Illinois Human Rights Act restricts consideration of arrest records not resulting in conviction, mirroring California’s approach.
- Massachusetts, New Jersey, and others — Maintain overlapping restrictions on arrest-record use in employment decisions.
If your workforce spans multiple states, your arrest notification policy cannot be one-size-fits-all. Build state-specific addenda or consult counsel on a jurisdiction-by-jurisdiction matrix before rolling out a national policy.
FCRA Considerations
The Fair Credit Reporting Act generally governs employer-initiated background checks conducted through a consumer reporting agency — not self-reported arrest disclosures from employees. However, if an arrest notification triggers a new background check (for cause, promotion, or recertification), that check must follow full FCRA procedure: disclosure, authorization, and — if adverse action results — the standard pre-adverse and post-adverse action notice sequence.
This is a common gap: HR teams treat the self-report as the “compliance event” and forget that any resulting investigative check re-triggers FCRA obligations independently.
Documentation and Retention Risk
Store arrest-related documentation separately from standard personnel files, and clearly label records to reflect that no adjudication has occurred. Undifferentiated arrest data sitting in a personnel file is discoverable and can undermine your defense in a later discrimination claim if it appears the employer treated the arrest as established fact.
Action Steps for Your Team
Quick wins (implement within 30 days):
- Audit your current handbook language. If your policy requires disclosure of “any arrest,” narrow it to job-related and felony-level triggers.
- Confirm your adverse action workflow already separates “policy violation for non-disclosure” from “adverse action based on arrest conduct” — these require different documentation trails.
- Identify your policy owner. This should sit jointly with Employee Relations and Compliance/Legal, not solely with the recruiting or screening team, since it governs current employees rather than candidates.
Longer-term improvements (next 60-90 days):
- Build a state-specific compliance matrix if you operate in multiple jurisdictions, flagging where arrest-record use is restricted or prohibited outright.
- Train frontline managers on the arrest-vs-conviction distinction — most policy failures originate with a supervisor who disciplines based on the charge itself rather than an investigated finding.
- Integrate your notification policy with your background check vendor’s for-cause screening workflow so that any triggered investigation runs through the same FCRA-compliant, adverse-action-automated process you use for pre-employment checks.
- Schedule an annual policy review aligned with your handbook update cycle to capture new state fair-chance legislation.
FAQ
Can we terminate an employee solely because they were arrested?
Generally no. EEOC guidance treats an arrest alone as insufficient grounds for adverse action; you must independently assess the underlying conduct and its job-relatedness. Several states go further and prohibit any adverse action based on non-conviction arrest records.
What’s the difference between disciplining for the arrest versus disciplining for failure to report it?
Disciplining for failure to disclose is generally more defensible because it addresses a policy violation, not the alleged criminal conduct. Make sure your policy clearly states the reporting obligation and consequences for noncompliance as a standalone requirement.
Do we need employee consent to run a new background check after a self-reported arrest?
Yes. Any employer-initiated consumer report triggered by a self-report still requires FCRA-compliant disclosure and authorization, followed by pre-adverse and post-adverse action notices if the check informs a decision.
Should our arrest notification policy apply to all employees or only safety-sensitive roles?
Many organizations limit mandatory notification to safety-sensitive, licensed, or fiduciary roles to reduce disparate impact risk and administrative burden. Broader application should be justified by clear, documented business necessity.
How long should we retain arrest-related disclosures if no conviction results?
Retain only as long as necessary to document the investigation and decision, and store separately from standard personnel records. Consult your state’s data retention rules, as several fair-chance jurisdictions impose specific limits on non-conviction record retention.
Conclusion
A well-drafted employee arrest notification policy protects your organization’s legitimate safety and regulatory interests without crossing into the disparate-impact risk that has drawn EEOC and state-level scrutiny for years. The policy succeeds or fails on precision: narrow triggers, clear timeframes, documented individualized assessment, and airtight separation between “policy violation” and “presumed guilt.”
Getting this right also means your for-cause screening workflow needs to run with the same rigor as your pre-employment process. BackgroundChecker.com helps HR teams run FCRA-compliant background checks with fast turnaround, ATS integration, and transparent per-check pricing — including for-cause and promotional screening triggered by employee self-reports. Whether you’re screening 10 hires or 10,000, our platform scales with your program, backed by adverse action automation and dedicated account management. Request a demo or start screening today to see how a compliant, integrated screening workflow removes the guesswork from your next policy rollout.
This article is for informational purposes and does not constitute legal advice. Consult qualified legal counsel for compliance guidance specific to your organization.