mortgagelead-follow-upcrm

VantageScore 4.0 for Loan Officers: Which Old Leads to Re-Pull

·Terrell Gentry·9 min read
VantageScore 4.0 for Loan Officers: Which Old Leads to Re-Pull

The Oct 1 single-grid change means a score you declined six months ago might price differently today, and the Oct 12 WSJ story has your whole feed asking the same thing. The real question isn't the policy. It's which of the thousands of files already in your CRM and loan origination system (LOS) are worth re-pulling, and who on your team actually does the re-work before the moment passes.

Quick answer: For loan officers, VantageScore 4.0 matters most as a reason to re-work past files, not just new ones. As of Oct 1, 2026, Fannie Mae and Freddie Mac price Classic FICO and VantageScore 4.0 on one loan-level pricing grid, and VantageScore 4.0 ran 11-12 points higher than classic FICO on average in Rocket's review of ~1.4 million reports. Re-pull the borderline and just-declined files where a 10-12 point lift could cross a qualifying threshold, confirm the qualifying model with secondary marketing first, and assign one owner per file.

What actually changed on Oct 1, and why it's a workflow trigger

The change is that two credit models now price on the same grid, and lenders can pick the model one loan at a time. That's it. But for a sales team it turns a dead file into a maybe.

Per HousingWire, FHFA's single-grid move removed the prior 20-point downward adjustment on VantageScore 4.0, so a 680 is now priced as a 680 regardless of which model produced it. Credit Technologies' plain-English guide adds the other half: since Sept 9, 2026, any approved Fannie/Freddie lender can use VantageScore 4.0, choosing the model loan by loan, with one model per loan and the same model for every borrower on the file. The model locks at delivery.

Why this reaches into your database: a Credit Law Center explainer notes VantageScore 4.0 uses trended data and generally excludes paid collections, which can help borrowers with paid collections or recent paydown progress. The Yahoo Finance writeup of the WSJ story, quoting Rocket's Bob Banfield, puts the average gap at 11-12 points higher across those 1.4 million reports. A borrower you declined at 618 on classic FICO is the one worth a look. Not every file. The ones sitting just under a threshold.

Which past files are worth re-pulling (and which aren't)

Re-pull the files where a 10-12 point lift plausibly crosses a line that mattered, and leave alone the ones where it wouldn't change anything. The cost of guessing wrong is a second hard inquiry on someone you've already contacted once, so this is a prioritization problem, not a mass re-pull.

Three groups tend to pay off, per the Credit Law Center breakdown:

  • Just-missed borrowers who fell a handful of points below a qualifying or pricing threshold on classic FICO.
  • Borrowers whose file carried paid collections that classic FICO still counted against them.
  • Borrowers who've been paying down balances since you last pulled, where trended data now reads the direction, not just the snapshot.

What to skip: files where the gap to the next threshold was 40 points, files already deep in another product, and anyone who opted out of contact. A higher VantageScore does not automatically mean approval or better pricing. Credit Law Center is explicit that lender guidelines, underwriting, and investor considerations still apply. That's the line that keeps your re-contact honest, which matters a lot when you're reaching back out to someone you already told no.

One guardrail before you touch any borderline file: Credit Technologies advises confirming with your secondary-marketing team which score model is used for qualifying on each loan. And classic FICO is still required for manually underwritten loans per HousingWire, so VantageScore 4.0 only helps on the DU/automated-underwriting conventional path.

How to surface those files without reading every record by hand

Pull a filtered list, don't scroll your pipeline. The files that qualify for a second look are defined by data you already have: decline reason, the score on record, loan type, and the date.

Here's the manual version, which works if your book is small enough:

  1. In your LOS or CRM, filter for files declined or marked dead in roughly the last 12-18 months on conventional, DU-eligible scenarios.
  2. Narrow to records where the credit score on file sits inside a band below the threshold that mattered, usually 5-15 points, since that's the range a VantageScore lift would cover.
  3. Flag paid-collection and recent-paydown notes, since those are the trended-data wins.
  4. Set each flagged file aside for the qualifying-model check with secondary marketing before anyone re-pulls or re-contacts.

The trouble shows up at step one. Most teams don't have a clean "declined, 5-15 points under, conventional, paid collection" view. The data is split between the CRM (often Follow Up Boss) and the LOS, the notes live in free text, and nobody has the afternoon to read a thousand records. This is the same leak behind every past-client reactivation effort: the inventory exists, the capacity to work it doesn't. We've written about where that volume actually hides in where mortgage volume comes from and about the pre-approved buyers who went quiet and got buried, and the mechanics are identical here.

This is the part SalesOS is built for: it reads the files you already own across the CRM and LOS, surfaces the ones that match a rule you set (declined conventional, score in a 5-15 point band, paid-collection flagged), and queues them for re-engagement in your team's own voice, so the back catalog gets worked instead of written off. See how AI Cofounder works. It follows the rules your team sets on who to contact and how; your compliance team decides what's allowed, and re-pulling anyone's credit still requires the permissible purpose and consent your process already handles.

Who owns re-working these before the window closes

Assign one owner per file at the moment it's flagged, not "the team." A re-pull list with no name attached is the same as the declined list it came from: everyone assumes someone else has it.

The cleanest split is the LO owns the borrower conversation and the yes/no on re-pulling, an assistant or processor owns pulling the confirmed-eligible list and running the first re-contact, and secondary marketing owns the qualifying-model call per file. The failure mode is the opposite of a fast-closing window. Lenders can choose VantageScore 4.0 loan by loan and are turning it on gradually, so past files keep becoming re-work candidates as adoption spreads. That makes it a standing process, which is exactly why it dies on a human's memory. A spreadsheet of 60 re-pull candidates gets worked for a week and abandoned, and the same capacity problem that killed the first follow-up kills the second.

Tracking which re-pulled files actually moved matters as much as surfacing them. If you can't see which candidates got re-contacted, which re-pulled, and which went cold again, you're running blind and you'll re-pull someone twice. We cover the live-pipeline version of this in ending the weekly status meeting.

Manual re-pull sweep vs. a system that works the database

The gap between doing this by hand and running it as a system isn't effort, it's whether it happens at all after week one.

Manual sweepWorked as a system
Finding candidatesRead records across CRM and LOS by handFiltered list against a rule you set, across both systems
PrioritizingGuess from memoryScore band, decline reason, and paid-collection flag applied consistently
Who owns it"The team"One named owner per flagged file
Follow-up after first touchStops when someone gets busyContinues in your templates until the lead acts or is clearly dead
Tracking what movedAnother spreadsheetOne view of re-contacted, re-pulled, and gone-cold-again

The manual sweep is worth doing if your book is a few hundred files and someone has a quiet week. Past that, the thing that stops teams isn't knowing which files to re-pull. It's working inventory that sits in a system nobody has time to read.

FAQ

Do loan officers need fresh borrower consent to re-pull credit under VantageScore 4.0? Re-pulling credit requires a permissible purpose and the borrower consent your process already handles for any new pull, and adding a score the lender didn't originally pull means a second hard inquiry per Credit Technologies. Treat a re-pull like a new file for consent, not a free lookup, and let your compliance team confirm what your re-contact outreach can say.

Does a higher VantageScore 4.0 guarantee a past-declined borrower now qualifies? A higher VantageScore 4.0 does not guarantee approval or better pricing. Credit Law Center is clear that lender guidelines, underwriting, and investor considerations still apply, so the right move is to re-pull and re-evaluate the borderline files, not to promise the borrower a different answer when you re-contact them.

Is this VantageScore 4.0 re-pull opportunity a one-week window? Re-pull candidates keep emerging as lenders turn on VantageScore 4.0 gradually, loan by loan, so this is a standing process rather than a one-time event. That's exactly why a repeatable workflow beats a single manual sweep: the list grows on its own, and a spreadsheet nobody updates stops working fast.

How is the VantageScore 4.0 re-pull list different from my refi or pre-approved-but-never-bought lists? The VantageScore 4.0 list is defined by credit model and score band, while refi recapture is defined by rate and the pre-approved list is defined by a stalled application. They're different filters on the same owned database, and a team that can surface one can usually surface all three from the same CRM and LOS data.

Does VantageScore 4.0 help on every conventional loan? VantageScore 4.0 only helps on the DU/automated-underwriting conventional path. HousingWire reports classic FICO remains required for manually underwritten loans, so confirm the file is eligible for automated underwriting before you treat a VantageScore lift as a reason to re-pull.

If you're sitting on a book of declined and borderline files and the real blocker is that nobody has time to read a thousand records and work them, that's the exact leak SalesOS is built to close. Book a demo and we'll walk through surfacing and re-engaging the past leads already in your systems.

About Terrell Gentry

Founder at 6omb

Terrell is the founder of 6omb and runs Claude Community, the #1 Skool community for Voice AI agents. Over 16 months his team has built 100+ AI agent systems delivering $10M+ in business value, including voice agents like Emily, which booked 453 new clients for a law firm in 8 months. He is a Y Combinator Startup School alum (SUS20) and a Gold Retell partner.

AI AgentsClaude CodeVoice AIBusiness AutomationGrowth Marketing

Close more of the deals you already have

SalesOS follows up with every lead in your own voice, keeps your CRM in sync, and shows you where every deal stands. See it working on a pipeline like yours.

Book a Demo