When income stops, the loudest problem is rarely the most urgent one. In the early builds of a peer community for people between jobs, the first-week guidance was organised by topic: money, housing, benefits, job search. People in the middle of that week did not experience it by topic. They experienced it as a queue of phone calls, each with a deadline they could not see, and the order they made those calls in changed the outcome more than how much information they had read.
That reframing is the subject of this post: what happened when the first week was rebuilt as triage — a short, ordered list of calls — instead of a library of advice.
Designing the triage list
Three choices shaped this part of the build.
First, the order is fixed and short: housing first, then utilities, then any loan or card payments, then subscriptions that can pause. Not because housing is more important in the abstract, but because the consequences of a missed housing payment escalate fastest and the hardship options are widest before a payment is missed, not after.
Second, every call has the same shape, written down in advance: say that income has stopped, ask what hardship or pause options exist, write down the name of the person spoken to and what was agreed, and confirm the next date before hanging up. A script sounds cold on paper. In practice it removes the hardest part of the call, which is deciding what to say while already stressed.
Third, the list ends. Four categories, a handful of calls, and then it stops. The first version kept adding worthy tasks — update this profile, research that programme — until the list described a month, not a week, and nobody in week one finished it.
What worked
Calling before a payment was missed changed the conversation in a way no amount of budgeting advice did. Providers who were contacted early treated the household as a household with a temporary problem and offered pauses, reduced payments, and deferred dates that were simply not offered once an account was already in arrears. The same call, made two weeks later, was a collections conversation. Timing was not a detail; it was most of the value.
The written record per call — a name, an agreement, a next date — prevented the second-most-common failure: a pause agreed on the phone and then lost because nobody could prove what was said, or a follow-up date missed because it lived only in memory. Three lines per call, kept in one place, was enough.
A fixed order also removed a daily decision. People did not have to wake up and rank their problems while frightened. The list had already ranked them, on a calmer day, by someone thinking clearly. That is a small design choice with an outsized effect on whether anything gets done at all.
What broke, or nearly did
The first version sorted by amount owed, largest first. That looks rational and behaves badly: the largest debt is often the one with the slowest consequences, while a small utility payment can disconnect quickly. Sorting by money optimised for the spreadsheet, not for the week. Sorting by how fast consequences escalate, and how much better the options are early, is what survived.
Scripts broke when they were written as word-for-word lines. People sounded like they were reading, agents responded to the reading instead of the situation, and callers abandoned the script mid-call and then felt they had failed it. The version that worked is a shape, not a script: four beats, in the caller's own words.
There was also an honesty problem in early drafts. They implied that every provider will help if you just call early. Most did, in the cases tracked during the build. Some did not — a landlord with no pause policy, a lender whose hardship programme starts only after a missed payment. Guidance that promises a good outcome from every call teaches people to distrust all of it after the first refusal. The shipped version says what is usually true, names the exceptions, and gives the next step for a no as well as a yes: get the refusal and the reason in writing, with a date.
Lessons for builders
Order by consequence speed, not by size. In a crisis week, what escalates fastest deserves the first call, even when it is not the biggest number.
Give people a shape for a hard conversation, not a script for it. Beats survive stress; memorised lines do not.
Make the record part of the task. A name, an agreement, and a next date, written down during the call, are worth more than a perfect plan recalled afterwards.
End the list. Triage that never finishes is just a longer library. A short list that people complete in the week it was designed for beats a complete list nobody reaches the end of.
The project behind these lessons is WUUUH, a peer community for rebuilding after a layoff, where action plans put the urgent steps first, official links are gathered in one place, and members share what providers actually offered when they called early.
Top comments (0)