The Calm Before the Claim

When I started my construction business, there were long stretches where safety didn’t demand much of my attention.

No serious injuries. No investigations. No calls from WCB.

Work was moving. People knew their roles. From the outside, everything looked fine.

At the time, that calm felt earned. We had systems in place, people were trained, and nothing suggested those systems weren’t working. What became clearer over time is that calm doesn’t tell you how a system will hold up under pressure.

It only tells you that it hasn’t been required to yet.

When Nothing Goes Wrong, Confidence Fills the Gaps

Most organizations don’t ignore safety. I didn’t either.

Programs get put in place. Training happens. Expectations are set.

When nothing goes wrong, those systems start to feel solid by default. Familiarity turns into confidence. That confidence often sounds like this:

“We’ve never had a serious issue.” “If something happened, we’d figure it out.” “Our supervisors know what to do.”

Individually, those assumptions are reasonable. Together, they create a system that works — until it’s asked to do something unfamiliar. Earlier in my career, I would have agreed with all of them.

What Serious Incidents Tend to Expose

In serious incident investigations I’ve been involved in since, the issue is rarely a single failure.

More often, it’s a set of conditions that had existed quietly for some time.

Procedures that made sense on paper. Training that didn’t hold up under pressure. Roles that felt clear until responsibility actually mattered.

Investigations don’t just ask who was in charge. They look at documentation, communication, training effectiveness, and whether earlier warning signs — like near misses — were ever recognized. Most of what shows up in serious incidents made sense at the time.

That’s what makes these conditions hard to see beforehand. They blend into normal operations until pressure exposes them. Serious incidents rarely create new problems. They reveal what was already there.

How I Think Through a Disruption

When I imagine a realistic serious incident — disruptive enough to stop work — I pay attention to where clarity exists, and where it doesn’t. The moment it happens, people look to supervision.

Is it immediately clear who’s in charge? Or is it assumed?

Questions surface quickly.

Who needs to be notified? What needs to be documented? Does anyone actually know how?

What matters most isn’t whether people care. It’s whether the answers are consistent. That’s usually when systems get revealed.

A Moment That Changed How I Look at “Calm”

Several years ago, a friend of mine owned a construction company with about 25 employees. From the outside, things looked stable. They had operated for years without a major incident. Then a serious event occurred.

After the investigation, the company faced several charges and was ordered to pay $355,000.

Not because they didn’t care about safety. But because many assumptions had never been tested until everything was under scrutiny at once. Watching that unfold changed how I think about quiet periods.

Calm didn’t protect them. It delayed seeing where the system was fragile.

A Final Reflection

The calm before the claim isn’t a warning. It’s a window.

It’s one of the few chances leaders get to decide whether clarity comes by choice — or by force.

If things have been running without incidents and you want to look more closely at what your safety systems are really built to handle, check in with our safety team for a complimentary consultation.

If your WCB costs are climbing — or you want to make sure they don't — we can help you understand what's driving them.

Click here to start the conversation