Policy Management
Overview
Policies state intent and requirements; procedures explain how. A healthy policy lifecycle prevents both vacuum (no rules) and shelfware (unread rules).
When to Use
- Establishing or restructuring the policy hierarchy
- Drafting or updating policies, standards, and SOPs
- Policy exception and waiver processes
- Audit findings related to outdated or conflicting policies
Core Practices
- Define hierarchy: policy → standard → procedure → guideline
- Use clear ownership, approval authority, and review cadence
- Write for the people who must comply — plain language
- Version, communicate, and acknowledge material changes
- Manage exceptions with expiry and compensating controls
- Retire obsolete documents deliberately
Principles
- If nobody can find or understand it, it doesn’t control anything
- Policies should be enforceable and testable
- Conflicts between documents are compliance defects
- Shorter, clearer policies beat encyclopedias
Verification
- Each policy has an owner and review date
- Audience can locate the current version
- Exceptions are logged and time-bound