Databases are copies, not the source

Commercial Databases vs. Official Court Records: What Employers Need to Know

A criminal background report that takes three days to generate and not three hours, isn't faulty. At least not in most cases. It means that the screener encountered a discrepancy between database information and courthouse records, and took the time to resolve it before sending you a report you'd base a hiring decision on.

This database-courthouse disconnect is what's behind the "turnaround time". These are the top five differences that explain it:

Commercial databases don't generate records. They compile them from thousands of different court systems and put them in one, easily searchable location. This is helpful, except every database record is a derivative of something that exists elsewhere.

There's more than 10,000 state and local court jurisdictions throughout the country, each with their own independent, proprietary systems (National Center for State Courts). No vendor is able to pull from all of them in real-time. The clerk of courts in each county is still the sole source of truth for what was filed in a case. A database can tell you where a record is. It can't verify a record.

Refresh cycles create built-in lag

As soon as a courthouse clerk processes it, a new charge, hearing or dismissal is entered into the court docket. That's not how it works with a commercial database. A database can only update what it pulls, and it typically only pulls on a scheduled batch cycle, either weekly, monthly, or however the jurisdiction's agreement with the vendor requires.

So a recent arrest, (or recent dismissal) may still be in the courthouse for a few weeks before it shows up on any database. If a screener doesn't report back to a client until they're able to pull a database – whether because that's their firm's policy, or they've been told that's the only way to be cost-efficient – the client is working with old information. A day or two wait to check the actual docket isn't time-wastage, but rather a way to prevent you from reporting something that no longer holds true.

The disposition gap is where most delays happen

A database may indicate that someone was arrested, but may not have any information about what happened after the arrest. Details like convictions, dismissals, acquittals and diversion resolutions are often not included in a database, since cases may not have immediately resulted in a disposition after the arrest was entered.

These are the most important details, and reporting an arrest without knowing the final outcome could be unfair and damaging to the individual. This is why professional background checks use the database as a pointer and then contact the individual courthouses directly to verify what actually happened in the case. In this way, an arrest that eventually resulted in a dismissal won't be treated as though it resulted in a conviction.

Name-based matching creates false positives

There's no national identifier that unites public records the way a fingerprint or case number would, so most systems do a match on name and date of birth. For common names, that means generating multiple candidates for the same hit, and someone has to manually determine which record, if any, rightly belongs to the person being screened.

Get this wrong, and you've either cleared someone you shouldn't have, or flagged someone who's never had a record in their life. Neither is an acceptable outcome under the Fair Credit Reporting Act, which holds consumer reporting agencies to certain accuracy standards. Sorting out a name collision takes time, but is the difference between a report you can trust and one you can't.

Sealed and expunged records don't disappear on schedule

When a record is sealed or expunged by law, the court essentially erases it from public view. This can take some time to filter through all the commercial databases. An entry cached in a vendor's system may still be public long after the legal right to report it has been rescinded.

Reporting a sealed record isn't a technical slip, but a compliance problem with real consequences. Verifying a given sealing or expungement takes an extra step in the process but is the one that ensures your search is legal rather than just quick.

Slower is often the sign it's working

When you put these five differences side-by-side, a pattern emerges. Any point at which a check takes longer than expected, is a point at which a response from the database was actually questioned, rather than presumed. Questioned hits are not reported as clean – they're sent back to the courthouse for a real answer.

This isn't a bug with the system. This is the system working exactly as the Fair Credit Reporting Act intended: verify before you report. A fast result pulled straight from a database may look clean. The slower one that's been checked against the actual docket is the one that you'd be willing to defend in court.