Skip to content
The first pages of the Infrastructure Change Proposal template

Infrastructure Change Proposal

Document template for Google Docs and Word

Make a copy in Google Docs
Price
Free
Style
Modern
Difficulty
Beginner
Updated
November 6, 2026

Every page (8)

Overview

Infrastructure changes touch teams who were not in the room, and a decision made in chat is hard to trace later. This template gives the proposer one place to set out the scope, the cost, the effect on reliability, the security rules, the rollout and the rollback, and the record of who agreed. Each section answers a question a reviewer will ask, so objections can be resolved in writing.

The sample proposes moving checkout, search and sync services from three virtual machines to a managed cluster in the UK region. It shows a one-off cost of £28,000, a saving of £280 a month, a go-live check and a handover to the operations team. All names, figures and dates are fictional. Replace the scope, costs and owners with your own, and record each objection with the response you gave.

Useful for

  • A platform engineer proposing a move to a managed cluster and asking three teams to review it
  • A decision owner checking the cost, rollback and security sections before accepting the change
  • An operations lead preparing a handover and go-live checklist for the on-call rota

What's included

  • Change: what is in and out of scope, with the main assumptions and exclusions
  • Cost: a budget table with effort, timing and a contingency callout
  • Reliability: service targets as a scorecard, with the error budget defined
  • Security: numbered rules on access, secrets and data for the new cluster
  • Rollout and rollback: a timeline, a month Gantt and a handover checklist with sign-off
  • Make it yours: numbered steps for replacing the scope, costs and owners

How to use it

  1. 1

    Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Set the RFC number, author, reviewers and decide-by date on the change page.

  3. 3

    Rewrite the summary so a reader can accept or object after one paragraph, and list the teams affected.

  4. 4

    Record each objection with the author's response and whether the design changed, then mark the decision.

  5. 5

    Delete the guide page, then share the proposal with the affected teams for review.

What you need

Requirements

  • A Google account with access to Google Drive

Works with

  • Google Docs
  • Microsoft Word (download the .docx)

Questions

Are the organisation, people and figures fictional?

Yes. Cinderfield Systems, its engineers, the services and every cost and figure in this sample are fictional. Replace them with your own systems and costs before you circulate the proposal.

How long should a review window be?

Five to ten working days is typical for a change that affects several teams. Set a decide-by date in the header, so that the proposal does not drift for months without a decision.

What happens to a comment that is not resolved?

Mark it as an open question with an owner, and list it in the unresolved section. A blocker must be settled before the decision, not left until the end of the review.

  • #rfc-template
  • #infrastructure-change
  • #engineering-proposal
  • #devops
  • #change-management
  • #rollback-plan
  • #google-docs

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…