Turn the new editions into a transition plan you can actually run

01HLS chapter-sharing map (9001 / 14001 / 45001)

02Shared vs standalone list (what changes once, what stays per-standard)

• Shared, done once: gap analysis against the two new editions, the context and interested-parties register (incl. the climate call), policy wording, planning of changes, and the four procedures — document control, internal audit, corrective action, management review.
• Standalone: environmental aspects and compliance obligations (14001), product and service controls (9001), worker participation and OH&S risk (45001), and operational controls per discipline — the soul of each standard; integration must not dilute them.
• One register, three tags: every risk / opportunity / nonconformity is tagged quality / environment / safety — a defective valve on a chemical line can be all three. Share the workflow, keep discipline-specific criteria (45001 risk = likelihood × severity of harm; 14001 works with aspects and impacts), and never force one scoring scale onto all three.
• Accountability across disciplines: risk-acceptance criteria are set by your own rules and funnel into one management review — one risk committee for three disciplines, not three parallel review boards.

03Which clauses share naturally, which must stay separate — and why

• Naturally shared: clauses 4, 7, 9 and 10 — These chapters carry identical clause numbers, order and titles across all three standards, and the substance of the requirements is nearly the same — the only difference is that each standard points at its own domain (quality / environment / OH&S). Doing them once satisfies all three at once, because when an auditor opens any of these chapters against any single standard, the file and the records are the same; writing three versions only manufactures the stitching seams of “three systems glued together”. Chapter 5 (leadership) is largely shared too, but each standard keeps its own 5.2 policy subclause, and 45001’s clause 5 is titled “Leadership and worker participation” with its own 5.4 on consultation — one integrated policy (with three sections) plus one worker-consultation channel covers it all.
• Must stay standalone: the clause-6 registers and the clause-8 controls — Clause 6 can share the framework (one register, three tags), but the evaluation criteria must stay separate — 45001 rates OH&S risk as the combination of the likelihood of a hazardous event or exposure and the severity of harm, while 14001 works with environmental aspects and their impacts; the two concepts cannot impersonate each other, and forcing one scoring scale onto all three sands professional judgment flat. Clause 8 operational control is the soul of each standard: product and service control, aspect control and hazard-hierarchy control each get their own section — unify the templates and forms, never merge the content.
• Why “one register, three tags” holds — Because the three standards share the same logical skeleton for risk — identify, evaluate, treat, review — and differ only in object and criteria. A shared workflow (identify → evaluate → treat → close) plus standalone criteria (each discipline’s own scales) means you neither rebuild three times nor dilute the disciplines. That is the commercial logic of the chapter map: what is shared is the process and document skeleton; what stays separate is the domain content.

04The business case for integration: how the numbers actually work

• One manual to maintain: revision cost scales with the shared share — Say you hold N controlled documents with a shared share of r (rule of thumb: aim ≥60% — see the gap checklist). Every system revision — such as this two-edition transition — needs sign-off, controlled distribution and training notification for one shared family plus three discipline increments instead of three full sets, so revision effort scales roughly with r rather than tripling. The bigger win is consistency: one revision takes effect for all three at once, eliminating the “fixed the quality manual, forgot the environmental one” version drift that auditors love to probe.
• One internal-audit plan: one calendar, one audit team — Three audit programmes merge into one annual schedule, one team and one mobilization. Operations get audited once for all three disciplines instead of three visits a year; findings reuse across disciplines naturally — the same production line need not be examined twice, once by the quality audit and again by the environmental audit.
• One CAPA stream: same root cause no longer opens three nonconformities — Under separate systems, one tripped breaker can trigger three nonconformity tickets from quality, environment and safety, with root-cause analysis done three times and corrective actions fighting each other. On one CAPA stream: one ticket, three tags, one root-cause analysis, one set of actions — and the economic call (fix the equipment or change the procedure) is made once.
• One management review: three agendas, one meeting — Top-management time is the scarcest resource. After integration the review inputs and outputs are matched in three blocks, so quality, environment and safety performance are covered in one meeting, and cross-discipline trade-offs (budget to test equipment or to guard retrofitting) are made in the same room — a decision perspective separate systems can never produce.

01The rule

• 20% is the hard cap — Under the accreditation framework (Global ACI — ILAC and IAF combined operations from 1 January 2026), a certification body may audit an integrated system in one combined visit, but the reduction is capped at 20% of the sum of the standalone audit times. A bigger “discount” does not exist within accreditation — whoever promises more is either off-script or cutting your audit coverage.
• What is saved is structural duplication, not audit depth — The saving comes from three places: three document libraries become one, three audit programmes become one, three reviews become one — the audited object itself shrinks. What cannot be saved is the audit depth of each discipline’s operational controls: aspects, product controls and OH&S risks are checked as before.
• Put the transition audit inside the next surveillance — Transition can happen at a scheduled surveillance or recertification audit, or as a separate visit. For three-certificate holders: change the shared elements once and negotiate one combined transition audit — the 14001 (2029-04-30) and 9001 (2029-09-30) cutoffs are close enough to plan together.
• Extra time has an official standard: “possible”, but must be justified — The official transition requirements (TECH-3-TR) rate extra time as “possible”: the CB must justify it per ISO/IEC 17021-1 and IAF MD 5 (historic file name; Global ACI TECH-3-004), considering at minimum the degree of system change and whether the audit rides the annual visit; the note states a full system audit may need none. On the ground: ask for the justification before accepting a surcharge — “because transition” is not one.

02Worked example of the 20% cap (illustrative — always price with your CB)

• The example set up — Assume standalone audit days of ten for 9001, eight for 14001 and seven for 45001 (numbers purely illustrative). Standalone the total is 25 days; for an integrated audit the combined base is that same 25 days, and the 20% cap equals 25 × 20% = 5 days. The plausible range for the integrated audit is therefore 20-25 days: 25 at the top (no reduction), 20 at the floor (cap fully applied). Where inside the range you land depends on the CB’s assessment of shared depth, team composition and site conditions. The example also hands you a ruler: against a 25-day base, any quoted integrated total can be sanity-checked — a quote above the 25-day standalone sum is an arithmetic error, and a quote below the capped 20 days already breaks the accreditation limit; in both cases require the calculation in writing.
• Where you land is the CB’s own algorithm — The actual reduction is the CB’s own calculation; the accreditation rule caps it but guarantees nothing. Negotiation script: ask the CB to quote the standalone days per standard and the integrated days, then check the reduction sits within 20%; a “discount” beyond 20% either breaks the accreditation rule or hides a cut in audit coverage — probe both. Again: this example only explains the structure; actual days and fees always come from your CB’s quote.
• What triggers extra time — Under the official wording, extra time is “possible” and must be justified. Common triggers: multi-site operations (controls and sampling across several locations), high risk (heavy on-site verification for chemical processes, work at height, confined spaces), wide scope (many product lines or service types widening the sample), and a large degree of system change (transition stacked on integration is the widest). Conversely, with a simple system, one site and deep sharing, a full system audit may need no extra time at all — the official note says exactly this. When extra time is contested, ask the CB to anchor the justification in specific clauses of 17021-1 and MD 5, not in “practice”.
• Where the reduction comes from: three structural duplications vanish — The 20% is not the auditor’s discount — the audited object genuinely shrinks: three document libraries become one (document review no longer walks three controlled directories), three audit programmes become one (internal-audit results cross-reference), three management reviews become one (outputs cover everything at once). These three merges are exactly what your transition project was going to do anyway — so the order “integrate first, then discuss audit days” stands naturally: the deeper the integration, the closer the reduction sits to the cap; a “integration” with three separate file sets gets priced by the CB as three separate systems.

01The six phases

• Phase 1: 9001 as the foundation — Quality management offers the strongest process framework. Use the existing QMS as the backbone and layer environmental and safety requirements onto it — not a third system from scratch. Action: run the quality-side gap analysis against the two 2026 editions and set governance (a single management representative). Goal: fix integration governance and scope, and surface the quality-side gaps. Deliverables: integrated scope and site list, the management-representative appointment, a 9001:2026 gap-analysis report, and a project milestone table. Common failure: going straight to document edits and skipping governance — with no single owner, three file sets collide halfway through; and writing a gap analysis that restates standard clauses without checking your own processes, producing a report that drives no action.
• Phase 2: add 14001 — Identify environmental aspects, compliance obligations and operational controls, mapped into the existing clause structure. Action: expand the context analysis (climate / biodiversity / pollution / resources), land the new 6.1.4/6.3 documents, upgrade the compliance register — shared parts (context register, change planning) done once for both. Goal: fold the environmental dimension into the shared frame and finish the environmental specials in one pass. Deliverables: the expanded context and interested-parties register, new 6.1.4/6.3 procedures and record forms, the upgraded compliance-obligations register, and aspect-evaluation records (including life-cycle perspective and abnormal/emergency conditions). Common failure: aspect identification reduced to three lines on wastewater and exhaust while missing life-cycle perspective and abnormal/emergency conditions; and a compliance register that lists regulation names without applicable clauses or a method for evaluating compliance status — the two spots where certification auditors most often raise findings.
• Phase 3: layer in 45001 — Bring in hazard identification, risk assessment, worker consultation and the hierarchy of controls. ISO 45001:2018 remains the certifiable edition — this phase pre-wires the interfaces: a safety column in the shared register, a safety row in the competence matrix, with the standard-side revision after the new edition publishes. Goal: bring the safety dimension in, land the interface pre-wiring, and keep 45001:2018 compliance intact. Deliverables: hazard-identification and risk-assessment records (attached to the shared register), worker-consultation channels and records, the safety column/row in the shared register and competence matrix, and a pre-study list along the DIS direction (covered by this pack’s free update). Common failure: treating 45001 as a paper exercise — no genuine consultation, workers unable to answer a single question, and a straight nonconformity on 5.4; or rewriting documents ahead of the new edition only to rework them when the DIS differs from the final text — pre-wire the interfaces, never pre-rewrite the content.
• Phase 4: unify documentation — Merge three sets of policies, manuals and procedures into one document family. Action: one numbering scheme, one integrated manual (built on this pack’s skeleton), the shared-document map fully tagged, and the four procedures (document control / audit / CAPA / review) merged. Goal: one document family out of three, one numbering scheme, one revision effective for all three. Deliverables: the integrated manual, the four merged shared procedures, the final tagged shared-document map, the unified numbering rules, and a hierarchy note (manual / procedure / work instruction / form, four levels). Common failure: merging to the lowest common denominator so the discipline-specific requirements are sanded off (see obstacle 5) — the costliest rework of this phase; and over-deep document hierarchies that live in silos, breaking the reference chain at level three so an auditor’s trail runs into a dead end.
• Phase 5: integrated internal audits — Train cross-discipline internal auditors and build a combined schedule covering every clause of all three. Action: one integrated internal audit over all clauses (discipline criteria kept separate), one report with conclusions per standard, and nonconformities in a single CAPA stream. Goal: use one integrated internal audit to verify the documents and operations actually close the loop. Deliverables: the annual integrated audit programme (objective defined per audit), the integrated audit report (conclusions per standard), the nonconformity and observation list (one CAPA stream), and cross-discipline auditor competence records. Common failure: internal auditors who only know one standard, missing cross-discipline clauses such as 6.3 change and 7.4 communication; and findings all softened into observations with no nonconformities raised — the problems simply detonate at the certification audit, at the highest possible price.
• Phase 6: combined certification audit — Choose a certification body accredited for all three standards and run one integrated certification audit. Action: lock the arrangement in writing per the CB checklist; the integrated-audit time reduction caps at 20% (see its dedicated document); the 45001 transition follows as a third wave after the new edition publishes. Goal: pass one integrated certification audit and land two new-edition certificates. Deliverables: the eight written confirmations with the CB, the integrated audit schedule with itemized pricing, the transition-audit report and new certificates, and the third-wave pre-briefing minute. Common failure: booking the audit before confirming the CB’s own transition decision — if the CB has not yet passed its accreditation transition (9001 side: AB decisions by 2027-09-30), the audit runs but no certificate can issue; and squeezing the 45001 transition into the same audit — with the new edition unpublished, the third wave can only be pre-studied, and “expected” wording in the contract will be bounced by the body’s legal review.

01The three steps

• Step 1 · Prepare — Leadership alignment and scope: top management commits to one transition for all three; define the integrated scope (sites / products / activities); appoint a single management representative for the integrated system; estimate the share of common documents. Key move: get the three transition timelines (14001 earliest, 2029-04-30) and let the earliest cutoff set the project cadence. Actions in detail: (1) collect the three official transition requirements (Global ACI-TECH-3-TR) and align the AB/CB milestones with your own certification cycle; (2) have top management sign one integrated-transition decision (budget, staffing, milestones included); (3) define scope across sites, products/services and activities — the three scope statements may differ in wording but must match in coverage, otherwise the integrated audit’s sampling base is tilted; (4) make a first estimate of the shared-document share (count common-topic files across the three controlled sets) — this number sizes both the benefit and the resourcing.
• Step 2 · Connect — Map each standard’s requirements onto existing processes: use the shared-chapter map to mark shared / shareable / standalone; map the two new editions’ changes (9001 culture & split, 14001 expansion & change management) into shared processes; build a shared risk-opportunity register (quality / environment / safety in columns). Key move: by the end of this step you hold a three-way requirements→process→document matrix. Actions in detail: (1) mark the chapter map item by item into the matrix — every standard clause number must point to a process name and a document name; anything that cannot is a gap; (2) map the new-edition changes one by one — 9001’s culture and split, 14001’s expansion and change management, the clause-10 renumbering in both — into the revision list for each shared document; (3) design the register table in one pass (columns for system tag, description, evaluation criteria, action, owner, status), with discipline criteria in their own columns, never mixed; (4) cross-check: how many standards reference each process? The ones referenced by all three are the first merge candidates — that is where the matrix pays off.
• Step 3 · Integrate — Close gaps and embed into daily operations: revise shared documents per the matrix; combine the audit programme and run one management review; embed culture, change and emergency routines into existing meetings and dashboards rather than parallel mechanisms. Key move: the acceptance test is “an auditor can’t tell this was three systems stitched together” — one numbering scheme, one record format, one dashboard. Actions in detail: (1) batch-revise the shared documents and sign off once, effective for all three — no half revisions like “quality first, environment and safety next quarter”; (2) merge the audit programme and the review agenda, then run one integrated internal audit to test how the new documents really work (objectives defined per audit as the 2026 editions require); (3) embed into the routine: culture indicators on the meeting dashboard, the seven change factors in the change-request form, worker consultation in the shift-meeting record — integration is not one more mechanism, it is fitting three systems’ requirements into the motions you already run; (4) accept it through an “auditor’s eyes”: ask a colleague who was not on the project to walk the documents against a single standard, hunting for stitching seams — any seam found means integration is not done.

02Three-step self-check (9 actions)

• Prepare: top management signs one integrated-transition decision (one document, not three). Why: a single decision keeps budget and cadence unified; three decisions announce half of the integration has already failed — every turf fight downstream traces back here.
• Prepare: integrated scope and site list finalized; a single management representative appointed. Why: the scope and site list is the sampling base of the integrated audit; the representative must hold real authority to draw resources across all three disciplines — a title without authority equals no appointment.
• Prepare: three cutoffs on the wall, with 14001 (2029-04-30) setting the pace. Why: back-plan every phase from the earliest cutoff and stagger the 9001 and 45001 work around it; a project plan without dates on the wall is a wish list.
• Connect: mark the shared-chapter map item by item (shared / shareable / standalone). Why: the marks generate the merge list directly — keep what is shared, schedule what is shareable, keep the domain version of what is standalone; skip this and every file’s ownership becomes an argument.
• Connect: map the new-edition changes into shared processes (9001 culture & split; 14001 expansion, change management, emergency scope). Why: every new-edition change must land on a concrete document revision — a change that lands nowhere is an undigested gap, and the certification audit will find it for you.
• Connect: shared risk-opportunity register built (quality / environment / safety columns, one mechanism). Why: design the columns once with discipline criteria kept apart — every risk, opportunity and change from all three systems enters this table, and reworking its structure means reworking every record in it.
• Integrate: shared documents revised; one numbering scheme and format. Why: revisions follow the matrix — no half revisions that update the manual but not the procedures, or the procedures but not the forms; wherever the reference chain breaks, that is where the auditor raises the finding.
• Integrate: run one combined audit programme cycle; one management review covering all three. Why: integrated-audit conclusions come out per standard so each certificate takes what it needs; the review decisions must cover improvement directions for all three — a quality-only review never happened for the other two.
• Integrate: culture, change and emergency routines embedded in existing meetings and dashboards. Why: the acceptance line is that daily motions already carry the three systems’ requirements — people do not act “for the system” on top of the work; any integration that demands extra motions will not survive its first year.

01The five obstacles

• Obstacle 1: split departmental ownership — Quality, environment and safety usually sit in different teams with different reporting lines, so nobody owns the whole after integration. Countermeasure: clear governance — appoint a single management representative (or IMS manager) for all three; the discipline leads stay as domain owners; cross-cutting topics go to one risk committee. Root cause: organizations are designed by specialization and the systems copied that structure — three reporting lines will not merge on their own, and waiting for them to is waiting for an event that never happens. Verify it works: all controlled documents across the three systems have one owning approver; cross-discipline topics appear in the same risk-committee minutes; domain owners’ job descriptions state their integration duties — with all three on record governance is real; miss one and it is governance on paper only.
• Obstacle 2: maturity gaps — A QMS may have run for a decade while the EMS launched last year — aligning uneven maturities creates fake sharing. Countermeasure: run an honest maturity assessment first, and integrate from the most mature system (why Phase 1 of the roadmap is 9001-first); newer systems close their basics before joining the shared frame. Root cause: a maturity gap is really a gap in the completeness of basic motions — a new system that cannot even collect its records has no business sharing a process with a mature one, and forcing it spreads the weak system’s problems into the strong one. Verify it works: before each new system joins the shared frame, its own internal audit demonstrates a closed basics loop (nonconformities close, records trace); in its first cycle inside the frame its clauses produce no cluster of findings; and the assessment result plus the integration order exist in writing — so when an auditor asks “why integrate in this order”, you hand over a report.
• Obstacle 3: staff resistance — Staff used to their own discipline see merged processes as extra burden. Countermeasure, three parts: training (how the shared flow works), visible leadership commitment (the management representative explains integration wins in routine meetings), and embedding shared records into existing forms (one form with three tags, not three forms). Root cause: resistance is not really “against integration” — it is against doing more without doing less; three forms collapsing into one wins support, while one form trailed by three annexes earns universal opposition. Verify it works: spot-check operations after training (randomly ask staff to walk a shared form); after the shared form goes live, the old forms record zero submissions; in shift meetings staff can name what they stopped filling in — if they cannot, the burden never dropped and the resistance will be back.
• Obstacle 4: auditors competent in all three are scarce — Combined audits need audit teams competent across quality, environment and OH&S — not every certification body can staff them. Countermeasure: make “accredited for all three + able to field a cross-discipline team” a precondition in the CB checklist; build your internal-audit bench the same way. Root cause: cross-discipline audit capability stacks experience in three standards, so supply is naturally thinner than for single-standard auditors — this is a supply-structure problem, not a price problem, and no amount of urgency can buy what is not there. Verify it works: every member on the CB’s proposed team has checkable credentials (accreditation across the three plus domain background); at least two people in your internal bench have completed full audits of all three standards; the integrated audit schedule assigns the cross-discipline clauses (6.3, 9.2, 10.2) to named team members — get the roster and the split in writing before signing, because after signing they are unobtainable.
• Obstacle 5: integration diluting discipline depth — Shared documents written to the lowest common denominator sand off each standard’s specific requirements — the number-one integration failure and an auditor favourite. Countermeasure: write the manual by the three-lens rule (every shared clause reads through quality / environment / safety), flag standard-specific additions explicitly, and keep discipline criteria (scoring, evaluation scales) as standalone versions. Root cause: whoever writes the shared files usually knows one standard well, or none — the lowest common denominator is the default output of insufficient knowledge, not deliberate dilution; nobody can write a requirement they do not know exists. Verify it works: sample three shared clauses and walk each against a single standard’s audit logic — every one must pass and locate its discipline-specific content; the flags follow a fixed format (a “(45001)” prefix, say) and are synced through the reference chains of procedures and forms; and the latest internal audit raised no finding of the “shared document does not cover this standard’s requirement” kind — even one means dilution is still happening.

01Chapter-by-chapter skeleton

02Manual acceptance test (four “cans”)

• Every shared clause reads through three lenses: flip to any page and a quality / environment / safety reader each finds their requirement — if not, you wrote a single-system manual.
• Standard-specific requirements are explicitly flagged: life-cycle perspective, worker consultation, hierarchy of controls — marked in the manual so an auditor working to any single standard can find them.
• Clause references trace to all three standards: procedure citations support the three-line annotation (or a mapping table), so old- and new-edition references stay traceable through the transition window.
• No visible stitching: one numbering scheme, one manual, one CAPA stream, one dashboard — “an auditor can’t tell this was three systems” is the acceptance line.

01Shared-document map

02Merging the four shared procedures

• Document-control procedure — Merge points: one controlled list covers every document across the three systems, the numbering scheme embeds the system tag (a Q/E/S prefix or a three-tag column), and versioning, approval, distribution and withdrawal run on one process. The easiest miss: the “availability” basis for documented information is already unified in the 2026 editions, but the older “retain” wording can survive in record forms — sweep every form during the merge, because one record reading both “retain” and “available” invites the auditor to ask which basis is current.
• Internal-audit programme — Merge points: one annual programme with an objective defined for every audit (a hard 2026 requirement); criteria listed per discipline with domain experts on the team; one report with conclusions per standard. The easiest miss: sampling coverage — shared clauses need one sample, but the discipline clauses (chapter 8) must be sampled under their own criteria; and the auditor competence roster must show cross-discipline capability, otherwise your “integrated audit” reads to an auditor as three audits printed into one report.
• CAPA process — Merge points: one nonconformity ticket serves all three systems, carrying the system tag and clause-reference columns; root-cause tools are shared (5 Whys, fishbone), with discipline criteria affecting only severity grading; the effectiveness-verification step is uniform. The easiest miss: separating the intake for incidents (45001) from ordinary nonconformities — incident investigation has its own report requirement and should join the CAPA stream as the front end of 10.2, not run as a parallel lane; two intakes, one exit, and the flowchart must show the merger for the auditor to see.
• Management review — Merge points: one review covers all three systems with inputs and outputs matched block by block; cross-discipline topics (risk acceptance, resource allocation, policy revision) get their own agenda segment. The review may run as a series of top-management meetings, but the decisions must land in one minute. The easiest miss: the input lists differ — 9001 wants customer satisfaction, 14001 wants environmental performance and compliance evaluation, 45001 wants injury and participation data — so tick through a three-block input template, where any gap becomes the next audit’s lead; and the cross-discipline trade-offs (test equipment or guard retrofitting) must be decided in the same meeting — deciding them in batches means integration never happened.

03Three files that must never merge — and why

• The environmental-aspects register (14001) — Why it cannot merge: aspect evaluation addresses the aspects and impacts of activities, products and services, judged by the significance of environmental impact (including life-cycle perspective and abnormal/emergency conditions); no counterpart exists in the quality or safety systems. What can be shared is the carrier and the workflow — keep aspects as an “environment” section of the shared register or a standalone register with native evaluation criteria, and every record in the shared section must still stand alone under a 14001 clause audit.
• Compliance-obligations registers (14001 and 45001, each their own) — Why it cannot merge: the legal sources differ (environmental statutes versus OH&S statutes), and so do the duty holders, evaluation frequency and regulator reporting routes; blending the two domains into one register means a single missed legal update breaches both systems at once. What is shared is the framework — identify obligations → evaluate compliance → fix problems — while the registers stay per-domain; if separate registers feel heavy, at minimum use strictly separated sections with their own update owners.
• Hazard identification and risk evaluation (45001) — Why it cannot merge: OH&S risk is rated as the combination of the likelihood of a work-related hazardous event or exposure and the severity of injury and ill health, aimed at processes, equipment and behaviour, and must carry the process evidence of worker consultation; this scale is not interchangeable with quality risks or environmental aspects, conceptually or legally. The safety section of the shared register keeps its own criteria and participation-record columns — the merge boundary stops at the carrier, never at the method; if the evaluation records show no trace of worker participation, a 5.4 problem will surface through 6.1.2.

01Eight written confirmations

• Accreditation: the body holds valid accreditation for ISO 9001, ISO 14001 and ISO 45001 and can field a cross-discipline audit team. In writing: the accreditation-scope evidence (certificate annex or scope page) plus the proposed team roster with credentials. Watch for: headquarters accreditation shown while the local office holds none; or “multi-standard auditors” who actually hold a single-standard qualification — match every name to a credential, one by one.
• Integration offer: does the body provide integrated audits? If so, how is the schedule built, how is the team composed, and how are results reported (conclusions per standard, or one report with sections)? In writing: a sample integrated schedule, the team-composition note, and a report template with per-standard sections. Watch for: verbal “we can do integrated audits” with no sample schedule or report template — most likely three audits squeezed into the same days, reported separately and invoiced three times; the sample is your touchstone.
• Transition carrier: which audit carries each transition — the next surveillance, the recertification, or a separate transition visit — with time and cost differences for each. In writing: a comparison table of the three carrier options (surveillance, recertification, separate visit) with timing and pricing. Watch for: a default push toward the “separate transition audit” without mentioning it can ride the surveillance or recertification — the separate visit is usually the pricier route and the CB owes you no savings; the table must price all three.
• Days and pricing: any extra time must be justified in writing per ISO/IEC 17021-1 and IAF MD 5 (TECH-3-004) — require: total days for the integrated audit, how the 20% cap is applied, the extra-time justification, and an itemized quote. In writing: standalone days per standard, integrated days, the reduction calculation, the extra-time justification anchored to specific clauses, and an itemized quote. Watch for: verbal extras like “we usually add a day” — the official wording is “possible, must be justified, and a full system audit may need none”; and hidden integration surcharges inside the quote — ask item by item “what is this and why is it charged”.
• Combined transition: can the 14001 (cutoff 2029-04-30) and 9001 (cutoff 2029-09-30) transitions run as one combined audit (shared elements changed once)? A separate audit is the body’s call. In writing: the combined-transition schedule plus separate completion commitments for both cutoffs (14001 by 2029-04-30, 9001 by 2029-09-30). Watch for: refusing the combination on “our system can’t schedule it” with no rule behind it — the cutoffs are adjacent and combination is feasible in most cases; the answer should be a technical reason on the spot, not a process excuse.
• The 45001 handling: confirm ISO 45001:2018 + Amd1:2024 stays the certifiable edition, with a third transition wave scheduled once the new edition publishes under Global ACI’s own timetable. In writing: a confirmation letter that 45001:2018 + Amd1:2024 remains current, plus a pre-briefing minute for the third wave. Watch for: the expected timeline written into the contract as a commitment — the transition period is unpublished (by convention about three years, expected in H1 2030; an estimate, not an official promise); the contract may only say “per the transition requirements announced at the time”, and any clause with a specific date should be bounced by legal — yours or theirs.
• Evidence compatibility: how the body accepts dual clause references during the transition window — can records carry both old- and new-edition clause citations? In writing: the body’s stated position on dual references (a written reply or email). Watch for: a verbal “no problem” followed by audit reports returned for rework — demand a written position and confirm your records system can carry both citations; internal audits during the transition will inevitably cite both editions, and without a written position you are laying a trap for yourself.
• Calendar lock: after confirming the three transition-audit dates plus the integrated audit and review dates, put them on the certification calendar — confirmed in writing, never by word of mouth. In writing: a certification-calendar confirmation letter (the three transition-audit dates plus the integrated audit/review dates) and the body’s duty to notify in writing of any delay. Watch for: locking only your side of the dates while the body’s own milestones stay unlocked — if the CB has not passed its own transition decision (9001 side: by 2027-09-30), your whole schedule voids; the letter must state the premise “subject to the body’s accreditation readiness” with a notification deadline if that slips.

01Unified milestone timeline

02Concrete pre-wiring actions for the 45001 third wave

• Reserve manual sections — Reserve a “OH&S operational control (new-edition alignment placeholder)” section inside chapter 8 of the integrated manual, stating that the section follows the expected direction of ISO/DIS 45001 and will be aligned within 90 days of publication; placeholder paragraphs go into the worker-consultation section of chapter 5 and the safety section of the register in chapter 6 too. The point of reserving: after publication you replace content without touching the document skeleton — the third wave drops from “rewrite” to “fill in the blanks”, which is the only way it fits a 90-day alignment window.
• Reserve a competence-matrix column — Add an empty “45001:2027 competence requirements” column to the matrix and keep maintaining the role rows; reserve the matching column and budget line in the training plan. After publication, fill the column row by row against the new clauses’ competence requirements, and the gaps flow straight into the training plan — the competence side of the third wave becomes one matrix update instead of a from-scratch resurvey; the empty column itself also shows an auditor you are waiting for the standard, not forgetting it.
• Reserve a checklist block — Build the internal-audit checklist on the current 45001 clause structure and add a “2027 mapping” placeholder tab: once the final text publishes, fill in the old-to-new clause mapping, run one clause walkthrough on the placeholder tab to confirm the shared processes cover the new structure, then fold the tab into the formal checklist — the first audit of the new edition starts with a complete mapping instead of guessing clause numbers mid-audit.
• Pre-wiring discipline — Pre-wire interfaces, never content: placeholders follow the expected DIS direction, and rewriting live documents against the draft is forbidden — the DIS and the final text may diverge, so premature rewriting writes rework into the plan. The trigger for every pre-wiring action is “the final edition publishes”, sharing one closure line with item 5 of the gap checklist; placeholders state the expected basis and the update commitment (this pack updates free of charge on publication), so an auditor reading a placeholder sees a controlled wait, not an uncontrolled blank.
• How to spend the gap between waves — The gap between waves is not idle time but digestion time: close the previous wave’s findings, finish the training on the revised documents, and run one full cycle of records — keep at least one quarter of record-running between waves so the evidence grows itself rather than being manufactured two weeks before the audit. Put the gap’s usage into the project milestones: dates for finding closure, training completion, and the record-running window — a dated gap has discipline; an undated one gets eaten by daily business.
• Set the third wave’s acceptance line now — Set the third wave’s acceptance line now: align the documents within 90 days of publication, run one integrated internal audit covering the new structure within 180 days, and put new-edition clause topics on the next management review — three dates into the project milestones, with the clock starting on publication day. Fixing the acceptance line early means the pre-study team never re-debates “how deep” after publication and goes straight to execution; that is the line between pre-study and procrastination — with an acceptance line it is a project, without one it is delay.

01Gap checklist (tick off as you close)

• List the shared controlled documents (use the map): one numbering scheme, one revision, effective for all three. Owners: the system lead (list and share statistics) and the document controller (directory merge). Done when: the shared share is quantified (aim ≥60%) with a catch-up plan for any shortfall below it, the directory is merged, and the retirement of the old directories is on record.
• Merge 9001 quality culture, 14001 environmental culture and 45001 safety culture into one “organizational culture” leadership process. Owners: the management representative (merged procedure and indicators) and the three discipline leads (module content). Done when: one procedure, one indicator dashboard and one standing review item exist — and all three discipline leads have signed the procedure (a “merge” signed only by quality is not one).
• Use 14001’s 6.1.4/6.3 as the shared risk and change framework, with the shared register running in columns. Owners: the risk-committee chair (framework setting) and each discipline lead (criteria-column upkeep). Done when: risks, opportunities and changes from all three systems live in one register and one process, the discipline criteria columns are maintained with update records, and any sampled record shows all four elements — tag, criteria, action, owner.
• Combine the audit programme and run one integrated audit + one management review for all three. Owners: the lead internal auditor (programme and report) and the management representative (review organization). Done when: one programme, one integrated audit report and one review minute (with decisions for all three) exist — and every audit’s “audit objective” field is filled; an audit without an objective is a non-compliant audit under the 2026 editions.
• Do the 45001 “expected” pre-study: prepare shared interfaces for hazards / participation / emergency along the DIS direction; align via the free update once published. Owners: the 45001 pre-study owner (named by the system function) and the management representative (post-publication acceptance). Done when: the pre-study list exists and the three pre-wiring actions have landed (reserved manual section, competence-matrix column, checklist block), with alignment completing within 90 days of publication — counted from publication day, not from pre-study completion.
• Stagger the certification calendar: 14001 (2029-04-30) first, 9001 (2029-09-30) next, 45001 (expected ≈2030) later — schedule each transition audit into the nearest surveillance/recertification window. Owners: the certification coordinator (schedule and body confirmation) and the management representative (milestone approval). Done when: all three transition-audit dates are confirmed with the certification body in writing and placed on the certification calendar, with enough gap between waves to close the previous wave’s findings — a schedule too dense to breathe is no schedule.

02Diagnosing maturity gaps (they decide the integration order)

• Compare internal-audit nonconformity counts — Pull the latest internal-audit nonconformity and observation lists per system and count them separately: a large spread (say single digits on quality versus dozens on safety) marks a clear maturity gap — integrate from the system with fewer findings and a higher closure rate (usually 9001), and let the heavy system burn down its backlog before joining the shared frame. The comparison table is itself maturity evidence for management review; and the closure rate says more than the raw count — many findings closed fast beats few findings all left hanging.
• Survey document-version disorder — How many versions of the same-topic file live across the three directories? How wide is the revision-date spread? How many broken links? Survey three indicators: same-topic file count (three parallel sets = duplicated build), days since the latest revision (long-unrevised = a dead file), and the dead-reference rate (citations pointing at withdrawn files = failed control). Merge the most disordered domain first — merging is itself a dredging operation; the survey also answers the auditor’s certain question “how do you maintain your document system” — three directories with three numbering schemes are an incubator for document-control findings.
• Compare management-review decision closure — Check the implementation status of each system’s management-review decisions one by one: a low closure rate (items stuck at “in progress” for ages) means the improvement mechanism does not really run — fix the mechanism before integrating, or integration merely welds three broken mechanisms into one bigger broken one. Write the diagnosis into the project plan: which systems join first, which need remedial work first, and what each entry condition is — an integration order with entry conditions survives the certification auditor’s probing of project management far better than an “all at once” plan.