Disconnected Safety Systems Are Creating Hidden Risk in Field Operations
According to ISHN, the next serious safety incident in your operation may not originate from a single point of failure, a bad actor, or a missed procedure. It may originate from the space between your systems, where a maintenance flag, an incident log entry, and a quality deviation all existed but never connected into a single, legible warning.
That’s the central argument made by author Mike Blasdell in a recent ISHN analysis piece, and for subcontractors and field service companies managing distributed crews, multiple client systems, and a mix of paper and digital workflows, it lands hard.
Background
Blasdell identifies a structural problem common to modern operations: safety-critical information is spread across incident logs, maintenance systems, ERP and MRP platforms, quality systems, spreadsheets, and email threads. Each of these tools may function well in isolation. The problem is that they were not designed to share data in real time, and in many organizations, they don’t.
According to ISHN, this integration gap produces a predictable pattern. Early warning signals, repeated minor incidents, maintenance delays, quality deviations, operator workarounds, appear across different systems, owned by different teams, reviewed at different times. Individually, none of them trigger an alarm. Collectively, they can point toward something far more serious. But if no one is looking at them together, that signal never forms.
The piece also highlights how EHS teams compound the problem from the other direction. They’re frequently managing multiple reporting tools, handling manual data entry, and chasing follow-ups across departments. The result, as Blasdell frames it, is a difficult double bind: too little information in some areas, too much fragmented information in others. Neither condition supports fast, confident decision-making.
Blasdell draws on a simple but effective analogy from emergency response. On the fireground, experienced responders don’t rush. Speed matters, but control and situational awareness matter more. That principle, he argues, applies directly to how safety data should flow through an organization. Rushing without full awareness isn’t faster. It’s just more dangerous.
Analysis
For subcontractors, this issue cuts deeper than it might for a fixed manufacturing facility. A service company running crews across multiple client sites is often operating inside several different digital ecosystems at once. One client uses a major ERP for work order management. Another runs a proprietary permitting system. Your own company may track incidents in a standalone platform that has no integration with either. You’re already operating in exactly the disconnected environment Blasdell describes, and you may have less visibility into the gaps than an in-house team would.
The underreporting problem Blasdell raises is also more acute in the field. In subcontract environments, there are real or perceived pressures around reporting near-misses and minor incidents, whether it’s fear of losing a contract, concern about slowing down a job, or simply not having a clear, accessible reporting channel when you’re two hours from the nearest office. When those small signals go unreported, the early warning pattern never forms at all.
What Blasdell is describing is, at its core, an integration problem, not a technology problem. That distinction matters. Many field service companies have already invested in software, whether that’s a field service management platform, a safety observation app, or a digital permitting tool. The question isn’t whether those tools work. It’s whether they’re talking to each other, and whether the people responsible for safety decisions are seeing a complete picture or a series of disconnected fragments.
The practical implication is that auditing your systems for integration gaps is itself a safety activity. It belongs on the same checklist as inspecting PPE or reviewing lockout/tagout procedures. If your maintenance alerts live in one platform, your incident reports live in another, and your near-miss observations live in a spreadsheet that one person updates on Fridays, you have a gap. And that gap is where the next incident may already be forming.
What It Means for Subcontractors
-
Audit your data touchpoints. Map out every system where safety-relevant information is captured, including maintenance logs, inspection apps, permitting tools, and incident reporting platforms. If they don’t share data automatically, that’s a risk that needs to be addressed.
-
Ask who connects the dots. In your organization, identify who is actually responsible for reviewing signals across systems. If the answer is “nobody” or “it depends,” that’s a gap in your safety process, not just your technology stack.
-
Don’t wait for a major incident to expose the cracks. Minor incidents, workarounds, and equipment delays are early warning signals. Build a process to surface and review them together, even if that means a weekly cross-functional review using existing data.
-
Push for integration when selecting new tools. When evaluating field service management software, safety apps, or reporting platforms, ask directly how the tool connects to your other systems. Integration capability should be a purchasing criterion, not an afterthought.
-
Consider platforms that unify safety with daily operations. Tools like Aimsio, designed for field service contractors, connect crew dispatching, field ticketing, safety documentation, and real-time reporting in a single system — so the data Blasdell describes stays connected from the start rather than fragmenting across half a dozen platforms.
-
Address the underreporting culture. Systems can only surface signals that get entered. Make reporting frictionless and consequence-free for field crews, especially for near-misses and minor incidents that might otherwise go unlogged.
