Back to Blog
Blog

How do you keep procedures current after acquisitions bring in different SOP libraries?

How do you keep procedures current after acquisitions bring in different SOP libraries?

An acquisition usually hands you a second procedure library with its own templates, numbering and approval process, and the easy choice is to leave it…

An acquisition usually hands you a second procedure library with its own templates, numbering and approval process, and the easy choice is to leave it alone until someone has time to merge the two. The risk is that both libraries keep drifting and nobody is sure which standard applies at which site, which becomes a real problem once people, contractors and lessons learned start moving between the old and new parts of the business.

The drift is not only cosmetic, since the two libraries often reflect different approaches to isolation, permits, hold points and sign offs, and a contractor who works at both sets of sites can end up following one company’s practice at the other’s facility. Audits and incident reviews get harder too, because the question of which procedure was in force at a site on a given day depends on which library that site still uses and whether anyone updated it after the acquisition.

The practical approach is to decide what is an enterprise standard and what is genuinely site specific, then bring both libraries into one structured system so they follow the same review process going forward. Enterprise standards tend to cover the things the company wants done the same way everywhere, such as lockout, confined space entry or critical control checks, while site specific procedures cover equipment, layouts and local conditions that genuinely differ.

Having every procedure in the same step based format is what makes the comparison possible in the first place, since it lets the team line up an acquired procedure against the existing standard step by step and see exactly where they differ. It is also what lets a change to the standard reach every site that uses it instead of only the ones someone remembered to update, because the standard is maintained once and the sites that follow it are known.

A sensible rollout starts with the procedures that carry the most risk and the ones used at the most sites, rather than trying to merge everything at once. Acquired sites should be part of the review rather than having the existing standard imposed on them, since their procedures sometimes handle a task better, and the merge is a good chance to adopt the stronger version across the whole company.