By the time a meaningful rate move shows up in your origination volume, you have roughly six weeks before it shows up in your closing volume. That’s the operational lead time. Most title companies are using those six weeks to be surprised.

The Refi Cycle post on May 26 made the case that the next refi wave isn’t a question of if but when, and that the trigger — a meaningful sustained move in the 10-year, probably in the 75 to 125 basis point range from current levels — isn’t predictable, but the response to it is. This post is the operational follow-up: what those six weeks actually look like, and why most operations don’t use them well.

The Sequence

Rates drop. Mortgage applications spike — this shows up in the MBA weekly survey within about 7 to 10 days of the move. The applications that pencil get into the lender’s pipeline another week or two after that. The lender pulls a title commitment somewhere in the 2-to-4-week window from application. The file lands in your queue. From there, depending on your operation, you’re 21 to 35 days from closing. Add it all up and the front-end-to-closing lag is about six weeks. That’s not a precise number — it can be four weeks on a very fast lender and eight on a very slow one — but it’s the right order of magnitude.

The implication is that the operational signal arrives in advance of the operational impact. You can see the file count starting to swell in your queue two to three weeks before your closing volume actually moves. You can see the rate-lock indicators in the lender data even before that. By the time your closers are drowning, the information you needed to staff for it was sitting in your system three to six weeks earlier.

Most operations don’t use this. The reason is structural, not lazy. The people who watch the macro — rates, applications, mortgage news — are usually not the people who watch the operational pipeline. The people watching the pipeline are watching it day-by-day, file-by-file, and don’t have a lens on the four-week-forward picture. The two signals live in different parts of the building. By the time they converge into “we’re about to be overwhelmed,” it’s a week before the wave actually hits, and by then your only options are mandatory overtime and turning away files.

The Fix Isn’t Complicated

You don’t need a new system to do it. You need three things. First, a small dashboard that shows incoming file count by week, not by day — the day-by-day view masks the trend. Second, a tie between that dashboard and a macro signal you trust — the MBA weekly applications index is free, public, and updated every Wednesday, and it leads your file count by about two to three weeks. Third, a pre-agreed staffing posture for each combination of those two signals: applications up plus pipeline up equals surge mode kicks in at a specific threshold, not when the closers are already underwater.

The actual operational moves inside surge mode are the boring stuff — examiner overflow agreements with two or three other operations, a tested process for splitting search and exam, a pre-approved closer floater list, a clear policy on what files you don’t take during peak. All of that is doable in the six-week lead time. None of it is doable in the one-week panic.

If you’ve never built this kind of macro-to-operational tie before, walk through your refi-readiness gaps with us. We’ve built the dashboard for a few dozen agents at this point, and the patterns of what breaks — and what people get wrong about staffing the wave — are pretty consistent across operations.

Walk through your refi-readiness gaps with us — request the audit →