Back to Blog
Blog

How do you determine which regulations actually apply to a particular procedure?

How do you determine which regulations actually apply to a particular procedure?

Most sites are covered by a long list of regulations, standards and internal policies, but only some of them apply to any given procedure, and figuring…

Most sites are covered by a long list of regulations, standards and internal policies, but only some of them apply to any given procedure, and figuring out which ones usually depends on the experience of whoever wrote it. An author who has worked through a few audits will know that a tank cleaning procedure touches confined space entry, atmospheric testing, isolation and possibly respiratory protection, while a newer author may only cite the rule that seems most obvious. That makes it easy to miss a requirement or to cite regulations that do not really apply, and both problems tend to surface at the worst time, during an audit or after an incident.

Over citing looks harmless but it causes real trouble, since a procedure that lists ten regulations “just in case” tells the reader nothing about which ones shape the steps, and it creates review work every time any of those regulations changes. Under citing is the more serious failure, because a requirement nobody linked to the procedure is a requirement nobody checked the steps against, and the gap only becomes visible when someone outside the team asks how the procedure satisfies it.

The better approach is to map regulations to the equipment, activities and hazards they cover, then match procedures to them through those same attributes. A pressure systems regulation applies to pressure vessels and to the activities of testing, opening and repairing them, a confined space rule applies to entry into spaces with particular characteristics and a working at height rule applies to tasks above a set height. When a procedure is tagged with the equipment it covers, the activities it describes and the hazards involved, the match to regulations comes from those attributes rather than from someone’s memory.

Once that mapping exists, it becomes clear which regulations each procedure needs to satisfy, and gaps show up as procedures with no coverage for a requirement that clearly applies. A compliance lead can look at a regulation and see every procedure it touches, or look at a procedure and see every requirement it should meet, and both views make it easier to plan reviews and to answer an auditor’s questions with something more solid than a spreadsheet maintained by one person.

The mapping takes some upfront effort, and the sensible way to start is with the regulations that carry the most risk and the procedures that are used most often, rather than trying to map the entire library in one pass. The attributes also need to be applied consistently, so a short agreed list of activity and hazard categories works better than letting each author invent their own, since inconsistent tags lead straight back to the same missed matches the mapping was meant to prevent.