Most practices that buy a client portal end up running it alongside email and a messaging app, which is the worst of the three outcomes: the same work, in more places, with the record split across all of them.
The failure is rarely the software. It is that adoption was treated as something that would happen once the portal existed, rather than as the thing being designed.
Adoption is decided in the first ten minutes
A client forms their habit at the first point where they need to send you something. Whatever channel works then is the channel for the whole matter, and every subsequent attempt to move them is a request to change something already working.
Three things follow.
Introduce the portal at the moment of first need, not at engagement. An invitation sent with the service agreement gets read as administration. The same invitation sent with "your first documents go here" gets used, because it arrives attached to a task.
Do not offer a choice. If you accept documents by email as well, most clients will email — not out of preference, but because it is what they already have open. Offering both is choosing email.
Assume a phone. Most clients will photograph documents rather than scan them, in the evening, on a phone, possibly on mobile data. A portal that is awkward on a phone will lose to a messaging app every time.
Our guide to the first 48 hours of onboarding covers where this fits in the sequence.
The clients who struggle are the ones you owe most to
This is the part that gets skipped in adoption advice, and it matters here more than in most industries.
Section 37 of the Code of Conduct requires an agent to arrange an appropriately qualified interpreter to assist a client in their dealings with the agent if the client requests it. Section 39 requires you to keep the client informed in writing about lodgements and material developments. Section 33 requires you to have regard to the client's dependence on your knowledge and experience.
None of that is discharged by a portal the client cannot navigate. A practice whose entire client communication runs through an English-only interface has, in effect, made accessibility a condition of receiving the service.
Practical consequences:
- Have a supported path for clients who cannot use it. Not "email it then" — a deliberate alternative, recorded as an exception on the matter so the file still holds the record.
- Reading should never require a login. A client should be able to receive news without authenticating, even where uploading a passport requires it.
- Where a family member or interpreter helps, that is a third person under section 35. Confidentiality requires the client's written consent before their affairs are discussed with someone else, however helpful the arrangement.
The messaging problem, and why it is a record problem
Clients want to message. It is faster, it is what they use for everything else, and it produces quicker answers from you as well.
The obstacle is not preference. Section 56(2)(c) requires the client file to include copies of all written communications, including electronic communications, between you and the client. A messaging thread about a matter is a written communication about that matter. It belongs on the file, and on a personal phone it is not on the file — it is on a device, outside every control the practice has, and unavailable to anyone else when that person is on leave.
Two workable positions, and one that is not:
- Absorb it. Route messaging into the system so threads land on the matter. This is the honest answer if clients will message regardless, which they usually will.
- Bound it. Messaging is fine for scheduling and confirmations; anything substantive moves to the portal, and you move it explicitly rather than answering in place.
- Ban it and hope. This is the position most practices claim and none maintains, and it produces the worst outcome: a rule everyone breaks, so nobody records anything.
Sponsored matters need the access question answered
Where you act for both a sponsor and an applicant, portal access is a confidentiality decision rather than a convenience one.
The employer paying your invoice is a third person as regards the applicant's health, character or relationship information. A portal that gives the sponsor visibility of the whole matter is a standing disclosure. Section 35 requires the client's written consent, and consent obtained in the service agreement is far better than consent sought in the middle of a difficult moment.
The practical requirement is a portal that can distinguish parties — the sponsor sees the nomination, the applicant sees their own documents — rather than one that grants access per matter.
Making the first use succeed
The single highest-value intervention is assisting the first login rather than explaining it.
- Do it during a call. Five minutes walking a client through their first upload converts more reliably than any set of instructions.
- Set the expectation at the same time. "This is where everything for your application lives, and it is where I will post updates."
- Send the invitation from a person, not from a no-reply address that looks like phishing to someone already anxious about scams.
- Make the first task trivial. One document, not twelve. The goal is a successful interaction, not progress.
- Follow up once by phone if they have not logged in within a few days. This is where most silent drop-off is recovered.
Channel boundaries worth stating
Write these down once, tell clients at engagement, and hold to them:
- Documents go in the portal, always.
- Advice and formal updates come in writing, through the portal or by email, because section 39 requires it in writing.
- Scheduling and quick confirmations can go wherever the client prefers.
- Anything substantive said by phone gets recorded as a file note — section 55 requires a contemporaneous written record of oral communications, and OMARA's guidance on practice management duties lists recording all client contact on the file among the arrangements a practice should have.
Measuring whether it worked
Adoption is measurable, and worth measuring monthly:
- What proportion of clients logged in at all?
- What proportion of documents arrived through the portal rather than another way?
- How many matters have client communication in more than two channels?
- Where clients fall back to email, at which step does it happen?
That last question is the useful one. Fallback clusters at a specific point — an upload that fails on large files, a step that requires a desktop — and fixing that one point does more than any amount of encouragement.
The adoption test
- Is the portal introduced at engagement or at first document request?
- Do you accept documents by email as well?
- Can a client read an update without logging in?
- What is the supported path for a client who cannot use it?
- Are messaging threads reaching the file?
- On a sponsored matter, can the sponsor see the applicant's personal documents?
Where a system helps
The distinction that decides this is whether the portal is a separate product or a view onto the matter.
A bolted-on portal creates a second place documents live, so staff work in the system and clients work in the portal and someone reconciles them. A portal that is a view onto the matter means an upload is filed the moment it arrives, a message becomes part of the record, and access follows the matter and the party rather than being granted wholesale.
That is also what makes the boundaries above enforceable rather than aspirational — the compliant path is the convenient one.
LodgeHQ gives clients a portal that writes directly to the matter, with per-party access for sponsored work. Our guide to starting a migration agency covers setting this up before habits form; start a free trial to see how it handles a first upload.
Verify before you rely on it
Interpreter arrangements, accessibility obligations and confidentiality consents are matters of substance rather than software configuration. Read the Code's requirements directly and check OMARA's practice management guidance on recording client contact.
This is general information for migration practices, not legal advice. Where a client cannot engage with your systems, or where a third party is helping them, get the confidentiality position right on that matter specifically.