Change Management Policy

Draft template. This is generic starting content, not a reviewed or binding company policy. Have Legal review and approve before publishing externally.

Purpose

To ensure changes to production systems (software releases, configuration changes, infrastructure updates) are made in a controlled, low-risk manner.

Typical process

1. Change is requested and documented (what, why, impact, rollback plan).
2. Change is reviewed and approved by the relevant technical owner.
3. Change is scheduled, ideally during a low-traffic window.
4. Change is implemented and verified.
5. Outcome is logged; incidents trigger a post-change review.