Decision Notice¶
Document — instantiates Procedural Fairness Design
A notice document or message explaining a pending or completed decision and available process rights.
A Decision Notice is the outward-facing message that carries a decision — or the intention to make one — to the person it will affect, in time for them to do something about it. Its whole reason for existing is reachability before closure: it names who is affected, states what is being decided and under which rule, says when the decision takes effect and by when the party must act, and tells them which routes — respond, submit evidence, request a hearing, appeal — are open. It is the envelope, not the file. It delivers standing to the affected party; it is not the internal record of why the decision was reached, and it does not itself run the appeal it points to. A notice that arrives after the meaningful moment, or that buries the deadline, has failed at the one job that makes it a fairness mechanism rather than a formality.
Example¶
A public housing authority is preparing to terminate a family's rental assistance after a reported lease violation. Before anything is final, the authority mails and hand-delivers a Decision Notice. It names the household as the affected party, states the specific conduct alleged and the exact lease clause and regulation at issue, and says the termination cannot take effect earlier than a date roughly a month out. Crucially it lists what the family can do in the interim: inspect the case file on request, submit a written response or documents, and request an informal grievance hearing by a stated deadline — with a phone line for questions and the option of a translated copy. Contrast the failure it prevents: a one-line letter reading "your assistance has ended," dated after the fact, with no deadline and no route. The same outcome may follow either way, but only the first version gives the family standing to contest it while contesting still matters.
How it works¶
- Identify and address the affected party — by name or role, including representatives where the decision hits a household or group.
- State the decision and its trigger — what is being decided, under which rule or standard, plainly enough to act on.
- Fix the timeline — effective date, the window to respond, and the deadline for each available route, so the clock is visible rather than buried.
- Enumerate the process rights — respond, supply evidence, request a hearing, appeal — and where each is exercised, pointing to those routes without operating them.
- Deliver through a channel the party actually receives, in accessible formats, and keep proof of delivery.
Tuning parameters¶
- Lead time — how far ahead of the effective date the notice lands. More lead time gives a real chance to respond; less speeds urgent action but risks token notice.
- Specificity — a case-specific account of what and why, or a generic template. Specific notice is actionable but costs drafting; generic notice scales but can be unactionable.
- Channel and proof — certified mail, in-app, email, or in person; stronger proof of receipt versus lower friction.
- Pre- vs. post-decision — notice before closure (which invites voice) or after (which announces and points to appeal). Emergencies may force post-hoc notice, which must then be fast and paired with review.
- Accessibility of the notice itself — reading level, translation, format — how far the document is built for the recipient rather than for the file.
When it helps, and when it misleads¶
Its strength is that it is the hinge on which every later right turns: you cannot exercise voice, evidence, or appeal rights you were never told you had, and timely, specific notice is exactly what the pre-termination-notice principle protects.[1] It also disciplines the decider, because a notice that must state the rule and the deadline exposes a decision that has neither.
Its failure mode is token notice — technically sent, but too late, too vague, or through a channel the party never checks, so the rights it lists are unusable. A companion misuse is the deadline-burying notice that satisfies the letter of notification while defeating its purpose. The guarding discipline is to measure a notice by the recipient's realistic ability to act on it — enough lead time, plain and specific content, a channel that reaches them, and proof that it did — and to treat a missed or defective notice as a defect that reopens the clock, not a technicality to wave through.
How it implements the components¶
Decision Notice fills the reach-the-party-in-time slice — delivering standing, not documenting reasoning:
notice_requirement— it is the notice: what is communicated, when, and how, including the party's rights and routes.affected_party— it identifies and addresses the materially affected person or group so the process has someone to notify.decision_timeline— it fixes and surfaces the effective date and the deadlines to act on each route.
It does NOT implement reason_giving or consistency_standard — the durable why-and-like-cases file is Transparent Decision Record; and it points to but does not run review_or_appeal_path, which Appeals Process provides.
Related¶
- Instantiates: Procedural Fairness Design — the notice is the archetype's entry point, converting an affected party into a party with usable process rights.
- Sibling mechanisms: Transparent Decision Record · Appeals Process · Review Panel · Grievance Process · Moderation Appeal · Hearing Procedure · Ombuds Channel
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: Decision Notice operates as a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding because it a notice document or message explaining a pending or completed decision and available process rights.
Independent corroboration: The frozen evidence defines Decision Notice as 'A notice document or message explaining a pending or completed decision and available process rights', so its operative form is Communication, Facilitation & Learning.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Procedural due process cohered timely adequate notice of a contemplated or completed decision, its rule and effective date, and usable rights to respond, submit evidence, seek hearing, or appeal.
Related originating lineages:
- Public Administration & Policy — Administrative practice operationalized standardized notices to affected parties in benefits, licensing, and enforcement systems.
Review resolution: Procedural due process cohered timely adequate notice of a contemplated or completed decision, its rule and effective date, and usable rights to respond, submit evidence, seek hearing, or appeal.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] In Goldberg v. Kelly (1970) the U.S. Supreme Court held that welfare recipients are entitled to timely, adequate notice and an opportunity to be heard before benefits are terminated. It is a canonical source for the idea that notice must precede the deprivation to be worth anything. registry ↩