Clause 10 – Improvement

Clause 10.1 Continual improvement

Mandatory requirement

What it means in plain language

Keep making the ISMS more suitable, adequate and effective over time – not only fixing problems but actively looking for improvements.

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 continual improvement as a managed habit, not just a reaction to nonconformities. The ISMS should absorb lessons from audits, incidents, metrics, supplier reviews, exercises, and staff suggestions, then turn them into tracked improvements that are visible in management review and linked to risk reduction, control refinement, or better operational discipline.

Common auditor findings to check for

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

  • Improvement ideas are captured informally but never prioritised, so potentially valuable changes stay in inboxes, chat threads, or meeting notes without execution.
  • Corrective action is mistaken for continual improvement, leaving no separate path for proactive enhancements that are not tied to a specific failure.
  • Management review receives no trend evidence, so leadership cannot tell whether improvement efforts are increasing ISMS maturity or simply closing isolated issues.

How you can implement it

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

  • Maintain a living improvement backlog, ideally within the Non-Conformity & Corrective Action Register or a linked improvement log, with sources such as audit results, incident lessons, user feedback, monitoring trends, and supplier reviews. Tag each item as corrective, preventive-style enhancement, or strategic maturity improvement so priorities stay clear.
  • Score proposed improvements using impact on risk, effort, dependency, and urgency. A lightweight monthly triage by the ISMS manager and process owners can separate quick wins, such as updating a checklist, from larger changes, such as redesigning access reviews or expanding logging coverage.
  • Give each approved improvement a named accountable role, milestone dates, and acceptance criteria. Track evidence of completion, such as revised procedures, new training, changed configuration, or updated controls, rather than relying on a statement that the task was finished.
  • Report progress in management review with trends: closed items, overdue items, recurring themes, and measurable outcomes where available. If an improvement exposes a new risk or control gap, route it into risk assessment and treatment rather than treating it as a standalone task.

What an auditor will ask to see

  • Improvement backlog or register with source, priority, owner, and target date.
  • Before-and-after records showing revised procedures, controls, training, or system settings.
  • Management review minutes discussing improvement status, trends, and decisions.
  • Closure notes linking improvement actions to evidence, acceptance criteria, and any follow-on risk treatment.

Baseline documents in the kit

These free kit documents help you document or evidence clause 10.1. 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 10.2 — Nonconformity and corrective action. 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.