Using accident reports to sharpen an assessment without overstating them

An incident summary is a story with a missing middle. It may say a rung gave way, a child fell, and a ladder was involved, without saying how old the ladder was, how it was fixed to the bed, or whether the child was climbing in socks on a polished floor. Reading such summaries well means asking what is missing before drawing any conclusion.

The seller should collect summaries from comparable ladders, not only from the exact model being sold, and should note the source of each one. A summary from a safety alert, a customer message, and a news report carry different weights, and the assessment should show which is which rather than blending them into a single alarming total.

Patterns matter more than single stories. If several summaries mention a rung splitting at the same joint, or children climbing the ladder from the side rather than the front, that repetition points to a sequence worth tracing in the assessment. A single dramatic fall, however sad, does not by itself show that a ladder design is at fault.

Context should travel with every pattern. The same rung failure may occur in ladders used by older children who climb quickly, in ladders fixed to a bed that wobbles, or in ladders stored in a damp room. Without context, a pattern can mislead the assessor into fixing the wrong part of the product.

Illustration: a seller gathers 30 incident summaries about ladders and finds that 20 of them, in round illustration terms, mention a rung problem, while the rest mention slipping feet or loose fixings. Those figures, as presented in Using accident reports to sharpen an assessment without overstating them, are invented, not measured. They do not prove that rung problems are the main risk, because the summaries were gathered for a reason and may overrepresent the problem that prompted the search.

The useful step is to compare the pattern with the ladder itself: does this ladder share the joint, the timber, or the fixing described in the rung summaries. If it does not, the pattern may be interesting but not directly relevant, and the assessment should say so.

When a pattern does match the ladder, the assessment should be updated with a dated entry that cites the summaries, describes the sequence they suggest, and states what action follows. That action might be a design change, a clearer fixing instruction, or a decision to gather more information by handling the ladder and testing its rungs.

• Record the source and date of each incident summary used.
• Separate repeated patterns from single dramatic stories.
• Check whether the ladder shares the feature behind the pattern.
• Add a dated assessment entry citing the summaries and the action taken.

Overstating accident data is easy because incident summaries feel vivid and authoritative. A seller who reads five frightening reports may feel certain that a ladder is dangerous, even when millions of ladders are used without incident and the reports describe different ladders, different ages, and different fixings. Certainty built on a small, biased sample is not evidence.

Understating data is the opposite error. A seller who dismisses every summary as anecdotal will miss a genuine pattern, such as a joint that fails after a few years. The balance lies in treating summaries as prompts for investigation, not as verdicts, and in writing down how each prompt was investigated.

Keep the summary file beside the assessment, with a short index noting which summaries were used, which were set aside, and why. That index lets a later reviewer see that the data was considered thoughtfully, rather than cherry picked to support a decision already made.

Revisit the summaries when a new batch of reports arrives, when the ladder design changes, or when a customer reports a rung problem. Each revisit should ask the same question: does this new information change the sequence, the judgement, or the next check, and if not, why not. The seller should also keep a note of summaries that were deliberately set aside, with the reason, so a later reviewer does not mistake a considered exclusion for an oversight.