Practice with mock tests, learn from structured notes, and get your questions answered by a global forensic community, all in one place.
The three theories of product liability, design defect, manufacturing defect, and failure to warn, and the engineering analysis frameworks courts and practitioners use to evaluate them.
Last updated:
A ladder collapses. A car rolls over on a normal motorway curve. A power tool amputates a finger that the operator placed nowhere near the blade. In each case someone is injured by a product, a lawyer files suit, and at some point an engineer gets a call. The engineer's job is not to decide liability, that is the judge and jury's work. The engineer's job is to determine what happened physically and whether the product behaved within the bounds of acceptable design.
Product liability law gives the technical analysis a structured framework built on three theories. Each theory asks a different engineering question. A design defect claim asks whether the category of product was conceived badly from the start. A manufacturing defect claim asks whether this particular unit deviated from the design that was approved. A failure-to-warn claim asks whether the hazards were communicated clearly enough to the people who actually used it. Getting the theory right before diving into the engineering is not a lawyerly formality, it determines which data you need, which tests you run, and which standard of comparison you apply.
This topic walks through the framework an engineer uses when called into a product liability matter. It covers the three theories, the two competing design-defect tests (Consumer Expectation and Risk-Utility), the state-of-the-art defence, the critical distinction between intended use and foreseeable misuse, and how the same analytical logic translates across the major legal regimes, the US Restatement Third, the EU Product Liability Directive, and Australia's consumer law framework.
Each theory asks a distinct technical question, and demands different evidence.
The first step in any product liability investigation is correctly identifying which theory, or which combination of theories, the facts support. Courts and practitioners classify claims under three heads, each of which maps to a distinct engineering inquiry.
In a single case, all three can coexist. A pharmaceutical device might have a design that crowds multiple failure modes into one assembly (design defect), one batch might have been filled incorrectly at the plant (manufacturing defect), and the hazard from prolonged use might have been underplayed in the instructions (failure to warn). The engineer has to assess each independently.
A seemingly simple standard that turns on who the 'ordinary consumer' really is.
The Consumer Expectation Test is the older of the two main design-defect standards. Traceable to the original Restatement Second of Torts (1965), it asks a single question: did the product fail to perform as safely as an ordinary consumer, with the product's ordinary knowledge about it, would have expected? If yes, the design is defective.
For simple consumer products, this test has intuitive appeal. A kitchen knife that shatters on first use of normal chopping pressure has obviously failed ordinary consumer expectations. The problem appears in complex products, aircraft components, industrial machinery, pharmaceutical formulations, where an ordinary consumer has no expectations at all about the internal engineering.
This limitation drove courts, especially in California, where Barker v. Lull Engineering Co. (1978) is the leading authority, to supplement the Consumer Expectation Test with a risk-utility alternative for technical products. The Restatement Third of Torts: Products Liability (1998) effectively replaced the Consumer Expectation Test for design defects, requiring plaintiffs to identify a reasonable alternative design.
Every product is a tradeoff, the test makes the tradeoff explicit and auditable.
The Restatement Third of Torts: Products Liability § 2(b) (1998) defines a design defect as one where the foreseeable risks of harm could have been reduced or avoided by a reasonable alternative design and the omission of that design renders the product not reasonably safe. This is the Risk-Utility Test in statutory form, and it aligns closely with the way engineers already think about design decisions.
The engineer's report in a Risk-Utility case typically compares these factors quantitatively where data exist, and qualitatively where they do not. A court assessing an airbag inflator design defect needs to weigh the probability of over-aggressive deployment against the reduction in thoracic injury in a genuine crash, against the cost of a redesigned inflator, against any performance loss. These are engineering and statistics inputs, not legal conclusions, but they drive the outcome.
Manufacturers are judged on what was knowable then, not what we know now.
Two concepts bracket the outer edges of liability. The state-of-the-art defence limits what knowledge manufacturers are expected to have had. The intended-versus-foreseeable-use distinction limits which uses they must design for.
State-of-the-art defence: a manufacturer is not required to incorporate safety features, materials, or warnings that were not reasonably available or known at the time the product was manufactured and sold. The relevant date is when the product left the factory. Asbestos litigation tested this defence extensively. When a defendant insulation manufacturer sold asbestos panels in 1955, the carcinogenicity of asbestos fibres was not established in mainstream industrial medicine. Courts in different jurisdictions reached different conclusions about whether the state of medical knowledge at that time was sufficient to put a reasonable manufacturer on notice.
The engineer's contribution to this defence is documenting the technical literature, patents, standards, and industry practice that existed at the date of manufacture, and contrasting it with what was unknown or genuinely contested at the time. This is a historical engineering review, and it often involves reading conference proceedings and technical standards from decades past.
| Concept | Definition | Engineering implication |
|---|---|---|
| Intended use | The use the manufacturer designed, labelled, and marketed the product for | Design must be safe for this use; failure here is straightforward design defect territory |
| Foreseeable misuse | A use the manufacturer could reasonably predict, even if not intended | Design and warnings must account for this; ignoring foreseeable misuse may defeat the state-of-the-art defence |
| Unforeseeable misuse | A use no reasonable manufacturer would anticipate | Manufacturer generally not liable; engineer must demonstrate the use was genuinely outside reasonable prediction |
| State of the art at manufacture | Technical knowledge available when the product was made | Defines the ceiling of required safety features; post-sale knowledge does not retroactively create a defect |
The engineering analysis is universal; the legal standard varies by jurisdiction.
Product liability engineering practice operates in every major manufacturing jurisdiction, and while the engineering logic is consistent across borders, the legal frameworks it feeds into differ in important ways. Three regimes are worth knowing at the practitioner level.
From a broken product on a lab bench to a defensible technical opinion.
Regardless of theory, the forensic product liability investigation follows a consistent workflow. Short-circuiting any step weakens the opinion under cross-examination.
A batch of bicycle helmets passes all applicable safety standards but the shell moulding temperature was below the approved specification on that day. Which theory of product liability applies?
Test yourself on Forensic Engineering with free, timed mocks.
Practice Forensic Engineering questionsSpotted an error in this page? Report a correction or read our editorial standards.