How to propose changes with RFCs

This article goes over how to propose changes with RFCs (Request for Comments).

Scrabble letters arranged to display “BE THE CHANGE”
Photo by Brett Jordan on Unsplash


Request for Comments (RFC) is a useful tool for proposing, sharing, and discussing a change you’d like to make.


  • Convey a problem or change.
  • Get buy-in from stakeholders for a proposal.
  • Document the reasons for a decision.

RFCs can be:

  • A process update.
  • A technical change.
  • A decision on a vendor.
  • Anything you want feedback on.

RFC Template

  • Date: 20XX-XX-XX
  • Author: Your Name

1–2 sentences that describes your RFC in a high-level.


Why are we doing this?

What are the pain points?

What use cases does it support?

What is the expected outcome?

This is the bulk of the RFC so explain your options in as much detail as appropriate.

Try to give each option a fair consideration.

Who are the reviewers/stakeholders who can approve this RFC?

If it’s your supervisor, please reach out to them first.

What option do you think is best?

What alternatives were considered and what were the reasons for not choosing them?

Why should we not do this?

If there are tradeoffs to choosing an approach, please identify them there.

What is the impact on users (external/internal)?

Remaining questions to be answered before the implementation.

What is required for the RFC to be closed?



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store