Decision record template
Captures the decision, dissent, and follow-ups with owners.
Capture high-stakes calls, dissenting views, and follow-ups so governance stays legible to teams and impacted people.
Where it fits
Tagged for Governance, Policy with validator handshakes. Includes 3 steps, 3 reusable assets, and 4 snippet blocks.
Jump to
Key sections
Copy citation (APA/BibTeX)
APA
Ethotechnics Institute Research Team. (2026). MEC-01 Decision log with dissent. Ethotechnics Institute. https://ethotechnics.org/mechanisms/patterns/decision-log
MLA
Ethotechnics Institute Research Team. "MEC-01 Decision log with dissent." Ethotechnics Institute, 2026, https://ethotechnics.org/mechanisms/patterns/decision-log.
Chicago
Ethotechnics Institute Research Team. "MEC-01 Decision log with dissent." Ethotechnics Institute. Jan 9, 2026. https://ethotechnics.org/mechanisms/patterns/decision-log.
BibTeX
@misc{mechanism_decision-log,
title={MEC-01 Decision log with dissent},
author={Ethotechnics Institute Research Team},
year={2026},
howpublished={Ethotechnics Institute},
url={https://ethotechnics.org/mechanisms/patterns/decision-log},
version={v1.1.0}
}
RIS
TY - WEB TI - MEC-01 Decision log with dissent AU - Ethotechnics Institute Research Team PY - 2026 UR - https://ethotechnics.org/mechanisms/patterns/decision-log ER -
Specification overview
Capture the scope, assets, and validator handshakes before diving into the steps.
Spec essentials
Filters & validators
Tagged in 2 filters with 1 linked validators.
Glossary anchors
Jump to the glossary terms that frame this mechanism.
Steps
Start with the field cues, then use the assets to keep the work legible.
3 steps with checklist-ready owners, plus linked assets for handoffs.
0 of 3 steps complete
Assets
Link or copy these assets into design docs, runbooks, and briefs so the mechanism travels with the work.
Captures the decision, dissent, and follow-ups with owners.
One-paragraph recap teams can paste into briefs or release notes without jargon.
Review reminder aligned to maintenance or appeal windows.
Reuse-ready snippets
Use these snippets in requirements, audits, and postmortems with the mechanism permalink.
Policy requirement
Policy requirement (MEC-01 Decision log with dissent) - Maintain a decision log for high-stakes changes with dissenting views and a dated review owner. - Store the log in a shared system of record and retain links in audit and incident records. Reference: https://ethotechnics.org/mechanisms/patterns/decision-log
Product requirement
Product requirement (MEC-01) - Every high-stakes automated decision emits a decision-log entry ID in the receipt. - The UI links to a plain-language summary within two clicks of the decision outcome.
Audit evidence checklist
Audit evidence checklist (MEC-01) [ ] Decision log entries include owner, dissent, and review date. [ ] Plain-language summaries are attached and shareable. [ ] Stewardship reviews were completed on schedule.
Postmortem trigger
Postmortem trigger (MEC-01) Trigger review if a high-stakes decision ships without a logged entry or dissent record.
Example usage
A concrete scenario to help teams see how the pieces fit together.
How it plays out
A cross-functional team logs why an automation launch was delayed, notes dissent from support leads, links the appeal path, and schedules a stewardship review in six weeks.
Anti-patterns
Use these to avoid superficial compliance and clarify what success requires.
Records the decision but omits rejected options and dissenting views.
Counterfactual: Decision logs include rejected options, dissent, and a dated review owner.
False-positive warning: If no dissent exists, log the absence explicitly so future reviewers can see it was considered.
Keeps accountability logs in private documents that impacted teams cannot access.
Counterfactual: Logs live in the canonical record with a shareable receipt link.
False-positive warning: Sensitive data can be redacted, but the receipt must remain referenceable.
Validators
Use these tools to size risk and keep the stewardship path visible.
Validator
Quantifies task load, cognitive friction, and risk exposure so you can reroute toil before it burns people out.