
Engineering RFC
Docs + Word8 pages
Free
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.
Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.
Set the RFC number, author, reviewers and decide-by date on the change page.
Rewrite the summary so a reader can accept or object after one paragraph, and list the teams affected.
Record each objection with the author's response and whether the design changed, then mark the decision.
Delete the guide page, then share the proposal with the affected teams for review.
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.
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.
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.
More Google Docs templatesMore developer workflows templates

Docs + Word8 pages
Free
Slides + PowerPoint11 slides
Free
Docs + Word7 pages
Free