Why Your Safety Program Looks Compliant But Isn't Preventing Injuries
According to ISHN, most safety programs claim to be proactive but are still fundamentally built to document what already happened, not to surface risk early enough to stop the next incident. Writing for ISHN, safety consultant Michael Bruns argues that the gap between compliance theater and actual prevention is costing organizations far more than the paperwork suggests, and that field operations are where this failure shows up most clearly.
Background
The numbers behind workplace safety failures are hard to ignore. Workplace injuries and illnesses cost the U.S. economy between $174 billion and $348 billion annually, according to Bruns’ analysis. But for subcontractors and field service companies operating on thin margins, the more punishing costs are closer to home: operational disruption, lost crew time, repeated exposure to the same preventable incidents, and the liability exposure that follows.
Bruns identifies a pattern common across construction, energy, and other high-hazard sectors. When an incident occurs, teams document it, close it out, and move on. The corrective action gets filed. The OSHA recordable gets logged. The box gets checked. But the underlying condition that allowed the incident to happen in the first place often goes unaddressed, waiting to produce the next near miss or injury.
This is the compliance trap. Regulatory requirements from OSHA and state-level safety agencies are designed around documentation as a floor, not a ceiling. Companies that treat documentation as the goal end up with safety programs that look rigorous on paper but leave real risk unmanaged in the field.
Analysis
The visibility gap Bruns describes is particularly acute for subcontractors running crews across multiple sites. A general contractor or asset owner may have a unified safety management system. The sub doing the actual hands-on work, often with smaller administrative staff, is left managing risk through inspection forms, paper tailgate meeting logs, and corrective action tickets that stall somewhere between the field supervisor and the safety manager’s inbox.
Two failure points stand out for field operations specifically.
The first is reporting friction. Bruns notes that the problem in most field organizations isn’t that workers lack awareness of hazards, it’s that reporting systems are designed around office workflows rather than field conditions. A driller’s assistant on a Permian Basin location isn’t going to fill out a six-field web form to report a near miss on a connection. If the process takes longer than the conversation he’s about to have with his pusher, it doesn’t happen. The near miss goes unreported, and the pattern that would have revealed a systemic equipment problem stays invisible.
Mobile-accessible, low-friction reporting is the practical fix here. Several field safety platforms now offer single-tap near-miss capture tied to equipment IDs or location data. The value isn’t just convenience. It’s that aggregate data from simple reports can reveal patterns that no single incident report ever would. Five near misses tied to the same pump skid across three locations tells a story that one corrective action ticket never could.
The second failure point is what Bruns calls the operationalization gap around leading indicators. Most safety programs in the field collect leading indicator data, near-miss counts, inspection completion rates, corrective action aging. But collecting the data and actually acting on it before an incident occurs are two different things. Corrective actions that stall or close without verification, training completions that satisfy a requirement without changing behavior, recurring minor incidents tied to the same equipment or shift pattern, these are the signals that a reactive program misses or dismisses.
For multi-site subcontractors, this problem compounds quickly. A safety manager covering 10 active locations across two basins cannot manually track corrective action aging on every open item. Without a system that flags stalled actions or surfaces recurring incident patterns by asset or crew, that manager is effectively flying blind between audits.
The shift Bruns advocates, from reactive reporting to proactive risk visibility, requires more than new software. It requires rethinking who owns safety information and how quickly it moves from the field to decision-makers. In practice, that means giving frontline supervisors real-time visibility into open hazards on their locations, not just the safety department.
What It Means for Subcontractors
- Audit your corrective action closure rate. If a significant share of corrective actions are stalling open past 30 days, you have a process failure, not just an execution problem. Set aging thresholds and assign ownership at the supervisor level, not just the safety team.
- Cut reporting friction immediately. If your near-miss reporting process requires more than two or three steps on a mobile device, your field data is incomplete. Incomplete data means hidden risk.
- Look for patterns across sites, not just incidents at single locations. Recurring near misses tied to specific equipment, shift times, or crew configurations are your most actionable leading indicators. You need a system that lets you see across locations, not just manage one site at a time.
- Treat OSHA compliance as the floor, not the goal. Meeting recordkeeping and reporting requirements under 29 CFR 1904 is mandatory. But a program designed only to satisfy those requirements will always be one lagging indicator behind the next preventable injury.
- Train supervisors to act on data, not just collect it. The supervisor at the wellsite or job trailer is the person who can actually intervene before a hazard becomes an injury. If your safety program only flows information up to a central safety manager, you’re adding lag time at the moment when speed matters most.
