Clause 6 – Planning

Clause 6.3 Planning of changes

Mandatory requirement

What it means in plain language

New in the 2022 version: when the ISMS itself needs to change (new scope, reorganisation, new processes), plan the change in a controlled way instead of improvising.

Is it mandatory? Yes. Clauses 4–10 are the management-system requirements; all of them must be met to be certified, and none can be excluded.

Documented information

  • No specific document required.

Why this requirement matters

The operational priority is to control changes to the ISMS itself, not just operational changes in the business. Change planning needs to treat a scope extension, reorganisation, or process redesign as a planned change with review of risk, affected documents, responsibilities, and timing. The objective is to avoid silent drift: readers should understand who approved the change, what was updated, and how evidence shows the change was implemented in a controlled way.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • A new office, team, or service is added to ISMS scope without a documented impact review, leaving unclear whether risk treatment, controls, and responsibilities were adjusted.
  • Process or role changes are made verbally, but affected procedures, registers, or responsibilities are not updated through documented-information control.
  • Management review discusses a major ISMS shift, yet there is no record of approval, implementation steps, or post-change verification that the new arrangement works as intended.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Treat any change that affects scope, governance, processes, tools, or responsibilities as a planned item with defined reason, impact assessment, approver, and implementation date. Include the likely effect on risk treatment, objectives, competence, and documented information. Avoid presenting the change as purely administrative if it changes how information security is actually managed.
  • Use a lightweight change record to capture the trigger, options considered, affected clauses or controls, dependencies, and rollback or contingency actions where needed. For larger changes, add a pre-implementation risk check and a post-change review date so the team confirms the change did not introduce gaps or conflicting instructions across procedures, registers, or systems.
  • Route updates to controlled documents through the documented-information procedure so obsolete versions are not retained as active references. Name the document owner and the reviewer, and note what changed: scope statement, org chart, control ownership, procedure steps, or record retention. Keep evidence that communication happened to impacted teams before the change took effect.
  • Use management review minutes as the central decision record for significant ISMS changes, especially where the change affects resourcing, accountability, or risk acceptance. After implementation, verify the change through a brief effectiveness check: for example, confirm the revised procedure is used, the new owner is trained, and any transitional actions are closed.

What an auditor will ask to see

  • Approved change record showing reason, impact assessment, owner, and effective date.
  • Updated procedures, scope statements, or role assignments with version control history.
  • Management review minutes capturing approval of ISMS changes and follow-up actions.
  • Post-implementation verification notes confirming the change was communicated and used.

Baseline documents in the kit

These free kit documents help you document or evidence clause 6.3. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with 9.3 — Management review and 7.5 — Documented information. Keep the ownership and evidence consistent across these activities.

Plan your ISO/IEC 27001 implementation timeline for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.