Reasoned Decision Notice¶
Decision notice — instantiates Accountable Gatekeeping Design
Gives an affected party the specific reasons the gate decided their case as it did — enough to understand it, fix it, or contest it.
A Reasoned Decision Notice is the individual, party-facing statement a gate issues after it decides a specific case, naming the actual reasons for that outcome. Its defining move is particularity aimed outward: not the general rubric everyone can read in advance, and not the complete internal record, but this applicant's result and the specific grounds behind it, written to be intelligible and actionable by the person on the receiving end. A bare "declined" tells someone nothing they can act on; a reasoned notice converts the outcome into an addressable fact — a reason they can correct, or challenge as mistaken — and the mere requirement to write one disciplines the decider, because a reason you must put in writing is one you must be prepared to defend.
Example¶
Under US lending law a lender that denies credit must send an adverse action notice stating the specific principal reasons for the denial. An applicant refused a small-business loan receives one: the decision turned chiefly on a short credit history and a high existing debt load, and the notice explains how to request reconsideration and how to check the underlying report. The document does two jobs at once. It gives the applicant something to act on — pay down the balance and reapply, or dispute a debt that was reported in error — and it draws a boundary around disclosure, stating the operative reasons without exposing the lender's full internal scoring model or another person's data. Six months and a corrected report later, the second application clears.
How it works¶
- Tie the reason to the case. The notice states the specific grounds this decision actually turned on, referenced to the criteria the case failed, not a generic rejection phrase.
- Write for the recipient. The explanation is pitched to be understood and used by the affected party, not merely to be technically complete.
- Draw the disclosure boundary. It reveals enough to understand and contest the decision while withholding what would enable gaming or expose third parties — the deliberate line between informative and unsafe to say.
- Point onward. It tells the party what they can do next: correct and reapply, or escalate to review.
Tuning parameters¶
- Reason specificity — the top one or two decisive grounds versus the full set. Naming the decisive reason is actionable; dumping every factor obscures what actually mattered.
- Disclosure boundary — how much of the operative logic is revealed. Reveal more and the party can act precisely but the gate becomes more gameable; reveal less and the notice risks becoming uninformative.
- Standardization — templated reason codes (fast, consistent, but blunt) versus bespoke prose (informative, but slow and less comparable).
- Timeliness — how soon after the decision the notice issues; a reason that arrives too late to act on is a record, not a remedy.
When it helps, and when it misleads¶
Its strength is that it makes a decision addressable: the affected party can fix a fixable problem, catch a factual error, or mount a specific challenge, and none of that is possible against silence. It also deters arbitrariness, since a gatekeeper who must state a reason cannot rest on an unexaminable hunch.
Its failure mode is the reason that satisfies the form without informing: boilerplate ("did not meet our standards"), or grounds written to be litigation-proof rather than true. The sharpest misuse is the post-hoc reason — a justification assembled after the fact to dress up a decision that actually turned on something else, so the notice documents a rationalization rather than the operative basis. The safeguard is the principle behind the whole mechanism, the duty to give reasons: the reasons stated must be the ones the decision actually rested on[1], which is why a notice is only trustworthy when drawn from the recorded decision basis and spot-checked against what really drove the outcome.
How it implements the components¶
Reasoned Decision Notice fills the per-case explanation slice — the outward-facing reason and the line drawn around it:
decision_reason_record— it is the party-facing record of why this specific case was decided as it was.transparency_boundary— it fixes, for each notice, how much of the reasoning to disclose and how much to withhold for gaming or privacy reasons.
It does not publish the general standard in advance — that is Published Selection Criteria — nor keep the complete internal record of every decision (that is Gatekeeping Decision Log), nor provide the venue that actually hears a challenge (that is Independent Review Panel or Appeals or Reconsideration Workflow).
Related¶
- Instantiates: Accountable Gatekeeping Design — it turns each outcome into a specific, contestable reason the affected party can act on.
- Consumes: Gatekeeping Decision Log supplies the recorded basis the notice is drawn from; Published Selection Criteria supplies the standard the reason refers to.
- Sibling mechanisms: Published Selection Criteria · Independent Review Panel · Appeals or Reconsideration Workflow · Gatekeeping Decision Log · Editorial Standards Board · Quota or Portfolio Guardrail · Random Sample Audit · Blind or Double-Blind Review · Algorithmic Ranking Audit · Transparency Report · Conflict-of-Interest Disclosure
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: Reasoned Decision Notice operates as a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding because it gives an affected party the specific reasons the gate decided their case as it did — enough to understand it, fix it, or contest it.
Independent corroboration: The frozen evidence defines Reasoned Decision Notice as 'Gives an affected party the specific reasons the gate decided their case as it did — enough to understand it, fix it, or contest it', so its operative form is Communication, Facilitation & Learning.
Nearest alternative: Representation, Specification & Plan — Reasoned Decision Notice includes features of a static representation, map, specification, schema, or prospective plan that externalizes information, but its defining operation is a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Notice of reasons is a canonical procedural-justice and administrative-law safeguard.
Related originating lineages:
- Public Administration & Policy — Administrative practice operationalizes notices for eligibility, licensing, and service gates.
Review resolution: Both blind reviewers agree that law_governance is the primary origin. Explicit reconciliation of alternate origin disagreement, domain reach disagreement adopts reviewer_a's classification because notice of reasons is a canonical procedural-justice and administrative-law safeguard. The resulting lineage records alternates=public_administration_policy, origin_mode=single_lineage, and domain_reach=multi_domain; these describe formative provenance separately from later applicability.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
A reasoned notice is what makes an appeal meaningful — you cannot contest what you cannot see — so it is the hinge between a decision and any review path. Its worth is measured not by whether a reason was given but by whether the reason given was the real one.
References¶
[1] Supreme Court of the United States. Securities and Exchange Commission v. Chenery Corporation et al., 318 U.S. 80 (1943). Requires administrative action to be reviewed on the reasons the decision-maker actually disclosed, not post hoc substitutes. registry ↩