A dropped objects prevention program needs five things to survive an audit: a written policy on what equipment is allowed at height, rated tethering and containment gear matched to the tools in use, a sized and enforced exclusion zone below the work, a documented inspection schedule for the gear, and a near-miss log that actually gets reviewed. Miss any one of the five and what you have is a toolbox talk, not a program.
That distinction matters because OSHA and most insurance auditors aren't asking "do your workers use tethers." They're asking for the paper trail that shows the control is systematic, not incidental. A crew that tethers tools because one guy is conscientious has equipment. A crew with a program has a document trail showing the same control applies every day, to every crew, regardless of who's on shift.
The Checklist
1. Know what goes up
Write down — literally — what tools and equipment are approved to go to height on a given job, and what has to stay on the ground. This sounds basic, but it's the step that catches the random tool someone grabs mid-task that was never evaluated for tethering.
2. Match gear to the hierarchy
For each tool class, decide: remove (don't bring it up), retain (tether or secure it), or arrest (catch it if retention fails). Document the tether rating against the tool's actual weight — a lanyard rated for a hand tool clipped to a heavier item is a paper control, not a real one.
3. Size the drop zone correctly
The exclusion zone below elevated work has to scale with height, not use a flat distance regardless of whether the work is at 20 feet or 200. Mark it, barricade it, and assign someone the job of actually enforcing it — a cone with no one watching it is a suggestion, not a zone.
Recommended certification
Dropped Objects Prevention for Work at Height
$39 · ~2h online · certificate issued same day · valid 2 years
Also read: Preventing Trench Fatalities: Key Takeaways from NUCA's Safety Month · Breland Homes Faces $115,855 OSHA Penalties After Fatal Trench
4. Inspect on a schedule, not on a feeling
Tethers, anchor points and containment gear degrade — UV exposure, abrasion and repeated loading all shorten their service life. A real program has a written inspection interval (not "when it looks worn") and a record of who checked what and when.
5. Track near misses as data
Every near-miss report should capture what was being carried, what control failed or almost failed, and what changed afterward. If nothing ever changes after a near miss, the log isn't a safety tool — it's paperwork.
6. Put it in the pre-task briefing
A dropped objects program only works if it's part of the daily conversation, not a binder that gets pulled out for audits. The pre-task briefing is where "what's going up today, and how is it secured" gets asked out loud, every time.
Where Training Fits
A program needs people who actually understand why each step exists — otherwise the checklist becomes a compliance exercise that gets filled out without being followed. BuildRight's Dropped Objects Prevention for Work at Height course ($39, about 2 hours) covers the physics of why height changes the stakes, the remove-retain-arrest hierarchy, tether ratings under ANSI/ISEA 121, zone control, and — in its final module — exactly how to turn all of it into a documented, auditable program rather than a one-time talk. It finishes with a test and a certificate of completion valid 24 months, which doubles as the training record your program checklist calls for.
For crews building a full elevated-work safety stack, pair it with fall protection training and PPE training — together they cover the three controls OSHA expects to see documented for anyone working above ground level.
Frequently Asked Questions
What's the difference between dropped object equipment and a dropped object program?
Equipment is the physical gear — tethers, containers, anchor points. A program is the documentation around it: what's approved, how often it's inspected, how near misses get logged, and who's accountable for the zone below. Both are required to meaningfully reduce risk.
How often should tool tethers be inspected?
There's no single OSHA-mandated interval; most programs inspect tethering gear before each use for visible damage and on a longer documented schedule (often monthly) for wear that isn't obvious at a glance. Manufacturer guidance for the specific tether should set the baseline.
Who is responsible for enforcing the exclusion zone?
It needs a named person, not an assumption that "everyone will stay out." On most crews this falls to a ground-level spotter or the competent person running the job, and it should be assigned explicitly during the pre-task briefing.
Does a near-miss report need to go to OSHA?
No — near misses aren't a recordable event and don't get reported externally. They're an internal tool, and their only value comes from being reviewed and acted on inside your own program.
Can one course really teach "how to build a program," or is that something only a safety manager can do?
The course gives the framework and the specific controls (hierarchy, tether ratings, zone sizing, inspection and near-miss tracking) that any program needs. Turning that into your company's actual written program still takes someone applying it to your specific sites and equipment — the course gets you the knowledge to do that correctly.
