Placeholder. This article is placeholder copy written to test layout and tone. It is not published research and makes no factual claims.
Event reviews are where an organization decides what it has learned. This briefing sets out why describing conditions, controls and systems produces more learning than describing individual behavior.
Where event reviews stop
“Human error” describes where a review stopped looking. Asking what made the action reasonable at the time, and which controls were expected to catch it, keeps the review open long enough to find a condition that can be changed.
Exhibit 1 Illustrative data
In this illustrative sample, nearly half of event reviews stopped at an individual action
Last cause recorded in each review, illustrative sample of 30 event reviews, count
SourceIllustrative data for design purposes only. Not a research finding and not to be quoted.
NoteValues are placeholders chosen to demonstrate the exhibit format. They describe no real reviews.
Data behind this exhibit
| Item | Value |
|---|---|
| Individual action | 14 |
| Equipment condition | 6 |
| Procedure gap | 5 |
| Critical control not verified | 3 |
| Planning and scheduling | 2 |
Cite this exhibit
Before the Incident, “In this illustrative sample, nearly half of event reviews stopped at an individual action,” Exhibit 1 (2026). Illustrative data; not a research finding and not to be quoted. Link
What leaders can ask for
- A description of the conditions on the day, in the words of the people doing the work.
- The critical controls that applied, and the state each was in.
- One change to the system, with an owner and a date.
The current report
The controls that prevent a fatality
Many operations have spent a decade driving recordable injury rates down. This report asks whether the controls that prevent a fatality have improved at the same pace, and how a leadership team would know.