Writing Technical RFCs

What Is an RFC and When to Write One

An RFC (Request for Comments) is a formal document that proposes a technical approach to a problem, inviting feedback and discussion before implementation. Originally popularized by the IETF for internet standards, RFCs have become a staple of software engineering culture—especially at companies like Stripe, Shopify, and Vercel.

When to write an RFC: Write one when the decision has lasting impact, involves multiple teams, introduces significant risk, or requires stakeholder buy-in beyond your immediate team. Migrating from REST to GraphQL, adopting a new state management library, or rearchitecting your build pipeline—these all warrant RFCs. Fixing a bug or adding a small feature typically does not.

When to skip it: For low-risk, reversible changes or decisions that affect only your squad, a quick design doc or async discussion may suffice. RFCs take time; reserve them for decisions that warrant the investment.

RFC Structure: Problem, Solution, Alternatives, Risks, Timeline

A well-structured RFC guides readers through your thinking and makes feedback actionable. Follow this proven template:

Problem Statement