Client Portal Adoption: How UK Mortgage Brokers Get Clients Using It

Client Portal Adoption: How UK Mortgage Brokers Get Clients Using It

Client portal adoption is the share of your clients who actually upload their documents, answer requests and track progress in the portal instead of emailing photos and PDFs. For a UK mortgage brokerage, adoption rises when the portal asks for the right documents once, works on a phone, carries the firm's own branding, and gives the adviser a clear queue to review. Casefile is built around that approach: document lists that build themselves from the client's payment type, automatic cross-checks, and a branded client experience that needs little learning.

A portal that clients ignore adds a second inbox to your day. This guide covers why clients stall, what to measure, how to roll the portal out in six steps and what to check once documents arrive.

TL;DR

  • Adoption is a behaviour, not a login count. Measure the share of clients who complete their full document list, and how long that takes.
  • Clients drop out when they are asked for the same thing twice, do not know what is needed, or cannot use the portal on a phone.
  • A document list that builds itself from the client's employment and income type removes the most common reason for chasing.
  • Brief the client before the first request, and give advisers one approval queue rather than several inboxes.
  • Review quality matters as much as upload rates: discrepancies caught before the lender sees them prevent queries later.

Table of Contents

What adoption means for a mortgage brokerage

A portal is adopted when both sides use it by default. Clients upload through it. Advisers and case administrators review, approve and request more through it. If either side falls back to email, the portal becomes a parallel channel and the manual work returns.

The pressure on clients is real. An October 2024 Censuswide survey of 5,000 UK homebuyers and sellers for the Open Property Data Association found 40.6% named communication between parties as the most challenging part of the process, 39.5% had to chase for updates and 62.3% reported multiple requests for identical information. The same survey found 82.2% viewed a digital property pack positively and 76.7% would use such technology for secure sharing of data and information.

Those figures concern the wider home-buying process rather than mortgage broking alone, but they describe the same client frustration: repeated requests and no visibility. A portal that removes both gives clients a reason to use it.

What adoption means for a mortgage brokerage

Why clients do not use the portal

Most non-adoption has practical causes. These are the ones a brokerage can fix.

They do not know what is needed

A generic checklist sends a salaried client looking for self-employment documents, and sends a contractor looking for payslips they do not have. The client uploads what they can, misses the rest and waits. The adviser then chases by phone, and the portal looks like an extra step.

They are asked for the same thing twice

Repeated requests are the most cited irritation in the OPDA data. In a brokerage the cause is usually a gap between intake forms, the fact find and the document request. If the portal does not know what the client already supplied, it asks again. See our guide to document intake forms for UK mortgage brokers for how to remove the overlap.

The upload experience is poor on a phone

Many clients will photograph a payslip at the kitchen table or on a commute. Blurred, cropped or partial images lead to rejections and another round of requests. The practical points are covered in our guide to mobile document capture for UK mortgage brokers.

They worry about where their data goes

Bank statements show spending, commitments and family details. Clients are right to ask who sees them and where they are stored. A brokerage that can state plainly where data sits and who can access it removes a common hesitation. Casefile keeps data in the UK, in line with UK residency requirements, and our data security page explains how documents are handled. The regulatory side is covered in our UK broker's guide to mortgage data privacy.

They get no feedback

A client who uploads a file and hears nothing assumes it failed. Visible status, such as received, approved or needs replacing, is what stops the follow-up call.

What drives staff adoption

Adviser adoption is decided by whether the portal reduces work in the first week. Three things matter.

  1. One queue. Documents arrive in a single approval queue per case, not scattered across email threads.
  2. Checks that run themselves. Matching wage deposits to payslips, spotting undeclared commitments in bank statements and flagging signs of tampering is slow by eye. When the platform surfaces these, advisers spend time on judgement rather than on reading every line.
  3. A record of what happened. An audit trail showing what was requested, received, changed and approved supports file reviews and lender queries.

Smaller brokerages feel this most. With few staff, every manual check comes out of adviser time, and a portal that adds steps will not survive a busy month.

How to measure adoption

Login counts say little. Measure outcomes at case level, and review them monthly.

MeasureWhat it showsHow to calculate
Completion rateWhether clients finish the listCases with all required documents received, divided by cases opened
Time to completeHow long the file waits on the clientDays from first request to final approved document
Rejection rateWhether instructions and capture are clearDocuments sent back, divided by documents received
Chase countManual work still happeningReminders or calls per case
Off-portal documentsWhether the portal is the defaultDocuments arriving by email or messaging apps

Research on a wealth-management portal supports looking at tasks, not opinions. A 2018 Frontiers conference study of 37 users recommended usability testing that measures task performance as well as self-reported ease. Users completed easy tasks with 86% accuracy and difficult tasks with 66.2%, which shows how a hard step exposes a bottleneck. The study is small and from another sector, so treat it as a method: find the step where your clients fail, then fix that step.

In a brokerage, the equivalent is the step where uploads stop. If most clients stall at bank statements, look at the instructions for that document, not at the whole portal.

Six steps to roll out a portal clients use

This sequence follows the stages in our mortgage onboarding workflow for UK brokers. Each step shows where adoption tends to fail.

1. Decide what the portal replaces

Name the channels it replaces: email attachments, messaging apps, paper. If the adviser still accepts documents by email, clients will keep sending them that way. Agree a rule across the firm that documents are requested and received in the portal.

2. Build the document list from the client's situation

The list should reflect how the client is paid and who is applying: employed, self-employed, contractor, joint applicants, a mix. Casefile builds the document list from the client's payment type, so a salaried applicant is not shown a self-employed checklist. A list that fits the client is the single biggest reduction in questions.

3. Brand it and explain it before the first request

Clients trust a portal that looks like it belongs to their adviser. Casefile carries the brokerage's branding. Add a short message before the first request: what the portal is, what will be asked, how long it takes and who will see the documents. Make the same point in the first call. A short prepared script also helps staff. Our automated document collection guide sets out how requests and reminders work in practice.

4. Ask once, in the right order

Request identity and proof of address first, then income, then commitments. Keep each request specific: the period, the format and the account. Client onboarding guidance in other service sectors makes the same point, that reducing repeated information requests shortens onboarding and reduces drop-off.

5. Review in one queue and respond fast

Clients upload faster when they see quick responses. Approve or return documents in the same working day where you can, and give a clear reason for each return, such as the page that is missing or the date range needed. Casefile manages approval queues so advisers can see what is waiting.

6. Track, then adjust

Use the measures in the table above. Review the documents most often rejected, rewrite those instructions, and brief staff on any step where clients stall. Adoption improves when each cycle removes one cause of friction.

Quality of review decides whether adoption pays off

Getting documents in is half the job. A high upload rate still creates queries if the contents are not checked before submission.

Typical problems are a wage deposit in the bank statement that does not match the payslip, a regular payment to a lender or card provider the client did not declare, or a document that has been altered. Finding these by eye across several applicants and months of statements is slow, and a miss shows up when the lender's underwriter raises a query and the case stalls.

Casefile cross-checks bank statements, payslips, tax forms, ID and utility bills, matches wage deposits, flags undeclared commitments and checks document authenticity, so these issues surface before the file reaches a lender. Applicant privacy is preserved, and every action is recorded in an audit trail.

This ties back to adoption. Clients who see their adviser resolve issues quickly, with specific and polite requests, keep using the portal. Clients who face vague queries weeks later do not.

The regulatory context points the same way. The FCA's good practice on consumer understanding says communications should be clear and presented so customers can understand them, and that firms should test communications with real customers and use insight to see where consumers struggle. Portal wording, request messages and status updates are communications in that sense. Review them with the same care as client letters.

Quality of review decides whether adoption pays off

Keeping communication simple

Portal messages should do one job each. A useful request names the document, the period and the reason. For example: "Please upload your last three months of payslips. Your lender requires them to confirm your income." Compare that with "Please send income documents".

A few habits help:

  • Send one reminder sequence, not several overlapping ones.
  • Use the portal's status updates so clients can see progress without calling.
  • Keep a single named contact for each case.
  • Use plain language for document names, such as "payslip" rather than internal codes.

Teams interested in building the wider communication routine can also read this client communication workflow guide, which covers keeping clients informed and able to find their documents.

Perspective

Adoption is won in the first request. If a client opens the portal and sees a list that matches their own situation, with their adviser's branding on it, they usually finish it. If they see a generic list, they phone.

We built Casefile around that. The document list builds itself from how the client is paid, the checks run as documents arrive, and issues such as undeclared commitments or mismatched wage deposits are flagged before they reach a lender. Data stays in the UK, with no manual or offshore handling, and the audit trail records each step.

For a small brokerage, the aim is simple: fewer chasing calls, fewer lender queries, and advisers spending their time on advice rather than reading statements line by line.

Darren

Using Casefile for client document collection

Casefile is a cloud-based platform for UK mortgage brokerages. It collects client documents through a branded portal, builds each client's document list from their payment type, cross-checks the documents and flags discrepancies, and keeps data in the UK. It supports different applicant types and gives advisers an approval queue for each case.

If your brokerage wants to raise portal use without adding to adviser workload, see Casefile for how onboarding and setup work.

Gocasefile

FAQ

What is a good client portal adoption rate for a mortgage brokerage?

No single published benchmark applies to UK brokerages, so set your own baseline. Record the share of cases where every required document arrives through the portal and the average days it takes. Aim to improve both each quarter, and track off-portal documents as the sign that the habit has not yet formed.

How do you persuade clients to use a portal instead of email?

Explain it before the first request, make the request specific, and stop accepting documents by email once the portal is live. Clients follow the route the adviser uses. A branded portal with a document list that fits their circumstances makes the portal the easier option.

Do clients need training to use a portal?

They need a short explanation, not training. Tell them what will be asked, how to photograph or upload a document and when they will hear back. Casefile is designed to need minimal technical learning, which keeps the client's side to a few actions.

How should a brokerage deal with clients worried about data security?

Tell them where documents are stored, who can see them and how long they are kept. Casefile keeps data in the UK, and the data security page sets out how documents are handled. Use the same wording in the first call and the portal invitation so the message is consistent.

Sources

This article was generated with AI, and whilst it is our expectation that the article is accurate, it should not be taken as advice.