When a Region Is Hit: Collections After a Disaster

A hurricane, flood, or wildfire does something no other event does to a portfolio: thousands of accounts go delinquent in the same week, for the same reason, in the same place. An operation still running its normal sequence will call, text, and write to people who have lost their homes, their workplaces, or their phones — recovering almost nothing and generating the kind of complaints and coverage that outlast the storm. The response has to be decided before the event, because in the first days after it there's no time to design one.

Why this isn't ordinary delinquency

	Ordinary delinquency	Disaster-driven delinquency
Cause	Varied, individual	One event, shared
Timing	Spread out	Simultaneous
Customer can respond	Usually	Often not — displaced, no services
Contact data	Mostly valid	Address and phone may be useless
Says something about the borrower	Sometimes	Almost nothing

The last row is the principle. A missed payment the week after a flood tells you about the flood, not about the borrower. Per our segmentation analysis, treatment should follow the reason an account isn't paying — and here the reason is known, shared, and temporary for most.

Per our correlation analysis, a disaster is also the case where every protection a household has fails at once: work stops, property is damaged, local family is affected too. The borrower's usual ways of finding the payment are gone at the same time as the payment falls due.

Finding the affected accounts

The first task, and it needs to happen the same day.

1. Map the affected area to postal codes, using official declarations where they exist and news where they don't yet.
2. Flag every account with an address in those areas — service address and mailing address, since they can differ.
3. Include business accounts in the area, and consumers whose employer is there if you know it.
4. Accept self-identification — anyone who tells you they're affected is treated as affected, whatever the postal code says.
5. Widen the area as declarations expand, which they usually do over the first days.

Item four matters because addresses lag reality. People who moved recently, who work in the affected area, or whose family is there won't show up in a postal-code match — and per our vulnerability analysis, a disclosure should change treatment as fast as a flag does.

What to switch off first

Before anyone reviews individual accounts — stop the machines.

• Automated dialers and texts to the flagged accounts.
• Letter runs — including ones already printed and queued.
• Late fees and penalty interest for the affected period.
• Negative reporting pending review.
• Automatic payment retries that will bounce against empty or inaccessible accounts, per our failed payments guide.
• Placements with agencies and any litigation steps.
• Repossession or enforcement activity.

Per our restrictions analysis, a pause is only as good as its propagation: it has to reach the dialer, the letter vendor, the text platform, and any agency, or the flag sits in one system while the others keep running. Test that it's reached each channel the same day.

Accommodation at scale

The offer has to be simple, because the people receiving it have no capacity for anything else.

Accommodation	Purpose
Payment deferral or skip for a defined period	Removes the immediate obligation
Fee waivers for the affected period	Prevents the balance growing from penalties
Term extension to absorb deferred payments	Stops deferred amounts all falling due at once
Interest reduction, where economics allow	Keeps the balance manageable
Longer restructuring for those still affected later	For accounts where recovery is slower

Make it proactive. Offer it to everyone flagged, rather than waiting for a hardship application. Per our time analysis, a process that requires documentation and a call during business hours will be completed by the least affected people and missed by the most affected.

Make acceptance minimal — a reply, a click, a single call — per our self-service analysis. And per our workout analysis, the economics favour it: an account kept whole through a deferral is worth far more than one pushed into charge-off by pressure it couldn't respond to.

Regulators have frequently encouraged lenders to work with borrowers after declared disasters, and some programmes attach specific requirements to particular loan types. Check what applies with compliance before the event, so the offer is designed in advance.

What to report

The decision with the longest consequences for the borrower.

A disaster-driven missed payment reported as ordinary delinquency can affect someone's access to credit for years — per our record retention analysis, at full weight in many uses — at exactly the moment they need credit to rebuild.

• An agreed deferral changes what's due, and reporting should reflect the terms actually in force.
• Metro 2 includes a special comment code for accounts affected by a natural or declared disaster (code AW in current guidance), which tells users of the file why the account looks the way it does. Confirm current usage against the reporting guide.
• Remove the code when it no longer applies, since a stale flag is its own inaccuracy.
• Review any negative reporting that went out before the flag was applied.

Per our reporting analysis, accuracy is the obligation — and accurate reporting of a disaster account means reporting the accommodation and the reason, not the payment that the disaster made impossible. Review the approach with compliance.

Reaching people who've been displaced

Contact data is frequently useless after a disaster — the address is uninhabitable, the phone was lost, the landline no longer exists.

• Use every channel you have consent for — email and app notifications often survive when addresses don't.
• Publish the offer publicly — on your site, in local media — so people can find it without being reached.
• Run inbound lines with extended hours, per our inbound analysis, staffed by people with authority to apply the accommodation on the call.
• Accept updated contact details easily, and treat them as temporary.
• Don't treat silence as refusal. An unanswered offer from a flooded area means an unreached customer.

And be alert to what may also be happening: some borrowers will be dealing with a death or serious injury. Per our deceased accounts guide, those accounts need their own handling, and the first contact from family may come months later.

Planning the return

The second wave, and it's avoidable.

Deferrals end — often for thousands of accounts on the same date — while the region may still be recovering. If deferred payments are added to the next instalment, a household that could just manage one payment faces two.

1. Decide at the start how deferred amounts will be repaid — term extension is usually kindest and most collectable.
2. Contact customers before the deferral ends, with the new schedule.
3. Offer an extension to anyone who says they can't resume.
4. Stagger resumption if the operation would otherwise face a wall of accounts in one week.
5. Watch early performance closely, per our cure analysis — accounts that resume and hold are fine; accounts that break need a fresh look, not the standard sequence.
6. Keep the treatment separate from ordinary collections for a defined period.

Item five matters for measurement too. Per our early warning analysis, disaster-affected vintages will look unusual for months — keep them out of model monitoring and performance benchmarks, or they'll distort every signal about the rest of the book.

Preparing before it happens

Everything above is faster if it's decided in advance.

• A written disaster playbook — who decides, what's paused, what's offered.
• A tested geographic flag that can be applied to a list of postal codes in hours.
• A pre-approved accommodation with compliance sign-off already obtained.
• A kill switch for each automated channel, tested — including for vendors.
• Pre-written customer messages and a public notice template.
• A reporting procedure for disaster status.
• Portfolio concentration awareness — per our correlation analysis, knowing how much of the book sits in high-risk regions tells you how large the response will need to be.

Run it once as an exercise. Pick a region, apply the flag, confirm every channel stops, and time it. The gap between "we have a plan" and "the dialer stopped" is usually discovered during the real event, which is the worst time to find it.

Frequently asked questions

---

This guide is educational and does not constitute legal or compliance advice. Regulatory expectations following declared disasters, programme-specific accommodation requirements, credit reporting standards and codes, and collection conduct rules vary by product, lender type, and jurisdiction and change over time. Confirm current reporting guidance and consult your compliance function and counsel before and during any disaster response.