In , a man named James Braidwood died because he believed in a wall. Braidwood was the first director of the London Fire Engine Establishment, a man who literally wrote the book on how to stop a city from burning.
He was a master of the standard procedure. He knew how many men it took to man a pump, how many gallons of water a leather hose could sweat, and exactly where a fire-break should be cut. On a June night, a warehouse in Tooley Street caught fire. The building was a modern marvel of its time, built to the highest “standard” of iron and brick.
Braidwood, following the established logic of the day, led his men into the shadow of a massive brick wall, confident that the structure was a shield. It wasn’t. The heat from the burning tallow inside was so great that it expanded the iron girders, which acted like levers, prying the “standard” brickwork apart.
The wall didn’t just fall; it exploded outward. Braidwood was crushed not by a mistake of courage, but by a mistake of geometry. He followed the rules of a typical building, but he was standing inside an outlier.
1
The Map is Not the Woods
We often think of a Standard Operating Procedure (SOP) as a map. It is supposed to tell us where the dragons are and where the safe water flows. But a map of London is useless if you are lost in the woods of British Columbia.
In the world of industrial safety and property protection, we treat the SOP as a holy relic. We polish it, we laminate it, and we hand it to a guard with the instruction to follow it to the letter. This works perfectly until the building stops being a box.
The Mississauga warehouse: A case study in how cumulative renovations create “ghost floors” invisible to standard patrol maps.
Last year, I spent counting ceiling tiles in a warehouse in Mississauga. I wasn’t bored; I was trying to find a leak that the “standard” inspection route had missed for six months. The SOP for that site was a masterpiece of corporate clarity. It told the guards to check the main floor every two hours. It told them to log the temperature of the server room. It told them to ensure the front gate was locked.
The problem was that the warehouse had been renovated four times since 1890. It had a “ghost floor”-a narrow mezzanine built to house steam pipes that no longer ran. You could only get to it by a ladder hidden behind a stack of shipping pallets.
Because that floor wasn’t on the “standard” patrol map, no one ever went up there. When I finally climbed up, I found a pile of oily rags left by a contractor three winters ago, sitting right next to a frayed electrical junction box.
The procedure was followed. The site was “compliant.” And yet, the building was a match waiting for a strike.
2
The Template Trap
This is the central lie of the standard procedure: the assumption that every site is a “typical” site. When a company applies a generic template to a complex industrial environment, they aren’t just saving time; they are creating blind spots that look like safety.
I once talked to Avery S.-J., a food stylist who spends her life making things look like what they aren’t. She told me:
“
You can follow the recipe for a roast turkey to the letter, but if the bird is actually made of foam and lacquer for a photo shoot, you’re just heating up poison.
– Avery S.-J., Food Stylist
It’s the same with fire watch. If you apply the “recipe” for a square office building to a sprawling paper mill in Northern Alberta, you are just performing a ritual. You aren’t actually protecting the asset.
Industrial sites are rarely “standard.” They are ecosystems of hazards. They have high ceilings that trap heat long before a floor-level sensor trips. They have “dead air” pockets where smoke can pool for an hour without being noticed.
They have multi-level layouts with catwalks that require a specific physical path that a generic SOP author in a glass office in Toronto could never imagine. When a guard is told to “patrol the perimeter,” they might walk the fence line, while the real risk is sitting 40 feet up in a dust-clogged ventilation duct that has been bypassed by the main alarm system during maintenance.
3
Judgment vs. Instructions
This is where the mismatch becomes dangerous. When fire-prevention systems go offline-whether for a planned upgrade in a Vancouver high-rise or an emergency repair in an Ontario manufacturing plant-the human element becomes the only thing standing between a minor mechanical failure and a total loss.
Insurance companies and fire marshals demand a Fire watch security company because they know that a machine cannot think. But if you give that human a machine’s instructions, you lose the very thing you are paying for: judgment.
Machine Instructions
- Follow point-to-point map
- Scan tag every 60 minutes
- Log numerical data
- Report binary status
Human Judgment
- Listen for groaning machinery
- Identify chimney effects
- Detect metallic “tang” smells
- Adapt frequency based on risk
A thinking person sees the gap. They notice that the SOP doesn’t account for the fact that the north stairwell is currently acting as a chimney because of a broken skylight. They realize that the “standard” 60-minute interval is too long for a room filled with pressurized oxygen tanks.
But the rigid SOP often forbids this kind of adaptation. It says “Do X,” and the guard, fearful of a bad audit or a digital strike on their TrackTik report, does exactly X, even as Y is starting to glow orange.
I remember a project in a restoration site in Calgary. The building had been gutted by a flood, and the electrical system was a nightmare of temporary “spider boxes” and extension cords. The standard fire watch protocol for the firm involved was to check the “points of interest” every hour.
The problem was that the points of interest were based on the old blueprints. The new “points of interest” were the places where the wet drywall was touching the exposed wiring. A guard following the old map was literally walking past the fire to check a room that no longer existed.
We have a habit of confusing the documentation of a task with the completion of the task. If a guard scans a tag on a wall, the software says the site is safe. But a tag doesn’t breathe. A tag doesn’t smell the metallic tang of an overheating motor.
If the tag is placed in a “standard” location-conveniently at eye level in a hallway-the guard will never see the smoldering debris in the crawlspace below their boots.
The solution isn’t more procedures. It’s better ones. It’s site-specific protocols that are built by walking the floor, not by copying and pasting a Word document. It’s about identifying the “unusual impairment.”
If a sprinkler system is down in a warehouse that stores tires, the risk profile is vastly different than if the system is down in a warehouse that stores steel beams. A standard procedure treats them the same. A site-specific procedure knows that tire fire smoke is a toxic, oily beast that kills in minutes.
The Minimum Viable Effort
The cost of this mismatch is often hidden until it is catastrophic. When an insurer looks at the logs after a fire, they see that every patrol was logged on time. They see that the guard was where they were “supposed” to be. But the building is still gone. The gap was in the “supposed.”
We need to stop asking if the procedure was followed and start asking if the procedure was relevant. In the three provinces where these industrial hubs thrive-BC, Alberta, and Ontario-the complexity of the buildings is only increasing.
We are building taller, deeper, and with materials that Braidwood would have considered witchcraft. Yet, our “standard” way of watching them hasn’t changed much in fifty years.
COMPLIANCE
REAL SAFETY
Compliance is a floor, not a ceiling. It is the minimum viable effort to keep the lawyers away. But real safety is found in the corners that the SOP forgot.
It’s found in the intuition of a guard who knows that the “standard” route is a lie and decides to look up at the ceiling tiles instead of down at their feet. We pay for the watch, but we are really buying the ability to see the things that aren’t on the map.
Listening to the Machine
If you ever find yourself in a large industrial space at three in the morning, stop moving. Listen to the building. It makes noises. It groans as it cools. It hums with the phantom energy of machines that are supposed to be off.
A standard operating procedure cannot hear those noises. It can only check a box. We have to decide if we want our safety to be a checked box or a living, breathing awareness of the ground we actually stand on.
When we talk about digital reporting and TrackTik records, we often pitch them as “proof of work.” And they are. They are vital for the audit trail. But their true value only emerges when the “points” being scanned are the right ones.
If I tell a guard to scan a point in the middle of a clear hallway, I am wasting their time. If I tell them to scan a point behind the heavy-duty compressor that has been whining for three days, I am forcing them to engage with the risk.
This is the shift from “standard” to “specific.” It requires more work on the front end. It requires a supervisor to walk the site with a critical eye, looking for the “unusual hazards” mentioned in the theme of this discussion. It requires an admission that the corporate manual doesn’t have all the answers.
I have seen the result of the alternative. I have seen the charred remains of a “compliant” site where the fire started in a gap that “wasn’t on the list.” The guard felt terrible, but they weren’t to blame. They did what they were told. They followed the procedure. They were a perfect soldier for an imperfect war.
We owe it to the people watching our buildings-and to the people who own them-to give them better tools than a generic list. We need to map the “ghost floors.” We need to account for the “dead air.” We need to recognize that every building is a unique machine, and like any machine, it has its own ways of breaking.
The next time you look at a safety manual, don’t look at what’s in it. Look for what’s missing. Look for the mezzanine that isn’t there. Look for the hazard that “isn’t typical.” Because that is exactly where the fire will start. And no amount of “standard” paperwork will be able to put it out once the iron starts to pry the bricks apart.
In the industrial heartlands of Canada, where the scale of operations can swallow a person whole, that distinction isn’t just academic. It’s the difference between a quiet Tuesday morning and a headline that no one wants to read.
We have to be brave enough to deviate from the standard when the standard no longer fits the walls we are trying to protect. That is the only way to ensure that the next James Braidwood doesn’t die believing in a wall that was never really there to begin with.
The procedure must serve the site, never the other way around. If the stairs are outside, the guard must go outside. If the risk is in the rafters, the guard must look up. Anything less is just a very expensive way to watch a building burn.