Negligence per se is a legal doctrine that treats the violation of a safety statute as automatic proof that the defendant breached their duty of care. Instead of asking a jury what a reasonably careful person would have done, the court accepts the legislature’s judgment: if you broke the law, you were negligent. The plaintiff still has to prove the violation caused their injury and produced real damages, so it is not an automatic win. The doctrine shows up most often in traffic collisions and building code cases, where the statutes draw a clear line between acceptable and unacceptable conduct.
How It Differs From Ordinary Negligence
In a standard negligence claim, the jury weighs whether the defendant acted the way a reasonably careful person would have under the circumstances. Weather, visibility, experience, local customs — all of it gets filtered through the subjective reasonable-person test.
Negligence per se replaces that open-ended question with a binary one: did the defendant violate a specific safety statute, yes or no? When the answer is yes, the defendant cannot argue, “I was being careful despite breaking the law.” The Minnesota Supreme Court articulated the principle in Osborne v. McMasters, treating a statutory violation as conclusive evidence of negligence because the statute itself fixes the measure of legal duty.1Justia. Osborne v. McMasters
Important caveat. The doctrine only resolves two of the four elements of a negligence claim: duty and breach. Causation and damages still have to be proved the ordinary way. A driver who ran a red light is negligent per se, but if the collision was actually caused by the other driver’s blown tire, that violation did not cause the harm.
The Elements a Court Checks
Before applying the doctrine, courts run through a structured test. Failing any element kicks the case back into the ordinary negligence framework.
- Statutory violation. The defendant must have violated a statute, regulation, or in some jurisdictions an ordinance that sets a specific, mandatory standard of conduct. Vague guidelines or aspirational policy statements don’t count.
- Protected class. The injured person must fall within the group the law was written to protect. A building code requiring stairwell handrails protects tenants and visitors; most courts would not extend its benefit to a trespassing burglar who fell on the same stairs.
- Type of harm. The injury must be the kind the statute was written to prevent. A handrail code is designed to prevent falls, so a broken wrist from tumbling down fits. A respiratory illness from mold in the same stairwell does not, even though it happened in the same building.
- Causal connection. The violation must have been a substantial factor in producing the injury. If the defendant would have caused the same harm while following the law, the violation is legally irrelevant.
Legislative intent drives the protected-class and type-of-harm questions. Judges look at the purpose behind the statute to decide whether a particular plaintiff and a particular injury fall within its scope. That filter prevents parties from piggybacking on unrelated statutes just because a technical violation happened to coincide with their injury.
How Jurisdictions Treat Statutory Violations
States do not agree on how much weight a statutory violation carries in civil court. Three distinct approaches exist, and the differences can change the outcome of a case.
- Conclusive negligence. Under the strictest approach, an unexcused violation is negligence as a matter of law. The judge takes the breach question away from the jury. The defendant’s only path is to raise a recognized legal excuse for why the statute was broken.
- Rebuttable presumption. Several states presume negligence upon proof of a violation, but the defendant gets to rebut it with evidence they were acting reasonably. California follows this approach. The presumption shifts the burden without locking in the result.
- Evidence of negligence. Under the most lenient approach, a statutory violation is one piece of evidence the jury considers alongside everything else. It carries weight, but the jury can still conclude the defendant was not negligent.
The same facts can produce different verdicts depending on where the case is filed. In a conclusive-negligence state, proving the violation essentially wins the breach element outright.
Common Violations That Trigger the Doctrine
Traffic Safety Laws
Traffic violations are the most frequent basis for a negligence per se claim. Running a red light, exceeding the posted speed limit, failing to yield — each violates a statute specifically designed to prevent collisions. Driving with a blood alcohol concentration at or above 0.08 percent is a particularly strong trigger because every state treats it as a per se offense under federal incentive standards.2Office of the Law Revision Counsel. 23 USC 163 – Safety Incentives to Prevent Operation of Motor Vehicles by Intoxicated Persons DUI violations almost always satisfy the protected-class and type-of-harm elements because the laws exist to protect everyone on the road from collision injuries.
Building and Housing Codes
Codes requiring fire escapes, minimum railing heights, smoke detectors, and emergency lighting exist to protect occupants from falls and fire-related injuries. When a landlord ignores a code requiring working smoke detectors and a tenant suffers smoke inhalation injuries, the violation fits the doctrine cleanly. The occupants are the protected class, and the injury is exactly what the code was written to prevent.
Workplace Safety Standards
Federal law requires every employer to maintain a workplace free from recognized hazards likely to cause death or serious physical harm,3Office of the Law Revision Counsel. 29 USC 654 – Duties of Employers and Employees and OSHA regulations address machine guarding, fall protection, and chemical exposure limits. Courts are split on whether an OSHA violation qualifies as negligence per se in a civil lawsuit. Many jurisdictions treat such violations as evidence of negligence rather than conclusive proof, reasoning that federal administrative regulations carry different weight than state legislative statutes. The answer depends heavily on jurisdiction.
Violations That Usually Do Not Qualify
Not every broken law supports a negligence per se claim. Courts consistently exclude certain categories.
Licensing statutes. Driving without a valid license violates the law, but the overwhelming weight of authority holds that the lack of a license has no causal connection to a collision. An unlicensed driver can be perfectly skilled behind the wheel; the license is an administrative requirement, not a standard of driving conduct.
Local ordinances. Many jurisdictions treat ordinance violations as mere evidence of negligence rather than negligence per se, reasoning that local legislative bodies do not carry the same authority as a state legislature to redefine the standard of care in tort law.
Administrative regulations. Most states treat state-agency regulations the same as legislative statutes for these purposes, provided the agency was acting under a clear legislative directive. A few hold that only the state legislature itself has the power to alter common-law tort standards, so agency rule violations are only evidence of negligence.
What the Plaintiff Still Has to Prove
Even with negligence per se established, the harder half of the case remains. Proving the violation happened is often straightforward: a police report, a building inspection, or a citation establishes it. Proving the violation actually caused the injuries takes more work.
Causation has two parts. The injury would not have occurred if the defendant had followed the law, and the injury was a foreseeable consequence of the type of violation involved. If a driver was speeding but the collision happened because the other vehicle’s brakes catastrophically failed, the speeding may not be the legal cause of the crash. The jury must find that the specific violation was a substantial factor in producing the harm.
Damages require hard evidence. Medical records, billing statements, employment records showing lost income, repair estimates, and expert testimony all go into building the damages case. The shortcut negligence per se provides covers duty and breach only. Everything else is proved the same way as in any personal injury case.
One point that often trips people up: negligence per se does not automatically open the door to punitive damages. Punitive damages generally require proof that the defendant acted with willful, malicious, or recklessly indifferent conduct. A simple statutory violation usually falls short of that threshold unless the circumstances show the defendant knowingly disregarded a serious risk. Drunk driving cases sometimes clear this bar; a garden-variety speeding violation almost never does.
Recognized Defenses and Excuses
The name suggests the doctrine is ironclad, but defendants have several well-established ways to defeat a claim. The Restatement (Second) of Torts identifies five recognized excuses for a statutory violation, and most courts follow some version of this framework.
- Incapacity. The violation was reasonable because of a physical or mental incapacity the defendant could not have anticipated. A driver who suffers a sudden, unforeseeable heart attack and drifts across the center line has a viable excuse. A driver who knows about a seizure disorder and gets behind the wheel anyway does not.
- Lack of knowledge. The defendant neither knew nor should have known about the circumstances requiring compliance. A property owner with no reason to know a newly enacted code applied to their building could invoke this defense, at least until they received notice.
- Inability to comply. Despite reasonable efforts, the defendant could not comply. Equipment failures, supply shortages, or physical impossibility can qualify, but only if the defendant exercised reasonable diligence in trying to comply.
- Emergency. An unexpected emergency not caused by the defendant’s own misconduct forced the violation. Swerving into oncoming traffic to avoid a child who darted into the road is the textbook example. The emergency must be sudden and not self-created.
- Greater risk of harm. Compliance would have created a greater danger than the violation. A driver who crosses a double yellow line to avoid a head-on collision with a wrong-way vehicle broke the law, but following it would have been worse.
These excuses share a common thread. Each requires the defendant to show that breaking the law was the reasonable thing to do under the specific circumstances. Forgetting the law, or finding compliance inconvenient or expensive, gets no shelter.
When the Plaintiff Also Broke a Law
The doctrine cuts both ways. If the plaintiff violated a safety statute and that violation contributed to their own injury, the defendant can use the same doctrine against them. A pedestrian who jaywalked into traffic and was hit by a speeding driver may have committed their own act of negligence per se.
How that plays out depends on the jurisdiction’s approach to shared fault. In pure comparative negligence states, the plaintiff’s recovery is reduced by their percentage of fault but never eliminated. In modified comparative negligence states, the plaintiff can recover only if their share stays below a threshold, typically 50 or 51 percent. The handful of remaining contributory negligence jurisdictions bar recovery entirely if the plaintiff was even slightly at fault. A plaintiff’s statutory violation, analyzed through the same protected-class and type-of-harm framework, can be devastating in any of these systems.
Compliance Is Not a Shield
Defendants sometimes assume that following every applicable statute means they cannot be found negligent. That is wrong. A statute sets a floor for acceptable conduct, not a ceiling. You can follow every traffic law on the books and still drive negligently if you fail to slow down for an obvious hazard no statute specifically addresses. The reasonable-person standard still applies to everything the statute does not cover.
Federal preemption creates a narrow exception in certain product liability and regulatory contexts. When a federal safety regulation is intended to set a uniform national standard, a defendant who complied with it may argue that state tort law cannot impose additional requirements. The defense is highly fact-specific and depends on whether Congress intended the federal regulation to occupy the field. Outside those preemption situations, following the statute is relevant evidence of reasonableness but never a complete defense on its own.