Help a person who owes fines, fees, or a traffic ticket ask the court to reduce or waive what they cannot afford, and get a suspended driver's license back.
Why it matters for peopleFines and fees set at what a person can pay keep a ticket from turning into a suspended license, a lost job, and a growing debt.
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 ticket or a court case leaves a person owing money to a court. Left unpaid it grows with penalties, goes to a collection agency, and in many places puts a hold on the person's driver's license. Losing the license often costs the job that would have paid the fine.
Courts can usually reduce the amount, waive it, set a payment plan, or allow community service instead, based on what the person can afford. The person has to ask, on the court's own form, with something showing what they earn and what they spend. Each court does it slightly differently, and somebody with tickets in more than one place is asking several times.
A system here gathers what is owed, assembles what the person can show about their finances, and drafts the request each court wants.
This workflow overlaps with Waiving Fines and Fees After a Criminal Case in the reentry cohort. The two cohorts share what they write rather than drafting the same ability-to-pay material twice.
A person works out what they owe, case by case and court by court, finds which court takes which kind of request, fills in a financial statement by hand, and asks. A license hold usually runs on its own track, so clearing the debt and getting the license back are two separate errands.
A good system pulls together what is owed across cases and courts, turns what the person says about income and expenses into the financial statement each court asks for, drafts the request, and says what order to do things in so a license comes back soonest.
Who this serves: People who owe court debt, and the advocates, clinics, and court self-help staff who help them ask for relief.
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 debt collection 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.