Common Background Check Mistakes Founders Must Avoid

A founder is ready to hire, the candidate seems strong, and someone says, "Let's just run the background check and make sure everything is fine." The room gets quiet for a second because everyone knows the check matters, but nobody is fully sure what they are allowed to do with the results.

That moment is more common than most leaders admit. Background checks feel like a simple safety step until the company has to decide what to ask for, how to interpret the results, and whether anything in the report should change the hiring decision.

Every background check should start with a business reason

Let's walk through this the way I would with a client. The first question is not which background check company to use. The first question is why you are running the check in the first place.

That may sound obvious, but this is where founders often get sideways. They want to be careful, so they ask for everything. Criminal history, credit history, driving records, education verification, employment verification, drug testing, and whatever else the vendor offers.

More information feels safer. In reality, more information creates more risk if the company has not connected the check to the role.

A background check should be tied to the job. If someone will drive for the company, a motor vehicle record may make sense. If someone will handle company funds, certain financial checks may be relevant depending on the role and applicable law. 

For many roles, the company does not need every possible report. It needs the information that helps confirm whether the person can safely and appropriately perform the job.

When I review this with companies, I often ask what decision they are trying to make with this information. If the answer is unclear, the check is probably too broad. 

Federal guidance from the Federal Trade Commission makes clear that employers using a third-party company for background reports must follow Fair Credit Reporting Act requirements, including disclosure, authorization, and specific steps if the report may affect the employment decision.

HR Tip: A background check should not be a fishing expedition. If you cannot explain why a particular screen is job-related, pause before including it.

Consent and timing are not small administrative details

This is something I see fairly often when businesses grow. A founder starts with informal hiring, then adds background checks as the company gets larger or enters more sensitive work. The intent is good. The process is where mistakes happen.

If you use a third-party background check company, you generally need to give the candidate a clear written disclosure and get written authorization before obtaining the report. The disclosure should not be buried inside a long application or pile of unrelated paperwork. 

That step matters because the candidate has rights in the process, and sloppy paperwork can turn a routine check into a compliance issue.

Timing matters too. Some companies run checks early before they have decided whether the person is a serious candidate. Others wait until after a conditional offer. The right timing depends on the jurisdiction, the role, and any state or local rules that apply.

Some states and cities have fair chance hiring rules that restrict when criminal history can be considered. Those rules vary, so a process that works in one location may not work in another. Do not treat background checks as a step that can happen whenever it feels convenient. Build a process and apply it consistently.

Most companies do not notice this until a candidate challenges the process or asks why they were screened differently from someone else. That is usually the moment leaders realize the issue was not the background check itself. It was the lack of structure around it.

Criminal history should be reviewed with context, not panic

Criminal history is one of the areas where founders can make fast decisions for the wrong reasons. A report comes back with a record and the immediate instinct is to move on.

The problem is that not every record is relevant to every job. A blanket rule that says "we do not hire anyone with a criminal record" can create legal and practical problems. The Equal Employment Opportunity Commission has explained that an employer's use of criminal history can violate Title VII if it results in discrimination based on protected characteristics such as race or national origin.

The review needs context. Consider the nature of the offense, how much time has passed, and how the record actually relates to the job. A year-old conviction unrelated to the role is not the same as a recent conviction directly tied to the position's responsibilities.

Someone applying for a warehouse role with an old, unrelated misdemeanor deserves a different conversation than a candidate applying for a finance role with a recent conviction involving financial misconduct. The point is not to ignore risk. The point is to evaluate the right risk for the right role.

HR Tip: The question is not simply "Did something come back?" The better question is whether the information is job-related, current enough to matter, and connected to a real business concern.

Founders often get adverse action wrong

This is usually where things get interesting. A background report comes back, the company decides not to move forward, and someone sends a quick email saying they are going with another applicant. That may feel efficient. It can also skip required steps.

If a third-party consumer report influences a negative employment decision, employers generally need to follow an adverse action process under the Fair Credit Reporting Act. Before taking final adverse action, the employer must provide a pre-adverse action notice, a copy of the report, and a summary of the candidate's rights. 

This gives the person a chance to review and dispute anything inaccurate before the final decision is made.

There is a moment when the company is considering a negative decision based on the report. Then there is the final decision. Those are not the same thing, and the candidate needs a meaningful opportunity to respond in between.

Background reports can contain errors. Records can be mismatched. Information can be outdated. A candidate may also have context that the company should consider. That does not mean the company must hire the person. It means the report should not be treated as the final word without following the proper process.

This is usually the moment founders pause and realize their background check process has been mostly vendor-driven. A vendor can provide tools, notices, and workflow support. The employer still owns the decision.

Consistency and judgment both matter at the end of the process

A background check process should be consistent across similar roles. That does not mean every role needs the same check. It means the company should be able to explain why different roles require different screens.

Driving record checks make sense for employees who drive as part of the job, not for someone who never drives for work. Credit-related checks may be relevant for a narrow finance role but not for a general administrative position. 

The more tailored the process is, the easier it is to defend. Consistency also helps prevent unconscious bias. If one candidate gets extra scrutiny and another does not, there needs to be a legitimate job-related reason for the difference.

Background reports should not be passed around casually. They often contain sensitive personal information, so access should be limited to the people who truly need it for the employment decision. 

When a report raises a concern, document what was reviewed, why it mattered to the role, and how the decision was made. Keep the notes factual and restrained. Write down the business reason, not a reaction.

This is also where leaders sometimes put too much weight on the report itself. They want certainty. They want the background check to say safe or unsafe, hire or do not hire. Real hiring is rarely that clean. 

A background check should sit inside a broader process that includes interviews, reference checks, and clear role expectations. The strongest employers do not make fear-based decisions. They make structured ones.

HR Tip: If you cannot explain the hiring decision using job-related reasons that have nothing to do with fear, the process probably needs more structure before the next offer goes out.

The HR Lens

After working through this with many growing companies, one pattern shows up consistently. Background checks become risky when leaders treat them as a yes-or-no tool instead of a decision-making process.

The issue usually appears as the company moves from informal hiring into more formal operations. With five employees, the founder may know everyone personally. At 25, the company starts adding a process. At 75, inconsistency starts showing up.

The moment companies usually realize there is a problem is not when every report comes back clean. It is when one report comes back with something uncomfortable, and leaders have to answer questions they have not prepared for. What matters for this role? Who reviews the report? Do we give the candidate a chance to respond? Are we treating this person the same way we treated others?

The underlying reason this keeps happening is that background checks feel operational, but they are tied to judgment, fairness, privacy, risk, and compliance. A better process gives leaders room to think clearly at the moments that matter most. It also protects candidates from being reduced to one line on a report.

Background checks should create clarity, not confusion. When the process is built before the problem appears, the decision is easier to make, easier to explain, and easier to stand behind.

What I'd Recommend if This Sounds Familiar

If you are reading this and realizing your background check process is more informal than you thought, that is common. Many companies add checks as they grow without building a decision process around them.

The best place to start is reviewing what you currently check for each role and why. Look at consent, timing, vendor forms, adverse action steps, criminal history review, documentation, and who has access to the results.

Every company's situation is a little different. Your industry, locations, job duties, and workforce structure can all affect what makes sense for your business.

If you want a second set of eyes on it, you can schedule a call with Brittney, and we can walk through your specific circumstances together. Sometimes the process only needs a few clean-up steps. Other times, it needs a more complete reset before the next hire.

Either way, the conversation does not need to be overwhelming. A good background check process is not about making hiring harder. It is about making sure the decisions you already need to make are clear, fair, and grounded in the role.

---

About Savvy HR Partner

Savvy HR Partner is an HR and payroll consulting firm that helps growing organizations build strong people operations. We specialize in HR strategy, compliance, employee relations, policy development, compensation guidance, and payroll support designed to scale with your business.

To learn more about our services, visit www.savvyhrpartner.com.

You can also follow Savvy HR Partner on LinkedIn, Facebook, and Instagram for practical HR insights and guidance for founders, leaders, and HR professionals.

If you are looking for HR support, you can schedule an appointment during HR Office Hours.