Criminal-Record Hiring Just Lost Its Federal Playbook.

The EEOC withdrew guidance, not the statute

The Commission's October 29 release is unusually direct. It says the EEOC voted the previous day to rescind its 2012 Enforcement Guidance on the Consideration of Arrest and Conviction Records in Employment Decisions Under Title VII, and that the rescission took effect immediately. It does not restore policies displaced by the 2012 document. It does not require employers to abandon lawful practices adopted because of that document. And it does not announce a new criminal-record standard.

Chair Andrea Lucas framed the change as a return to the Constitution and the limits Congress placed on the agency's authority. In the same statement, she said Title VII continues to prohibit discrimination based on race or national origin, including requirements used as proxies for intentional discrimination. That combination matters. The Commission is narrowing its own interpretive position while acknowledging that the underlying prohibition remains.

Guidance is not a statute or a judicial holding. It can organize an agency's enforcement analysis, tell regulated parties what facts the agency considers important, and influence compliance systems. It cannot rewrite the elements Congress enacted. Rescinding guidance therefore changes the quality and predictability of the signal employers receive from Washington. It does not turn every criminal-record exclusion into a lawful one.

Disparate impact did not begin with the 2012 document

Title VII expressly addresses disparate impact. A complaining party must identify a particular employment practice that causes a disparate impact based on a protected characteristic. The employer may then defend the practice as job related for the position and consistent with business necessity. The statute also addresses alternative employment practices and generally requires separate analysis of each challenged part of a decision process.

That framework is older and more durable than the rescinded guidance. In Griggs v. Duke Power Co., the Supreme Court held that facially neutral diploma and aptitude-test requirements violated Title VII where they disproportionately excluded Black workers and were not shown to measure successful job performance. Congress later codified the disparate-impact burden in the Civil Rights Act of 1991. Reasonable lawyers can disagree about how particular criminal-record policies fit that doctrine. They cannot treat rescission of an agency document as repeal of the doctrine itself.

The practical implication is not that every statistical difference proves liability. Plaintiffs still need evidence connecting a particular practice to a protected disparity. Employers retain statutory defenses. Different jobs can justify different qualifications, and some positions are subject to legal restrictions that make particular convictions relevant. The point is narrower: an employer that uses the same exclusion for every offense, every time period, and every job is making a factual claim about risk. It should be able to prove that claim rather than assume the absence of guidance proves it for them.

The disappearance of a compliance document does not reduce a policy's impact. It reduces the amount of federal explanation surrounding it.

An arrest and a conviction still describe different things

One of the old guidance's most useful contributions was conceptual rather than ideological: an arrest records an accusation and state action, not an adjudication of guilt. A conviction ordinarily carries different evidentiary weight, but even conviction databases can be incomplete, stale, misclassified, sealed, expunged, or matched to the wrong person. The decision to remove guidance does not improve the data.

The EEOC's criminal-record resource page, as available on October 30, still tells applicants and employers that a person cannot be rejected simply because of an arrest and that employers may instead examine the underlying conduct when relevant. It also advises considering the nature and seriousness of an offense, the time elapsed, and the nature of the job. The continued presence of that page may change, and it is not a substitute for the rescinded enforcement guidance. It does, however, illustrate the operational problem the guidance was trying to solve.

For applicants, the distinction is personal and practical. A database entry can outlive a dismissal. A record may omit a later disposition or report a downgraded offense incorrectly. A categorical rule converts those data defects into employment consequences before anyone asks whether the record is accurate or the conduct matters to the work. For employers, an individualized review is not an act of charity. It is a way to test whether the information predicts a job-related risk rather than merely producing a reason to say no.

The background-check process has its own federal law

Many employers receive criminal-history information from a background-screening company. That introduces a separate statute. The Fair Credit Reporting Act requires, among other things, notice and authorization before obtaining certain employment reports and a defined adverse-action process when an employer relies on a consumer report. Before the adverse decision, the applicant must receive the report and a summary of rights. Afterward, the employer must provide additional information, including the reporting company's identity and the right to dispute accuracy or completeness.

Those procedural protections matter most when a report is wrong. They give the person a chance to identify a mismatched identity, a missing disposition, or another defect before the employment decision becomes final. The EEOC's rescission does not amend the FCRA, displace the Federal Trade Commission's enforcement authority, or remove the employer's obligations when a third-party report drives the decision.

State and local law adds another layer. Some jurisdictions delay criminal-history questions until later in the hiring process, restrict the records an employer may consider, require job-related analysis, or prescribe notices. The precise requirements vary. A national employer cannot safely replace the rescinded federal guidance with a single nationwide permission slip. It needs a jurisdictional map and a process that records which law, which job, which record, and which decision applied.

Less guidance makes disciplined judgment more valuable

The most defensible response is not to freeze every policy in its 2012 form or to delete every safeguard because the Commission changed course. It is to separate legal requirements from internal risk controls. Identify which exclusions are mandated by law, which are based on a demonstrable job risk, which exist only because they have always existed, and which cannot be explained without reference to a withdrawn document.

A serious review should preserve the distinction between arrests and convictions, verify the record and disposition, connect the conduct to the responsibilities of the position, account for time and rehabilitation where applicable, apply standards consistently, provide required notices, and document the reason for the decision. It should also test outcomes. A policy can be written in neutral terms and still produce a pattern the organization needs to understand.

The rescission may reduce the likelihood that an investigator begins with the 2012 framework. It may change enforcement priorities and the arguments available in a particular case. Those are meaningful consequences. But employers should be skeptical of any advice that compresses the development into four words: background checks are easier. The law is still layered, the records are still fallible, and the people excluded by a shortcut still experience the decision as final.

The better conclusion is less dramatic. Washington withdrew a playbook. Employers still have to make hiring decisions under statutes, cases, and a patchwork of local rules. When the government supplies less explanation, the quality of the employer's own reasoning becomes more visible, not less important.