---
title: "[000] Title"
source: Architecture Decision Records (JPH)
source_url: https://github.com/joelparkerhenderson/architecture-decision-record
licence: CC0-1.0
domain: engineering
subdomain: adr-examples
date_added: 2026-04-25
---

# [000] Title
*Allocate each ADR a number for easy reference and cataloging* \
*NOTE: All italicised text provides hints and should be removed for production*

## Status - DRAFT / ACTIVE /  DEPRECATED by [000] / SUPERSEDES [000]

## Context
*Briefly describe the problem(s) that this ADR intends to address, and why the problems exist.*

## Decided Approach
*Detail the architecturally significant decision that has been / will be made and describe how it addresses the problems outlined in the Context section.*

## Consequences
*What is the impact of this decision on the architecture characteristics and functional requirements of the system?*

## Governance
*How will the outcomes of this decision be monitored?* \
*How will compliance with this decision be ensured?*

## Options Analysis
*If applicable, include or link to any trade-off analysis which has been performed to arrive at the decision made in this document.*

### Key
*Optional: Provide visual aids to stakeholders which can help to quickly spot the positive and the negative trade-offs - for example simple traffic-light highlights with positive or negative prefixes.*

A green background indicates a good fit, worsening through amber, with red being the worst fit. \
\+ indicates a positive impacting comment \
\- indicates a negative impacting comment

### High-Level Overview
*How well does each option fit the problem context at a glance?*

<table>
  <thead>
    <tr>
      <th>Summary</th>
      <th>Option 1</th>
      <th>Option 2</th>
      <th>Option 3</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Ease of Implementation</td>
      <td>
        
          + Super easy
        
      </td>
      <td>
        
            - Tricky
        
      </td>
      <td>
        
            - Large implementation requiring expert knowledge
        
      </td>
    </tr>
    <tr>
      <td>Timescales</td>
      <td>
        
            + Very quick
        
      </td>
       <td>
        
            - Fairly slow
        
      </td>
      <td>
        
            - Very slow
        
      </td>
    </tr>
    <tr>
      <td>Strategic Value</td>
      <td>
        
            - No strategic value, purely tactical
        
      </td>
       <td>
        
            + Slightly improves the customer onboarding experience
        
      </td>
      <td>
        
            + Ideal for the upcoming merger
        
      </td>
    </tr>
  </tbody>
</table>

### Functional Requirements
*How well does each potential option fit the desired functional requirements?*

<table>
  <thead>
    <tr>
      <th>Scenario</th>
      <th>Option 1</th>
      <th>Option 2</th>
      <th>Option 3</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Scenario 1</td>
      <td></td>
      <td></td>
      <td></td>
    </tr>
    <tr>
      <td>Scenario 2</td>
      <td></td>
      <td></td>
      <td></td>
    </tr>
    <tr>
      <td>Scenario 3</td>
      <td></td>
      <td></td>
      <td></td>
    </tr>
  </tbody>
</table>

*Optional: Add rows / another table to cover known future scenarios.*

### Non-Functional Requirements
*How well does each potential option fit the desired architecture characteristics?
Note: ‘Architecture Characteristics’ would be a more appropriate title, but tailor this to familiar language for your business domain.*

<table>
  <thead>
    <tr>
      <th>Architecture  Characteristic</th>
      <th>Option 1</th>
      <th>Option 2</th>
      <th>Option 3</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Scalability</td>
      <td></td>
      <td></td>
      <td></td>
    </tr>
    <tr>
      <td>Performance</td>
      <td></td>
      <td></td>
      <td></td>
    </tr>
    <tr>
      <td>Availability</td>
      <td></td>
      <td></td>
      <td></td>
    </tr>
  </tbody>
</table>

*Optional: Add in or link to definitions of the architecture characteristics as they pertain to your business / product.*
