NewIntroducing the Vexum advisory boardRead the announcement
All posts · 7 min read

How a change gets back into the procedure

A walk through one change in Vexum, from what people did on real work to a new version that is live everywhere.

VexumVexum
An approval stamp on a signed document next to a seal with a check mark
In short
  • Procedure change control is how a manufacturer proposes, reviews, approves, publishes and trains on a change to a written procedure, with a record of every version and signature.
  • In Vexum a change moves through five steps: work the procedure, compare what people did with what’s written, suggest a change, approve it on your route, then publish and retrain.
  • In this example, four of the last five customer complaints were contained differently from the written step, so that difference became a suggested change from version 3 to version 4.
  • Old versions are never overwritten, every signature is recorded, and people trained on the old version are flagged to retrain.

Most procedures change slowly because changing them is hard work. Someone has to notice the problem, write the change, get it approved, publish it and make sure people are trained on it. Here is how one change moves through Vexum, using a step from a customer complaint procedure.

What is procedure change control?

Procedure change control, also called document change control or management of change (MOC), is the process for changing a written procedure without losing control of it. A good process answers the same questions every time: what is changing, why, what else it affects, who approved it, when it went live and who needs to be retrained.

For many plants it’s also a requirement. ISO 9001:2015 asks organizations to control their documented information (clause 7.5.3) and to review and control changes to production (clause 8.5.6). Plants with processes covered by OSHA’s Process Safety Management standard need written procedures to manage changes, including changes to operating procedures, and must inform and train affected employees before start-up (29 CFR 1910.119(l)).

Where procedure changes usually stall

  • Nobody sees the problem. The evidence that a step is wrong is spread across records, emails and people’s heads.
  • Writing the change takes time. Someone has to draft it, explain it and find the documents it affects.
  • The impact is unclear. It’s hard to know which other procedures, locations and training a change touches.
  • Approvals happen in email. Signatures get lost, and the record of who approved what is hard to rebuild.
  • Rollout is uneven. One location gets the new version, another keeps working from the old one, and retraining is tracked in a spreadsheet.

Each of the five steps below removes one of those stalls.

A worked example: one change, start to finish

Step 5 of the procedure, Decide containment, says: hold every lot in the date window.

1. Work the procedure

Your team works each complaint in the Vexum workspace, step by step. Vexum does the routine steps in your systems, like matching the complaint to the part and lot and pulling the inspection data. Your people make the decisions, and every step, reading and decision is recorded.

That record is what makes the rest possible. Without it, the only evidence of how the work is really done is what people remember.

2. Compare

Vexum checks what people did against what is written. Across the last five complaints, the team held only the lots made to the affected drawing in four of them, and recorded which lots they held. That isn’t what the procedure says.

One person doing something different is a one-off. The same difference across most runs is a pattern worth a look.

3. Suggest a change

The difference becomes a suggested change, with the reason attached. Anyone on your team can also propose a change on their own.

Customer complaint handlingv3 to v4
In review
Step 5 · Decide containment
WasHold every lot in the date window.
NowHold only the lots made to the affected drawing, and record which ones.
Reason

Suggested by Vexum from what people did in the last 5 complaints.

Approval route
QMQuality managerWaitingPMPlant managerWaiting
A suggested change shows what the step said, what it would say and why.

The suggestion is only a draft. Nothing changes until the people who own the procedure approve it.

4. Approve

Before anyone approves it, Vexum shows everything the change touches: the procedures that refer to this step, the locations that run it and the training built from it. Then the change follows your approval route, here the quality manager and the plant manager, and every signature is recorded.

5. Publish and retrain

Once it’s approved, version 4 goes live everywhere at once. Version 3 is kept, never overwritten. The people trained on version 3 are flagged to retrain, and their managers are told. The training is built from the new version, so people learn the step as it now reads.

What a procedure change record should include

Whatever system you use, every procedure change should leave a record that answers these questions. Here is the record for this change.

Change record: Customer complaint handling, version 3 to version 4
What changedStep 5, Decide containment
WasHold every lot in the date window.
NowHold only the lots made to the affected drawing, and record which ones.
WhyWhat people did in four of the last five complaints
What it touchesThe supplier escalation procedure, three locations and the containment training
Approved byThe quality manager and the plant manager, each signature recorded
Went liveVersion 4 at every location at once, with version 3 kept
RetrainingEveryone trained on version 3 flagged, and their managers told

Then the loop starts again

The next complaint runs on version 4. If people find an even better way, that difference shows up the same way, and the procedure keeps up with how the work is really done.

The point isn’t that Vexum writes your procedures for you. It’s that the work your team already does becomes the evidence for the next version, and the approved procedure stays the one everyone works from. For the bigger picture, read Every plant has two versions of every procedure, or see how Vexum handles engineering and supplier change and release and audit.

Frequently asked questions

What is management of change (MOC) in manufacturing?

Management of change is the process for reviewing and approving a change before it’s made, so its effects on safety, quality and other procedures are understood first. OSHA requires written management of change procedures for processes covered by its Process Safety Management standard, and many manufacturers apply the same discipline to every procedure change.

How do you update an SOP without losing control of it?

Treat every edit as a change. Record what changed and why, check what else it affects, send it to the right approvers, keep the old version, publish the new one everywhere at once and retrain the people who used the old one.

Who should approve a procedure change?

The people accountable for the work the procedure covers. In this example, a change to a quality procedure goes to the quality manager and the plant manager. Vexum follows the approval route each procedure already has, and records every signature.

What happens to old versions of a procedure?

In Vexum they’re kept, never overwritten. Every old version stays in the history, along with who approved it.

How do you make sure people are retrained after a procedure changes?

Tie training to the version. When version 4 goes live, everyone trained on version 3 is flagged to retrain and their managers are told, and the training is built from the new version.

Does Vexum change procedures on its own?

No. Vexum suggests changes from how the work is really done, with the evidence attached. People decide, and every change follows your approval route.

If you run procedures at a manufacturer and want to see a change move through Vexum on one of your own, request a demo.

Get new posts by email

Product news and notes on procedures, change and training.