Mortgage broker weekly pipeline meeting

Most pipeline meetings in broker firms are a status readout. Someone goes through every live case, each adviser says a sentence about it, forty minutes disappear, and nobody's behaviour changes. The information shared was already available in the system, and the cases that needed attention did not get any.

A useful pipeline meeting does something a report cannot: it makes decisions about cases that are stuck, in front of the people who can unstick them.

Do not review every case

This is the change that fixes most pipeline meetings. Reviewing everything guarantees you spend equal time on the case sailing through and the case that has been silent for a month.

Review by exception. Before the meeting, whoever runs it pulls four lists:

• Anything live that has nobody assigned to a follow-up.
• Follow-ups whose agreed date has already gone by.
• Cases waiting on a third party longer than expected.
• Cases that have not moved a stage in a defined period.

If those four lists are empty, the meeting takes ten minutes and everyone goes back to work. That is a good outcome, not a wasted slot.

Who should be there

Everybody who touches a live case: advisers and administrators both. Excluding administrators from the pipeline meeting is common and it is a mistake, because they hold most of the information about where cases actually are and they are the ones who will action most of the decisions.

Keep it to the people doing the work. A meeting with an audience becomes a performance, and people stop saying that a case is in trouble.

A structure that fits half an hour

Two minutes: the headline numbers. New enquiries this week, submissions, offers, completions. No discussion, just the shape of the week.

Ten minutes: the exception lists. Case by case, and for each one a single question — what is the next action and who owns it. Not a discussion of the case history. If a case needs a real conversation, note it and take it offline; that is one person's problem, not seven people's.

Five minutes: cases at risk of a deadline. Offers approaching expiry, exchange dates, rate deadlines, anything with a hard date in the next fortnight.

Five minutes: incoming. What is arriving next week — appointments booked, cases ready to submit — so that workload can be balanced before it lands rather than after.

Five minutes: one thing to fix. A recurring problem someone raises, with a named owner and a date. One per week, not a list.

Three minutes: anything anyone is worried about. Leave this genuinely open. It is where the useful information comes out.

Rules that keep it short

Cases needing detailed discussion come out of the meeting. Say so explicitly and enforce it, because the drift towards case-by-case storytelling is relentless.

No status updates that the system already shows. If someone reads out what is on the screen, the meeting has become a report and should be replaced by one.

Every case discussed leaves with an owner and a date. If neither can be agreed in the meeting, that is itself the finding.

Same day, same time, every week, including quiet weeks. The value comes from it being unmissable.

Start on time regardless of who is missing. Waiting rewards lateness and punishes everyone else.

The tone problem

A pipeline meeting fails silently when people stop mentioning cases that are going badly. It happens gradually, and it happens because someone was made to feel foolish once.

The signal to watch for is a case appearing on the stuck list without anyone having previously flagged it. If the meeting is working, problems arrive before the report finds them.

The person chairing sets this, mostly by how they react to bad news. Reacting to a stalled case with curiosity rather than irritation costs nothing and determines whether you hear about the next one.

What to do about the perpetually stuck case

Every pipeline has cases that appear on the stuck list week after week. The client has gone quiet, the chain is stalled, the lender is unmoved.

Give these a defined path rather than letting them recur indefinitely. After a set number of appearances, the case gets a decision: escalate it, park it formally with a review date, or close it and tell the client. Closing is not failure; carrying dead cases forever distorts your pipeline figures and demoralises people.

The rule matters more than the specific threshold. Without one, the stuck list grows until people stop reading it.

Separate this from the other meetings

The pipeline meeting is about live cases. It is not a sales meeting, a training session, a business update or a compliance briefing. Those are all legitimate and they all need their own slot.

The moment a pipeline meeting acquires an agenda item about marketing, it starts growing, and within a quarter it is an hour long and attendance becomes optional in people's minds.

Preparing for it

The preparation should take one person about ten minutes, and it should be pulling lists rather than assembling narrative. If preparing for your pipeline meeting takes an hour, your case management system is not doing its job and that is the real finding.

Circulate nothing beforehand except the four lists. Pre-reading that nobody reads is worse than no pre-reading.

Recording outcomes

Write down only the decisions: case, action, owner, date. Put them straight into the case records rather than into meeting minutes, so they turn up in front of the right person at the right time rather than in a document.

Then start the next meeting by checking last week's decisions. Two minutes, and it is the single thing that stops the meeting becoming decorative.

When it is working

You will know because the stuck list gets shorter over a few months, because problems get raised before they appear on it, and because people stop needing to ask each other where a case is between meetings.

If none of that happens after a couple of months, the meeting is not the problem. The underlying case data is, and no amount of meeting design will compensate for a pipeline nobody keeps current.