The file died on a Thursday at 4:40. The insurance binder never came back from the listing agent, the Closing Disclosure clock ran out, and the closing slid a week — a buyer's moving truck, an agent's confidence, and a chunk of your month, rearranged by one document nobody was chasing.
Here's the part that should bother you. That file was on Monday's agenda. Somebody said the words "clear to close, just waiting on insurance" out loud, in a room with seven people in it, and everybody nodded. It got mentioned. It never got assigned. A file that gets mentioned does not move, because mentioning is not a verb anyone performs.
That is the diagnosis for most Monday pipeline meetings. They produce information. A pipeline meeting has to produce commitments — a name, a verb, a date — and thirty minutes is plenty if you spend all thirty on that.
The short version
- Status is homework. Nobody reads the pipeline aloud; it's written by Friday afternoon, in one place everyone trusts.
- Run the clock backward from the closing table: last week's commitments, files closing inside ten business days, stalls, new submissions, read-back.
- Give stalls twelve of your thirty minutes. Three questions per file — waiting on what, who owns it, by when — and the only acceptable output is a name and a date.
- Define "clean" or the word is a lie: clear to close, CD delivered, lock cushion, funds documented. Three of four is optimistic, not clean.
- Any conversation that involves only two people gets named, booked, and taken out of the room. That one rule saves more time than everything else combined.
Status is homework, not agenda
The change that makes the other twenty-nine minutes possible: nobody reads the pipeline aloud. Ever.
Status lives in writing, updated by end of day Friday, in one place everyone trusts. If an LO or a processor walks in Monday not knowing where every active file stands, the meeting can't fix that — it can only spend everyone else's time compensating. Reading status aloud produces nothing, because a status update by itself is not a decision.
The meeting exists for the three things a written update can't do: force a decision, break a tie between two people's priorities, and unstick a file that is waiting on somebody sitting in the room.
Which makes the prerequisite boring and non-negotiable. If your pipeline lives in the LOS, a spreadsheet, the processor's head, and three text threads, fix that before you touch the agenda. MAVYN exists partly for this — pipeline, leads, coaching, recruiting, and branch P&L behind one login — but a shared sheet everybody actually updates beats a system nobody opens.
The countdown agenda: work backward from the closing table
The file closing Friday can still be saved on Monday. The lead that came in Saturday can wait until this afternoon. Most branches run the meeting in exactly the wrong direction — new and exciting first, urgent and boring at minute forty-two, when three people have already left mentally.
Minutes 0–3: last week's list, one word each
Open with last Monday's commitments. Read the name, read the commitment, then stop talking. "Binder from the listing agent — done or not?" Not "how's that going," which invites a paragraph.
One word each. Done, or not. No explanations in the room; a miss gets a new date and a private conversation later. Three minutes, and it is the reason everything after it works: people close loops when the loop gets checked in front of their peers.
Minutes 3–10: the ten-day board, and what "clean" means
Every file scheduled to close in the next ten business days. One question apiece: what could still blow this up, and who owns it today?
"Clean" is a complete answer — but only if the room means the same thing by it. Define it once and never renegotiate it file by file:
- Clear to close issued. Not "conditions submitted." Not "should be today."
- Closing Disclosure delivered, with the three-business-day clock actually started — not planned for tomorrow.
- Lock cushion. Expiration sits comfortably past the closing date, with room for one slip.
- Funds documented. Down payment sourced and seasoned, wire instructions confirmed.
Three of four is optimistic, not clean. You are hunting one thing here: the closing everybody assumes is fine because it looked fine last Wednesday.
Minutes 10–22: walk the stalls
Twelve of thirty minutes, on purpose. This is the block that pays for the meeting.
Define a stall objectively — no status change in five business days — and hold that line, because "it's moving" is not a status. Pull the list before the meeting, never during it. MAVIS watches files for stalls and surfaces them on its own, but a last-activity column in a spreadsheet gets you most of the way there.
Then three questions, same order, every file, every week.
The trap is the answer that sounds like an owner and isn't. "Waiting on the borrower" is not an answer — the LO owns the borrower. "Underwriting has it" is not an answer — the processor owns knowing the queue position. Anything owned by "the team" is owned by nobody, which is how it became a stall.
Cap each file at two minutes, enforced without apology. If the fix needs a real conversation, it involves at most two people. Name them, book it, next file.
Within a month you will see the pattern: stalls cluster at handoffs, not inside stages. The file that sat wasn't being worked badly — it was between owners. If that's your branch, the fix is upstream of the meeting: where files stall between the stages.
Twelve minutes looks generous until you price a stall. Say a purchase file loses six days in the conditions loop and the lock now expires four days before closing. Say your extension pricing runs an eighth of a point for a week — on a $400,000 loan that's $500, straight out of the file's margin, which means out of branch net or LO comp depending on how your plan splits it. Two of those a month is $12,000 a year. That's the cheap version. The expensive one is the stall that becomes fallout, where you don't lose basis points off a file — you lose the file, the pull-through, and the agent who sent it.
Minutes 22–27: the submission handoff, said out loud
This is where next month's stalls get born. Two sentences per file entering processing: the LO confirms it is actually complete — not "mostly there" — and the processor states what happens in the first forty-eight hours.
The sentence worth protecting is the processor's: "That file isn't complete, so I'm not starting the clock." A processor who can say that in front of the room is worth real money. It kills the resentment that builds when junk gets tossed over the wall, and it stops the LO from believing a file is moving when it is sitting in a queue nobody has opened.
Minutes 27–30: read it back
Every name, every date, out loud, once. Then end. Ending early is allowed and should happen often.
If you can't write it as person, verb, thing, date, it isn't a commitment — it's a status wearing a commitment's clothes. That list is the only artifact the meeting produces, and it is the first thing read next Monday at minute zero.
What to skip
Every one of these has a better home than your thirty minutes:
- Rate and market talk. Interesting, endless, moves zero files.
- Clean files. "Clean" is a complete report. Don't reward narration.
- Coaching. A struggling LO's numbers are a one-on-one, not a group exhibit.
- Marketing, events, announcements. Send an email.
- Pre-approvals and new leads. That's the sales meeting. This one is for files under contract, with money and deadlines attached.
- Any conversation that involves only two people. Name them, book it, move on.
What each person leaves with
If people leave with vibes, you held a gathering.
- Each LO: the borrower-facing items they owe — the condition to chase, the call to make — each with a date, in writing.
- The processor: a ranked order of files for the week, and explicit air cover on any escalation the room agreed to.
- The branch manager: the two or three files that need your personal weight — the lender escalation, the exception request, the call an LO can't make alone.
- Everyone: their name on a list that gets read at minute zero next Monday.
Holding the shape
Two rules keep it at thirty minutes for good. Same day, same time, starting on time regardless of who's missing — waiting punishes the people who showed up. And one shared screen with the pipeline on it, no other laptops open.
The first few weeks feel abrupt. Then somebody notices a file moved Tuesday because of something that happened Monday, and the meeting stops being tolerated and starts being defended.
The test isn't whether the meeting felt thorough. It's whether the pipeline looks different by Wednesday.
Next Monday, do three things. Send the stalled list Friday afternoon instead of reading it aloud. Start with last week's commitments even if that list is empty — the loop is what trains the room. And keep one page in front of you with two columns, name and date, and refuse to move to the next file until both are filled in.