Mortgage broker admin assistant workflow

The first administrator is the highest-leverage hire most brokerages ever make, and also the one most often wasted. The waste has a consistent cause: the adviser hires someone to help, gives them whatever is annoying that week, and never defines the role. Six months later the administrator is busy, the adviser is still doing admin, and neither can explain what happened.

This is about defining the role properly, in terms of what moves and what does not.

The dividing line

The clean way to split adviser and administrator work is by whether the task requires a regulated judgement or a client-facing recommendation.

The administrator can own: document collection and checking, data entry, case packaging, lender submission mechanics, progress tracking, status updates to clients, liaison with conveyancers and estate agents, diary management, post-completion follow-up and reporting.

The adviser must retain: the advice itself, the recommendation, anything that involves discussing suitability, and any conversation where a client is deciding between options.

The grey area is where clients ask advice questions of the administrator, which they will, constantly. Give the administrator a script for it that does not make them sound obstructive, and make clear internally that passing the question on is the correct answer rather than a failure.

If you are an appointed representative, your network will have views on what unregulated staff may say to clients, and those views are binding. Check them before you set the boundary, and treat what follows as an operational structure rather than a statement of what is permitted.

The daily shape

An administrator with no rhythm reacts to whatever arrives. A rhythm turns the same hours into much more output.

Morning block, before the phone gets busy: work through anything received overnight, check documents that came in, action lender correspondence, update case statuses. This is the block where the pipeline gets accurate.

Late morning: outbound work that needs other people — lender calls, conveyancer chasing, employer references. Batch it rather than spreading it.

Early afternoon: client contact. Scheduled updates, document requests, follow-ups on things promised earlier in the week.

Late afternoon: preparation for tomorrow, packaging of anything ready for submission, and a sweep of cases with no next action.

The specific shape matters less than having one. What it prevents is the day disappearing into the inbox.

What the handover into admin should contain

Most administrator frustration comes from receiving cases that are not ready. Define what a complete handover looks like and let the administrator refuse incomplete ones without it being a confrontation.

• The recommendation, made and recorded.
• Client contact details confirmed as current, including preferred method and any access needs.
• The document list already sent to the client, with a copy in the case.
• Any known complications flagged in a sentence, not left to be discovered.
• Fee arrangement recorded.
• The deadline, if there is one, and what drives it.

A returned case should be routine and unemotional. Log it, because a pattern of returns from one adviser is useful information.

Access, permissions and what the administrator can do alone

Decide deliberately what the administrator can do without asking:

• Which systems they have full access to and which are read-only.
• Whether they can submit to lenders directly or only prepare for submission.
• Whether they can send client communications in their own name, the adviser's name, or the firm's.
• What they can commit the firm to — a callback time, a fee waiver, a deadline.
• Who they escalate to when the usual adviser is unavailable.

Under-granting access is more common than over-granting, and it quietly recreates the bottleneck the hire was meant to remove. If the administrator has to ask permission four times a day, you have hired a very expensive pair of hands.

Measuring the role without measuring the wrong thing

Task counts are a poor measure. An administrator who closes forty small tasks may be doing less useful work than one who spent the day untangling two difficult cases.

Better indicators:

• Median time from documents received to case fully packaged.
• Number of lender queries per submitted case, trending over time.
• Cases with an overdue next action at the end of each week.
• Adviser hours spent on non-advice work, sampled occasionally.
• Client-initiated contact asking for status, which should fall as the role beds in.

The last one is the honest test. If clients stop chasing you, the administrator is doing the job.

Building the role's own documentation

Have the administrator write the process notes rather than the adviser. Two reasons: they are the ones doing the work so the notes will be accurate, and writing them surfaces every place where the process is actually undefined.

Keep the notes in a form that can be handed to a temporary replacement. The realistic test is whether someone competent but unfamiliar could cover two weeks of holiday using them. Most firms discover they cannot, and that the knowledge lives in one head, which is a business risk quite apart from an operational one.

When one administrator becomes two

The transition from one to two support staff is harder than it looks, because the first administrator has usually developed a personal system rather than a firm system.

Split by function rather than by adviser if you can. One person owning document collection and packaging across all advisers, another owning post-submission progression and client updates, tends to work better than each administrator shadowing one adviser. It produces consistency, makes cover trivial, and prevents the pattern where each adviser has their own private way of doing everything.

If you split by adviser instead, at least standardise the case record and the templates first, or you will end up running two firms.

Data handling

Administrators touch more client personal data than anyone else in the firm. Make sure they have had proper data protection training, that they know not to move documents into personal email or storage, and that they know what to do if something is sent to the wrong recipient. The ICO's guidance on personal data breaches is worth reading with them rather than filing.

Get the boundaries, the handover and the access rights right and the role pays for itself within a quarter. Get them wrong and you have added cost without removing any.