Running the ISO 9001:2026 transition while an ERP rollout is happening.
ISO Cloud Consulting editorial teamYou can run the ISO 9001:2026 transition during an ERP rollout if you treat them as one plan for one workforce. Log the ERP as a planned change, design its records with quality input, sequence procedure updates after the ERP design is stable, combine training, and keep one change log for both projects.
Can the transition and an ERP rollout run together?
Many companies are facing two large projects at the same time this year: the ISO 9001:2026 transition and a new enterprise resource planning system, or ERP. Run them separately and they will fight over the same people. Run them together and each one can make the other easier.
Why does one workforce matter?
Start by recognizing that it is two projects and one workforce. The same production managers, buyers and quality staff will be asked to attend ERP workshops, test new screens, update procedures and attend awareness training, all in the same months. If nobody plans that load as a whole, both projects slip, and the quality system is usually the one quietly neglected.
Why treat the ERP rollout as a planned change?
The second point is that the ERP rollout is a planned change to your quality system. The 2026 edition strengthens the expectations around planning changes. That means considering the purpose, the possible consequences, the resources, communication, monitoring and review. An ERP rollout touches purchasing, production, inventory, traceability and records. It is exactly the kind of change the standard has in mind. So log it as one, and manage the quality impacts deliberately. That gives you, in one go, an excellent piece of transition evidence.
How do you design records once?
Third, design records once. The ERP will generate records your quality system depends on: purchase orders, goods receipts, batch or lot traceability, inspection results, nonconforming stock. If the ERP team configures these without quality input, you will end up with parallel spreadsheets for years. Put a quality representative on the ERP design team, and for every process ask which records the ERP should produce, so that nobody has to fill them in somewhere else.
How should the work be sequenced?
Fourth, sequence the work sensibly. Do the gap analysis and the transition planning early, because they need little system change. Leave procedure updates for the processes the ERP touches until the ERP design is stable, so you write them once. Schedule your internal audit and management review after go-live, when the new processes have produced real records.
Why build one training plan?
Fifth, build one training plan. People should not attend an ERP session on Tuesday and a quality awareness session on Thursday covering overlapping topics. Combine where you can. Teach the new process once, with the quality requirements built in.
How does the change log tie it together?
Finally, use the change log throughout. Every significant decision, deferral and risk goes in one place, with an owner. At management review, that log tells the story of both projects and shows the new edition's change expectations being met in practice.
Done this way, the ERP becomes the backbone of the new quality system rather than a competitor for attention.
Which tools help?
The Change Management Procedure & Log is built around the change considerations described here. For the transition itself, see the ISO 9001:2026 Gap Analysis Workbook, the ISO 9001:2026 Transition Toolkit and the ISO 9001:2026 Internal Audit Checklist.
