ISO 22333 Revision CheckerISO/DIS 22333
Draft stage
40.60, close of voting
Voting closed
20 June 2026
Publication estimate
16 September 2027, an estimate
Certificate basis
ISO 22301:2019, unchanged

Stage 40.60, voting closed 20 June 2026. Publication estimate 16 September 2027, an estimate. Certificate basis ISO 22301:2019, unchanged.

01Position02Processes03Impact and risk04Strategies05Plans06Exercises07Evaluation08Audit and improvement
P8 public record The draft and its process model

The operational view beside the requirements view

The draft complements the requirements and risk-management view of ISO 22301 with an operational, process-oriented view; it does not replace the requirements.

Basis: Stated in the public scope. The draft text is not public. This page reads the public scope and the held ISO 22301:2019 clause set, and does not quote either as draft text.

01What applies

The public scope says the document will complement the requirements-oriented perspective of ISO 22301, which is based on risk management, with an operational, process-oriented point of view. The consequence is that ISO 22301 remains the requirements standard, a certificate remains against ISO 22301, and the draft adds a way of seeing and operating the system. A gap against the draft is a process improvement, not a nonconformity against a certifiable requirement. This site states that consequence because it follows from the public scope's own description, and labels it as our reading.

02Why it matters

A buyer needs to know what can and cannot be written in an audit report. A guidance document can inform an observation, but a certificate is issued against a requirements standard. Confusing the two produces either unnecessary remediation or a false sense of assurance. The distinction also tells the buyer how to use the draft: as a design aid, not as a new checklist.

03What good looks like

Keep two columns in the BCMS dashboard: conformity against ISO 22301 and process performance against the model. Report them separately. When a process underperforms, record it as an improvement, not a nonconformity, unless it also breaches a requirement. Tell the certification body which column is which.

04Evidence an auditor asks for

Ask whether a weak process outcome would be written as a nonconformity. If the answer is automatic yes, the two views are conflated.

EvidenceThe record
DashboardConformity and process performance reported separately
ClassificationA rule for when a finding is a nonconformity and when it is an improvement
BriefingThe certification body briefed on the distinction

05Where it commonly fails

  • Treating the draft as a certifiable requirement set
  • Using a process weakness as a nonconformity without a clause
  • Reporting one blended score that hides the difference

06What to do before the estimate

Add the two columns to the dashboard and the classification rule to the audit procedure.

07Read across

Full process model / The dates / Free check