Cohort forming

Benefit Denial Notices and Appeals

Help a person read a denial or termination notice, check it against the program's rules, and request a fair hearing and prepare the appeal in time.

Why it matters for peopleAppealing a wrong denial or cutoff restores the benefits that keep a household stable, sometimes with back payments.

← All Workflows

This page is the shared target for this situation. Any court, legal aid office, or builder working on it in their own region can take the vision, the blueprints, and the standards here instead of starting over, and set the parts that are local to them. The point is that the same work is not designed from scratch in every county.

Does this match how it goes where you are? Leave a note on this workflow.

What This Workflow Is

A notice says a benefit is denied, cut, or ending. It gives a reason, cites a rule, and sets a short deadline for asking for a hearing. In many programs, a request filed fast enough keeps the benefit running while the appeal is decided.

The notices are written in program language. The reason given is often a category rather than an explanation, and sometimes it does not match the facts of the case at all. A person who cannot tell which rule is being applied cannot tell whether the agency applied it correctly.

A system here reads the notice, says what is being decided and on what basis, checks that basis against the program's rule and against what the person says happened, and drafts the hearing request.

How it works today

A person reads a notice written for agency staff, works out which rule it relies on, whether that rule fits their situation, how long they have, and whether their benefits continue meanwhile. Then they write the request themselves, often without knowing which facts are the ones in dispute.

What a good system does

A good system reads the notice, says in plain words what is being decided and why, sets the stated reason against the program's rule and the person's own account, names the deadline and whether benefits can continue meanwhile, and drafts the hearing request around the facts that are actually in dispute.

How the service would work, step by step
Person uploads the notice What is being decided, and on what basis, is stated plainly Person says what they think is wrong about it The stated reason is checked against the program's rule The deadline and any continued benefits are worked out The hearing request is drafted around the disputed facts Person or advocate reviews it The request is filed in time
Person Deterministic check Output Human review

Who this serves: People whose benefits have been denied, reduced, or ended, and the advocates and benefits counselors who represent them at fair hearings.

The Package

Nothing in this package is written yet. The cohort takes the workflow on, writes the step-by-step agenda first so practitioners can argue with it, and the rest follows from what comes back. This page says plainly where each piece stands, and it changes as they exist.

A diagram of a tech system beside its specifications

Stage 1

Specify and build

Planned

What a good tool does at every step of this work, written so a practitioner can argue with it and a builder can build from it.

Planned

Step-by-step agenda

The work in order, with what a good tool does at each part, what it must never do, and one question for the practitioners who do this work. This is the first thing the cohort writes.

Planned

Functional Agenda

The same work written as a numbered specification, capability by capability, for a builder to build against and an evaluator to test against.

Planned

Reference Architecture

How the pieces fit together, and which decisions deterministic rules make rather than the model.

A clipboard headed how to test, with a pen

Stage 2

Test and run

Planned

How a team checks whether what it has is good enough to rely on, and how it keeps checking once the tool is running.

Planned

Conformance Standards

The tests a tool has to pass on accuracy, safety, usability, and whether the organization can keep it running.

Planned

Evaluation Protocol

Who runs the tests, what a pass takes in staff time, and how the results get written up so somebody outside the team can read them.

Join This Cohort

The public benefits cohort is forming now. Members bring what they have seen in their own practice, argue about what a tool here has to do, and read the drafts as they are written.

Join this cohort See all the cohorts