What this policy is
Operational counterpart to onboarding/offboarding — focused on the specific obligations triggered when employment ends (whether voluntarily, by termination, or by role-change).
Why every organization needs one
The terminated-employee account that retained production access is the textbook insider-risk incident. The policy enumerates every revocation step so none are missed.
What a competent Termination Or Exit Management Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Last-day account-revocation checklist
- Final-pay / leave settlement linkage
- Equipment recovery + data extraction
- Post-departure access (alumni email, etc.)
- 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_termination_or_exit_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.11 | Return of assets | Organizational controls |
| ISO/IEC 27001:2022 | A.6.5 | Responsibilities after termination or change of employment | People controls |
2 controls across 1 framework 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.