Architecture Decision Record
Reference model
A structured way to document architectural decisions for future reference.
About this model
An Architecture Decision Record captures the context, decision, and consequences of architectural choices made during a project.
Originator not stated.
How to read it
- Read the context to understand the background of the decision.
- Focus on the rationale to see why a particular option was chosen.
What this does
Documents the decisions made regarding software architecture, including the context, options considered, and the rationale behind the chosen solution.
When to use it
Use it when a significant architectural decision needs to be made and documented for future reference and clarity.
Not when: Do not use it for trivial decisions or when the context is not well understood, as it may lead to confusion later.
What happens next
Review the decision with stakeholders to ensure alignment and understanding.
Golden thread
Builds on ←
- Requirements analysis
- Options evaluation
Feeds into →
- Project documentation
Use this tool, free
Sign in to open the worksheet. Your work saves as you type, the AI can draft the parts you have not filled in, and you finish with an analysis and a 30/60/90-day action plan.
Drafted with AI and reviewed by Eccellere on 04/11/2026. Guidance, not advice: apply your own judgement.