What this policy is
Sets the structure for the Crisis Management Team — who is on it, when it activates, who decides what, and how the organization communicates internally and externally during a serious incident.
Why every organization needs one
In a real crisis, the org that wins is the one whose people know in advance who decides. A policy that names the team and the chain is the difference between coordinated response and Slack chaos.
What a competent Crisis Management Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Crisis-classification criteria
- CMT membership and alternates
- Activation procedure and authority
- Internal/external communication chain
- 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_crisis_management_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.5 | Contact with authorities | Organizational controls |
| ISO/IEC 42001:2023 | A.8.4 | Communication of incidents | Organizational controls |
2 controls across 2 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.