Here's a rule that sounds simple and isn't. In a growing number of states, certain criminal records now get sealed automatically. No petition, no lawyer, no court date. The state just does it, once someone qualifies. These are called Clean Slate laws, and they've spread fast since Pennsylvania passed the first one in 2018.
Here's the problem nobody tells employers about. A record can be sealed by the state and still show up on a background check you order. Not because your vendor did something wrong on purpose. Because "automatic" describes what the state does. It doesn't describe what every commercial data vendor's database does.
That gap is what this article is about. If you've ever searched "do expunged records show up on background checks" or worried about clean slate law employer liability, this is the actual mechanism behind both questions. Let's start with what these laws do, then get into why the data doesn't always keep up.
The old way to clear a record was expungement by petition. The person had to go to court, fill out paperwork, often pay a lawyer, and ask a judge to seal or destroy the record. It worked, but it took effort, time, and money that a lot of people never had.
Clean Slate laws flip that around. A state agency, usually the state police records repository or the courts' own administrative office, runs eligible criminal records through an automated process on a schedule. If a record meets the state's conditions, it gets sealed. Nobody has to ask.
The conditions vary by state, so I won't hand you one universal number here. Generally, states exclude violent felonies, sex offenses, and often certain DUI or weapons charges.
They usually require a waiting period since the sentence ended, with no new convictions in between, and full payment of fines or restitution. Check your specific state's law before you assume a record qualifies. Don't guess.
One more distinction that trips people up: sealed and expunged aren't the same thing. Sealing generally hides a record from most public and commercial requesters, but the record still exists in the underlying system somewhere.
Expungement, in some states, means the record is actually destroyed or treated legally as if it never happened. Courts and background check companies can treat these two situations differently in what they're allowed to disclose.
And here's a limitation worth flagging on its own, because employers assume it doesn't exist. State-level sealing doesn't automatically update the FBI's federal criminal history database.
A fingerprint-based background check, the kind required for a lot of licensed professions, banking, healthcare, and government-adjacent roles, pulls from federal and interstate systems. Those can still surface a record the state considers sealed.
That's not a vendor mistake. That's a gap between state and federal systems that nobody has fully closed yet. That part's not optional to know if you hire into any of those fields.
I'm going to be careful here, the same way I'm careful anytime I talk about state law in this column. This list changes fast, and I mean that literally, not as a disclaimer I toss in out of habit.
Broadly, states fall into three groups. Some have automatic sealing systems that are live and actually processing records today. Some passed a Clean Slate law that's still being phased in, or is dealing with a backlog that's delaying real implementation.
Some have a bill moving through their legislature right now that hasn't become law yet. Where any specific state sits changes throughout the year, sometimes within a single legislative session.
I won't hand you a static list here and call it final, because by the time you read this it might already be wrong. If you operate in more than a couple states, look up each one's current status directly, or ask a lawyer who tracks this.
Here's something directly relevant to everything else in this article, though. More than one state's automatic sealing system has taken years longer to actually start working than the law's effective date suggested.
The law passed. The sealing didn't start on time. If a state's own system can run behind on its own records, it's optimistic to assume every third-party data vendor is somehow ahead of the state itself.
The trend line, without overclaiming specifics: interest in Clean Slate laws has been bipartisan and it's been growing, year over year. This isn't a fringe policy experiment anymore. Expect the list of states, and the number of sealed records sitting in old databases, to keep growing through the rest of 2026 and into next year.
Let's start with the baseline rule, then I'll get into the exceptions. Once a record is sealed under a Clean Slate law, you generally can't ask about it, can't consider it when you're making a hiring decision, and can't take adverse action because of it.
Treat that as your default. Then check your specific state for exceptions, because there are some.
Several states don't stop at "just don't use it." They attach real teeth. Some create a private right of action, meaning the candidate can sue you directly. Others treat it as a form of unlawful discrimination enforced by a state agency.
I'm not going to hand you a specific penalty dollar figure here, because that's exactly the kind of detail that varies by state and changes. Ask a lawyer for your state's actual exposure.
Here's a practical one that catches employers off guard. Standard application language, "have you ever been convicted of a crime," can itself be a compliance problem in a Clean Slate or ban-the-box state if it doesn't carve out sealed records.
Your application form is part of your exposure here, not just your background check process. Go look at yours.
There are carve-outs, generically speaking. Law enforcement and public safety hiring. Roles working with children, the elderly, or other vulnerable populations.
Positions requiring a state professional license. Jobs where federal law mandates a fingerprint-based check no matter what your state's sealing law says. If you hire into any of these categories, don't assume the general rule applies to you. It might not.
This is the part that actually matters most, so let me walk through the mechanism instead of just asserting it.
Most cheap, fast "instant" criminal searches don't call the courthouse in real time. They search a database the vendor built by scraping court and state records in bulk, on a schedule. Weekly. Monthly. Sometimes longer than that.
When you order an instant search, you're not asking the court a fresh question. You're asking a copy the vendor made a while ago.
So to say that again a different way, because it's the whole point of this article: when a court seals a record, that doesn't reach backward into every commercial database that already scraped and stored a copy of it.
The cached copy just sits there. It stays until the vendor's next scrape catches the change, and only if the vendor's process is actually built to detect and remove sealed records, not just add new ones as they come in.
Identity matching makes it worse. A lot of instant databases match records by name and date of birth instead of case number. So a sealed record can still attach itself to your candidate through a loose match.
That happens even after the actual court record is hidden from a direct court lookup. The record's sealed at the source. The copy sitting in someone's database doesn't know that.
Here's the contrast that matters most in this whole piece. A true primary-source search, one that queries the actual court directly at the time you request it, should reflect current sealed status.
A database-only "instant" search reflects whatever the vendor last scraped, which could be months old. Both of these get sold to you as "a criminal background check." They are not the same product.
Remember that the next time someone on your team buys screening services based on price alone.
I'll be honest about the limits of even the good option, though. Primary-source lookups can still lag right after a new Clean Slate law takes effect, if the court's own docketing system hasn't finished processing its backlog of newly-eligible records. Primary-source search is materially better. It's not a perfect guarantee. Nothing here is.
Here's the reframe I want HR teams to sit with. This isn't "our vendor gave us a stale report" and then it's their problem to fix. It's layered legal exposure that lands on you, the employer, because you're the one who took the adverse action. Not the data vendor.
Under federal law, background check companies have to follow reasonable procedures to keep what they report as accurate as possible. A sealed or expunged record showing up on a report sits squarely inside the kind of accuracy dispute that federal law is built to address.
I'm going to say the exact provision generically on purpose. I want you checking current text with a lawyer rather than trusting a citation I typed from memory.
State law stacks on top of that, it doesn't replace it. A report can be technically compliant with federal accuracy rules and still put you in violation of a state's "employers may not consider this" rule, if the report contains a sealed record and you act on it.
Here's the part that makes this genuinely unfair to employers, and I mean that. You usually can't tell from the report alone that a record should have been sealed. Nothing on a standard instant report flags "this may be sealed in your state as of this date."
You're not being careless. You're missing information the report itself doesn't give you. That invisibility is exactly what makes this a trap instead of an obvious risk you'd naturally manage around.
I won't name specific lawsuits or dollar figures here, because I haven't verified any and I'm not going to make one up to sound more convincing.
What I can tell you honestly is that this is a known, active area of employment-screening litigation and regulatory attention. Treat it that way. Don't wait for a specific case to convince you it's real.
Match your search product to your actual risk. If you're hiring into a state with an active Clean Slate law, or into roles where an aged, low-level record is plausible, don't default to the cheapest instant database search.
Use a vendor that offers direct primary-source court verification, at least for anything that looks like it could be sealing-eligible.
Build yourself a simple pause rule. If a report shows a record that looks old, low-level, and resolved, fines paid, no new offenses since, treat that as a signal to run a fresh primary-source check before you make any adverse action decision. Don't act on the instant report alone just because it's faster.
Go fix your application language for every state you hire in that has ban-the-box or Clean Slate rules. Make sure your conviction-history question doesn't accidentally solicit information about a sealed record.
And tell your hiring managers, plainly, not to ask about criminal history based on rumor or something they heard informally. That happens more than people admit.
Keep a living list. Which states you actually hire in, which of those have Clean Slate or automatic sealing laws, and what each one restricts. Date it. Review it every quarter, not once and done, because the pace of change in 2026 makes a one-time setup obsolete fast.
And default to getting a second opinion, from counsel or a compliance-focused reviewer, before you take adverse action on anything that could plausibly be sealed-eligible. The report is not the final word. Treat it as a starting point, not a verdict.
These are questions you can put directly into an email today. Keep them this specific, because vague questions get vague answers.
A vendor that answers these clearly and specifically is telling you something real about how seriously they take this. A vendor that gets vague or defensive is telling you something too.
Momentum toward automatic sealing has been consistent and it's crossed party lines. That's not a prediction, it's just the pattern so far. The list of states keeps growing. So does the volume of records getting newly sealed. Which means the data-lag problem this whole article is about gets bigger before it gets smaller.
Courts, state agencies, and background check vendors are working toward better data sharing, states building bulk feeds that authorized CRAs can pull from directly instead of scraping. That kind of infrastructure work has historically taken years to actually land, not months. Don't plan your compliance process around it arriving on any particular date.
The honest takeaway for 2026 is this. The burden right now sits with your process, not with hoping the data eventually catches up on its own.
Which vendor you use. Which search type you default to. Whether you build in a verification step before you act on an old-looking record. That's the part you actually control.