Architecture decision record (ADR) template
Record one decision: status, context, the decision, consequences and the options you considered.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
- Status
- Accepted · 2026-11-08 · Deciders: tech lead, architect, PM · Supersedes: none
- Context
- Orders need ACID transactions + reporting joins · Team knows SQL; 5k orders/day, growing 3× a year
- Decision
- Use managed PostgreSQL (RDS / Cloud SQL) for the order service
- Consequences
- + Strong consistency, mature tooling · + No new technology to learn · − Scale-up limits: plan read replicas · − Schema migrations need care
Table columns: Option, Pros, Cons, Verdict.
Also on the board
- Options considered
How to use this template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- Sketch, then convert. Draw boxes and arrows with the pen, select the strokes and click Convert sketch: they become real boxes and links.
- Ask Kelvo right on the board (Pro). With Pro, type @kelvo and what you want in any box or text, for example “@kelvo add error handling”, and press Enter. The change is made there and the request disappears; ⌘Z undoes it.
- One page per level. Put the C4 context view on one page and the container view on the next, so each diagram stays readable.
Good for
- architect
- adr
- documentation
- decision
- Agreeing on boundaries and responsibilities between services
- Recording why a design was chosen (and what was rejected)
- Comparing integration options side by side
Related templates
C4 system context diagram
C4 level 1: the system in scope, the people who use it and the external systems it depends on, with a legend.
C4 container diagram
C4 level 2: the apps, APIs, databases and queues inside the system boundary, with the technology on each link.
Microservices with API gateway
Clients behind an API gateway, services that each own their database, and an event bus for asynchronous work.
Event-driven architecture
Producers publish facts to a broker; independent consumers react — with the design rules that keep it reliable.
Basic flowchart
Start, steps, a decision with yes/no branches, and an end — the classic shape to build from.
Prompting vs RAG vs fine-tuning
A decision tree for choosing prompt engineering, RAG, fine-tuning or an agent, with a cost and speed comparison.