Background checks seem to be an easy task for the majority of employers. They conduct a check, receive a result, and proceed with the hire. However, the truth is that lawsuits arise from the discrepancies between the processes of background screening and the perception that most organizations have regarding these processes.
The stakes Are higher than most HR teams realize
Almost 94% of employers conduct pre-employment background screening (Professional Background Screening Association / HR.com). That’s almost universal – and it also means regulators have a huge pool to fish from when they’re looking for enforcement actions. The Fair Credit Reporting Act, EEOC guidance, and a growing pile of state and local laws combine into a compliance landscape that’s all too easy to misunderstand. But getting it wrong doesn’t mean you’ll just get your hand slapped. It means class-action litigation, negligent hiring claims, and discrimination suits that hurt.
These seven common mistakes – along with two more slippery errors that those with deep HR experience sometimes fall into – are the ones we see time and again in the cases that go bad.
Misconception 1: Instant database searches are complete and compliant
There are services that will return a criminal background result in seconds for a few bucks. You see a clean result and off you go. The issue is those instant searches are drawing on aggregated databases that were built by scraping the web of possible criminal record hits – not by directly searching official county-level courthouse records. Specifically, it’s the official courthouse records that the FCRA says you’re supposed to be searching.
In addition to that, the FCRA requires that consumer reporting agencies “follow reasonable procedures to assure maximum possible accuracy”. A database that doesn’t verify its findings against courthouse records doesn’t meet that standard. You also shouldn’t base a negative employment decision on the results of a database that is out of date. Or that misses entire jurisdictions. Or that is riddled with mistakes.
To avoid those violations and get results that hold up legally, employers need to work with an accredited CRA like Direct Screening that conducts verified county-level searches and uses multi-jurisdictional results only as a locator tool, not the final answer.
Misconception 2: A clean national check means no criminal record exists
There is no single national criminal registry. None. The FBI maintains records, but employers can’t access them directly for civil employment purposes. What’s commonly sold as a “national criminal background check” is actually a search across a patchwork of state and commercial databases – useful for flagging potential hits that need follow-up, but nowhere near complete on its own.
Most criminal records live at the county court level. If a person was charged, prosecuted, or convicted in a county that doesn’t report to state repositories consistently – or at all – that record won’t show up in a national database search. A candidate can walk through a national check looking completely clean and still have a conviction sitting in a county courthouse a few states over. The only way to surface those records is to run manual county court searches in every jurisdiction where the candidate has lived or worked.
Misconception 3: Ban the Box laws eliminated background checks
This misconception arises from misinterpreting the actual implementation of Ban the Box. These laws do not ban criminal history inquiries; they establish guidelines for when those inquiries can be made. In practice, most stipulate that employers cannot ask about criminal history on the initial application and must wait until after extending a conditional offer of employment before doing so. Or at the very least, until after the first interview.
The goal is to ensure that candidates are considered on their merits rather than being summarily dismissed for an entry in their criminal history. The result, on the employer’s side, is that you’re effectively shifting the criminal background check from the application-review phase to the post-offer stage. Many employers have found this pretty manageable to adjust to and have even discovered that the quality of their hires has increased because the focus is on qualifications first.
Misconception 4: A blanket “no felony” policy is legal and defensible
It isn’t. The EEOC has been explicit on this: categorical exclusions based on criminal history violate Title VII of the Civil Rights Act of 1964 when they produce a disparate impact on protected classes – and they almost always do.
What employers are required to do instead is conduct an individualized assessment. That means looking at the nature and gravity of the offense, how much time has passed, and whether that specific offense is directly related to the specific duties of the job. A DUI in someone’s past doesn’t automatically disqualify them from a desk job. A fraud conviction might be highly relevant to a financial role while being irrelevant to a warehouse position. The assessment has to be specific to the person and the role, not applied as a blanket rule.
This doesn’t mean employers have no ability to decline candidates with certain criminal histories. It means you have to do the work of evaluating each situation rather than applying a policy that eliminates an entire population.
Misconception 5: Telling a candidate verbally that they didn’t pass is legally sufficient
One of the most mishandled parts of the background check process and one of the biggest generators of FCRA litigation is that when a background check finding is going to go into your decision not to hire someone, there’s a mandatory two-step process.
You have to do the notice of pre-adverse action. Before you make your final decision, you have to send the candidate a copy of the background check report, a written notice that you’re considering not hiring them based on the findings, and a document called “A Summary of Your Rights Under the FCRA.” This puts the candidate on notice and gives them a chance to review the report and dispute inaccuracies.
Then you wait. The candidate must receive a reasonable amount of time to respond – at least five business days would likely be considered reasonable, with some legal guidance suggesting longer. Only after that window has passed can you send the final adverse action notice, which is the formal notice communicating that you’ve decided not to proceed.
Skip it, shortcut it, or have a verbal conversation in its place and you will get sued. Those cases tend to go as class actions because the same procedural violations tend to be applied consistently across multiple candidates.
Misconception 6: You can look back as far as you want into someone’s history
Federal FCRA rules restrict the reporting of non-conviction arrests to seven years. Convictions can typically be reported indefinitely at the federal level; however, many states have adopted more stringent regulations and limit all criminal record reporting to seven years, regardless of conviction status, and some do so regardless of salary or position.
As a result, a background check process that is legal in one state might violate consumer protection law in another. In an ever more mobile workforce, employers with operations in multiple jurisdictions must appreciate that their screening policy must comply with the most stringent applicable rules wherever a candidate lives and where the job is located.
Misconception 7: Arrests and convictions are legally equivalent
An arrest is an accusation. It is not a piece of evidence that someone is guilty. Denying employment to someone solely based on an arrest record goes against EEOC guidelines under Title VII. It is considered discriminatory because arrest rates differ widely among demographic groups, meaning that using arrest records to exclude potential employees would have the same effect as basing a decision on an obviously biased policy.
There’s a narrow carve-out – if an employer has independent evidence of the underlying conduct that the arrest relates to, that evidence might be considered in an individualized assessment. But the arrest itself, without more, can’t be the basis for a hiring decision.
Misconception 8: Social media searches are a free, low-risk alternative
Some employers rely on a quick Google search and LinkedIn review to take the place of an actual background check. Not only is this insufficient, but it also poses a risk. When you look up a candidate online, you will likely come across details relating to protected characteristics – such as their age, religion, race, disability status, family circumstances, or political affiliation. If you view that information and the candidate is not hired, you could be setting yourself up for a difficult-to-defend failure-to-hire discrimination claim.
Formal background screening through a compliant CRA keeps that information out of the decision-making process until and unless it’s legally relevant.
Misconception 9: US background checks catch international criminal history
They don’t. Domestic searches don’t cross borders. A candidate who spent five years working or studying in another country and has a criminal record there won’t have that record surface in any US county court search or national database. International screening requires separate protocols, and those protocols have to comply with the data privacy laws of whatever countries are involved – including regulations like GDPR in Europe, which impose strict rules on what can be collected, from whom, and how it can be used.
For roles that require trust, access to vulnerable populations, or significant financial responsibility, international screening isn’t optional for candidates with overseas histories.
Background screening done right protects companies from two directions at once: negligent hiring claims that come from not screening carefully enough, and compliance lawsuits that come from screening in legally impermissible ways. The companies that get this right treat it as a process that’s designed and managed, not a checkbox that gets clicked. The gap between those two approaches is where most of these misconceptions do their damage.
