Most things on a background check report aren't automatically disqualifying. Only a small handful genuinely are. Everything else deserves a real look before you say no, not just a quick scan for anything that seems bad.
That distinction trips up a lot of employers, especially ones doing this for the first time. A report lands in your inbox, something on it looks alarming, and the instinct is to reject on the spot. Sometimes that's the right call. But more often, it isn't. Let's go through both sides so you know which is which.
Three things belong here, and not much else does.
Identity fraud. The Social Security number doesn't trace back to the person, or the identity documents don't hold up. This isn't a record that needs interpreting. It means you don't actually know who you're hiring.
A conviction that's both severe and directly tied to the job. A theft conviction for someone who'd be handling company money. A violent offense for someone who'd work alone with vulnerable people. The offense and the job risk have to line up closely, not loosely, for this to count.
An active, disqualifying license issue. The job legally requires a license, and the current status comes back revoked, suspended, or doesn't exist at all. If the law itself says this person can't do the job, that's not a judgment call.
Notice what all three have in common. They go to whether the candidate is who they say they are, or whether the specific risk from what happened actually matches the specific risk of the role. That's a narrow bar. Most of what shows up on a report doesn't clear it.
I wrote a separate piece on the individualized assessment the EEOC expects for criminal convictions specifically. This is the shorter version. Before you treat any conviction as an automatic no, ask how severe it actually was, how long ago it happened, and how closely it relates to this specific job.
"Directly and severely related" is doing real work in that sentence up above. Not any conviction. Not an old one. One that's actually this serious and actually maps onto what could go wrong in this role. A ten-year-old shoplifting charge doesn't clear that bar for almost any job. A recent conviction for the exact kind of harm the role could enable does.
So even inside the deal-breaker category, you're still asking questions before you decide. That's not optional. It's what keeps a real reason to reject from turning into a blanket policy a court reads as discrimination, whether you meant it that way or not.
These four show up constantly, and none of them should end a candidate's chances by themselves.
Look at that list again. None of these tell you the candidate is dishonest or dangerous. They tell you a report came back incomplete, or that something happened a while ago and the person moved on. And those two things aren't the same, even though they can look similar at a glance.
It's simpler than it sounds. Go back to the candidate before you finalize anything, and let them respond to the specific item. Write down what they said and what you decided, every time, not just when the call feels close.
Apply the same process to everyone in the same situation. If one candidate with a decade-old conviction gets a real conversation and another gets an automatic rejection, that inconsistency is its own legal exposure, separate from whatever the record actually says.
I'm not a lawyer, and I'm not handing you a state-by-state list here and calling it final. Some states add their own rules on top of the federal baseline, like limits on how far back a conviction counts. Check your state's current law, or talk to one, before you build a policy around this article.
Here's the habit that actually protects you. Treat the report as the start of the conversation, not the end of it. The three real deal-breakers are rare enough that most reports won't have one. Everything else is asking you to look twice before you decide. That part's not optional either.