The flashlight is heavy, made of anodized aluminum with a knurled grip that has long since filled with a fine, grey dust from the construction site. It isn’t just a tool for cutting through the pitch-black hallways of a building whose power has been cut for a major electrical retrofit; it is a weight. For a guard on the graveyard shift, that weight is a reminder that they are the only biological sensor currently functioning in a multi-million dollar asset. When the sprinklers are off and the smoke detectors are bagged for painting, this piece of metal and glass is the last line of defense.

But lately, there is a different kind of weight being carried by the people holding these lights. It’s the weight of the “Communication Flow Chart.”

From Functional Intimacy to Protocol v3.2

A few months ago, most sites operated on a loose, functional intimacy. If a guard saw a pile of oily rags left too close to a temporary space heater, he’d walk over to the site manager’s trailer the next morning or catch him during the shift change and say, “Hey, Jim, those rags in the northwest corner are a problem.” Jim would grumble, move them, and the risk was gone. It was messy, it was informal, and it worked because it was fast.

Then came the formalization. The “Efficiency and Communication Protocol v3.2.”

Now, that same guard looks at those rags and pauses. He remembers the memo. “All non-emergency site observations must be logged through the digital portal and escalated to the Shift Lead for review before contacting client representatives.” The Shift Lead is currently handling an incident at a different site three towns over. The digital portal requires a login that sometimes hangs on the loading screen. The guard looks at the rags, then at his watch. He thinks about the last time he tried to jump the line to talk to Jim directly and got a “gentle reminder” from HR about the “chain of command.”

He sighs. He decides to wait until his formal hourly patrol report is due in ninety minutes. He’ll put it in the notes then.

When we talk about Fire watch security, we often focus on the physical presence-the boots on the ground, the rounds made every thirty or sixty minutes, the eyes watching for that first thin ribbon of smoke. But the most critical component isn’t the eyes; it’s the voice. And in many modern security environments, the voice is being throttled by the very policies designed to “organize” it.

I learned about the danger of forced silence in a completely different context. Last year, I found myself at a funeral for a distant relative. It was one of those incredibly somber, highly choreographed affairs where everyone is wearing their stiffest clothes and their most performative expressions of grief. The priest, a man who seemed to be moving in slow motion, tripped over the edge of a heavy Persian rug and did a full-length belly flop into the aisle.

The Inevitable Pop

The silence in that room was so thick you could have cut it with a trowel. And in that silence, I laughed. It wasn’t a small chuckle; it was a loud, involuntary snort that echoed off the vaulted ceiling. I wasn’t being cruel. It was just that the hierarchy of the “solemn occasion” was so rigid that the sudden intrusion of reality-gravity, in this case-was more than my brain could process without a release valve.

Organizations are the same. In security, that “pop” is usually a disaster that could have been prevented if someone had felt comfortable enough to speak out of turn.

In my day job as a precision welder, I deal with heat and pressure for a living. Quinn J.-M. is the name on my certs, and if there’s one thing I’ve learned about joining two pieces of metal, it’s that the most beautiful, structured weld in the world is worthless if it has “slag inclusion”-tiny bits of junk trapped inside the bead because the welder didn’t want to stop the “flow” to clean the joint.

In a security context, your communication policy is the weld. If you prioritize the “flow” of the hierarchy over the “cleaning” of the information, you’re just trapping slag.

The way a site audit actually works, for those who haven’t lived it, is rarely as clean as the manuals suggest. A real auditor doesn’t just look at the logs; they look at the people. They look for the “frozen middle”-that layer of management where information goes to die because everyone is too afraid of the person above them to pass on bad news.

When a guard sees a deficiency, they are handing a piece of raw, unfiltered truth to the organization. If the organization forces that truth through three layers of “formatting” and “approval,” the truth loses its edge. By the time it reaches the person who can actually fix the heater or move the rags, it’s no longer a warning. It’s just a line item in a Tuesday morning meeting.

Turning Judgment into Data Entry

The cost of this friction is measured in more than just risk; it’s measured in the soul of the workforce. When you tell a professional guard-someone hired specifically for their judgment-that their judgment must first be vetted by a flow chart, you are telling them that their judgment doesn’t actually matter. You are turning a specialized safety professional into a data entry clerk who happens to be wearing a uniform.

I’ve seen this happen on construction sites across Alberta and BC. You’ll have a guy who has been doing fire watch for 12 years. He knows how the wind whips through a half-finished high-rise. He knows that the smell of hot dust isn’t a problem, but the smell of hot insulation is a 3 a.m. phone call. But if the 3 a.m. phone call is “out of protocol,” he’ll sit on that knowledge. He’ll wait for the system to catch up.

We need to embrace the “informal candor” that safety demands. This doesn’t mean getting rid of reporting structures. It means ensuring that the reporting structure is a ladder, not a wall. A guard should be able to reach the top of that ladder instantly if they see something that threatens the site. They should feel that the organization has their back when they “overstep” to prevent a catastrophe.

True security isn’t found in the rigidity of the chain of command. It’s found in the density of the relationships between the people on that chain. If the guard doesn’t know the PM’s name, or if the PM has made it clear that they are “too busy” for direct reports, the security of that site has already been compromised.

You can have the most advanced digital reporting system in the world, with time-stamped GPS coordinates and high-res photo uploads, but if the culture says “don’t bother the bosses,” the system is just a digital ledger of your eventual failure.

The Permission to be Human

It’s about the permission to be human. Humans are messy, they’re direct, and they’re occasionally loud at funerals. But they are also the only things capable of sensing that something is “wrong” before the sensors even know there’s a problem.

Think about the last time you formalized a process in your own company. Did you do it to make things safer, or did you do it to make things “orderly”? Because in the world of fire safety and site protection, order is often the enemy of the truth. The truth is usually inconvenient. It usually interrupts your dinner. It usually requires someone to admit they forgot to do something.

And politeness doesn’t put out fires.

The Power of Informal Exchange

I remember a specific shift where I was doing a small repair on a site in Ontario. It was late, maybe 2:40 a.m., and the fire watch guard came by. He didn’t just walk past. He stopped and looked at my rig. He asked me about the sparks. He wasn’t checking a box; he was actually worried about where those sparks were landing. He told me a story about a site he’d worked three years prior where a stray spark had smoldered in a pile of sawdust for six hours before catching.

He didn’t put that conversation in a portal. He didn’t wait for his supervisor to approve the “safety interaction.” He just talked to me, man to man, professional to professional. That informal exchange did more to secure that site than any 50-page communication manual ever could.