How to Build a Weekly Renewal Action List

A brokerage with 400 funded borrowers and 65 renewals maturing in the next six months does not have a motivation problem. It has a sorting problem.

Sixty-five names is a pile. Nobody works a pile on a Tuesday morning. Eight to twelve names, ranked, with a reason attached to each, is an hour of work — and it is the same sixty-five names, seen differently.

This is how to produce that list.

What the list is

One output, produced on the same day each week, containing only the borrowers someone should contact this week.

Three properties do the work:

• Bounded. If it is longer than a person can work in a sitting, it will not be worked.
• Ranked. The most valuable conversation is at the top.
• Reasoned. Each row says why it is there, so nobody has to reconstruct the context.

Everything else is detail.

The fields

Eight columns. More than this and the list becomes a report; fewer and it is not actionable.

Reason is the field most often left out and the one that makes the list usable. "90-day window, no contact since funding, $612k" tells someone what they are walking into. A name and a date does not.

Outcome is the field most often left blank. Without it the list regenerates identically each week and the team learns to distrust it.

Ranking

Sort by time pressure first, then value, then silence:

1. Anything inside 30 days, largest first.
2. Anything inside 60 days, largest first.
3. 90-day window, largest first, prioritising borrowers with no recorded contact.
4. 120-day window, only if there is room.

That ordering encodes a judgement worth stating plainly: a smaller mortgage at 30 days beats a larger one at 90. Time pressure is not recoverable and size is not urgent. A $200,000 renewal maturing in three weeks is a decision being made right now; an $800,000 renewal at 100 days will still be there next week.

The exception is the outer edge. If a very large balance enters the 120-day window and nobody has spoken to that borrower since funding, lift it to the top regardless. That is not a renewal touch, it is a relationship repair, and it needs longer than four months.

Where the fields come from

Most of this is derivable from records a brokerage already has.

• Days to maturity — from the renewal date, or derived from close date plus term where it was never recorded directly.
• Window — bucketed from days to maturity.
• Last contact — only reliable if recording a touch is part of making it. If it is a separate administrative step, this field will be empty within a month and the list will start double-contacting people.
• Reason — assembled from the other fields: window, silence, amount.
• Owner — assigned by whatever rule fits: originating broker, geography, round-robin. The rule matters less than the field never being empty.

The genuinely manual field is Outcome, and it is worth protecting. It is what turns the list from a static extract into a process that learns.

The weekly routine

The routine matters as much as the list.

Same day, same time. Monday morning is common; the specific day is irrelevant and the consistency is not. A list produced when someone remembers is produced during quiet weeks, which are the weeks it matters least.

Produced by someone other than the caller. Where the person making the calls also assembles the list, the list gets assembled when the calls feel worth making. Separating the two is the single most effective structural fix available.

Reviewed, not just distributed. Ten minutes at the end of the week: what got worked, what did not, what happened. Rows that were not worked either roll forward with higher priority or get explicitly dropped — never silently.

Bounded deliberately. If the list runs long, cut it at what is workable rather than shipping fifty rows. A list of twelve that gets worked beats a list of fifty that gets skimmed.

Two rules that keep it honest

Suppression is checked before every outbound step. A borrower who asked not to be contacted must be excluded from the list, not merely skipped by whoever is calling. Relying on the caller to remember means it holds until someone is away.

Missing consent flags, it does not hide. A borrower whose consent status is empty or withdrawn should still appear, marked as unable to be contacted electronically. Dropping them silently means the record never gets fixed and the borrower stays invisible indefinitely.

What the first list usually reveals

The first time a brokerage produces this properly, the list is rarely the interesting part. The interesting part is what will not go on it:

• Borrowers with no derivable maturity date
• Borrowers with no recorded contact since funding — often a large share of an older book
• Borrowers whose contact details are years stale
• Duplicate records for the same person under two email addresses
• Borrowers already past maturity that nobody noticed

That residue is usually more valuable than the list itself, because it is a precise inventory of where the process has been leaking. The names that cannot be ranked are the ones that have been invisible the longest.

Doing this by hand

For a smaller book, entirely reasonable. A brokerage with 120 funded borrowers can maintain this in a spreadsheet with a sort and a filter, and should.

The honest threshold is roughly where deriving the list stops taking ten minutes and starts taking an hour. At that point it stops happening weekly, and a list that happens monthly is not the thing described here — it is a report.

That is the point at which producing the list needs to stop being a person's job. Not because the work is complicated, but because it is repetitive, and repetitive work performed by a busy person is the first thing dropped in a busy week.

The operating guide covers the surrounding process, and the cadence guide covers what to actually say at each window.