Skip to content

Public-Reason Decision Memo

Decision artifact — instantiates Institutional Rule–Role Stabilization

Attaches a written, public statement of reasons to each significant decision, so the decision is legible, accountable, and testable against the rule it claims to apply.

A decision announced as a bare verdict — granted, denied, removed — hides whether it followed the rules or someone's mood. Public-Reason Decision Memo is the short written artifact issued with a significant decision that states the facts found, the rule or authority relied on, and the reasoning connecting them. Its defining move is forcing the decider to show their work at the moment of deciding: a call that must be justified in writing, to the people it affects, is a call made more carefully and one that can be checked against the rule it claims to apply. Where the precedent repository is the accumulated archive, this is the single, live, forward-facing document for one decision — the unit the archive is later built from.

Example

A municipal zoning board of appeals hears a homeowner's request for a variance to build closer to a property line than the code allows. Instead of a one-word "denied," the board issues a decision memo: the specific hardship standard the code sets, the facts it found about the lot, and why those facts did or didn't meet the test. The applicant can now see they were judged by a rule rather than a whim; they have concrete grounds on which to appeal; and neighbors facing similar lots have a public, citable statement of how the standard gets applied.

The memo changes the character of the power. A board that must publish its reasoning can't quietly grant favors to the well-connected, because the reasons would have to survive being read next to the denials. The decision becomes legible, contestable, and — filed away — part of the institution's memory.

How it works

  • State the decision and its basis. Name the specific rule or grant of authority the decision rests on, not just the result.
  • Show the reasoning. Lay out facts found → rule applied → conclusion, including how any discretion was exercised, so the path from rule to outcome is visible.
  • Publish at decision time. Give the reasons to those affected (often the public) when the decision lands, not only if someone later demands them.
  • Make it citable. Issue it as a standing record others can point to and rely on.

Tuning parameters

  • Depth of reasons — from a one-line ground to a full opinion. More depth means more accountability but higher cost and, sometimes, more caution about deciding at all.
  • Publication scope — parties only versus fully public. Wider publication maximizes transparency; some matters carry privacy or safety limits.
  • Timeliness — reasons issued with the decision versus after the fact. Reasons produced later are weaker evidence of the actual basis.
  • Standardization — freeform prose versus templated fields. Templates aid consistency but invite box-ticking that mimics reasoning without doing it.
  • Bindingness of stated reasons — whether the institution can later act inconsistently with a rationale it once published.

When it helps, and when it misleads

Its strength is converting raw power into accountable power. A decider who must publish reasons decides more carefully; affected parties get the material they need to appeal; and every memo feeds the precedent archive, so today's justified call stabilizes tomorrow's.[1] Sunlight on the reasoning is what lets an institution be trusted without being blindly trusted.

Its classic failure is the post-hoc rationalization: the memo presents a tidy, rule-shaped reason while the decision was actually made on other grounds, laundering an arbitrary or captured call behind a presentable one. This is the mechanism run backwards — writing the justification to fit a decision already made rather than to reach it. Its milder cousin is boilerplate: memos that recite the rule and assert it was met, giving the form of accountability with none of the substance. The discipline is that reasons must be specific to this case's facts and capable of being wrong — a rationale that could be pasted onto any decision is decoration, not accountability.

How it implements the components

  • public_reason_record — the memo is the public statement of reasons: the record that makes a decision's basis visible and contestable.
  • interpretation_and_discretion_rule — it puts on the record how the rule was interpreted and how discretion was exercised in this specific case, exposing the reasoning rather than hiding it.

It does not accumulate those records into retrievable precedent (that's the Precedent and Rationale Repository) or provide the channel to contest the decision (that's the affected-party review panel and the appeal and exception protocol).

References

[1] The duty to give reasons — the administrative-law principle that a body exercising public power should state the reasons for its decisions, enabling review and guarding against arbitrariness. ↩