Why Everyone Needs a Drops Prevention Program

A webinar-based breakdown of how to build a dropped-object prevention program using written procedures, defined responsibilities, ANSI/ISEA 121-aligned equipment, training, and reporting.

Why Everyone Needs a Drops Prevention Program

Source: Construction Business Owner

Summary

This webinar presentation argues that dropped-object prevention should be treated as a formal safety program, not a loose collection of habits. Presented by Mathew Moreau, it frames the problem with U.S. injury and fatality data, then walks through the core elements of an effective program: clear purpose and definitions, assigned responsibilities, practical work rules, procurement requirements, and consistent training. A major emphasis is aligning equipment selection with ANSI/ISEA 121-2018, including the four core product categories of anchor attachments, tool attachments, tool tethers, and containers. The slides also stress pre-task inspection, installing tethering products on the ground, housekeeping, passive controls, incident reporting, and routine program refreshes. The overall message is that prevention works best when policy, equipment, behavior, and follow-through are all managed together.

Key Facts

  • Who: The webinar was presented by Mathew Moreau, identified in the slides as Product Manager - Dropped Tool & FME at Pure Safety Group and 2020 vice chair of the ISEA Dropped Objects Product Group.

  • What: The presentation outlines how to build a dropped-object prevention program, including written procedures, responsibilities, work practices, procurement guidance, ANSI/ISEA 121 alignment, tool-tethering basics, and incident reporting.

  • When/Where: The slide deck was published on Construction Business Owner on Mar. 26, 2020, as part of its webinar content.

  • Outcome: The practical takeaway is that companies should create or refine a written drops procedure, evaluate tooling, reinforce training daily, and review the program often.

Quotes

“It is a company’s way of managing and preventing dropped objects.” — Mathew Moreau
Context: This line defines the program as an organized management system, not just PPE or a tether purchase.

“Capturing details of a dropped object incident can be crucial.” — Mathew Moreau
Context: The slides connect reporting to learning, corrective action, and future prevention.

Takeaways

  1. A dropped-object program needs structure: purpose, scope, definitions, responsibilities, and work practices should be clearly documented.

  2. ANSI/ISEA 121 matters because it gives employers a consistent baseline for design, testing, environmental performance, and safety factors across key product categories.

  3. Prevention is broader than tethering alone; PPE, housekeeping, area clearing, toe-boards, debris netting, inspections, and pre-task checks all play a role.

  4. Reporting and retraining are not administrative extras - they are core feedback loops that help improve program performance over time.