The Anatomy of a Modern Background Check: Understanding the Different Levels of Employee Screening

The “result” of a background check isn’t a fact. It’s a pointer. The database hit comes quickly, but it doesn’t do your due diligence for you. The only effective way to screen out false positives and screen in the right candidates is to measure the database hit against real-world information you already know about an applicant. Is this the right Jane Doe? Does she have the right record? Was the case fully resolved by the justice system, or does she have more recent convictions that should concern you? Does this really belong to your candidate, or is there another Jane Doe in her zip code with a criminal record you just missed?

Identity comes before anything else

To make sure any criminal search is accurate, you need to go through a couple of steps first. The first is obvious (but gets skipped a lot): you must confirm who it is you’re actually looking for. A social security trace can help with this. It tells you if the number is valid and to whom it belongs. Most importantly – that map of previous addresses is a roadmap of where to search for records. Criminal checks are just more guesses without it.

County court records are the bedrock

Most criminal cases are filed and adjudicated at the county level. This makes county court record searches the best layer of any screening program, as they access the most up-to-date primary source information.

The issue is that with county searches, you only get information from one county. So if your applicant has lived in four counties across two states, you would need to run four county searches based on the address history report we mentioned above. If you miss one, you miss a record. For those of you who like the nitty-gritty, running down courthouse records one at a time is how background checks used to work in the old days. It’s slow. It’s manual in many courthouses to this day. And it’s why turnaround times can be as quick as a few hours and as long as a few days. This is also the way to prove you have taken “reasonable care” in that court- and regulator-facing policy we mentioned above.

National database sweeps fill the gap, but they need a second look

County searches – the ones you’re strongly advised to run in combination with a national database check – are the opposite of that. They’re hands-on, in-depth, checked-and-double-checked, and locally updated as recently as the local courts’ files were last updated. But they’re not getting some of that stuff a national database just spat back at you. They’re not set up to. They don’t overlap counties, let alone states. They don’t cover a whole year if the local sheriff’s office just switched from dusty ledger books to a cloud database last August. They read one local record set. But they read it well.

That’s where broader database sweeps earn their place. Multi-state aggregated databases can flag records across dozens of jurisdictions in seconds, catching things a county-by-county search might miss entirely – an out-of-state conviction, a prior alias, a record from a state the candidate never mentioned living in. The tradeoff is accuracy. These databases mostly match on name and date of birth, sometimes SSN, and they’re compiled from whatever data sources agreed to share information, updated on whatever schedule those sources chose. False positives happen. Common names collide. Records go stale. This is exactly why national criminal background checks work best as a discovery tool rather than a final answer: they tell you where to look next, and every hit needs to be validated against the primary-source record before it factors into a hiring decision. Treating a database flag as confirmed fact is how employers end up rejecting the wrong person – and how they end up on the wrong side of a defamation claim.

Statewide repositories: better than nothing, not a substitute

Between the county layer and the national layer is the state repository – a state-level database that collects court records from sources within its own borders. In principle, this should be a clean, single-search answer for statewide coverage.

In practice, it’s messy. States vary widely in how frequently they aggregate and update these repositories. Many are weeks or months behind on updates with local sources. Some counties report religiously; for others, the state repository is the only place they send data. And for others still, especially more remote or rural areas, this is the only place where data is recorded at all. Data on what actually happened to a charge (whether it was dismissed, reduced, or resulted in a conviction) rarely makes it out of the county. A statewide search is a middle layer for figuring out where to look – it is not a perfect criminal history.

Federal records live in a separate world entirely

Here’s the step that causes headaches for a lot of screening programs: federal crimes don’t appear in any county or state search, ever. Wire fraud, drug trafficking across state lines, some white-collar offenses, certain tax crimes, federal mail fraud – that’s a federal case, and it’s adjudicated in federal district court, which maintains its own separate national courthouse record system.

If your screen doesn’t reach federal district court, you could hire a federally convicted fraudster and never know it, because you were looking in the wrong courthouse. The federal district court search isn’t a nice-to-have, third layer. It’s a mandatory fourth layer whenever the role involves money, access to sensitive information, or any reasonably construed fiduciary obligation to the organization. For some employers, after this fed search, you go a step further and request a fingerprint-based FBI check, which confirms identity biometrically rather than by name matching. Slower, more invasive, it’s reserved for positions where the stakes justify it – licensed health care employees, financial services, highly sensitive government-adjacent positions.

The criminal check is only part of the picture

A background check gives you legal history – it doesn’t confirm a degree, a job, or a professional license. People lie about those all the time. In 2017, CareerBuilder’s annual background screening survey reported that 75% of HR managers had caught a lie on a resume. The month before the survey, in August 2017, the Financial Industry Regulatory Authority fined Wells Fargo Advisors $3.4 million for falsely certifying that 73 of their registered reps had completed their training. 58% of employers surveyed by CareerBuilder said they’d calculate a bad hire cost them $15,000 or more, once you figure in the direct and the indirect expenses. Skimping on education, employment, and professional license verification because the background check is back is just that – skimping, not efficiency. Resumé fraud is an Achilles Heel. Administrative overload across a large applicant pool isn’t a reason to cut corners. That’s false economy.

Verification has to end somewhere – and that’s the adverse action process

After you have obtained layered, verified results, the FCRA (Fair Credit Reporting Act) has a specific sequence of steps that you have to follow before you rely on that information. This part isn’t optional, it isn’t negotiable, and a cookie might help it go down easier. If a report could result in a “no,” the applicant first gets a pre-adverse action notice, a copy of the report, and a summary of their rights. Then you’re looking at a reasonable waiting period to give them a chance to dispute anything. Only after that window has closed can you send a final adverse action notice and wish them the best of luck.

Layer on top of that the EEOC’s (Equal Employment Opportunity Commission) guidance that flat rules against hiring anyone with a record are problematic; they expect an individualized analysis and a determination of the nature of the offense, how long ago it occurred, and whether it relates to the position. Ban the Box laws in over 35 states push this concept even further by limiting when you can inquire about criminal history in the process. None of this is legal advice, but the common thread is: you’re on pretty firm ground generally when you have documentation showing that you fairly looked at each applicant in turn.

Layering is the liability strategy, not just a compliance checkbox

Employers can avoid liability under the negligent hiring doctrine when they can demonstrate a good faith effort to determine a new hire’s fitness for a position. A background check is the most common tool, with 95% of employers using some form of pre-employment screening according to industry surveys. But not all checks are equally defensible when they’re made the subject of a lawsuit. A quick vendor scan of a small database? A day’s county criminal records dump? A single identity verification? They lack rigor and validity, and they won’t look so hot in legal discovery.

More organizations are also adopting continuous screening, re-checking current employees on a regular schedule rather than treating the pre-hire check as a one-time event. People’s records change after they’re hired. A clean check on day one doesn’t guarantee anything about year three. Clients, insurers, and increasingly courts are starting to expect this kind of ongoing diligence, not just a single point-in-time report filed away and forgotten.

A background check result is cheap and fast to get. A verified, layered, properly documented screening process is what actually stands up when it matters – to a candidate who disputes a finding, to a regulator, or to a courtroom asking what a reasonable employer should have known.