Help a person who owes court debt after a criminal case ask for it to be waived or reduced, with the presumptions established, the hardship documented, and the argument ready for the hearing.
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.
People leaving the criminal justice system often owe the government large amounts in fines, fees, and court costs. The amount grows with late charges, and falling behind can bring a suspended license, a warrant, and a collection account. For somebody earning low wages the debt can look permanent.
A court can waive or reduce that debt when a person shows they are unable to pay. In some places a clerk has to start that process once a person falls behind. A summons arrives in the mail scheduling a hearing about ability to pay, and going to that hearing is what stops the court from issuing a warrant. A person can also ask for the hearing themselves.
Somebody has to find every case and every balance across counties and across more than one record system, establish any presumption the statute provides, fill in an affidavit about benefits, household, income, expenses, assets, employment, health, and hardship, gather proof, write a motion tying each hardship to the statute, and make the argument at the hearing. The affidavit is the sworn statement a judge decides from, and the motion is the legal argument filed alongside it.
What a court has to weigh is set by statute. The statute behind these materials lists household income and living expenses, the number of dependents, assets, child support obligations, physical or mental health conditions that reduce a person’s ability to earn or manage money, and other case-related costs. It leaves child support income, need-based government assistance, and assets exempt from bankruptcy out of the calculation. It also presumes that a person is unable to pay when they are designated totally disabled, receive certain need-based benefits, receive a housing subsidy, or earn below a set share of the federal poverty level.
The form, the statute, and the local practice differ from state to state. The work itself is much the same everywhere: a court applies a test, a presumption can settle part of it, and a document has to set out the person’s situation in enough detail for a judge to act on.
The same request gets prepared in very different settings. A legal team may sit with somebody for hours well before the hearing, may meet them in a courthouse hallway minutes before it, may work with them across several months in a diversion program, or may hand them a guide and leave them to do it alone. A good system has to produce a sound document in all of those.
The affidavit is a financial breakdown and a persuasive document at the same time. The filings that succeed tell a connected account of employment, housing, health, and family, and tie each part of it to the statute.
A summons arrives and some people do not know a waiver is possible at all. They come to the hearing afraid that showing up is what gets them arrested, fill in the form in the hallway minutes beforehand with nobody to ask, answer the judge’s question about how much they can pay each month with a number they cannot afford, and leave on a payment plan. Where a legal team is involved, a paralegal spends hours opening case records one at a time to work out what is owed.
A person knows before the hearing what it is for and what can come out of it. Every case and balance is found across counties, with what can be waived separated from what cannot. Any presumption is established and documented. The affidavit comes out of a conversation in plain language that draws out the past as well as the present, and the motion ties each hardship to the statute. The sensitive material reaches the judge without going onto a public docket, and the advocate has the argument ready in a short version and a long one.
This is one vision, taken from the workflow a legal aid reentry practice already follows. Technology could play out in other ways here, and the cohort weighs them against this one.
Who this serves: People who owe court debt after a criminal case, the paralegals and attorneys who prepare these requests, the public defenders who raise ability to pay at a plea, the court staff who schedule these hearings, and the judges who decide them with little legal support of their own.
Where this came from: A legal aid reentry practice shared the workflow it follows, the affidavit form it uses, the rubric it scores a good affidavit against, and the checklists it wrote for the tools it wants. This page is built from those materials. The cohort for this area picks it up from here.
Court debt is one of several things that follow a person out of the criminal justice system. These are the workflows around this one, with the point where each one hands over.
Criminal records data assembly and analysisWorking out what a person owes means reading the same records that workflow assembles, across every county and every case. What it produces is the balance this workflow asks the court to waive. Expungement eligibility screeningUnpaid court debt can prevent a record from being cleared, so getting the debt waived is often the step that comes first. Court record retrievalPulling the dockets, the sentencing documents, and the payment history is machinery several of these workflows need, so it sits on the common tools page rather than here.The step-by-step agenda is open for review now. The cohort writes the functional agenda and the standards from the answers that come back, and this page carries them when they exist.
What a system here has to do, written as the work in order and in plain words, with the question the Commons team wants answered about each part. Start here if you prepare these requests or decide them, and want to say what a tool needs.
Read the step-by-step agenda →What the system must do, from explaining what the hearing is for, through finding every balance across counties, checking whether the law already presumes the person cannot pay, filling in the affidavit with them, gathering the proof, writing the hardship account and the motion, deciding what goes in the public file, preparing the argument, and recording what the judge decided. Two findings from the practice belong in the specification: a tool that reports a confident total from a record it could not fully read is worse than one that says it does not know, and an affidavit saying a person is employed without saying it is 10 hours a week at minimum wage reads to a judge as somebody who can pay.
How anyone judges whether a builder did this well: whether the affidavit is complete and specific, whether every figure traces back to something the person said or a document they provided, whether a contradiction in the answers is shown rather than written around, whether the totals match the court records, and what the reviewing attorney still has to correct. A rubric for a good affidavit already exists, written by the people who prepare them, and the cohort starts from it.
The rest of the package follows once those two exist. It covers the baseline numbers, the procurement and contract terms, the reference architecture, which says what any jurisdiction can take as it is and what each place has to set for itself, the stories and materials from teams who have already built something here, and the tests.
The reentry cohort is forming now, and this is one of the workflows in front of it. Members bring what they have seen in their own courts, argue about what a tool here has to do, and read the drafts.