How to keep SOPs current across multiple plants
Every plant you add multiplies the gap between what's written and what actually happens. Here is how to keep one procedure true across all of them.

- With more than one plant, each site's real work drifts from the written procedure in its own way, and the copies drift from each other.
- Keep one controlled procedure per process, organized by location, instead of a copy per plant.
- Compare the real work at every site with that procedure, so you can see where each plant has drifted and whether the difference is a problem or a better method.
- Run every change through one approval route that shows each location it touches, roll it out one site at a time, and retrain at every location.
One plant has one gap between what's written and what actually happens. Two plants have at least three: each plant's own gap, plus the gap between the two plants' copies of the procedure. By the time a company has five sites, the same process is often run five ways, and nobody can say which one the document describes.
Why do SOPs drift apart between plants?
Every plant keeps its own copy. A procedure written at one site gets adapted at the next, for different equipment, a different layout or a different customer. Each copy changes on its own schedule.
Improvements stay local. When one plant finds a better way to do a step, it rarely makes it back to the master procedure, and almost never to the other plants.
Nobody can see the difference. Corporate quality sees the documents, not the work. The differences only surface in a customer complaint or an audit finding at one site.
Should every plant run exactly the same procedure?
Not always. Some differences are justified by equipment, material or local rules. The goal is not identical work everywhere. It is that every difference is known, approved and written down, instead of discovered during an audit.
How do you keep procedures current at every site?
Keep one controlled procedure, organized by location. Each site works from the same approved source, always on the latest version, with old versions kept but never confused with the current one.
See where each plant has drifted. When the work runs through the procedure at every site, each reading, photo and decision is recorded against its step. That shows where one plant does a step differently from the others, and lets you ask whether it is a problem or a better method that every site should adopt.
Change once, roll out site by site. In Vexum, every change shows each procedure, location and training it touches before anyone approves it. It can go live at one plant or line first, then expand, and everyone trained on the old version at every site is flagged for retraining.
Keep the systems each plant already runs. Plants rarely run the same ERP, MES or QMS. Vexum builds an integration for each system a plant uses, read-only by default, and replaces none of them.
The best method in your company is probably already being used at one of your plants. The trick is seeing it.
What does drift between plants look like?
Take a changeover procedure written at the first plant. The second plant has a newer press, so operators skip a warm-up step the procedure requires. The third plant added a first-piece measurement after a customer complaint two years ago, and never told anyone. On paper, all three plants run the same procedure. In practice, there are three procedures, one of which is better than the document and one of which is worse.
When the work at each site is recorded against the same steps, those differences stop being anecdotes. Corporate quality can see that one plant skips step 3 every time and another adds a check after step 5. Then the conversation becomes useful: should the second plant's warm-up step be removed for newer presses, and should the third plant's check be added everywhere?
How should you handle legitimate local differences?
Write them down as part of the procedure, with the reason, instead of letting each plant keep a private copy. A difference that is approved and visible is a variant. A difference nobody approved is drift. The test is simple: if an auditor asked the plant manager why the step is different here, could they point to the approved reason?
Who should own a procedure that runs at several plants?
One owner, usually in corporate quality or engineering, with a reviewer at each site. The owner approves changes; site reviewers confirm the change works with their equipment before it goes live there. Rolling out to one plant first gives the owner evidence from real runs before the change reaches everyone.
What should you look for in software?
- One controlled version per procedure, organized by location.
- The real work compared at every site against the approved procedure.
- Procedures not being followed, by plant, line and step.
- One approval route that shows every location a change touches.
- Gradual rollout, one plant or line first.
- Automatic notifications when SOPs change, with training assignments at each location.
See how it works in SOP management and document control.
Frequently asked questions
Can one plant pilot a change first?
Yes. In Vexum a change can go live at one line or location, then expand to the rest when you are ready.
Do our plants need the same systems?
No. Vexum builds a custom integration for every system each plant uses, read-only by default, and replaces none of them.
Does this replace our QMS?
No. Vexum connects to your QMS and exports its record of every approved change to it.
If you run procedures at a manufacturer and want to see where your written procedures and the real work differ, request a demo.
Get new posts by email
Product news and notes on procedures, change and training.

