Back to Blog
Blog

How do you handle site specific critical controls within an enterprise standard?

How do you handle site specific critical controls within an enterprise standard?

Enterprise standards set the minimum controls every site has to meet, but sites have different equipment, layouts and hazards, so they often need extra…

Enterprise standards set the minimum controls every site has to meet, but sites have different equipment, layouts and hazards, so they often need extra controls or different ways of meeting the same requirement. A site with older equipment may need additional isolation steps, a site in a hot climate may need heat stress controls that others do not, and a site with a particular process may face hazards the enterprise standard only covers in general terms.

Forcing every site to use exactly the same procedure usually leads to either unrealistic procedures or quiet workarounds, because operators given a procedure that does not match their equipment will adapt it in practice. Once the written procedure and the actual work diverge, the company loses visibility of how the control is really being performed, which is the opposite of what a standard is meant to achieve.

The cleaner model is to keep the enterprise standard as the base layer and let each site add its own controls on top, with anything that changes or replaces an enterprise control going through review. Adding a control is usually low risk and can be approved locally, while changing how an enterprise control is met deserves review by the people who own the standard, since they can judge whether the site’s approach still achieves the same level of protection.

Layering site controls on the enterprise standard means the company can see where sites differ and why, and a change to the enterprise standard still reaches every site. When the enterprise team updates a control after an incident somewhere in the business, each site can see which of its procedures are affected and whether its local variations need to change too, rather than the update depending on someone at each site happening to notice it.

Keeping the variations visible also turns them into useful information, since a local control that several sites have adopted independently may be a candidate for the enterprise standard, and a variation that only one site has may need a closer look. Recording the reason for each variation when it is approved makes these reviews much easier, especially years later when the people who made the original decision have moved on.