Beyond the Incident-Free Record: A Construction Safety Consultant on What Sites Actually Miss
When a general contractor says a jobsite is safe because nobody has been hurt yet, that claim deserves a closer look. That premise shaped a recent email exchange with the owner of Blackrock Consulting LLC, a construction safety consulting firm based in Apex, North Carolina. The firm was recently included in a Peekwire roundup of construction safety consulting firms alongside HazTek and Antea Group, and the owner agreed to answer three questions by email about how safety actually gets evaluated in the field.
His answers focus less on paperwork and more on systems, communication, and the gap between how work is planned and how it is performed.
An Incident-Free Record Is Not Proof of Safety
The first question asked what he wants to know from a general contractor who points to a clean incident record as evidence of safety.
He said "I would ask them how they know their site is safe beyond the fact that no one has been injured. An incident-free record does not necessarily mean a jobsite is safe. It may simply mean that hazards have not yet resulted in an injury."
From there, he wants to understand how the contractor identifies risks, how well safety procedures are actually implemented in the field, and whether workers feel empowered to speak up when something isn't right. His framing is straightforward: "Safety should be measured by what we proactively prevent, not just by what we haven't experienced."
That distinction matters for anyone evaluating a safety program. A lack of reported injuries can reflect a genuinely controlled site, or it can reflect hazards that simply haven't connected with a person yet. The questions he asks are designed to separate the two.
Where Safety Plans Break Down in the Field
The second question addressed a common frustration: a safety plan that looks fine on paper but doesn't match what crews are actually doing.
He described the problem as "the gap between how work was planned and how work is actually being performed." On large-scale industrial and complex projects, he noted, construction environments change constantly. Schedules shift, trades overlap, site conditions evolve, and crews face pressures that may not have been anticipated during planning.
What often gets overlooked, in his view, is the human and operational side of safety. A plan can be technically sound, but as he put it, "if it isn't practical, communicated effectively, and understood by the people executing the work, it won't be effective." His conclusion is that safety has to be integrated into daily operations rather than treated as a separate requirement.
For readers who manage or review safety programs, the practical takeaway is to test plans against field reality. A document that satisfies a reviewer but doesn't survive contact with a shifting schedule, overlapping trades, or production pressure is not doing the job it was written to do.
After a Near Miss, the Rush to Blame
The third question asked what people tend to decide too quickly in the first days after a near miss on a large industrial job.
His answer was direct: "One of the biggest mistakes is rushing to identify someone to blame before fully understanding what happened." He framed a near miss as "an opportunity to identify weaknesses in the system before they result in a serious injury or fatality."
He said people sometimes focus too quickly on the immediate action or the individual involved without examining contributing factors such as planning, communication, supervision, coordination between trades, and operational pressures. The approach he described is to look beyond the immediate event, understand the sequence of decisions that led to it, and identify corrective actions that create lasting improvements rather than temporary fixes.
That perspective aligns with widely used investigation practices that treat near misses as free lessons, a concept often discussed in occupational safety resources and in broader incident investigation guidance. The underlying idea is that the same conditions that produced a near miss can produce a fatality the next time.
The Through-Line: Systems, Not Luck
Across all three answers, the same theme recurs. Safety is not defined by the absence of incidents, but by the strength of the systems, leadership, and decisions that prevent them. That is how he summarized the firm's position: "At Blackrock Consulting, we believe safety is not defined by the absence of incidents, but by the strength of the systems, leadership, and decisions that prevent them."
For contractors, safety managers, and owners, the practical implications are concrete. Ask how risks are identified, not just how many injuries have occurred. Test whether a plan is practical and understood by the people executing the work. And after a near miss, resist the pull toward a quick answer about who is at fault before understanding the sequence of decisions that created the exposure.
Those questions are the ones a newcomer searching for construction safety guidance would do well to start with, and they are the ones this firm's owner returns to regardless of the project.