Architecture Decision Record (ADR)
Record an architectural decision with context, decision drivers, alternatives, consequences, and conditions for revisiting it.
Use this templatePreview
ADR-[Number]: [Decision title]
| Field | Value |
|---|---|
| Status | Proposed / Accepted / Superseded |
| Date | [YYYY-MM-DD] |
| Decision owner | [Name or team] |
| Consulted | [Reviewers] |
| Related records | [Design, requirements, previous ADRs] |
| Supersedes / superseded by | [ADR reference, if applicable] |
Context
[Describe the problem and the conditions that make a decision necessary. Include relevant constraints and evidence.]
Decision drivers
- [Business or user outcome]
- [Operational constraint]
- [Maintainability or compatibility need]
- [Time, cost, or team capability constraint]
Options considered
| Option | Benefits | Drawbacks | Evidence |
|---|---|---|---|
| [Option A] | [Benefits] | [Costs and risks] | [Prototype or research] |
| [Option B] | [Benefits] | [Costs and risks] | [Prototype or research] |
| Keep current approach | [Benefits] | [Costs and risks] | [Current measurements] |
Decision
We will [chosen approach] because [rationale tied to the decision drivers].
Scope: [Where this decision applies and where it does not.]
Consequences
Positive
- [Benefit and who receives it]
Negative and accepted tradeoffs
- [Cost, limitation, or risk we accept]
- [Mitigation, owner, and residual risk]
Implementation and validation
Revisit conditions
[Specify measurable changes that would justify revisiting the decision, such as volume, cost, or a new requirement.]
Decision history
| Date | Change | Rationale |
|---|---|---|
| [Date] | Proposed | [Initial reasoning] |