Blog

The safety binder problem

2026-09-02

Every shop that has been in business ten years has a binder. It sits on a shelf in the office, it has procedures in it, and the owner can point at it. It represents real work by someone who cared.

It also answers a question nobody asks.

The question that gets asked

After an incident, the question is not whether your company had a procedure. It is whether the specific person involved had been trained on it, and whether you can show that.

The binder cannot answer that. It shows a document existed. It says nothing about whether the technician on that job had ever seen it, which version was current when he was hired, or whether the page was added last week.

Why the shared folder is not better

Moving the binder to a shared drive solves the wrong problem. It makes procedures available, which is genuinely useful for people who go looking. It still records nothing about who read what.

It also introduces a new failure. Files in a shared folder get edited in place, so the document you would produce as evidence is the current one, and there is no way to show what it said two years ago.

What actually holds up

Three properties, and each one is boring.

The document is versioned, so each edit becomes a new numbered version and the old text still exists. The acknowledgement names the person, the version, the date and where it came from. And the record cannot be altered afterwards, including by the owner, because a record you can quietly change is a record that will be argued about.

The part owners resist

Almost every shop that adopts this discovers something uncomfortable in the first two weeks: a good chunk of the crew has never read the procedures. Not refused, just never got to them.

That is unpleasant information and it is also the whole point. You would rather find it out in September than in a deposition.