Elias has spent thirty-seven years sitting in a glass box suspended three hundred feet above the pavement. He is a crane operator in Toronto, a man who views the world as a series of weight calculations and wind resistance factors.

When he talks about safety, he doesn’t talk about the “average” wind speed of the day. To Elias, an average wind speed of fifteen kilometers per hour is a meaningless piece of trivia. It’s the “jolt”-that singular, four-second gust hitting eighty kilometers per hour-that determines whether he stays in the cab or starts the long climb down.

The average wind speed might suggest a calm, productive Tuesday, but the crane doesn’t tip over on an average. It tips on the outlier.

The Grit in the Gears

This is the fundamental friction of risk management, and it’s a lesson I’ve been thinking about all morning while picking coffee grounds out of my keyboard with a toothpick. I knocked over the canister in a fit of morning clumsy, and now the ‘R’ and ‘T’ keys have this sickening, gritty crunch.

The “average” cleanliness of my desk is still quite high-probably ninety-eight percent of the surface is pristine-but that remaining two percent of grit is currently dictating my entire experience of reality. You don’t notice the ninety-eight percent of the keys that work perfectly. You only feel the one that hitches.

In the world of property management and construction across British Columbia, Alberta, and Ontario, we are being lied to by the “Mean.” A property owner or a general contractor sits down with a security proposal and sees a beautiful, comforting number: “Average Response Time: 4.2 Minutes.” It feels like a handshake. It feels like a promise.

But if you look closer at the spreadsheet, you realize that the average is a composite of a thousand quiet nights where the guard responded in thirty seconds because there was nothing happening, and one catastrophic Tuesday in February where the response took forty-five minutes because the system was down and the backup failed.

The average hides the night it took forever. It buries the most dangerous moment of your career under a mountain of trivial successes.

When a building’s fire suppression system goes offline-whether it’s due to a scheduled retrofit in Vancouver or a burst pipe during an Edmonton cold snap-the building enters a state of high-stakes vulnerability. This is when the “averages” become dangerous. If your fire watch provider tells you they have a stellar average response rate, they are essentially telling you about the wind on a calm day.

The Ghost in the Middle

They aren’t telling you about the gust. They aren’t telling you about the one time they missed a patrol because the reporting software glitched or the guard decided to take a nap in the stairwell. Safety is a binary. Either the fire was caught, or it wasn’t. There is no such thing as being “ninety-nine percent protected” from a total loss.

I’ve spent enough time at the bargaining table as a union negotiator to know how people use numbers to hide the truth. We call it “statistical anesthesia.” If I tell you that the median wage in a shop is thirty dollars an hour, I am concealing the fact that five people are making eighty dollars and fifty people are making fifteen. The “middle” is a ghost. In security, the ghost is the “mean response time.”

Consider a simple, reframed statistic that most providers won’t show you: If a security firm manages one thousand sites and has a “success rate” of 99.9%, it sounds elite. But in plain human terms, that means on any given night, one client is being completely failed.

If you happen to be that one client-the site where the “long tail” of the distribution curve actually lands-that 99.9% success rate is a 100% catastrophe for you. You aren’t paying for the average; you are paying to ensure you aren’t the outlier.

This is why the shift toward documented, verifiable physical presence is so critical. On construction sites where millions of dollars in materials and months of labor are at risk, the reliance on an “average” response is a form of professional negligence. You need the “Max,” not the “Mean.” You need to know the worst-case scenario is accounted for.

The Value of Constant Presence

When the sprinklers are off and the alarms are silent, the human element is the only barrier between a small electrical short and a headline on the evening news. This is where a Fire watch security company proves its worth, not by being fast on “average,” but by being present constantly.

The value isn’t in the speed of the arrival; the value is in the elimination of the departure. If a guard is on-site, performing documented patrols via systems like TrackTik, the “response time” to a fire in the north wing isn’t four minutes-it’s the time it takes to walk across a hallway. It is instantaneous. It bypasses the distribution curve entirely.

There is a specific kind of anxiety that comes with managing a large-scale project in places like Ontario or Alberta, where the sheer scale of the environment makes oversight difficult. You find yourself staring at reports, trying to find the “crunch” in the data. You’re looking for the coffee grounds in the keyboard.

You want to know if the guard was actually there at 3:15 AM when the temperature dropped to minus thirty and the space heaters started humming a little too loudly.

The insurance brokers know this. They don’t care about your provider’s marketing deck. They care about the audit trail. They want the time-stamped, GPS-verified proof that someone was walking the perimeter. They understand that a fire doesn’t care about your provider’s “Gold Award for Average Response.”

If you can’t prove the coverage was there at the exact moment of ignition, the “average” won’t save your claim. I remember a conversation with a project manager in Calgary who had just lost a three-story wood-frame development to a “hot work” fire that smoldered for two hours after the crews left.

“The most painful part wasn’t the loss of the building; it was the realization that he had been paying for a ‘safety net’ that was mostly holes.”

– Project Manager, Calgary Development

The security company he hired had a great reputation. Their average response time was under five minutes. But that night, their patrol vehicle had a flat tire, and the backup guard was covering two sites at once. The “average” was still intact for the company’s internal metrics, but for that specific site, on that specific night, the response time was effectively infinite.

Live or Die by the Grains

We tend to favor the “mean” because it’s a clean number. It’s easy to put in a report. It makes us feel like we’ve conquered the chaos of the world with a single digit. But the world isn’t clean. It’s gritty. It’s full of coffee grounds and flat tires and guards who get tired.

True safety-the kind that lets you sleep when you know the fire alarm system in your building is currently a pile of disconnected wires-comes from acknowledging the outlier. It comes from choosing a partner who understands that their job is to protect against the 1%, not to brag about the 99%. It means looking for a provider that doesn’t just promise to “be there fast” but promises to “be there already.”

In British Columbia, the regulations for fire watch are stringent for a reason. The fire code doesn’t ask for an “average” level of monitoring. It asks for “continuous” monitoring. There is a profound legal and ethical difference between those two words. Continuous means there is no tail. There is no distribution curve. There is only the presence.

When I finally got the last of those coffee grounds out of my keyboard, the keys started moving freely again. The friction was gone. But I realized that I had spent forty-five minutes of my life focused on a tiny, granular failure that the “average” state of my office would have deemed irrelevant. We spend our lives managing the averages, but we live or die by the grains.

Next time you’re looking at a security report, or a safety audit, or a performance metric, don’t look at the big, bold number at the top. Look for the “Max.” Ask about the worst night they had last year. Ask how long it took to respond when everything went wrong. Because when the wind starts gusting at eighty kilometers per hour, you don’t want to be told that the average breeze is a gentle fifteen.

You want to know that when the one catastrophic moment arrives-the one that will define your project’s success or failure-the person you hired isn’t five minutes away.

You want them to be right there, standing in the hallway, already holding the extinguisher. That is the only metric that matters. The rest is just math, and math has a nasty habit of hiding the truth until it’s too late to change the outcome.