Most first-time background check mistakes aren't about picking the wrong provider. They're process mistakes: the wrong form, the wrong order, the wrong package for the job. Here are seven I saw over and over, and exactly how to fix each one.
I ran background checks for almost 30 years before I retired, and every one of these showed up more than once. None of them are hard to fix. They just dont happen in the right order, and that's usually enough to cause real trouble.
| Mistake | The fix |
|---|---|
| No standalone disclosure form | Give candidates a document that only discloses the check, nothing else |
| Skipping the adverse action steps | Send a pre-adverse notice, wait, then send the final notice |
| Screening before the offer | Check your state and city's ban-the-box timing rule first |
| One package for every job | Match the check to what the role actually involves |
| Ignoring look-back limits | Ask your provider what your state allows a report to include |
| Picking the cheapest provider | Compare accuracy and turnaround before price |
| No written decision policy | Write down how results get evaluated, then use it every time |
Federal law requires you to tell a candidate, in a standalone document, that you're going to run a background check. Not a line item in the job application. Not mixed into a liability waiver. Its own page, its own signature.
First-time employers mess this up constantly. They figure a mention in the offer letter covers it. It doesn't. Pull the disclosure out onto its own page, and don't put anything else on it.
If a report is going to cost someone the job, you don't just send a rejection email. Federal law requires two steps: a pre-adverse action notice with a copy of the report, then a wait, commonly practiced as around five business days though the law itself just says "reasonable," before the final notice goes out.
Skip that wait and you've skipped the candidate's real chance to say the report is wrong. That's the part that actually gets employers in trouble. Not the rejection itself.
A growing number of states and cities won't let you ask about criminal history, or run a background check, until after you've made a conditional job offer. Do it earlier, and you've broken the law there, even if the report never once factored into your decision.
This trips people up because it feels backwards. Checking early seems like it saves time. It doesn't. It just moves the risk onto you. Check your specific state and city's timing rule before you screen anyone, not after.
I've watched companies run the same "Comprehensive" package on a remote bookkeeper and a warehouse driver. That's wasted money on one of them and a real gap on the other.
Match the check to the job. Driving needs an MVR. Money needs a credit check where your state allows it. A desk job usually needs neither. Buying the biggest package because it sounds thorough isn't caution. It's guessing.
Federal law generally caps how far back certain records, like non-conviction arrests, can appear on a report: about seven years, with an exception for higher-paying roles. Several states set their own, often stricter, limits on top of that.
First-time employers assume a report shows someone's full history. It usually doesn't, and it isn't supposed to. Ask your provider what your specific state allows before you're confused by what's missing.
Price is the easiest thing to compare, so it's what first-time buyers sort by first. It's also close to the least useful number on its own. A cheap check that comes back slow, or wrong, can cost you the candidate you actually wanted.
Ask about turnaround time and dispute rate before you ask about price. A provider that costs a little more and gets it right the first time is definately worth it. A cheap one that's wrong is more trouble than it's worth.
Two candidates, the same kind of record, two different decisions, no explanation for the difference. That's how a fine hiring choice turns into a lawsuit.
Write down, in advance, how you'll weigh what shows up: how serious it was, how long ago, how closely it relates to the actual job. Then apply that same standard every single time, not just when it's convenient. Consistency is most of the defense.