If you accept the premise that a clean background check no longer proves a clean history, the next question is entirely practical. What do you actually change on Monday morning?
Most screening programs were architected for a world where criminal records were permanent and public. That world is receding. More than a dozen US states now seal eligible records automatically, on statutory timelines, often reaching backward into records that were openly reportable a year ago. The programs built on the old assumption will not fail loudly. They will simply drift out of accuracy, returning clean results that are technically correct and substantively misleading, while occasionally reporting sealed records they should never have surfaced.
This is the operational response. None of it requires waiting for a federal law or for your jurisdiction’s rules to settle. It is a redesign you can begin now, and the organisations that do it early will spend far less time later explaining a decision made on data that had already gone dark.
Re-map where your data actually comes from
Start with a question most HR teams have never asked their provider directly: at the moment of a check, is this record pulled live from the court of record, or retrieved from an aggregated database that refreshes on a schedule?
The answer determines your entire exposure. Aggregated databases are fast and cheap, and they are exactly where sealing creates problems, because they lag the courts in both directions. They can report a record after it has been sealed, and they can keep showing a record as findable when the underlying source has already removed it. A live, source-level search reflects what is legally reportable today.
You do not need every check to be source-level for every role. You do need to know which of your checks are running on cached data, so you can decide, deliberately, where that risk is acceptable and where it is not.
Treat “no record found” as a sentence, not a verdict
The cheapest, highest-leverage change costs nothing but attention: fix the language.
Reports and internal policies that say “no record found” invite the reader to hear “no history.” Replace that phrasing with something accurate, along the lines of “no legally reportable record located.” Document, in your screening policy, that a clean result does not confirm the absence of criminal history, only the absence of records currently available to report.
This sounds like wordsmithing. It is not. Hiring managers make decisions on the words in front of them. If those words overstate what the check established, the organisation has manufactured a false sense of certainty that someone will eventually rely on.
Re-run rather than rely, and decide your cadence
In a world of sealing, the date of a check is part of its meaning. A criminal check is a snapshot of what was reportable on a specific day, and the reportable set is changing underneath you.
For most roles, this argues for a defined re-screening cadence rather than a single pre-hire check treated as permanent truth. For higher-risk roles, particularly those with financial authority, access to vulnerable people, or safety-critical duties, continuous monitoring is the more honest model. It accepts that the relevant picture is not fixed at the offer letter and keeps it current across tenure. The point is not to re-check everyone constantly. It is to match the refresh rate of your information to the actual risk of the role.
Build jurisdiction-aware logic, because the patchwork is the problem
There is no single national rule, and there will not be one soon. Each state’s sealing regime differs in eligible offences, waiting periods, exclusions, and rollout schedule. That means a consistent, one-size screening process is now a liability rather than a virtue.
The complication that programs most underestimate, as Littler’s attorneys have flagged, is the mobile workforce. Remote work and candidates applying across state lines mean the law governing a given record may not be the law of your headquarters. Your screening logic has to be able to vary by the candidate’s relevant jurisdictions, and your team needs counsel on hand for the genuinely ambiguous cases. This is precisely the kind of complexity worth handing to a provider with multi-jurisdiction infrastructure rather than trying to track fifty-plus moving timelines in a spreadsheet.
Tighten the adverse-action and dispute loop
The FCRA’s requirement to assure maximum possible accuracy does not relax just because records are harder to track. If anything, sealing raises the stakes, because the most damaging error is now reporting something that has already been sealed and then acting on it.
Two safeguards matter. First, before any adverse decision based on a record, run the full FCRA process: a pre-adverse-action notice with a copy of the report and the summary of rights, a genuine window for the candidate to review and dispute, and a final notice only if you proceed. A blank result does not reduce these duties, and neither does a busy hiring quarter. Second, make disputes easy and fast, because a candidate disputing a record that was recently sealed is often correct, and a quick correction is far cheaper than the alternative.
Decide your posture on sealed records and negligent-hiring fear
A real driver of over-reliance on old criminal data has always been fear of a negligent-hiring claim. It is worth confronting that fear with what the law actually says.
Several states that have enacted Clean Slate laws have paired them with explicit employer immunity, shielding employers from negligence liability for misconduct connected to a sealed record. The federal bill proposes the same. As employment counsel have noted, negligent-hiring suits tied to these hires remain uncommon, and the legislative trend is actively protecting employers who give people with old, sealed records a chance. The defensible posture is not to chase information you are no longer permitted to use. It is to follow the law, rely on what is reportable, and document that you did.
Keep individualised assessment alive when a record does surface
Sealing changes which records you see. It does not change what to do with the ones you still do. When a reportable record appears, the EEOC’s long-standing guidance still governs: assess it individually against the nature and gravity of the offence, the time that has passed, and its direct relevance to the specific duties of the job.
A blanket “any record disqualifies” rule was always legally fragile. In the current environment it is worse, because the records that survive sealing are disproportionately the more recent or more serious ones, exactly the category where a thoughtful, role-specific assessment protects you better than a reflex.
Audit your vendor’s data freshness, in writing
Finally, turn the first point into a procurement requirement. Ask your screening partner, and get the answer in writing: How often is your underlying data refreshed? When a record is sealed, how quickly does it leave your system? What is your process to avoid reporting sealed or cleared records? How do you handle a dispute on a record that should have been sealed?
A provider who can answer these crisply is one whose results you can defend. A provider who cannot is a latent FCRA claim sitting on your books, and the fact that the error originated with the vendor will be cold comfort when the report carried your decision.
Designing for a Record That Moves
The instinct, faced with all of this, is to treat sealing as something done to the screening process, a problem imposed from outside. That framing leads to the wrong work, hunting for ways to keep seeing what the law has decided to hide.
The better framing is that the criminal record has been demoted from a permanent backstop to one input among several, and the screening program should be rebalanced accordingly. That means leaning harder on the things sealing does not touch: rigorous identity verification, employment and education history confirmed at source, role-based risk design, and monitoring that stays live over time. It means sourcing criminal data from the court rather than from a cache, so that what you receive is accurate to the day. And it means saying, plainly, inside your own organisation, what a clean check now establishes and what it does not.
The record can move now. Design the process so that when it does, you are the first to know, not the last.
