Mandatory Reason-Giving for Exceptions¶

Procedural rule — instantiates Capture-Resistant Institutional Design

Requires the institution to publish a written, on-the-record justification every time it grants an exception, waiver, or deviation, so favours to the regulated actor cannot be handed out silently.

Mandatory Reason-Giving for Exceptions attaches a cost to discretion. Whenever the institution departs from its default rule — grants a waiver, an exemption, a sole-source award, an off-cycle approval — it must write down why, on the record, at the moment it acts. The distinguishing idea is that it neither forbids exceptions (too rigid) nor merely logs that one occurred (a bare access log does that); it forces a reason that has to stand up, converting silent discretion into an accountable, contestable act. Capture thrives on the quiet exception granted with no explanation; a reason requirement bites exactly there, because the favour that serves the regulated actor rather than the mandate is precisely the one for which no defensible sentence can be written.

Example¶

A public agency's default is competitive bidding. An official wants to hand a contract to a single vendor with no competition. The rule requires a written Justification and Approval — naming the specific reason competition is impractical, signed off a level above the official, and placed in the public file. "Let's just use our usual vendor" now has to become "only this vendor holds the certification the work requires, and here is the documentation" — a claim that can be read and challenged. If the real driver is a cozy relationship, there is no honest sentence to write and no senior name willing to co-sign it. The requirement does its work before any audit: it makes the indefensible exception hard to author in the first place.

How it works¶

Triggers on deviation, not routine. The obligation fires when the institution steps outside its own default — the exception, waiver, or override — not on ordinary in-rule decisions.
Demands a substantive, mandate-tied reason. A justification must connect to the governing criteria, not tick a box; a reason that could paper over any decision is no reason.
Contemporaneous and on the record. Written at decision time and filed where it can be seen, so it cannot be back-dated or invented afterward to fit the outcome.
Accumulates into a legible trail. Reasons pile up in a searchable record, so a run of exceptions all bending toward one actor becomes visible as a pattern rather than dissolving into isolated one-offs.

Tuning parameters¶

Trigger threshold — what counts as an "exception" worth a reason. Set it low and you catch more but bury everyone in paperwork; set it high and quiet favours slip under the bar.
Reason depth — a single sentence versus a documented case. Deeper is harder to fake but slower to produce.
Approval elevation — how senior the co-signer must be. Higher raises the friction on abuse but creates bottlenecks.
Publication scope — internal file versus fully public record. More public deters more, but runs into privacy and competitive-secrecy limits.
Contemporaneity — required before the fact versus tolerated after. Before-the-fact is what blocks post-hoc laundering.

When it helps, and when it misleads¶

Its strength is deterrence by authorship: the discipline of composing a defensible, signed reason quietly kills the favours that have no defensible reason, and it lays down the contestable trail on which appeals, audits, and oversight all depend.

Its failure mode is boilerplate — reasons decaying into copy-pasted formulae that satisfy the letter and reveal nothing. And the classic misuse is the mechanism run backwards: the reason drafted after the decision to launder a choice already made, a post-hoc rationale dressed as a contemporaneous one.^[1] The discipline that keeps it honest is to demand specificity tied to the governing criteria, insist the reason be filed at decision time, and run periodic pattern review so formulaic reasons and one-sided exception streaks are caught rather than filed and forgotten.

How it implements the components¶

This rule fills the transparency-and-discretion components — the record of exceptions and the legibility of the discretion behind them:

access_and_exception_transparency_record — every exception enters the record with its justification attached; the rule populates the exception side of this record, turning a quiet grant into a documented one.
discretion_and_enforcement_pattern_audit — by forcing a reason on each discretionary act, it makes discretion legible one decision at a time, supplying the raw, reasoned substrate a pattern audit later reads.

It does not log routine privileged access or off-record contacts (Privileged Access Log, Ex Parte Contact Disclosure Rule) or draw the aggregate enforcement-pattern picture (Enforcement Pattern Dashboard) — it produces the reasoned records those mechanisms consume and visualize.

Instantiates: Capture-Resistant Institutional Design — reason-giving makes the institution's discretion accountable rather than silent.
Sibling mechanisms: Enforcement Pattern Dashboard · Privileged Access Log · Capture Risk Audit · Conflict-of-Interest Disclosure and Recusal · Countervailing Stakeholder Panel · Ex Parte Contact Disclosure Rule · Funding Firewall Rule · Independent Oversight Board · Public Comment Docket · Revolving-Door Cooling-Off Period · Sunset and Reauthorization Review · Third-Party Technical Replication

References¶

[1] Reasoned decision-making — the administrative-law principle that a discretionary decision must rest on a contemporaneous, reviewable rationale, the basis on which a "hard look" or "arbitrary and capricious" review tests it. Reason-giving imports that discipline at the point where exceptions are granted. ↩