The 1:1 goes like this. You open the folder, read the funded number out loud, and it's down. He agrees it's down. He mentions the market, mentions June, mentions two good ones that should come together in a couple of weeks. You nod, say something about consistency, and book the next one for a month out. Forty minutes, and neither of you touched anything that could still change.
That meeting isn't a failure of effort. It's a failure of timing. A purchase file runs roughly thirty to forty-five days from application to funding, and the application came out of a lead somebody worked days or weeks before that. The number you just read out loud was decided six to ten weeks ago, by behavior that is finished. You can review a funded number. You cannot coach one.
The short version
- Coach inputs, not the scoreboard. Funded volume is a receipt — by the time you read it, the coachable moment is six to ten weeks gone.
- Four gauges, weekly, per LO: applications taken, pull-through, speed to conversation, pipeline age. Four is the ceiling. Track ten and you coach none.
- Define them so they can't drift: pull-through by application cohort, speed measured to a live conversation, age from the last material status change.
- Pull-through is usually the cheapest lever you own. It costs discipline, not lead spend.
- Fifteen minutes, weekly, prep done before anyone sits down. Public volume, private diagnostics.
Funded volume is a receipt
A scoreboard tells you whether you're winning. It cannot tell you what to fix, because by the time it moves, the swing is over.
Everything upstream is different. Applications taken this week are fundings six weeks out. A lead that sat until Thursday is a conversation somebody else had on Monday. A file that hasn't moved in eight days is an agent quietly deciding where the next referral goes. Those are readable now, and the behavior behind each one is still available to change this week.
So: a short list of inputs, wide enough to cover the funnel end to end. Four covers it.
The four gauges
Applications taken. The most direct thing an LO controls. Weekly, never monthly — a two-week app drought is a coachable event; a month-end drought is a post-mortem.
Pull-through. The share of applications that reach the closing table. This is the quality check on the first gauge. An LO with plenty of apps and weak pull-through isn't producing, he's generating motion, and motion costs your processor real hours. Split the fallout two ways. Denied points at the front of the file: thin qualification, income taken at face value, documents promised for later. Withdrawn usually means the borrower left for somebody else — a service problem or a rate-shop problem — and that's the one that should sting.
Speed to conversation. Not first attempt. Not first text. The clock stops when a human being on the other end is actually talking to your LO. On a fresh purchase lead the person who has the first real conversation usually gets the application, and this is the most trainable number on the list because it's pure habit: what interrupts the LO, what happens to a lead that lands at 6pm, whether follow-up is scheduled or improvised.
Pipeline age. Days a file has sat in its current stage past what that stage should take. Stuck files are always specific — a condition nobody owns, an appraisal nobody chased, a verification sitting in somebody's inbox. Age is your only forward-looking gauge on work already in the building.
Front, quality, speed, flow. One page per LO, every week.
Define them so they can't lie
Every metric gets gamed the moment it gets coached — usually not maliciously, just drift. Write the definitions down before you start, or you'll spend the fall arguing with your own dashboard.
Two deserve another sentence.
Pull-through has to be measured by cohort. Funded-this-month over apps-this-month is arithmetic, not information; when volume moves, the ratio swings for reasons that have nothing to do with the loan officer. Take the applications from one month, follow that group, read the result ninety days later. It lags by construction, which is fine: you're sizing a problem, not catching one in flight.
Age counts material change, not activity. If a note in the file resets the clock, every file in your branch will get a note by Friday. Count from the last real event: document received, condition cleared, appraisal in, submitted, approved.
Which gauge to push, and the arithmetic behind it
Managers reach for the app count by reflex. Run the numbers first.
Say an LO takes eight applications a month and about two thirds of them fund. Call it 5.2 units. To buy a unit with volume, he needs ten applications: twenty-five percent more prospecting, more lead spend, and more of your processor's week spent on files that were never going to close. To buy roughly the same unit with quality, pull-through moves from two thirds to four fifths on the same eight applications.
One route costs money and hours. The other costs discipline at application: verify income instead of accepting it, collect documents on the call instead of promising to, decline the file that only exists to hit an app goal.
Then make him do the math himself. On a hypothetical $320,000 average loan at 100 basis points of LO comp, that unit is roughly $3,000 a month in his own pocket, from a habit change that needs zero new leads. Coaching lands differently when the arithmetic is his.
The gauge picks the conversation
Without numbers, every 1:1 is "how's the pipeline?" — and the pipeline is always fine until the month closes soft. With them, the conversation picks itself.
- Apps down. Activity problem. "Walk me through last Tuesday, hour by hour." Something ate the calendar. Find it before you talk about goals.
- Pull-through down. Quality problem. "The last three that died — what did we know at application and ignore?" Then separate denied from withdrawn, because they're different failures with different fixes.
- Speed slipping. Systems problem. "A lead lands at 4:40 on a Friday. What happens to it?" Fix the routing or the habit. Don't fix the person.
- Age climbing. Ownership problem. "Name the file, the condition, the person, the date." Nothing short of all four counts as an answer.
None of those are about attitude. They're about mechanisms — which is what keeps coaching from turning into a lecture.
Fifteen minutes on rails
Weekly 1:1s die for one reason: they cost too much. An hour per LO, half of it spent hunting numbers, and by week six it's quietly off the calendar.
Cap it at fifteen minutes and move every minute of prep in front of it. You walk in with the four gauges, the change since last week, and one specific file you intend to ask about. The LO prepares nothing — every minute an originator spends building a report for his manager is a minute stolen from production. This is where one system earns its keep: in MAVYN, pipeline and coaching sit behind the same login, and MAVIS watches files for stalls, so the picture is assembled before you sit down. The discipline matters more than the tool — but pulling four numbers by hand for six LOs every week is how this dies in March.
Then run the clock:
- Two minutes — read the four. Out loud, against last week. No commentary yet.
- Five minutes — the one that moved. The gauge first, then the behavior underneath it.
- Five minutes — one stuck file. Next action, owner, date. Off the pipeline view, not from memory.
- Three minutes — one commitment. Written down, in his words, with a number and a deadline in it.
"Get my apps up" is not a commitment. "Every lead in before 4pm gets a phone call the same day, all week" is. Next week opens by checking it, which is the whole reason the loop has to be weekly. Monthly gives you twelve coaching cycles a year. Weekly gives you fifty.
Public volume, private diagnostics
Funded volume belongs on the wall. It's what everyone signed up to be measured on, and a leaderboard built right pulls the middle of the roster up.
The other three do not belong on the wall. Publish an LO's pull-through beside his peers' and you haven't created urgency, you've handed him a defense — people who feel exposed by a number stop trying to move it and start arguing with it. Same rule for anything with money attached: per-file margin and branch P&L are an owner's conversation — in MAVYN, financials render only for owner and sales-manager seats, enforced at the database row level. Less about secrecy than about keeping the 1:1 a working session.
Public numbers set the standard. Private numbers fix the swing. Confuse the two and you lose both.
Start Monday
Pick the four. Write down where each lives in your LOS or CRM and pull them by hand the first week if you have to — the definitions matter more than the plumbing. Book fifteen minutes with each LO, same day, same time, every week. Walk in with the numbers already written. Walk out with one commitment apiece and the next slot on the calendar before either of you stands up.
The improvement never comes from one meeting. It comes from there always being another one in seven days, and everybody knowing it.