What a good system for answering a debt collection lawsuit does
Somebody is served with a debt collection complaint, has a short window to answer, and often no answer is filed. Here is what a good system does, in order, with a question for you at each step.
This list comes from what the groups at a recent design workshop the Commons team ran said the work needs. Answer the questions on the parts you know from your own practice. The Commons team reads every answer, fixes what the list gets wrong, and takes the harder questions to the cohort working on this area.
Telling the person what to do on the notice itself
The papers are the one thing that reaches everybody who gets sued, and today they do not explain what answering does or who can help.
What a good system does
Carry the steps on the notice the person is served with, along with who can help.
Say what answering does and what it does not do.
Say what happens if nothing is filed, including that a judgment stays enforceable for years and can reach wages.
Give a way in from the notice itself, such as a code that opens the portal.
Who would have to agree to change what the notice says in your court?
Answer this
Part 2
Opening the case from the notice
A person who was sued is not in contact with the collector and often cannot tell what the case even is. Starting from the notice saves them from having to find their own case.
What a good system does
Open from the code on the notice, so the person does not have to search for their case.
Fill in the case number and the amount from the court record, and ask the person to confirm them.
Let the person say that the debt is not theirs.
Work for somebody who is not set up for electronic filing, because in some places people are locked into it whether or not it is working for them.
What it must never do
Share what the person enters with the collector or with anyone outside the court.
How does somebody sued in your court find out their case number and what is claimed?
Answer this
Part 3
Laying out the defenses
The protections that exist are not automatic, and the burden of showing what the collector has to show is effectively flipped onto the person who was sued.
What a good system does
Lay out the defenses available in that court and say what each one means.
Say what the collector has to prove, including what the affidavit and the note attached to the complaint are meant to show.
Name the protections that have to be claimed rather than applying on their own.
Be accurate about the deadlines and the filing requirements of that court.
What it must never do
Tell somebody they have no defense.
Which defenses do people in your court have and never raise?
Answer this
Part 4
Filing the answer in time
Judgment is entered for the collector because no answer came in, so the filing is the step the whole workflow turns on.
What a good system does
Track the window to answer and tell the person how long is left.
Produce the answer in the form the court accepts, including electronic filing where it is required.
Confirm that the filing was received and say what happens next.
Say which forms, deadlines, and filing rules are local, so a team in another county knows what it has to replace.
What makes an answer get rejected in your court?
Answer this
Part 5
Settling before a hearing
In some places the largest filers sit at tables on docket day and settle with the people who come, and in others nothing brings the two sides together before the hearing at all.
What a good system does
Let the person and the collector negotiate through the same portal, so neither side relies on a hallway conversation.
Show what a proposed schedule costs the person over its whole term.
Record what was agreed, and give the person a copy.
Schedule a hearing once a good faith effort to settle has been made.
What it must never do
Make settling easier to reach than a hearing.
Who is at the table on docket day in your court?
Answer this
Part 6
Reaching a person at any point
The process is confusing from start to finish, and the people who abandon it usually do so at the point where they needed to ask somebody a question.
What a good system does
Make a navigator or an attorney reachable at any point in the process.
Pass what the person has already entered to whoever picks up, so they do not start over.
Work for somebody who stops partway and comes back days later.
Who would answer that call in your county?
Answer this
Part 7
Showing that it works
The standards the cohort writes decide what counts as a system that worked here, and the measures below are the ones the groups asked for.
What a good system does
Check what the tool says about defenses, deadlines, and filing requirements against what that court requires.
Report who sees what a person enters.
Measure how much of a person’s time the process takes.
What would you need measured to believe this works?
Answer this
What happens to what you write
Every note comes to the Commons team. We read it, correct what this list gets wrong, and publish a new version saying what changed. The questions that need practitioners to argue them out go to the cohort for this area, which writes the functional agenda and the standards from what comes back.
A note about one line is as useful as a note that adds a whole step. If what you know is how docket day runs in your court, write about that.
The two agendas for this workflow
You are reading this one
Step-by-step agenda
This is the first round, and it collects what the people who do this work say a tool has to do, in the order the work happens and in plain words. Read it to argue with it, to correct it, and to say what your jurisdiction needs.
Not written yet
Functional agenda
The cohort writes the detailed specification after this round, using the answers that come back from this page. It numbers every capability, states the standard each one has to meet, and sorts them by the scope of the system being built, so a builder can build against it and an evaluator can test against it.
