Help a person who has been offered a settlement by a debt collector understand the terms, check whether they can pay, and negotiate a plan they can keep.
Why it matters for peopleA fair, affordable settlement ends the case without a judgment, a garnishment, or a payment plan the person cannot keep.
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.
Before a hearing, or in a letter after one, a collector offers to settle. The offer can be a good one, and it can be worse than what the person would get by defending the case.
The terms are what decide that. Whether the payment resolves the whole debt or only part of it, whether a missed payment restores the full amount and enters judgment, whether the account is reported as settled or as unpaid, and whether the collector gives up the right to sue again. A plan set at more than the household can carry breaks, and a broken plan usually leaves the person where they started with a judgment on top.
A system here reads the offer, states what it actually says, and sets the monthly payment against what the person has told it they can pay.
A person reads an offer alone, under time pressure, usually without knowing what the alternatives are or what defenses they have. Agreeing to a payment that is too high is common, and so is agreeing to terms that put a judgment back in play on one missed payment.
A good system reads the offer and states each term in plain language, including what happens on a missed payment, compares the payment to what the person says they can afford, and names the alternatives, including any defense in the case that has not been raised. The person decides whether to accept, counter, or defend.
Who this serves: People offered a settlement by a debt collector, and the advocates, hotline staff, and clinics who advise them before they sign.
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.