What Counts as a Defect That Must Be Reported

Two questions get collapsed into one and should not be. The first is whether a product contains a defect. The second is whether that defect could create a substantial product hazard. A firm can answer the first yes and the second no, and the reporting rule still reaches it if the defect could create such a hazard. Working the questions in order is what keeps the assessment honest.

What a defect is

The regulation defines defect by reference to ordinary meaning: a fault, flaw or irregularity that causes weakness, failure or inadequacy in form or function. A defect is a product's failure to perform as a reasonable consumer would expect, in a way that creates a risk of injury.

Five categories are identified. A defect may lie in manufacturing or production, where units depart from the intended design. It may lie in design, where every unit performs as intended and the intention was unsafe. It may lie in composition or contents. It may lie in packaging. And it may lie in warnings or instructions, where the product cannot be used safely without information the user was not given.

The last two categories are the ones firms overlook. A product that is safe when assembled correctly and dangerous when assembled the way the instructions describe is defective, and no amount of engineering evidence about the design answers it. The same is true of a warning that is present but placed where a user will not encounter it before the hazard.

Risk, not failure

Not every fault is a defect for these purposes. A product that stops working is a warranty problem; a product that stops working in a way that can injure someone is a safety problem. The distinction is whether the fault creates a risk of injury, and the analysis begins there rather than with the volume of complaints.

The regulation makes the point directly by tying the defect concept to consumer expectation and to risk together. A component that fails early and simply ceases to function is not a defect within the meaning of the rule unless the failure mode creates a hazard.

Conversely, a product that works exactly as designed can be defective if the design creates a foreseeable hazard in reasonably anticipated use, including misuse a manufacturer should expect. Reasonably foreseeable misuse is part of the analysis, not an answer to it.

This is where the two questions separate cleanly. Whether a defect exists is a question about the product. Whether it creates a substantial product hazard is a question about the population using it and what happens when the fault manifests. A firm that answers only the first has done half the work, and it is the half that produces the more comfortable conclusion.

Severity, likelihood and the exposed population

The evaluation of severity considers the potential for serious injury, illness or death, including whether medical treatment such as hospitalization or surgery would be required. It also considers the likelihood of injury, which turns on the operation of the product, the hazard's accessibility during normal use, the population exposed and the human factors involved.

Human factors do real work here. A hazard that requires deliberate defeat of a guard is treated differently from one that arises when a user does something the product invites. The intended user is part of the picture: a tool designed for trained operators is assessed against that population, while a consumer product is assessed against a population that includes the careless and the distracted.

Where the exposed population includes children, older adults, or people with disabilities, both the severity and the likelihood assessments shift. A hazard that a competent adult would recognize and avoid may be entirely unavoidable for a small child, and the analysis reflects that.

Who makes the assessment and when

The firm makes it first, and does so under time pressure. The reporting rule permits a reasonable investigation before reporting but bounds it, and the deeming provision means that a firm which took too long is charged with what a diligent investigation would have found. The mechanics of that timetable are set out under the twenty-four hour reporting clock.

The Commission makes it second, and independently. A firm may report while stating its position that no defect exists, and the report is not an admission. Staff then form their own view, request further information, and either close the matter or open a discussion about corrective action.

The two assessments are made with different information. The firm knows the design history, the production records and the specification changes. Staff have incident data across the market and comparison with similar products. That asymmetry explains why a firm's early confidence is so often revised.

Documenting a decision not to report

A firm that assesses a complaint and concludes no reportable defect exists has made a decision it may need to defend years later, usually after a subsequent incident has made the conclusion look wrong.

The protective step is contemporaneous documentation of the analysis rather than the outcome: what the fault was, what testing or engineering review was carried out, how severity and likelihood were assessed, what the distribution numbers were, and who signed off. A file recording that the matter was reviewed and closed says nothing useful.

Where the conclusion is that a defect exists but creates no substantial product hazard, the reasoning should address each of the factors the regulation lists rather than the one the firm found most favorable. That analysis is also the starting point for any discussion of remedy, because the same factors shape what a corrective action plan will be expected to cover, and they reappear in the assessment of the penalty factors if the matter escalates.