The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Deprecate an accepted architectural decision record (ADR) when its decision is no longer recommended and there is no accepted replacement. Mark it superseded when a new decision has been accepted in its place. Leave it unchanged while its decision remains in force and the record still accurately captures its reasoning and consequences. In every case, preserve the old record as decision history.
Organizations do not use one universal ADR status vocabulary or edit policy. The definitions below are a practical convention; document your team’s own rules and apply them consistently.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Blackout: The Human Survival Manual | $9.90 | Buy on Amazon |
| 2 |
|
IDEAS OF REFERENCE | Buy on Amazon | |
| 3 |
|
Alternative Dispute Resolution - USA Law Quick Reference Guide by Permacharts | $9.95 | Buy on Amazon |
| 4 |
|
How Adr Works | $88.11 | Buy on Amazon |
| 5 |
|
Negotiator's Desk Reference (The Negotiator's Desk Reference) | $39.90 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
How to choose the right status
| Question | Leave unchanged | Deprecate | Supersede |
|---|---|---|---|
| Is the decision still recommended and in force? | Yes | No | No; a replacement has been accepted |
| Is there a direct accepted replacement? | Not applicable | Usually no | Yes |
| What happens to the old ADR? | Keep it as the current decision record | Retain it and state why it is obsolete and what its scope is | Retain it, mark it “Superseded,” and link to the replacement |
| What additional documentation is needed? | None unless local policy permits a correction or clarification | A reason for deprecation and guidance for new work | A new accepted ADR explaining the changed decision, with links in both directions |
These are recommended meanings, not a mandatory industry-wide status schema. For example, Microsoft’s hve-core taxonomy describes “deprecated” as no longer recommended and not applied to new work, while Decentraland’s specification requires a deprecation reason: Microsoft hve-core and Decentraland ADR specification.
When to leave an ADR unchanged
Keep an ADR unchanged when the team still intends to follow its decision and its rationale and consequences remain accurate. Its age alone is not a reason to change its status. GOV.UK advises reviewing ADRs as their context or consequences change, rather than treating a date as an automatic expiry: The GDS Way.
#1 Best Overall
Whether to edit an accepted ADR for a minor clarification depends on local policy. AWS Prescriptive Guidance says an accepted ADR becomes immutable and recommends recording new insight in a new ADR: AWS: Architectural decision record process. GDS guidance allows some clarifications and consequence updates. Decide in advance whether non-substantive corrections are permitted; if the decision itself changes, create a new record rather than quietly rewriting the historical decision.
When to deprecate an ADR
Deprecate an accepted decision when it is no longer recommended for new work, but no new accepted decision directly replaces it. This can fit when a technology or approach has become unsuitable and the team has not yet chosen a successor. State why it is deprecated, what systems or work the status applies to, and any guidance readers need. Deprecation is not deletion: preserve the record and its rationale.
Rank #2
Terms vary by organization, so follow the status definitions in your own decision log. The key distinction is that deprecation signals obsolescence or non-recommendation without claiming that a replacement decision has been accepted.
When to supersede an ADR
Mark an older ADR “Superseded” after the team accepts a new decision that replaces, reverses, or materially changes it. A changed assumption or a better option is a reason to revisit the decision, but it does not make the old record superseded until the team has accepted the replacement.
Rank #3
- 4-page, 8.5" x 11" laminated Alternative Dispute Resolution Legal quick reference guide
- Alternative Dispute Resolution (ADR) has become a very important American legal mechanism. ADR often means huge savings in time, money and risk often associated with the American legal trial process.
- This comprehensive ADR guide gives highly relevant information to everyone interested in the efficient and timely resolution of disputes without going to the courts.
- The entire ADR process is neatly summarized, with all key definitions, terms, rules, and references comprehensively organized in this quick reference study guide.
- Great legal and law reference for lawyers, paralegals and law students.
Keep both records. The old ADR should explain that it has been superseded and link directly to the new one; the replacement should link back and explain why the earlier decision no longer fits. AWS recommends retaining the old record in the decision log, and the Ministry of Justice’s example likewise keeps a reversed decision and marks it superseded: AWS ADR best practices and Ministry of Justice ADR-000.
What to do when implementation is incomplete
A failed or partial implementation may reveal that the recorded decision needs attention, but the right treatment depends on what happened and on the team’s edit policy. GDS guidance distinguishes among clarifying a record, revising one when none of the decision was implemented and stakeholders agree, and creating a new ADR when some implementation has already occurred. AWS takes the stricter position that accepted records remain immutable and new insight belongs in a new ADR. Agree on the policy before a specific decision needs revision; discuss decisions that remain only partly implemented with the affected teams.
Rank #4
A workflow for changing a decision
- Confirm the decision has changed. Check that the issue is architectural and that the team no longer intends to follow the earlier decision.
- Draft a new ADR. Record the changed context, the proposed decision, its consequences, and why the prior choice no longer fits.
- Get the new decision accepted. Use the team’s normal review and approval process; do not mark the old ADR superseded before a replacement is accepted.
- Link the records. Mark the old ADR “Superseded” and link to the replacement. Add a reciprocal link from the new ADR to the old one.
- Preserve the history. Retain the old ADR and its rationale in the decision log. If the format supports it, record ownership or change history.
- Update current-practice documentation. Revise documentation that describes what teams should do now, while keeping the ADR as the history of the decision.
This approach aligns with AWS lifecycle guidance, GDS replacement-status instructions, and Google Cloud guidance on preserving decision history: AWS ADR process, The GDS Way, and Google Cloud architecture decision records.
When to review ADRs
Review a decision when a material part of its context changes: requirements, business needs, constraints, available technology, security or operational expectations, ownership, or consequences observed in implementation. A review does not automatically mean a status change; it is a prompt to decide whether the existing decision still applies.
Guidance recommends regular review but does not set a universal interval. GOV.UK advises regular review as context or consequences change, AWS recommends scheduling review discussions, and GDS calls for discussion of ADRs that are not fully implemented across relevant teams. Set a cadence suited to how quickly your architecture changes, and review sooner when a material trigger arises. The GDS page reports a last review date of 5 March 2026 and a due date of 5 September 2026, and warns it may be out of date; treat it as operational guidance rather than a universal rule.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
