Help a person get through the steps where SNAP applications are most often lost, such as documents, the interview, and card setup, so benefits are not denied over paperwork.
Why it matters for peopleGetting through the paperwork steps keeps food assistance from being denied on a technicality, so families can put their income toward rent and other needs.
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.
A SNAP application is decided on whether a household qualifies. A great many of them never reach that question, because the application closes at a step along the way.
The steps are ordinary and unforgiving. A document has to arrive in the form the agency asked for. An interview call comes from a number the person does not recognize, at a time nobody agreed, and a missed call can close the case. A card arrives and has to be activated. Each of these can end an application that would have been approved, and the person has to start again from the beginning.
A system here keeps track of where an application stands, says what the next step is and when it is due, and catches a closure that happened on process rather than on eligibility.
A person applies, then waits for instructions that arrive by mail or by phone. They have to send documents in a particular form, be available for a call that may come from an unknown number, and set up a card when it arrives. Missing any one of these closes the case, and the person often does not learn why.
A good system tracks where the application stands and what is due next, checks that what the person is about to send matches what was asked for, warns before a deadline passes, and flags a closure that looks procedural rather than substantive so an advocate can get it reopened rather than starting over.
Who this serves: People applying for or renewing food assistance, and the outreach workers, benefits counselors, and advocates who help them through the steps.
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.
Stage 1
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.
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.
The same work written as a numbered specification, capability by capability, for a builder to build against and an evaluator to test against.
How the pieces fit together, and which decisions deterministic rules make rather than the model.
Stage 2
How a team checks whether what it has is good enough to rely on, and how it keeps checking once the tool is running.
The tests a tool has to pass on accuracy, safety, usability, and whether the organization can keep it running.
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.
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.