Proximate cause is a legal requirement in negligence cases that limits the defendant’s liability to injuries that were a foreseeable result of their careless conduct. It answers the question: Even though the defendant’s breach of duty directly caused the plaintiff’s injury, should the defendant still be held legally responsible for that harm? A surgeon who leaves a surgical tool inside a patient’s body and causes immediate infection has proximate cause clearly established—the harm is a direct and foreseeable consequence of the negligence. But if that same patient later travels to another country and contracts a rare tropical disease, the surgeon’s breach would not be the proximate cause of that new injury, even though the patient wouldn’t have traveled if not for the initial surgery. Proximate cause is the legal boundary that separates which consequences of negligence a defendant must pay for and which ones remain the plaintiff’s loss.
Courts use proximate cause to prevent liability from becoming boundless. Without this requirement, a single moment of carelessness could theoretically make a defendant liable for every injury, ever, in any chain of events that somehow traces back to that moment. Proximate cause tethers liability to the scope of what the defendant actually risked when they acted carelessly. This doctrine varies significantly between states and even between federal circuit courts, but the core principle remains: liability attaches only to injuries that were a reasonably foreseeable result of the defendant’s conduct.
Table of Contents
- What Distinguishes Proximate Cause from Factual Cause?
- The Foreseeability Test and Why It Fails Sometimes
- Intervening Causes and When the Chain Breaks
- How Courts Actually Determine Proximate Cause in Personal Injury Cases
- When Proximate Cause Fails Despite Clear Actual Cause
- Public Policy as the Final Boundary of Proximate Cause
- Distinguishing Proximate Cause from Comparative Fault and Damages
What Distinguishes Proximate Cause from Factual Cause?
Negligence requires two separate causation elements, and many plaintiffs and even some legal professionals confuse them. Factual cause (also called “cause-in-fact” or “actual cause”) asks whether the defendant’s conduct was a substantial factor in producing the injury—usually framed as the “but-for” test: “But for the defendant’s breach, would the plaintiff have been injured?” If a driver runs a red light and hits a pedestrian, factual cause is clearly established; without the breach, the collision wouldn’t have happened. Proximate cause asks a different question: Should the law hold the defendant responsible for this particular harm? It’s a question of legal policy, not just physical fact. Consider a homeowner who hires an unlicensed electrician to rewire a room. The electrician does poor work, leaving a live wire exposed behind the wall.
A week later, a plumber hired by the homeowner punctures the wall and touches the live wire, electrocuting themselves. Factual cause is satisfied—but-for the electrician’s negligence, the plumber wouldn’t have been shocked. But many courts would find no proximate cause because the plumber’s injury was not a foreseeable result of sloppy internal wiring. The breach created a risk to people who would occupy the home, not to contractors working inside the walls. The intervening act of the plumber (choosing to puncture the wall) and the intervening circumstance (another contractor being present) break the causal chain that liability should follow.
The Foreseeability Test and Why It Fails Sometimes
Most jurisdictions use a foreseeability standard to determine proximate cause. The injury must have been a foreseeable result of the breach—that is, a reasonable person in the defendant’s position should have anticipated that this type of harm might occur. If a restaurant fails to clean floors regularly and a customer slips on spilled food, the injury is foreseeable; restaurants have a duty to maintain safe walking surfaces precisely because slips and falls are a predictable consequence of failure to do so. If that same customer is hit by a car immediately after exiting the restaurant due to the slip, the injury might still be foreseeable as an indirect result. But if the customer, shaken from the slip, drives home and is hit by a drunk driver hours later, courts increasingly reject the idea that the slip is the proximate cause of the second accident. Foreseeability becomes blurry at the edges, and this is where the doctrine breaks down in practice.
How far removed can an injury be before it’s no longer “foreseeable”? Is it foreseeable that someone injured in a slip and fall might develop psychological trauma? That they might delay medical care and worsen their condition? That they might make poor decisions during recovery due to pain medication? The Palsgraf v. Long Island Railroad case, decided in New York in 1928, exemplifies the limits of foreseeability. A railroad employee negligently knocked a package from a passenger’s hands. The package contained fireworks that exploded, which startled a woman standing nearby and caused her to fall, injuring her. The court held that the railroad’s negligence did not proximately cause the distant woman’s injuries because she was outside the zone of foreseeable danger created by handling a passenger’s package carelessly. This remains a warning that proximate cause requires a tight connection between the breach and the harm.
Intervening Causes and When the Chain Breaks
An intervening cause is an independent act or event that occurs after the defendant’s breach and helps create the plaintiff’s injury. It’s neither the defendant’s conduct nor something the defendant knew about in advance. The question is whether this intervening cause “breaks” the causal chain, relieving the defendant of liability. Some intervening causes are predictable—a third party’s reasonable response to a dangerous situation—and don’t break the chain. Others are so unexpected that they absolve the defendant. Imagine a construction company negligently leaves a large hole in a sidewalk without barriers or warning.
A pedestrian falls into the hole and is injured. Later that evening, a drunk driver swerves off the street and crashes into the injured pedestrian on the sidewalk. The drunk driver’s conduct is an intervening cause, but it doesn’t break the causal chain for the original fall injury. The construction company is still liable for the fall damage, even though a second accident compounded the harm, because drunk drivers on streets are a foreseeable (if unfortunate) possibility. However, if the drunk driver intentionally aimed at the pedestrian because of a personal grudge, courts might view that as a criminal intervening act so independent and unexpected that it breaks the causal chain entirely. The construction company created the condition that made the pedestrian vulnerable, but they didn’t create the criminal intent. Criminal acts by third parties frequently break the causal chain because they’re treated as independent moral agents’ choices, not as foreseeable consequences of negligence.
How Courts Actually Determine Proximate Cause in Personal Injury Cases
In practice, judges and juries evaluate proximate cause by considering multiple factors, even though the foreseeability test is the standard. Courts look at the directness of the causal sequence—how many steps or intervening events separate the breach from the injury. They consider the degree of foreseeability (highly foreseeable vs. barely possible). They examine whether the injury is of the general type that the duty was designed to prevent. And they often invoke policy considerations: Would holding the defendant liable in this situation place an unreasonable burden on them or create a chilling effect on normal activities? A medical malpractice example illustrates this practical approach.
A surgeon operates on a patient’s knee injury and does so negligently, leaving a piece of gauze inside the patient’s leg. Six months later, the patient develops chronic pain and depression from the ongoing injury and sues. Proximate cause is clearly established—this type of harm is exactly what medical negligence law is designed to compensate. But if the patient later develops a gambling addiction and blames it on depression from the untreated leg wound, and sues the surgeon for the gambling losses, most courts will reject the proximate cause claim. The surgeon’s duty was to treat the knee injury competently; the patient’s psychological response and subsequent voluntary conduct to gamble are too attenuated and represent the patient’s independent choices. Drawing the line requires judgment, which is why proximate cause is often hotly contested in litigation.
When Proximate Cause Fails Despite Clear Actual Cause
Some of the most legally interesting—and frustrating—negligence cases involve situations where actual cause is obvious but proximate cause fails. A store manager negligently hires a security guard with a violent criminal history. Weeks later, the security guard assaults a customer during a dispute. The assault is clearly the but-for result of the negligent hiring decision; the violent guard wouldn’t have been there otherwise. Yet many courts hold that the assault is not the proximate cause of the guard’s injuries because the guard’s deliberate criminal act is an independent intervening cause. The store manager is liable for negligent hiring (a failure to conduct a reasonable background check), but not for the specific assault because that act is attributed to the guard’s own moral agency.
Another troubling scenario involves chain-reaction accidents on highways. A driver runs a stop sign and causes a minor collision. Due to debris on the road from this first collision, a second car swerves and hits a third car. A fourth vehicle, unsighted due to the chaos, hits the injured driver from the first collision. When the original at-fault driver is sued, should they be liable for all four collisions? Most courts say no—after a certain point, the accumulating independent drivers’ actions and choices break the causal chain. The original breach created a dangerous condition, but the intervening acts of other drivers operating vehicles on a public road are too numerous and independent to trace back to one negligent moment. This limitation protects defendants from infinite liability but can feel unfair to victims injured in subsequent collisions.
Public Policy as the Final Boundary of Proximate Cause
Beyond foreseeability and intervening causes, courts sometimes invoke policy reasons to limit proximate cause. If holding the defendant liable would impose an unreasonable burden, expose a particular class of defendants to excessive liability, or radically reshape a profession or activity, courts may refuse to extend proximate cause even when foreseeability seems present. Architects and engineers often benefit from this policy limit; courts are reluctant to make them liable for every subsequent user injury that results from their design decisions, as this would make design work prohibitively expensive or impossible. A practical example: A software developer creates a word-processing program with a minor security flaw.
A hacker exploits this flaw to steal data from a corporate client who uses the software. The corporation is clearly harmed, and the developer’s negligent coding is a but-for cause. But should the developer be liable for the hacker’s criminal act and the corporation’s losses? Most jurisdictions say no, applying a policy limit. Imposing such liability would require software companies to insure against all possible criminal conduct by third parties, making software development economically impractical. The developer’s liability may extend to users’ direct device damage or data loss in their own systems, but not to downstream commercial losses caused by criminal theft, because the criminal act is both an independent intervening cause and a matter of policy best addressed through other legal regimes (criminal law, contract warranties, data security regulations).
Distinguishing Proximate Cause from Comparative Fault and Damages
Proximate cause should not be confused with comparative fault or the amount of damages awarded. A defendant can be the proximate cause of an injury and still face reduced liability if the plaintiff was partially at fault. A driver who runs a red light and hits a pedestrian is the proximate cause of the pedestrian’s injuries, but if the pedestrian was also jaywalking or not paying attention, their negligence may reduce the defendant’s liability proportionally. Proximate cause is a yes-or-no threshold question: Is this defendant’s breach legally responsible for this harm? Comparative fault is a separate calculation about how responsibility is divided between the parties. Similarly, proximate cause is not about the severity or remoteness of the actual injury compared to what was foreseeable.
A store owner fails to repair a defective step, and a customer trips, breaking their ankle. The ankle break is a foreseeable type of injury (falls cause fractures). But if that same customer has brittle bone disease and suffers a more severe fracture than a typical person would, or develops compartment syndrome and requires surgery, the store owner is still liable for all of these consequences. Proximate cause is satisfied by the foreseeable harm type; the specific degree of harm suffered by this particular plaintiff, including their pre-existing conditions, does not negate proximate cause. This principle is sometimes called “taking the plaintiff as you find them,” and it means defendants cannot escape liability because a plaintiff had unusual vulnerabilities.
- —