But-For Causation and Its Alternatives

Establishing causation is one of the most intellectually demanding tasks in tort law. It requires you to untangle a chain of events to determine whether a defendant’s wrongful conduct is legally responsible for a plaintiff’s harm. At the heart of this inquiry is the but-for test, the foundational rule for actual causation, but its limitations lead courts to several crucial alternative doctrines. Mastering these rules is essential for analyzing complex scenarios where multiple forces converge to cause an injury.

The But-For Test: The Standard for Actual Causation

Actual causation, sometimes called "cause-in-fact," is the threshold question of whether the defendant's breach of duty was a necessary antecedent to the plaintiff's injury. The primary test for this is the but-for test (or sine qua non test). It asks a counterfactual question: "But for the defendant's negligent act, would the plaintiff's harm have occurred?" If the answer is no—meaning the harm would not have happened without the defendant's conduct—then the but-for test is satisfied, and actual causation is established.

For example, imagine a driver, Dan, runs a red light and strikes pedestrian Paula. To determine if Dan's negligence caused Paula's broken leg, you ask: "But for Dan running the red light, would Paula have suffered a broken leg?" If the evidence shows she would have been safely across the street had Dan stopped, the answer is no. Dan's conduct is a but-for cause of the injury. This test functions as a gatekeeper; failure to meet it typically ends the causation inquiry in the defendant's favor. It forces a disciplined, step-by-step analysis of the sequence of events.

When But-For Causation Fails: Concurrent Independent Causes

The but-for test's logical framework breaks down in specific, challenging situations. The first major failure occurs with concurrent independent causes. This arises when two or more forces, each sufficient to cause the plaintiff's harm entirely on its own, operate simultaneously. The classic illustration is two separate fires, each set negligently by different defendants, that merge and burn down the plaintiff's house. Either fire alone would have destroyed the property.

Applying the but-for test to Defendant A leads to a problem: "But for A's fire, would the house have burned down?" Since Defendant B's fire was also burning, the answer is yes—the house would still have burned. The same logic absolves Defendant B when analyzing A's fire. Strict application of the but-for test would let both defendants off the hook, which courts find unjust. To solve this, courts adopt the substantial factor test. It asks whether the defendant's conduct was a substantial factor in bringing about the harm. In the two-fire case, each fire is deemed a substantial factor, so both defendants are held causally responsible. This test is a judicial correction for situations where the but-for test yields an unfair and illogical result.

Alternative Liability: The Summers v. Tice Doctrine

A second failure of the but-for test happens in cases of indeterminate wrongdoing, addressed by the doctrine of alternative liability. The seminal case is Summers v. Tice, where two hunters negligently fired in the plaintiff's direction, but only one pellet struck him. It was impossible for the plaintiff to prove which hunter's shot caused the injury. Applying the but-for test to each hunter individually fails, as you cannot say "but for Hunter A's shot, the injury would not have occurred," because Hunter B's shot might have been the cause.

The court shifted the burden of proof on causation from the plaintiff to the defendants. Because both defendants were negligent and the plaintiff was innocent of any contribution to the uncertainty, each defendant must prove his shot did not cause the harm. If they cannot—which is typically the case—both are held jointly and severally liable. This policy-driven exception is triggered by specific prerequisites: all possible tortfeasors must be before the court, all must have been negligent, and the harm must have been caused by only one of them in a way the plaintiff cannot feasibly prove.

Enterprise Liability and Market Share Liability

In products liability cases involving fungible goods, particularly defective pharmaceuticals like DES, another causation dilemma emerged. A plaintiff harmed by a generic drug produced by many manufacturers decades earlier could not identify which company made the precise pill that caused her injury. The but-for test was an insurmountable barrier. In response, some courts developed enterprise liability theories, the most famous being market share liability.

Under this theory, pioneered in Sindell v. Abbott Laboratories, if a plaintiff sues a substantial share of the manufacturers of a fungible, defective product, the burden shifts. Each defendant is held liable for a portion of the damages equal to its share of the relevant market at the time of injury, unless it can prove it could not have made the product that injured the particular plaintiff. This is not a traditional causation doctrine but a policy-based allocation of risk to an industry that collectively caused widespread harm while benefiting from the inability of victims to identify the specific source. It represents the furthest departure from the but-for test, aiming to achieve loss-spreading and deterrence where traditional causal proof is impossible.

Common Pitfalls

1. Conflating Actual and Proximate Cause: A common error is to jump from "but-for" cause directly to liability. Remember, actual causation is only the first step. A defendant must also be the proximate cause (legal cause) of the harm, which involves questions of foreseeability and scope of risk. A defendant can be a but-for cause but not a proximate cause (e.g., a negligently spilled coffee that causes a chain reaction leading to a freak, unforeseeable injury miles away).

1. Misapplying the Substantial Factor Test: Students often use the substantial factor test as a general, easier alternative to the but-for test. This is incorrect. The substantial factor test is reserved for specific scenarios, chiefly concurrent independent causes. In the vast majority of single-cause cases, you must rigorously apply the but-for test first.

1. Over-Extending Alternative Doctrines: The exceptions—substantial factor, alternative liability, market share—are not catch-alls for difficult proof. Each has strict, limiting conditions. For instance, Summers v. Tice does not apply if the plaintiff was also negligent or if all possible tortfeasors are not joined in the suit. Applying these doctrines outside their narrow boundaries is a critical mistake.

1. Forgetting the Burden of Proof: In standard but-for analysis, the plaintiff bears the burden of proving causation by a preponderance of the evidence. A key feature of the exceptions is that they shift this burden. Failing to note who bears the burden at each stage of the analysis can lead to an incorrect conclusion about whether causation has been established.

Summary

• The but-for test is the default rule for establishing actual causation, asking whether the harm would have occurred absent the defendant's negligence.
• When two or more concurrent independent causes, each sufficient to cause the harm, exist, the substantial factor test replaces the but-for test to hold all responsible parties liable.
• The alternative liability doctrine (Summers v. Tice) shifts the burden of proof on causation to multiple negligent defendants when the innocent plaintiff cannot identify which one caused the harm.
• Enterprise liability theories like market share liability are policy-driven responses to causation-proof problems in mass-tort, fungible product cases, allocating damages based on industry participation rather than specific proof.
• Always analyze actual causation separately from proximate cause, and apply the exceptional doctrines only when their specific prerequisite conditions are met.