Title: [Descriptive Title of the Proposal]
Author: [Your Name]
Created: [YYYY-MM-DD]
Reviewers: [List of relevant stakeholders]
Status: Draft / In Review / Approved / Rejected
Background
Describe the context and motivation for this proposal.
What problem are we trying to solve? Why now?
Summary / Proposal
A short, high-level summary of the proposal.
What is being proposed and why?
Goals/ Non-Goals
What do we aim to achieve with this change?
What is explicitly out of scope for this RFC?
Proposed Approach / Solution
Explain how you plan to address the problem.
Include technical details, systems affected, workflows, and any architectural diagrams or pseudocode if helpful.
Alternatives Considered
What other approaches were explored?
Why were they not chosen?
Trade-offs
What are the downsides or costs of this solution?
What risks might it introduce?
Rollout Plan
How will the proposal be implemented and released?
Will it be gradual or behind a feature flag? Include timeline or phases if needed.
Testing & Validation
How will we verify this works as intended?
Any QA strategy or success metrics?
Risks & Mitigations
What could go wrong, and how will we mitigate it?
Open Questions
What questions do we still need feedback or alignment on?
Stakeholders
| Role | Name | Responsibility |
| Engineering Lead | [Name] | Reviewer |
| Product Manager | [Name] | Decision-maker |
| QA | [Name] | Testing & validation |
Success Criteria
How will we know this RFC has succeeded?
Appendix / References
Include any external links, documents, diagrams, or prior RFCs.