Most brokers manage their pipeline reactively — checking whichever file just sent an email, or whichever client just called, and trusting that everything else is fine because nothing loud has happened. That approach works right up until a file that's been quietly stuck for two weeks surfaces as a crisis three days before closing, at which point there's no good option left, only damage control.
A weekly pipeline review flips that: instead of reacting to whatever's loudest, it forces a structured look at every file on a fixed schedule, so a stalled file gets caught while there's still time to fix it cheaply. Thirty minutes, run the same way every week, is enough — the value is in the consistency and the structure, not the length of the session.
Why weekly beats daily firefighting
Daily check-ins tend to focus on whatever file made noise that day — an email reply, a document that came in, a client call. That's useful for responsiveness, but it's a poor substitute for actually knowing the state of every file in the pipeline, because quiet files — the ones waiting on something, with nobody pushing — are exactly the ones that get missed.
A weekly review, done separately from the daily reactive work, is specifically built to surface the quiet files. It's a different mode of attention: not “what came in today” but “what hasn't moved this week, and why not.”
The four-list structure
Sort every active file into exactly one of four lists at the start of each review. The simplicity is the point — a file that's hard to categorize is usually telling you something worth investigating on its own.
| List | What belongs here |
|---|---|
| New | Files opened this week, not yet fully underway |
| In-progress | Files actively moving — documents being collected, conditions being cleared, on a normal timeline |
| Stuck | Files that haven't moved in longer than they should have, regardless of why |
| Closing this month | Files with a confirmed or expected closing date within the next 30 days, regardless of which other list they'd otherwise fall into |
The “stuck” list is where the review earns its keep — everything else is largely confirming what's already known, but the stuck list is where genuinely new information surfaces each week.
The stuck-file protocol
A file qualifies as stuck based on a simple age trigger — for example, no meaningful movement in seven calendar days — rather than a subjective feeling that something's off. A consistent, mechanical trigger is what prevents a stuck file from being explained away week after week.
- 01Flag the file as stuck once it crosses the age trigger, regardless of the reason.
- 02Assign one named owner for the next action — not “the file,” a specific person.
- 03Define the next action in one sentence — what happens, by whom, by when.
- 04Set a re-check date — if the file is still stuck at the next review, escalate rather than repeating the same flag.
The goal is that no file stays on the stuck list for more than two consecutive reviews without a materially different action being tried — repeating the same unsuccessful nudge for three weeks running is itself a signal to change approach.
The capacity read: files per stage against your ceiling
Beyond individual files, the weekly review is the natural point to check total pipeline volume against realistic capacity — how many files are actually in each stage, versus how many a broker or team can properly service at once without every file getting a little less attention than it needs.
This matters more than it might seem in years with a heavier renewal volume moving through the system — renewals have been the dominant driver of Canadian mortgage market activity into 2026, per CMHC's Residential Mortgage Industry Report, so pipeline volume for many brokers can shift independent of any change in their own marketing or lead generation. A capacity read that's accurate this quarter may already be out of date next quarter if renewal-driven volume shifts again.
The honest capacity question: if every file currently in-progress needed full attention today, could you actually give it? If the answer is no, the review just found the real problem — and it isn't any single file.
The metrics worth tracking weekly
A handful of simple counts, tracked consistently week over week, tell a broker more about pipeline health than any single file's status. None of these need to be complicated to track — a running tally is enough.
- →Total files stuck this week versus last week — a rising trend is worth investigating even if no individual file looks alarming.
- →Average time in each stage, tracked loosely over time, to notice if a particular stage is consistently where files slow down.
- →Files closing this month versus files that were expected to close this month at the start of the period — a gap between the two flags slippage early.
- →New files opened this week, to keep the capacity read in Check 4 current rather than based on last month's volume.
Running it solo versus with a team or a fulfillment partner
A solo broker running this review alone should still treat it as a scheduled, non-negotiable slot — the same time each week, done even when the week feels too busy to spare thirty minutes, since a busy week is exactly when a file is most likely to go quietly stuck.
With a team, or with an outsourced fulfillment partner handling part of the pipeline, the same four-list structure works as a shared review — each party reporting their own slice of files into the same lists, so nothing falls into a gap between “that's their file” and “that's my file.” The structure is what stays constant regardless of who's actually doing the work on any given file.
For the underlying question of how many files a broker can actually carry well, see Mortgage Broker Capacity Math, and pair this weekly review with a Lender Turnaround Tracker to make the “stuck” determination sharper for files waiting specifically on a lender.