My automated doubt development process

A long time ago I dealt with the on-site radio systems at a major oil refinery. It was interesting over the ten years or so that I worked for the company that provided them to see how their safety policies changed, and how other companies with a similar risk profile (like distilleries and whisky bonds) just plain didn't.

For example, they drastically changed how they view Permits to Work. Now a rigidly-enforced PtW would have prevented the Piper A explosion - the permit was returned to the Permit Office, not actually looked at, and then someone assumed that since it had been handed back and the work was *supposed* to be complete, then the work *was* complete. Had they looked at the permit they'd have seen there was more to do and the isolations should remain in place.

Anyway, when I started doing stuff at that site then every permit required a rigorous Method Statement and Risk Assessment. Your RA would get rejected if you failed to mention every single of PPE that you were required to wear on site, and your Method Statement would be rejected if it didn't describe the function and use of every last tool you planned to bring on site.

This was, frankly, fucking *stupid*. It took longer to write the RAMS and apply for the permit than it did to carry out most jobs, and if there was any deviation no matter how small (often because of other work you'd no way of knowing about) the whole thing would have to be stopped and relogged, with a new RAMS taking into account whatever was in your way. Someone's put scaffolding up near the aerial you want to replace? Well tough, you're not getting on site today with that permit!

They changed this about halfway through my time with my previous employer, to a "Risk-Assessed Permit", where you'd describe the risks around the specific tasks you needed to carry out and how you'd mitigate them.

Now your RAP would get rejected if you *did* put on lists of PPE. You're expected to use the correct PPE, you're expected to use your tools correctly and the correct tool for the job. Don't tell me that, just do that.

Hour-long meeting to go over the RAMS? No, five-minute "Toolbox Talk" - look up "Take Five" for some helpful guidelines - and if there are no screaming blockers, crack on, get the job done, get off site, get home. Safely.

Oh now there's some scaffolding right near the aerial you want to work on? Okay, ask the operator of that job if you're going to affect their work. Oh, they're letting you use the scaff to access the roof instead of bringing a boom lift on? Excellent, cross that off the RAP, bring it up at the Toolbox Talk, far safer that way isn't it?

I still do Take Five at work even though I'm predominantly working from home managing network equipment. If there are big complex changes to make or a major piece of work, we'll discuss it together. Anyone got any question? Anyone see something that's going to blow it all up and cause a major outage? Okay, well, you know where I am if you need help. Crack on.

It's a great way to eliminate the kind of mistakes that lead to "I wish I was still bored" days.