CONFIGURATION MANAGEMENT PLAN

System or project: [name]
Document owner: [name or accountable role]
Version: [version]
Effective date: [date after approval]
Approved by: [name, role, and approval reference]
Next review: [date]
Revision history: [version, date, author, and reason]

1. PURPOSE AND SCOPE
Objective: [what this plan protects or enables]
Included systems and environments: [list]
Controlled item types: [list]
Excluded items and their owners: [list]
Applicable policies or contractual requirements: [references]

2. ROLES AND APPROVAL AUTHORITY
Plan owner: [responsibility and delegate]
Configuration owners: [item types and responsible people]
Technical reviewer: [responsibility and delegate]
Business or service approver: [responsibility and delegate]
Release operator: [responsibility and delegate]
Emergency approver: [authority and contact route]
Separation of duties: [which roles may not be combined]

3. CONFIGURATION IDENTIFICATION
Register location: [restricted repository or register]
Required fields: [ID, name, type, owner, environment, state]
Naming and version rules: [convention]
Dependencies: [how relationships are recorded and checked]
Environment mapping: [how target-specific values are resolved]

4. APPROVED BASELINES
Baseline contents and location: [reference]
Approval criteria and authority: [requirements]
Permitted environment differences: [record location]
Replacement rules: [review, approval, and retained old reference]

5. NORMAL CHANGE CONTROL
Request record: [purpose, items, target, risk, and dependencies]
Review and approval route: [by change category]
Pre-release checks: [validation and test requirements]
Implementation: [operator, window, and approved artifact]
Post-release checks: [expected state and behavior]
Closure: [required evidence and owner]

6. STATUS ACCOUNTING AND EVIDENCE
Record links: [request, approval, artifact, tests, run, and audit]
Statuses: [proposed, approved, deployed, failed, superseded]
Retention and access: [policy, owner, and permissions]

7. VERIFICATION AND CONFIGURATION AUDITS
Checks: [which items and comparisons are reviewed]
Frequency and triggers: [schedule and event-based reviews]
Reviewer: [owner and independence requirements]
Findings: [how discrepancies are tracked and closed]

8. EMERGENCY CHANGES AND RECOVERY
Emergency criteria: [when the route may be used]
Authorization and minimum record: [requirements]
Recovery trigger, approver, and method: [details]
Aftercare: [review, baseline decision, and environment alignment]
Aftercare deadline and owner: [requirements]

9. TOOLS AND RECORD PROTECTION
Approved tools and their purposes: [list]
Secrets handling: [secure references, never embedded credentials]
Access review and record backup: [procedure and owners]

10. PLAN MAINTENANCE
Review schedule: [frequency]
Additional triggers: [system, team, tool, or policy changes]
Revision approval and communication: [procedure]