Mortgage broker workflow management

A workflow is not a diagram. It is the answer to a question someone asks forty times a day: what is the state of this case, and whose move is it? If your firm cannot answer that in under ten seconds without ringing anyone, you have a workflow. If it cannot, you have a habit.

This is about designing the thing deliberately.

Stages should be states, not activities

The most common design error is naming stages after activities: "researching", "packaging", "chasing". Activities have no clear end, so cases sit in them indefinitely and nobody can tell a stalled case from a busy one.

Name stages after states instead — conditions that are either true or not true. "Documents complete." "Submitted to lender." "Offer issued." "Exchange confirmed." Each has an unambiguous entry test, which means the board tells you the truth without anyone interpreting it.

A workable set for a residential purchase might be eight or nine states from enquiry through to completion. Fewer than six and you cannot see where things stick. More than twelve and people stop updating it accurately, which is worse than not having it.

Every case has exactly one owner and one next action

Two rules do more work than any amount of software configuration.

The first is single ownership. A case belongs to one named person at any moment. Shared ownership means nobody is uncomfortable when nothing happens. When an adviser hands a case to an administrator, ownership genuinely moves; the adviser does not keep a shadow copy in their head.

The second is that every open case carries a next action with a date. Not a status, an action: "call underwriter about employment reference", "send revised ESIS", "check with client whether the survey came back". If a case has no next action, that is itself a defect to be fixed, not a neutral state.

Together these two rules turn a list of cases into a workload you can actually manage.

Make waiting visible and different from working

Half a broker's pipeline at any moment is not being worked on. It is waiting: on a lender, a valuer, a solicitor, an employer, a client who has not sent a bank statement.

Waiting cases need a different treatment from active ones. They should not appear in the same view, because they inflate the apparent workload and dull people's response to it. They should carry an expected date and a source, so that "waiting" becomes "waiting on the lender's underwriting queue, expected Thursday" rather than a shrug.

A weekly sweep of anything that has been waiting longer than expected is the single highest-value routine in most broker firms. That is where cases go to die.

Design for the handover, not for the happy path

Workflows fail at boundaries. Adviser to administrator. Administrator to lender. Broker to conveyancer. Anyone to a client who is on holiday.

For each boundary in your process, decide three things in advance: what must be true before the case can cross, what information travels with it, and what happens if the receiving side rejects it. A handover with an acceptance test is a workflow. A handover without one is an email.

The rejection path is the part people forget. If an administrator receives a case that is missing something, can they push it back, and does the system record that this happened? If not, the administrator will either chase silently or fix it themselves, and you will never learn where the quality problem is.

Limit how much is in flight

Advisers instinctively want a large pipeline because it feels like security. Beyond a certain point it is not security, it is a queue with no exit, and everything in it moves more slowly because attention is spread thinner.

There is no universal correct number; it depends on case complexity, admin support and lender service. But most firms have never asked the question at all. Look at your completion rate and your average time from enquiry to offer over the last quarter, then look at what happened to both in the months when case volume was highest. If time-to-offer stretched significantly, you were above capacity, and the extra cases cost you money rather than making it.

If that is happening, the fix is not to work faster. It is to qualify harder at the front, or to add capacity behind the advisers.

Instrumentation that actually helps

You do not need a reporting suite. You need four things visible without asking anyone:

• Cases with no next action.
• Cases where the next action date has passed.
• Cases waiting longer than their expected date.
• Cases that have not been touched at all in a defined period.

Any of these four being non-empty is a prompt for a specific conversation. That is the whole point. Reporting that produces a number without producing an action is decoration.

Common failure patterns

The board that nobody updates. Usually caused by the board living somewhere other than where the work happens. If updating the status is a second act after doing the work, it will not survive a busy week. The status should be a byproduct of the work, not an additional chore.

The stage everything sits in. Almost every firm has one enormous stage holding half the pipeline. Split it. Whatever it is called, it is hiding at least three genuinely different situations that need different handling.

The workflow that only exists for new purchases. Remortgages, product transfers, buy-to-let and protection cases each behave differently, and forcing them through a purchase-shaped process produces constant exceptions. Either give them their own short flows or accept that a lot of your pipeline is being managed informally.

The process designed around the best administrator. It works beautifully until that person is on leave. Design for someone who joined six weeks ago and is having a bad day, then let the experienced people go faster.

Where regulatory requirements sit in this

A workflow is an operational tool, but it is also where evidence gets created or lost. Whatever your file must contain, the workflow should make it structurally difficult to reach the next stage without it. That is far more reliable than a reminder.

What the file must contain, and how long it must be kept, is set by the FCA Handbook and, for appointed representatives, by the network's own standards, which are frequently stricter. Confirm those requirements before you build gates around them, and treat this article as operational guidance rather than compliance advice.

Start by drawing what actually happens, including the informal parts. The gap between that and what people say happens is usually where your next improvement is.