Change Management Policy template (free, plain-language starter)

Free change management policy template for small companies: full text, the controls it supports and the decisions to make. Not legal advice or a certification.

Template · Updated · by the Controlkeep team

In short

How changes to production code, infrastructure and configuration are reviewed, tested, released and rolled back. This free starter covers 5 controls and leaves 5 decisions for you; it is original text, not a standard’s wording, and adopting it is not a certification.

How changes to production code, infrastructure and configuration are reviewed, tested, released and rolled back. Customers and auditors ask for it in auditors testing that code is reviewed before release; write it once more than one person deploys.

Starter policies are original templates written by Controlkeep. They are a starting point, not legal advice, and adopting them is not a certification or an audit opinion. Adapt every rule to how your company really works, and have a qualified adviser review policies with legal effect (privacy, employment, contracts).

Controls it supports

RefControlStarter framework
TC-CHG-01Changes are reviewed before releaseSOC 2-style common criteria starter
TC-CHG-02Environments are separatedSOC 2-style common criteria starter
IS-TEC-06Secure developmentISO 27001-style Annex A starter
TC-OPS-02Vulnerabilities are managedSOC 2-style common criteria starter
IS-TEC-07Technical vulnerabilitiesISO 27001-style Annex A starter

Decisions to make before approving

  • [the code repository / ticket system]
  • [1 working day]
  • [30 days]
  • [90 days]
  • [12 months]

The policy text

Purpose

Most outages and many security problems are caused by changes. This policy makes sure changes to [Company] production systems are reviewed, tested and reversible, without slowing the team down more than needed.

Scope

Changes to production application code, infrastructure, cloud configuration, databases, and security-relevant settings of SaaS tools that hold customer data.

Standard changes

Every production change:

  1. Is tracked in [the code repository / ticket system], with a short description of what changes and why.
  2. Is reviewed and approved by someone other than the author before release. For infrastructure and configuration, this includes changes made through consoles: record them afterwards if they cannot be reviewed before.
  3. Passes automated tests and checks where they exist, and is tested outside production first.
  4. Can be rolled back, or has a written plan for what to do if it fails.
  5. Is released by an approved deployment process, not by copying files by hand.

Environments

Development and testing happen outside production. Production customer data is not copied to development or test environments unless it is anonymised or [Policy Owner] approves the safeguards.

Emergency changes

When a fix cannot wait for review (for example during an incident), it may be released by an authorised person and must be reviewed within [1 working day] afterwards, with the reason recorded.

Security in development

  1. Dependencies are kept up to date; known vulnerabilities rated high or critical are fixed within [30 days], others within [90 days], or have a recorded risk acceptance.
  2. Secrets never go into source code.
  3. Changes to authentication, access control, payment or data export code get an extra security-focused review.

Records

Change history (who changed what, who approved it, when it was released) is kept for at least [12 months] as evidence.

Exceptions

Exceptions to this policy must be requested in writing, approved by [Policy Owner], recorded with a reason and an end date, and reviewed when they expire.

Enforcement

Breaking this policy may lead to loss of access and to disciplinary action in line with employment contracts and local law. Contractors may have their engagement ended.

Review

[Policy Owner] owns this policy and reviews it at least every [Review Period], and after any major incident or change in how [Company] works. Questions go to [Security Contact].

Adopt it

  1. Copy the policy below, or create it from the starter library in Controlkeep, where [Company], [Policy Owner], [Security Contact] and [Review Period] are filled from a form.
  2. Decide the 5 remaining bracketed items so the rules match how you actually work.
  3. Approve it, ask staff to acknowledge it, and link it to the controls it supports so auditors can follow the trail.

Related: collecting audit evidence, policies help, Remote Work and Device (BYOD) Policy, Access Control Policy.

Questions and answers

Does change management slow small teams down?

It doesn’t have to: a pull-request review and an automated test run are usually enough evidence.

Does adopting this change management policy make us SOC 2 or ISO 27001 compliant?

No. Policies are one part of a programme; an auditor tests whether you follow them over time. Controlkeep helps you keep the evidence, but it is not a certification or an audit opinion.

Try Controlkeep free

A working control register: owners, evidence, policies and reviews in one place, with exports your auditor can read. The Free plan needs no card; you can export or delete your data any time.