A recall notice lands in a client's inbox weeks after the injury, and the first instinct is to treat it as the case. It is not. A recall is useful evidence, sometimes powerful evidence, but standing alone it proves neither defect nor causation, and leaning on it too hard invites a defense that the product was fixed and the plaintiff simply failed to respond. The stronger approach treats the recall as one input into a defect theory built the ordinary way.
Pick the defect theory before you pick the exhibits
Products cases still sort into three buckets, and the proof for each diverges early. A manufacturing defect argues this unit departed from its own specification. A design defect argues the specification itself was unreasonable. A warning defect argues the product was adequately designed but inadequately labeled for a foreseeable use or misuse.
The choice drives which test governs. Most jurisdictions evaluate design claims under a risk-utility balance, asking whether the danger of the design outweighs its benefits and, in many states, whether a reasonable alternative design was feasible. A smaller set of jurisdictions, and some product categories within them, still allow a consumer-expectation test, which asks whether the product was more dangerous than an ordinary user would expect. The consumer-expectation route can carry a plaintiff without proof of an alternative design when a product fails in a way that plainly defies expectation, so identify early whether your state lets you plead in the alternative.
How the recall actually helps
A recall touches several elements without deciding any of them:
- Defect and feasibility. If the manufacturer redesigned the part or changed a warning as part of the corrective action, that change is evidence a safer alternative was feasible. Subsequent-remedial-measure rules vary, so brief admissibility before you build the theme around it.
- Notice. The reporting record shows what the company knew and when. A late report, measured against the roughly 24-hour expectation for urgent hazards, can support a punitive-damages posture.
- Scope. Recall population data, incident counts, and hazard classification tell you whether this was an isolated complaint or a known pattern.
What a recall does not do is establish that this plaintiff's unit was defective or that the defect caused this injury. Defense counsel will argue the recall reached the consumer, the remedy was free, and non-response broke the causal chain. Anticipate that argument and build causation independently.
Chain of custody is the case
The single most common way a strong products case collapses is loss of the product. Once the failed unit is gone, the design theory becomes a contest between experts working from photographs, and the defense expert always seems to have the better photographs.
Secure the product the day you are retained. That means:
- A written custody log from the moment of recovery, documenting every transfer and storage condition.
- Preservation of the product in its post-incident state, including debris, fragments, and any attached components, before any testing alters it.
- A joint-inspection protocol negotiated with the defense so destructive testing happens under agreed conditions and neither side can later claim the other altered the evidence.
- Preservation of the packaging, manuals, and warning labels, which are the warning-defect case in physical form.
When the client no longer has the product, the analysis shifts to who did, and whether their failure to keep it supports a spoliation argument against a party that had a duty to preserve.
Reconstruction and the expert's role
Expert reconstruction carries a design case, and the expert has to survive a gatekeeping challenge before the jury ever hears the opinion. Retain the reconstruction expert early enough to direct the inspection rather than react to it. The expert should test the alternative design, not just describe it, because a risk-utility opinion that never quantifies the tradeoff is the first thing a defense motion targets. Where the theory is manufacturing defect, the expert compares the failed unit against the manufacturer's own specification and quality-control records, which makes early discovery of those records essential.
The recall tells you a problem existed. The expert tells you why it existed in this unit and how a feasible alternative would have prevented this injury. Only the second gets you to a verdict.
Discovery targets that move the needle
Beyond the recall file itself, the documents that build the defect case tend to sit in a few predictable places:
- Pre-market design-failure-mode analyses and any internal testing that flagged the hazard.
- Customer-complaint and warranty-claim databases, which often show the manufacturer tracking the failure mode long before the recall.
- Communications with the CPSC, including the initial report and any back-and-forth over hazard classification and remedy scope.
- Supplier and component-maker records, because the right defendant is sometimes upstream of the brand on the box.
Pressure-cooker litigation over lids that can be opened while the vessel is still pressurized is a useful model here. The plaintiff theories succeed when they marry a concrete design mechanism to a documented complaint history, and they struggle when they rely on the recall as a substitute for that mechanism.
Bottom line
Treat the recall as corroboration, not foundation. Lock down the product and its custody before anything else, choose the defect theory that fits both the facts and your state's governing test, and retain the reconstruction expert early enough to shape the inspection. For related analysis, see our ongoing product-liability coverage, the recent case law and settlements driving these theories, and, where a defect proves fatal, the damages framework in wrongful-death practice.