Skip forward into hiring notes
RosterAcorn

3 purposes for each pre-hire background check you order

Every pre-hire background check you order serves three distinct purposes. Knowing which one drives your decision protects your company from costly mistakes.

  • Confirm qualifications and eligibility: verify that the resume matches the record.
  • Mitigate risk you can name: identify the specific harm a record could cause in this role.
  • Comply with rules that apply to you: run required checks because a law or regulation demands it.
  • Keep the three purposes separate so you can explain your decision later.
  • Write one sentence naming the role, the record, and their connection before sending any rejection.

Why you order a screen before you make an offer

A background check is not one thing. It is a process. Checkr defines it plainly: a background check "is the process of examining public and private sources to collect and review information about an individual." You are pulling records that already exist. You are not investigating a person's character. You are reading what institutions have already written down.

When you order a screen for a person you are considering hiring, you are doing three jobs at once, even if you have never named them. First, you are confirming that the person can do the work. Second, you are protecting your company from a risk you can see coming. Third, you are meeting a rule that applies to your industry or your state.

The trouble starts when you blend them. A hiring manager who only cares about risk will reject a strong applicant over an old, minor record. A recruiter who only cares about credentials will skip a check that a regulator requires. Keeping the three purposes separate is the difference between a defensible hiring process and a messy one.

Purpose one: confirm qualifications and eligibility

The first purpose is confirmation. Checkr lists it first when it explains why employers screen: background checks are "commonly used to confirm an individual's qualifications and eligibility for a role; mitigate risk; and comply with industry regulations." Confirmation comes first because it is the simplest of the three. You are checking that the resume matches the record.

A resume is a claim. A verification is a check against a source that does not care about how the person told the story. Employment verification compares what the applicant told you about past jobs against what those employers will confirm. Checkr describes its own verification work as something that helps you "scale screenings, reduce administrative work, and get accurate results faster," whether you are checking one person or hundreds. When verification is routine, you can run it on every hire instead of guessing which roles need it.

Qualification checks also cover education, licenses, and professional certifications. If the job requires a specific license, you are confirming that the license exists, is current, and has not been suspended. This is not a judgment call. Either the credential is there or it is not.

Eligibility is a narrower cousin of qualification. It answers whether the person is legally allowed to work in the role you are filling. Some roles carry additional eligibility requirements written into the job itself.

The first purpose fails when you treat it as optional for senior roles. A director-level hire who inflates a degree or a title will manage a team you assembled. Verification at that level is quality control on your own org chart. It also fails when you skip it for junior roles because "we will know quickly." Bad hires at the entry level still cost you training time, team trust, and a second recruiting cycle.

What confirmation asks of you

  • Decide, before you post the job, which qualifications the role actually requires.
  • Verify each one against a source, not against the applicant's own paperwork.
  • Keep the verification result separate from your risk assessment. They answer different questions.
  • Run the same checks at every level of the company so exceptions do not creep in.

Purpose two: mitigate risk you can name

The second purpose is risk. Checkr lists it directly: background checks "mitigate risk." Risk is not a vague fear. It is a specific harm you are trying to avoid, and you can usually name it before you order the check.

Risk shows up in different forms depending on the role. A person handling money can create financial exposure. A person driving a company vehicle can create safety exposure. A person working with vulnerable populations can create trust exposure. A person with access to systems can create data exposure. Each of these is a concrete thing you can describe in a sentence to your legal team.

The discipline is naming the risk before you see the record. If you cannot say, in advance, what specific harm a particular record type would cause in this particular role, you are not mitigating risk. You are reacting to a record. That distinction matters because it is the difference between a policy and a preference.

Wisconsin's statute on conviction records shows how the law thinks about this. The statute treats certain refusals as employment discrimination, and it carves out exceptions. One provision reads: "It is employment discrimination because of conviction record for a licensing agency to refuse to license any individual..." The statute also states that certain bars and terminations "do not apply if a conviction is for an exempt offense." The law is telling you that not every conviction should block an opportunity. Your risk process should read the same way: relevant, current, and connected to the work.

Risk mitigation also has a documentation side. If you reject an applicant based on a record, you should be able to explain, in writing, why that record connects to a specific risk in that specific role. A hiring manager who cannot write that sentence has not mitigated risk.

Risk is a question you ask before you see the answer

Ask yourself, before ordering any screen: what specific harm would this record type cause in this role? If you cannot name the harm, the check is not serving the risk purpose. It may still serve the compliance purpose, but do not pretend it is risk work.

This is also where talking to the person you are considering gets honest. When a record surfaces and you are considering it, you should be able to tell that person what you are worried about. "We are concerned about X because this role involves Y" is a conversation. "We found something" is a threat.

Purpose three: comply with rules that apply to you

The third purpose is compliance. Checkr's list ends with it: background checks help employers "comply with industry regulations." Compliance is the purpose with the least flexibility. You do not get to weigh it against cost or convenience. If a rule applies to your role, you run the check.

Compliance shows up in three layers. Industry rules add requirements for specific sectors. State and local rules add requirements for specific places. Your job is knowing which layers apply to the role you are filling, then running the checks those layers require.

The Federal Trade Commission publishes guidance for employers on using consumer reports. The FTC's business guidance page invites you to "Find the resources you need to understand how consumer protection law impacts your business." That is the entry point for the federal layer. Read it before you build your process, not after a complaint.

State rules vary, and the Wisconsin statute is a useful example of how a state frames the issue. Wisconsin's law addresses conviction records in licensing and employment, and it distinguishes between offenses. It provides that certain provisions "do not apply if a conviction is for an exempt offense." Some records are relevant, some are not, and the exemptions are written into the statute.

Your compliance purpose is not to interpret the law yourself. It is to know which laws apply, run the checks those laws require, and document that you ran them. When you are unsure which layer applies to a role, ask your counsel before you post the job.

Table: the three purposes at a glance

PurposeWhat it asksWhat a pass looks like What a fail means
Confirm qualifications and eligibilityDoes the record match the claim?Credentials verified, license current Reconsider the candidacy on merit
Mitigate risk you can nameWould this record cause a specific harm here?Named risk does not apply or is not current Reassess fit for this role only
Comply with rules that apply to youDoes a law or regulation require this check?Required check completed and documented You are out of compliance

Each purpose has a different definition of success and a different meaning of failure. Running all three in one undifferentiated screen is how you end up unable to explain your own decision.

Where the three purposes overlap and where they collide

The three purposes overlap most on the compliance side. Compliance checks often confirm qualifications at the same time. A license verification satisfies both the confirmation purpose and the compliance purpose in one step. That efficiency is real.

The collision happens between risk and compliance. Compliance says run the check. Risk says weigh the result. Those two instructions can pull in opposite directions. A regulation may require you to look at a record. Your risk analysis may conclude the record does not connect to any harm this role can cause. You still have to run the check because compliance demanded it, but consult counsel on whether the result can be considered.

This is the point where most hiring processes break. Teams either reject on compliance alone, which creates legal exposure, or they ignore compliance entirely, which creates regulatory exposure. The workable path is to run every required check, then evaluate the results through your named-risk lens, then document both steps separately.

Wisconsin's statute distinguishes exempt from non-exempt offenses. The statute distinguishes exempt offenses from non-exempt ones, which means the law itself does not treat all records the same. Run the check. Classify the result. Apply your named risk to every result, noting which records fall under an exemption. Document the classification.

Another collision shows up between confirmation and risk. An applicant may fully confirm their qualifications and still present a risk you care about. Or an applicant may have a record that looks risky but their qualifications are impeccable. Collapsing these two into one score is how you lose the ability to explain your decision later.

The sentence you should be able to write

For any rejection that touches a record, you should be able to write one sentence that names the role, the record, and the connection between them. If you cannot write it, you are not ready to send the rejection. That sentence is also what your legal team will ask for if the decision is ever challenged.

Writing the sentence before you decide is a useful discipline. It forces the three purposes apart. It shows you whether you are confirming, mitigating, or complying. And it turns a vague discomfort into a claim someone else can review.

How to explain each purpose to an applicant

Applicants ask you why you are running a check. They are entitled to a clear answer, and the three purposes give you three clear answers.

For confirmation, you say you are verifying the qualifications the job requires. The applicant told you something about their background. You are checking it against a source. It is how hiring works.

For compliance, you say a rule applies to this role and the check is part of meeting that rule. If an applicant asks and you cannot name the rule, that is a signal your process needs work before your next hire.

For risk, you say you are looking at whether a specific record connects to a specific part of the work. This is the hardest conversation. The fumble happens when the answer is vague. "We found something" tells the applicant nothing and invites a dispute. "This role involves X, and this record suggests a concern about X" tells the applicant exactly what you are weighing.

The applicant may have context you do not. A record may be older than it looks, resolved in a way the source does not show, or unrelated to the work you are worried about. Giving the applicant a chance to respond is how you avoid rejecting someone over a misunderstanding of your own record.

You are sharing the concern, inviting context, and then deciding.

Questions applicants actually ask

Why do you need my past employers' contact information? Because you are confirming the work history the applicant described. Verification compares the resume against what those employers will confirm. It is a confirmation purpose check, not a risk check.

Will an old conviction disqualify me? The honest answer depends on the role and on the law that applies. Wisconsin's statute, for example, provides that certain provisions "do not apply if a conviction is for an exempt offense." Tell the applicant you evaluate relevance to the specific role, and that exemptions may apply.

How long does the check take? You should answer with your own timeline, not a vendor's marketing claim. If you have not set a timeline, set one before the next person asks.

Can I see what you found? The rules around what you must share and when depend on the kind of report and the law that applies. Read it, know your obligations, and tell the person you will share what and when.

Does everyone get the same checks? They should. Running different checks for different applicants, without a role-based reason, is how you build an inconsistent process. Role-based differences are defensible. Differences based on the individual need a documented, role-based reason, and you should check with counsel before adopting them.

What happens if the check comes back with something? Tell them the truth: you will review it against the role's requirements and the named risk, you will give them a chance to respond, and you will document the decision. A process the person being screened can predict is a process they will trust.

Building a process that holds all three purposes

A hiring process that holds all three purposes has a few properties. It is role-based. It is documented. It separates the checks from the evaluation. And it has an owner who can explain any part of it.

Role-based means the checks follow the job, not the person. Two applicants for the same role get the same checks. Two roles with different requirements get different checks. The difference is written down before either role is posted.

Documented means you can reconstruct any decision months later. What you ran, what it showed, what you concluded, and why. That record protects you if an applicant disputes the outcome, and it protects you if a regulator asks how you handle a category of check.

Separated means the check and the evaluation are two steps. The vendor runs the check. Your team evaluates the result against the named risk and the applicable rules. Merging those steps into one number, one score, or one red flag destroys the ability to explain yourself.

Owned means one person in your company can answer questions about the process without escalating. When that person is on leave, the process should still work. If it does not, you have a key-person risk in your hiring pipeline.

What to fix first

If your current process is muddled, start by naming the purpose of each check you already run. For every check on your list, write one line: this check serves confirmation, or risk, or compliance. Any check you cannot assign a purpose to should be reconsidered for removal. Any purpose with no check assigned to it is a gap you should close.

That exercise usually produces two surprises. First, some checks you assumed were compliance turn out to have no rule behind them. They are habits, not requirements. Second, some roles you assumed were simple turn out to need a check you never run. Both surprises are cheaper to find now than after your next bad hire or your next audit.

Then write the sentence for each rejection. Then set the timeline you quote to applicants. Then read the FTC's guidance once, start to finish, and write down what applies to you. These small steps add up to a process you can defend.

Related guides: Minor hire pay and breaks: 4 checks before posting · New hire pay: 5 checks before the first paycheck · Noncompete checks before a new hire signs: 3 points.

Frequently asked questions

What is the difference between a background check and a consumer report? A background check is the general process of collecting and reviewing information about a person from public and private sources. The FTC publishes guidance for employers on using consumer reports, and that guidance is where you learn which rules attach to the report you are ordering.

Do I need to run all three purposes on every hire? No. Compliance checks are required only when a rule applies to the role. Confirmation checks should run on every hire because verified qualifications protect your hiring quality. Risk checks should run wherever you can name a specific harm the record could cause in that specific role. The mix is a role decision, not a company-wide default.

Who decides whether a record is relevant? Your team decides, guided by the law that applies to the role. Wisconsin's statute provides that certain provisions do not apply to exempt offenses, which shows that the law distinguishes between offense types. If your team cannot classify a record, ask your counsel before you decide.

What should I say if an applicant asks why a check failed? Tell them the role, the concern, and the connection between them. If you cannot name all three, the check has not earned a rejection. The applicant deserves a specific answer, and you deserve a decision you can write down in one sentence.

Is there a part of this your sources do not settle? Yes. Your sources do not tell you which specific checks your particular roles require. That answer depends on your industry and your location. Ask your legal counsel which rules apply to each role before you post the job.

How do I keep the three purposes from blurring again? Keep separate columns in your notes for confirmation, risk, and compliance. Review a sample of decisions each quarter against those columns. Blurring happens slowly, and a quarterly look is usually enough to catch it before it becomes your default.

Sources