Mortgage broker task handoff process

Watch where cases stall in a brokerage and you will find they rarely stall in the middle of someone's work. They stall in the gaps between people. The adviser has finished, the administrator has not started, and the case sits in a state that neither of them considers theirs.

Handoffs are cheap to fix and almost never designed. Here is how to design one.

A handoff has three parts, and firms usually build only one

The part everyone builds is the transfer: an email, a status change, a verbal "can you pick this up".

The two missing parts are the acceptance and the rejection. Without an acceptance step, nobody knows whether the case has been picked up, so the sender keeps half-watching it and the receiver assumes it is fine. Without a rejection path, an incomplete case cannot be sent back, so the receiver either fixes it themselves or lets it sit.

Build all three and you have a process. Build only the first and you have a hope.

Define the readiness standard

The most productive hour a firm can spend is agreeing, between advisers and administrators, what a case must contain before it crosses.

Write it as a short list of conditions, not aspirations. Something like:

• The recommendation is recorded, with the lender and product named.
• The client's contact details are confirmed correct and their preferred contact method is noted.
• The document request has gone to the client and a copy sits in the case.
• Income evidence has been sighted by the adviser, not just discussed.
• Anything unusual about the case is written in one sentence at the top of the notes.
• The fee position is recorded.
• Any deadline is recorded, with what drives it.

Then agree the crucial part: a case that does not meet the standard goes back. Not with an argument, and not as a criticism. It is logged and returned with the missing item named.

The logging matters. After two months you will have data showing which item is missing most often and which adviser sends the most returns. That is a coaching conversation with evidence behind it, which is a very different thing from a general complaint that the handovers are poor.

Make the transfer carry context, not just data

The system will carry the data. What gets lost at a handoff is context: the things the adviser knows that are not in any field.

That the client is anxious and needs more frequent contact. That the seller is difficult. That the deposit gift came from a relative who is uncomfortable providing statements. That there is a second application in the background that might affect this one.

Give this a home. A single free-text handover note, always written, never optional, and read before any client contact. Three or four sentences is enough. Its value is that it exists at all.

Point-to-point, not broadcast

Cases handed to a team are handed to nobody. If the transfer goes into a shared queue, make sure the first act of the receiving side is that a named person claims it, and that the claim is visible.

The same applies in reverse. When the administrator needs something back from the adviser — a decision, a call to the client, a judgement on whether to proceed — that should be a specific request to a specific person with a date, not a note in the file that the adviser might see.

Handoffs in both directions

Firms design the adviser-to-administrator direction and forget the return leg, which is where most delay actually lives. Cases bounce back to the adviser constantly: a lender query needing a judgement, a client wanting to change something, a valuation coming in low.

Give the return leg the same three parts. What must be included when a case comes back to the adviser? How does the administrator know it has been picked up? What is the expected turnaround?

Without this, administrators end up chasing advisers, which they are often reluctant to do, and cases sit.

Reduce the number of handoffs before you optimise them

Every handoff is a chance to drop something. Before making yours excellent, count them.

A case that passes between adviser and administrator eleven times is a case with eleven opportunities for delay. Some of those exchanges exist because the split of work is drawn in the wrong place — typically because a decision that could be delegated within clear parameters is being escalated every single time.

Look for the exchanges that always have the same outcome. If the administrator asks the adviser something eight times out of ten and the answer is always the same, write down the rule and let them apply it.

The timing rule

Attach a maximum to each direction: a case handed over is acknowledged within a set number of working hours, and either accepted or returned within a set number. A case sent back to an adviser gets a decision within a set number.

Set these from what you currently achieve, not from what would be ideal, and then tighten them. Numbers that are met are useful; numbers that are aspirational are ignored.

What to watch

• Cases sitting in a transitional state longer than the agreed acknowledgement window.
• The return rate, by adviser and by missing item.
• The number of exchanges per case, tracked as an average.
• Cases where the receiving person changed midway, since these are the ones that lose context.

The cultural part

None of this works if returning a case is treated as an insult. In firms where the administrator is junior and the adviser is the principal, the rejection path exists on paper and is never used, and the administrator absorbs the gap silently.

The fix is for the principal to be the first person whose case gets returned, publicly and without defensiveness. That establishes in one afternoon what a policy document will not establish in a year.

Where the regulatory line sits

The split of work between advisers and support staff has a regulatory dimension, particularly around what unregulated staff may say to clients and who is responsible for the advice. If you are an appointed representative, your network sets the boundaries and they are not negotiable. If you are directly authorised, you set them and you carry the responsibility for getting them right.

Confirm the boundary with your compliance support before designing around it. Everything above is about making the mechanics work once that line is drawn.