What's NewRelease NotesProduct RoadmapFieldtec BlogHelp ArticlesChat with us
← Field Notes

Field Notes|PT — 01/02|8 min read

Paper doesn't protect people. Programs do.

Every company with more than one worker already has a safety program — the only question is whether it's written down, followed, and provable. Here's why that difference matters at every size, from a five-person shop to a five-hundred-worker project.

FTFieldtec Team · Field Notes

The morning after an incident, every company discovers what its safety program actually was. Not the one in the binder — the one in practice. Who was trained, and can you prove it. When the equipment was inspected, and by whom. Whether the hazard that hurt someone had been reported before, and what happened to that report. If the answers live in someone's memory, a truck's glovebox, and three different spreadsheets, the honest answer is: there was no program. There was paperwork.

“A compliance program isn't a binder. It's a loop: find it, log it, fix it, prove it.”

That loop is the whole thing. A hazard or near-miss gets found and logged — not filed away, logged, with a date and a name attached. Someone with the authority to act on it gets assigned to fix it, with a due date. The fix gets closed out, on time or escalated if it isn't. And the record of all of it sits somewhere a person can actually pull it up later — not because a regulator might ask, though they might, but because the next incident investigation, the next insurance renewal, and the next new hire's orientation all draw on the same record.

Small companies feel it first

The five-person shop tends to think compliance is a big-company problem — something for outfits with a dedicated safety manager and a compliance budget line. It's backwards. A large contractor can absorb a bad audit, a lost bid, a WCB premium hike. It has the margin. A small one often doesn't. One serious incident carries a direct cost (medical, equipment, downtime), an uninsured cost most owners never sit down and add up (the investigation time, the retraining, the reputational hit with the client who was on site that day), and — the number that actually closes small businesses — the new sales it takes to cover both. A $40,000 incident on a company running 8% margins isn't a bad month. It's the year's profit, gone, plus the next one covering the gap.

The smaller the company, the thinner the margin between an incident and the end of the business. That's the argument for a program at five people, not against one.

Large projects demand it in writing

Get big enough to bid real work and the question flips. Nobody asks whether you have a safety program — they ask you to prove it. Prequalification forms, owner audits, ISNetworld, COR certification. The companies that keep winning that work aren't safer by accident; they're the ones who can produce the record on request, because the record produced itself as the work happened. A worker's certificate expiry, a corrective action's close date, an inspection's sign-off — all sitting somewhere queryable, not somewhere reconstructable.

That's the same loop as the five-person shop, just under more scrutiny. The size of the company changes who's asking. It doesn't change what they're asking for.

What it actually costs to skip it

Not having a program doesn't mean nothing happens when something goes wrong — it means everything that happens afterward is slower, more expensive, and more exposed than it needed to be. The investigation takes longer because nobody can say with confidence who was trained on what. The insurance claim takes longer because there's no clean paper trail to hand the adjuster. The next bid gets weaker because the prequalification questionnaire has a blank where the competitor has a number.

A program is cheaper than all three of those, run once. It just doesn't look that way on the Tuesday nothing has gone wrong yet.