Back to playbooks

Specific Reasons and Usable Notices

Community | playbook | Updated 2026-03-14

Tags

ai, claims, eligibility, notices, community

Specific Reasons and Usable Notices

Use this playbook when claimants receive denial, closure, disenrollment, or adverse-action notices that are too generic to challenge.

The point is simple: if the person cannot tell what happened, the appeal right is mostly decorative.

What problem this solves

Many notices technically explain that a decision was made. They do not explain the actual factors that shaped it.

Generic checklists, boilerplate reason codes, and missing attachments force the claimant to guess what evidence matters, what is disputed, and what to do next.

The basic rule

Every adverse notice should tell a normal person:

  • what decision was taken
  • the specific reason it was taken
  • what evidence or rule was relied on
  • what is missing, disputed, or time-sensitive
  • how to appeal and by when
  • who owns the review

What a usable notice looks like

The required reason is the one that actually shaped the decision, not a generic category broad enough to cover many possible errors.

Plain language matters. The point is not a legally dense notice that protects the institution. The point is a usable notice that lets the claimant respond before the decision becomes effectively final.

Minimum steps

  • define required fields for every notice type
  • attach or link the evidence summary the notice relies on
  • include the review owner and response deadline
  • test notices with non-specialist readers
  • track recurring notice-quality failures

Metrics and tripwires

Track:

  • notice completion rate
  • notice quality failure rate
  • percentage of notices returned, undelivered, or unreachable
  • appeal rate by notice type

Tripwires:

  • staff cannot explain the reason without looking elsewhere
  • notices omit the actual factor that drove the decision
  • claimants repeatedly appeal just to learn what happened
  • denials rely on outdated or incorrect contact information

Bridge language

“Explain the denial before expecting the person to challenge it.”

“A generic notice is often just a denial shield in plain view.”

Back to playbooks