You’re staring at an MBE question where the defendant ran a red light and hit the plaintiff. The call of the question asks whether the defendant breached the duty of care. You know running red lights is negligent, but something about the answer choices makes you second-guess yourself. One choice mentions “negligence per se” and suddenly you’re wondering: is this a different rule? Does the statute change how breach works?
This confusion costs points. Negligence per se is one of the most tested concepts in Torts on the MBE, and it’s also one of the most misunderstood. Students often think it’s a separate cause of action or that it automatically means the plaintiff wins. Neither is true. Understanding negligence per se means understanding exactly when and how a statute violation establishes breach of duty—and when it doesn’t.
What Negligence Per Se Actually Means
Negligence per se is not a standalone tort. It’s a doctrine that allows a plaintiff to use a defendant’s violation of a statute as conclusive evidence of breach of duty. Think of it as a shortcut: instead of arguing that the defendant’s conduct fell below the reasonably prudent person standard, the plaintiff points to a statute and says, “The legislature already decided what reasonable care requires here. The defendant violated it. That’s breach.”
Here’s the key: negligence per se only establishes duty and breach. The plaintiff still must prove causation (both actual and proximate) and damages. A statute violation doesn’t hand the plaintiff a verdict. It just removes the need to argue about whether the defendant’s conduct was unreasonable.
In a standard negligence case, you’d analyze whether a reasonably prudent person would have acted differently under the circumstances. With negligence per se, you skip that step. The statute defines the standard of care, and violating the statute is automatically considered a breach.
The Four Requirements for Negligence Per Se
Not every statute violation triggers negligence per se. The doctrine applies only when four specific requirements are met. The MBE loves testing whether these elements are satisfied, so you need to know them cold.
First, the statute must provide for a criminal penalty. Civil regulations don’t count. If the statute is merely advisory or carries no penalty, it won’t support negligence per se. The rationale is that criminal statutes represent a clear legislative judgment about what conduct is unacceptable.
Second, the statute must clearly define the required standard of conduct. Vague statutes like “drive carefully” or “maintain premises in a safe condition” won’t work. The defendant needs to know exactly what action was required or prohibited. A statute requiring vehicles to stop at red lights? That’s clear. A statute requiring “reasonable precautions”? Too vague.
Third, the plaintiff must be within the class of persons the statute was designed to protect. This is where many students trip up. Just because a statute was violated doesn’t mean every injured person can invoke negligence per se. The legislature must have intended to protect people in the plaintiff’s position.
Consider this hypothetical: A statute requires construction sites to be fenced to protect children from wandering in. An adult trespasser climbs the fence, gets injured, and sues. Even though the statute was violated, the adult isn’t in the protected class—the statute was meant to protect children, not adult trespassers. No negligence per se.
Fourth, the harm suffered must be the type of harm the statute was designed to prevent. This requirement focuses on the injury itself. A statute requiring motorcyclists to wear helmets is designed to prevent head injuries, not road rash on the arms. If a helmetless rider suffers only arm injuries in a crash, the helmet statute violation doesn’t establish breach for those injuries.
Common MBE Traps Involving Negligence Per Se
The bar examiners have favorite ways to test this doctrine, and recognizing the patterns will save you time and points.
Trap #1: Wrong class of plaintiff. You’ll see fact patterns where a statute was clearly violated, but the plaintiff doesn’t fit the protected class. A child labor law is violated, and an adult customer gets injured at the business. The adult can’t use negligence per se because child labor laws protect children, not customers.
Trap #2: Wrong type of harm. The defendant violates a fire code requiring sprinklers, but the plaintiff slips on a wet floor unrelated to any fire. The fire code violation is irrelevant to the slip-and-fall claim because the statute was designed to prevent fire-related injuries, not slip-and-fall accidents.
Trap #3: Vague statutory language. An answer choice will cite a statute requiring “reasonable safety measures” as the basis for negligence per se. This fails the second requirement—the standard isn’t clearly defined. The plaintiff would need to prove breach under the ordinary reasonably prudent person standard instead.
Trap #4: Causation confusion. The fact pattern establishes all four elements of negligence per se, and a wrong answer choice will suggest the plaintiff automatically wins. Remember: negligence per se only covers duty and breach. If the statute violation didn’t actually cause the plaintiff’s injury, there’s no liability. The defendant who runs a red light but gets hit by a plaintiff who was driving drunk and crossed the center line? Causation likely breaks the chain.
The Excuses That Defeat Negligence Per Se
Even when all four requirements are met, the defendant can avoid negligence per se by proving one of two recognized excuses.
First excuse: Compliance with the statute would have been more dangerous than noncompliance. Imagine a statute requires driving on the right side of the road. The defendant swerves left to avoid a child running into the street and collides with the plaintiff. Staying in the right lane would have killed the child. The defendant can argue that violating the statute was the safer choice under the circumstances.
Second excuse: Compliance was impossible under the circumstances. The defendant suffers a sudden, unforeseeable medical emergency (like a seizure) and loses control of the vehicle, running a red light. Compliance was physically impossible. This excuse applies only when the impossibility was truly beyond the defendant’s control—not merely difficult or inconvenient.
These excuses are narrow. The MBE will include wrong answer choices suggesting excuses that don’t actually exist, like “the defendant didn’t know about the statute” or “the defendant tried their best to comply.” Ignorance of the law is no excuse, and good intentions don’t matter. The only recognized excuses are greater danger or impossibility.
How Negligence Per Se Differs from Custom and Usage
Students sometimes confuse negligence per se with the role of custom and usage evidence. They’re related but distinct concepts, and the MBE tests the difference.
Custom and usage refers to industry standards or common practices. Evidence that “everyone in the industry does it this way” is relevant to the negligence analysis, but it’s not conclusive. A defendant can comply with industry custom and still be found negligent if a reasonably prudent person would have taken additional precautions. Conversely, violating custom is evidence of negligence but doesn’t automatically establish breach.
Negligence per se is based on statutory violations, not industry practice. When the doctrine applies, the statute conclusively establishes the standard of care. The jury doesn’t get to second-guess whether the statutory standard was reasonable—the legislature already made that determination.
One exception: In medical malpractice cases, compliance with the professional standard of care (a form of custom) is generally dispositive. But that’s a special rule for professionals, not the general negligence per se doctrine.
Applying Negligence Per Se to MBE Hypotheticals
Let’s walk through a typical MBE-style fact pattern to see how this works in practice.
Hypothetical: A statute requires all swimming pools open to the public to have a lifeguard on duty during operating hours. The statute provides for a fine for violations. Defendant operates a hotel pool and fails to hire a lifeguard. A guest’s child, age 7, dives into the shallow end, hits his head, and suffers a spinal injury. The child’s parents sue the hotel for negligence.
Analysis: Start with the four requirements. (1) The statute provides for a criminal penalty—a fine. Check. (2) The statute clearly defines the standard—a lifeguard must be on duty. Check. (3) Is the child in the protected class? The statute requires lifeguards at public pools, presumably to protect swimmers, especially children who might need supervision. The child is in the protected class. Check. (4) Is this the type of harm the statute was designed to prevent? Lifeguard statutes exist to prevent drowning and swimming-related injuries. A diving injury at a pool is exactly the type of harm contemplated. Check.
All four elements are satisfied. The hotel’s failure to have a lifeguard establishes duty and breach through negligence per se. The parents still need to prove that having a lifeguard would have prevented the injury (causation) and that the child suffered compensable harm (damages).
Now change the facts: The child isn’t injured in the pool. Instead, he slips on the wet deck surrounding the pool and breaks his arm. Does negligence per se still apply? No. The harm—a slip-and-fall on the deck—isn’t the type of harm the lifeguard statute was designed to prevent. Lifeguards prevent in-water injuries, not deck slip-and-falls. The parents would need to prove breach under the ordinary premises liability standard.
What to Memorize for Test Day
When you see a negligence question involving a statute violation, run through this checklist:
The four requirements: (1) criminal penalty, (2) clearly defined standard, (3) plaintiff in protected class, (4) harm is the type the statute was designed to prevent.
What negligence per se establishes: Duty and breach only. Not causation. Not damages. Not automatic liability.
The two excuses: (1) Compliance would be more dangerous, or (2) compliance was impossible. No other excuses apply.
Common wrong answers: Plaintiff wins automatically; defendant’s good intentions matter; ignorance of the statute is an excuse; custom and negligence per se are the same thing.
The distinction from custom: Statutory violations (negligence per se) are conclusive on breach when the four elements are met. Industry custom is merely evidence, not conclusive.
If you can spot these issues quickly, you’ll move through negligence per se questions with confidence. The doctrine isn’t complicated once you understand its limited scope. It’s a rule about proving breach, nothing more.
The FlashTables Torts table covers negligence per se alongside the other standard of care rules—the reasonably prudent person standard, professional standards, and the emergency doctrine—so you can see exactly how they fit together in the negligence framework. When you’re memorizing the four requirements and two excuses, having them laid out in a structured format makes active recall significantly easier than flipping through outlines trying to reconstruct the rule from scattered paragraphs.
The MBE will test negligence per se multiple times across your exam. It appears in straightforward questions where all four elements are clearly met, in tricky questions where one element is missing, and in combined questions where you need to analyze both negligence per se and causation or damages. Master the checklist, practice spotting the protected class and type of harm issues, and you’ll turn a commonly missed doctrine into a reliable source of points.