Help a person with a disability complete the Social Security disability application and its supplementary forms, so the first application has what it needs.
Why it matters for peopleA complete first application can avoid a denial and the long appeals that follow, so disability income arrives sooner.
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.
The disability application asks for a person's work history, every place they have been treated, and how their condition affects ordinary activities. Supplementary forms ask the same ground again in more detail, in language that does not match how anybody describes their own day.
An application that leaves out a treating source, or describes a good day rather than a usual one, tends to be denied. The appeal that follows takes a long time, and the person is without income while it runs.
A system here takes what the person says in their own words and turns it into the answers each form asks for, then shows what a decision-maker would still want to know.
This workflow sits next to Medical Records Review, which handles the evidence once it has been collected.
A person fills in long forms about work history and daily function, often while unwell, listing treating sources and dates from memory. They send it without knowing what the decision-maker is looking for, and the first time anyone reviews the answers is after a denial.
A good system asks the person about their work and their day in ordinary language, turns what they say into the answers each form asks for, builds the list of treating sources with dates, flags what a decision-maker would ask about and is missing, and hands a complete packet to the person and their advocate.
Who this serves: People applying for disability benefits, and the advocates, benefits counselors, and clinic staff who help them prepare an application.
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.