What this policy is
Establishes the management-review and improvement cycle that ISO 27001 requires (PDCA — Plan, Do, Check, Act) — the engine that keeps the ISMS alive between audits.
Why every organization needs one
Auditors look for evidence that the ISMS is operated, not just documented. The improvement policy is the procedural evidence.
What a competent Continuous Improvement Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Management-review agenda
- KPI / KCI tracking
- Improvement-opportunity intake
- Corrective-action lifecycle
- Review cadence (typically annual) and version control
- Approval, sign-off and effective date
How iCompaas tracks this policy
The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_continuous_improvement_policy_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).
Compliance frameworks that reference this policy
The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.
| Framework | Control | Title | Component |
|---|---|---|---|
| ISO/IEC 27001:2022 | A.5.27 | Learning from information security incidents | Organizational controls |
| ISO/IEC 27701:2025 | A.1.3.11 | Automated decision obligations | Obligations to PII principals |
| ISO/IEC 27701:2025 | A.3.16 | Compliance with policies | Security considerations |
| ISO/IEC 27701:2025 | A.3.18 | Confidentiality agreements | Security considerations |
| ISO/IEC 42001:2023 | A.2.4 | Review of policies for responsible AI | Organizational controls |
| ISO/IEC 42001:2023 | A.6.1.3 | AI system design and development process | Technological controls |
6 controls across 3 frameworks reference this policy.
About this page
This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.