Perspective · Event investigation

After the event, establish what the controls actually did

Publication date
Original date not recorded
Updated
Structure, summaries and source presentation
Article type
Perspective
Review status
Not peer reviewed

Summary

After an event, establish what each relevant control was expected to do and what evidence shows it actually did. Compare design, availability and performance under the event conditions, then verify that any proposed change improves protection during real work.

The current journal collection is not peer reviewed. The update above records changes to structure and presentation; it does not indicate a technical or independent review.

Key takeaways

  • A written control is not evidence that it worked in the field.
  • Keep the account of the event traceable to supporting evidence.
  • Revisit changes when field conditions continue to challenge the control.

An event puts pressure on everyone to explain it quickly. The first explanation is often a person’s last visible action. That may be part of the sequence, but it cannot tell us by itself why the work made sense at the time or whether the controls were capable of protecting anyone.

Build an account that can be checked

Begin with the available evidence: the scene, equipment, records, procedures, and accounts from people who were there. Record what each source can establish. Keep observations separate from interpretations, and mark gaps that still need to be resolved. A clear timeline helps, but a timeline is a starting point for questions, not a complete explanation.

Ask what people were trying to accomplish, what information they had, what changed during the task, and what tradeoffs the work required. Compare the planned process with the conditions people actually faced. A procedure may describe a safe path that was unavailable in practice; an informal adaptation may have helped work succeed many times before the event.

Test the controls

For each significant hazard, identify the control that was expected to prevent exposure or limit harm. Then ask whether it existed, was available, worked as intended, and remained effective under the conditions of the event. Do not treat a written control as proof that it functioned in the field.

  • What was the control supposed to do?
  • What evidence shows how it performed?
  • What conditions weakened or bypassed it?
  • Who will verify that a proposed change works during real work?

The response should fit the evidence. A reminder or retraining may have a place, but it cannot repair a poorly designed tool, missing capacity, or a control that fails under normal variation.

Know when to go deeper

An investigation develops a supported account of a particular event and tests the relevant controls. If that work exposes a broader question about how the task is routinely done, a Learning Team can explore it with the people who know the work. The two methods can inform each other while keeping their purposes clear.

Follow-through matters as much as the initial explanation. Assign owners, observe the change in use, invite feedback, and revisit the decision if the control still depends on people overcoming the same friction.

Adapted and edited from Todd’s 2024 article archive. ← All articles

Sources and further reading

These primary sources support the background concepts. The author’s examples and interpretations are identified in the article; links do not imply agency endorsement.

Article record

Suggested citation

Jenkins, T. J. (n.d.). After the event, establish what the controls actually did. Jenkins Industry Safety Journal. https://www.toddjeromejenkins.com/resources/articles/after-the-event

“n.d.” indicates that the original publication date is not recorded. Updated October 26, 2026: structure, summaries and source presentation.

Permanent article URL

Authorship & disclosures

Todd Jerome Jenkins, MS, CSP writes about occupational safety, event investigation, human and organizational performance, and practical uses of AI. He holds a Master of Science in Occupational Safety and Health and the Certified Safety Professional credential.

Published in Jenkins Industry Safety Journal, a publication of Jenkins Research Institute. The collection includes practical guides, explainers, perspectives and case analyses; they are not presented as peer-reviewed research.

Review status: not peer reviewed. Editorial policy, sources and corrections.

Submit a question or correction →