Negligent hiring is a legal theory that an employer can be held responsible when it placed someone in a role without reasonably looking into risks that turned out to be relevant to that job, and the employer knew or should have known about those risks. It is one of the main reasons employers run background checks in the first place. Negligent hiring is a matter of state common law, so the exact standard, and whether a court would find liability in any given case, varies by state and depends on the specific facts.
What “negligent hiring” actually means
Negligent hiring claims generally come up after an employee harms a customer, coworker, or member of the public, and the injured party argues the employer should never have hired that person for that role in the first place. The claim is not about the employee’s conduct alone. It is about whether the employer’s hiring process was reasonable given what the job involved.
Courts weighing these claims typically look at questions like: What did the employer know, or what could it have reasonably found out, before making the hire? Did the role involve access to people, money, vehicles, or property that made certain risks foreseeable? Did the employer have a process for checking on that, and did it follow that process consistently? Because this is common law that developed state by state, the specific elements of a negligent hiring claim, and how much weight a screening step carries as a defense, differ by jurisdiction. Nothing here should be read as a statement of the law in any particular state.
What “relevant to the role” means
The theory does not ask employers to uncover everything about a candidate’s past. It asks whether the employer looked into risks that reasonably relate to the job the person is being hired to do. A few examples of how that connection typically gets drawn:
- A role that requires driving a company vehicle raises questions about a candidate’s driving record, which is why employers in transportation and delivery often run a motor vehicle report alongside a broader background check.
- A role with unsupervised access to a customer’s home, a patient, or a child raises different questions than an entry-level warehouse role with no public contact.
- A role handling money or sensitive financial data raises questions distinct from a role with no financial access at all.
This is the “relevant to the role” test in practice: the screening effort should be reasonably tied to what the position actually does, not applied as a one-size-fits-all filter across every job in the company.
Why blanket exclusions are the wrong answer
A natural instinct is to set a single rule, such as automatically rejecting anyone with any criminal record, and apply it to every applicant regardless of role. The Equal Employment Opportunity Commission has explained why that approach creates its own exposure. EEOC guidance describes an individualized assessment that looks at factors including the nature and gravity of the offense, the time that has passed since the offense or completion of the sentence, and the nature of the specific job held or sought, and it states that “a policy or practice requiring an automatic, across-the-board exclusion from all employment opportunities because of any criminal record” is inconsistent with that analysis.
In other words, an automatic exclusion policy can create the exact opposite problem an employer is trying to avoid. Instead of managing risk, a blanket rule can expose a company to a different kind of legal claim, because it treats every offense and every job the same way instead of asking whether a specific record is actually relevant to a specific role.
That is why individualized assessment matters. It means giving a candidate the chance to provide context, and weighing the offense against the actual duties of the position, rather than letting a single data point make the decision automatically. Reveal Background never determines eligibility. Reporting the information and applying it to a hiring decision are two different steps, and the second one belongs to the employer, ideally supported by a documented, consistently applied policy and, where relevant, legal counsel.
Where a written, consistent screening policy fits
A written policy that describes what gets checked for which roles, and why, does two things at once. It helps the organization apply the same standard to every candidate in a similar role, which supports the individualized, job-related approach the EEOC guidance describes. And it gives the organization a documented, defensible answer to the question a negligent hiring claim eventually asks: what did you do to look into this, and was it reasonable for this job?
A policy typically covers which positions require which types of checks (criminal history, employment verification, education verification, driving records, professional license checks), how results are reviewed, who makes the final call, and how the process stays consistent across candidates in the same role. Industries with heightened foreseeable-risk roles, such as staffing agencies placing workers into client worksites, tend to formalize this earliest, because the agency is making a placement decision on behalf of another business.
Where documented screening fits into the process
A background check does not decide whether someone is safe to hire, and it does not guarantee that a workplace incident will never happen. What it does is give an employer documented, verified information about a candidate that is relevant to the role, obtained through a consistent process applied to every candidate in a similar position. That combination, relevance to the job plus consistency across candidates, is what turns screening from a checkbox into a genuine part of risk management.
Employers still need written authorization and a standalone disclosure from the candidate before ordering a consumer report for employment purposes, and if the information in a report leads toward a decision not to hire, the pre-adverse action step (notice, a copy of the report, and a copy of the Summary of Rights, followed by a reasonable waiting period before any final notice) is part of that process under federal law. Reveal Background supports employers through that consistent process. It does not replace an employer’s own judgment or its legal counsel’s advice about a specific candidate or a specific state’s requirements.
How screening scope typically maps to role risk
| Role type | Foreseeable risk factors | Screening elements commonly relevant |
|---|---|---|
| Delivery or field service | Operating a vehicle, entering customer property | Motor vehicle record, criminal history relevant to the role |
| Healthcare or in-home care | Unsupervised contact with patients or vulnerable people | Criminal history, license verification, healthcare sanctions checks |
| Financial or back-office | Access to funds or sensitive data | Criminal history, employment verification |
| General warehouse or production | Limited public or vulnerable-population contact | Identity and employment verification, criminal history as applicable |
This table is illustrative, not a legal checklist. What is “relevant” for a given role depends on the actual duties of that position and on the laws of the jurisdiction where the hire is being made, including any ban-the-box or fair chance rules that affect timing and process.
Frequently asked questions
Does running a background check protect an employer from a negligent hiring lawsuit?
A background check does not guarantee protection from a lawsuit and does not guarantee that a hire is safe. It is one part of a reasonable, documented hiring process that considers information relevant to the specific role. Whether a particular screening effort was “reasonable” in a given case is a legal question that depends on the state and the facts, and employers should talk to their own counsel about what is reasonable for their industry and jurisdiction.
Is negligent hiring the same in every state?
No. Negligent hiring is a state common law theory, and the elements, defenses, and how courts weigh a screening process differ from state to state. This article describes the general concept only and is not a statement of any specific state’s law.
Can an employer just reject every applicant with a criminal record to stay safe?
Blanket, across-the-board exclusion policies based on criminal history are specifically called out in EEOC guidance as inconsistent with an individualized assessment approach. Rather than reducing risk, that kind of policy can create separate exposure. An individualized approach that looks at the nature of the offense, time elapsed, and the specific job is the framework EEOC guidance describes.
What does “relevant to the role” mean in practice?
It means the information an employer looks into should reasonably connect to the duties of the position, such as a driving record for a role that involves driving, or a healthcare sanctions check for a role with patient contact, rather than applying the same checks and the same decision rule to every job in the company regardless of what it involves.
Do employers need consent to run a background check?
Yes. Under the Fair Credit Reporting Act, an employer must provide a clear, standalone written disclosure and get the candidate’s written authorization before procuring a consumer report for employment purposes.
What has to happen before an employer rejects a candidate based on a report?
Under federal law, before taking adverse action based in whole or in part on a consumer report, an employer generally must first provide the candidate a pre-adverse action notice, a copy of the report, and a copy of the Summary of Rights, and allow a reasonable amount of time before sending a final adverse action notice. State and local laws may add further requirements.
General information, not legal advice
This article explains a general legal concept for informational purposes and is not legal advice. Negligent hiring standards are established by state common law and vary by jurisdiction, and requirements around background screening, criminal history use, and adverse action change over time. Employers should confirm current obligations, including any state or local requirements, with their own qualified counsel before making hiring or screening decisions. For a broader look at how the required notice steps work once a report factors into a decision, see our post on the FCRA adverse action process. To see how documented, role-based screening works for your organization, visit our employment background check page or review pricing.
