SCHEMA TEMPLATES
Architecture Decision Record
Keep major technical decisions discoverable as systems and teams change, including decisions that replace earlier ones.
Architecture decisions lose context as systems evolve and people move teams. This template captures the domain, owner, decision date, status and relationship to earlier decisions, creating a record that future engineers can discover and review.
Fields
A decision record should survive the meeting that produced it. Use this structure to preserve its ownership, current standing and connection to decisions made before or after it.
| Field | Type | What it captures |
|---|---|---|
| Decision IDRequired · Indexed | Text | Stable identifier for finding and referring to a decision. |
| Architecture domainRequired · Indexed | Single choice | Technical area affected by the decision, such as data or infrastructure.Choices: Application, Data, Integration, Infrastructure, Security |
| StatusRequired · Indexed | Single choice | Current stage of the record's workflow or lifecycle.Choices: Proposed, Accepted, Superseded, Deprecated |
| Decision ownerRequired · Indexed | Confluence user | Person accountable for maintaining the decision record. |
| Decision dateRequired · Indexed | Date | Date on which the architecture decision was made. |
| Review dateIndexed | Date | Date planned for the next review of the risk, document or decision. |
| SupersedesIndexed | Text | Identifier of an earlier decision replaced by this one. |
| Related systemIndexed | Text | System affected by or connected to the architecture decision. |