Key takeaways
- Each complaint stands for other clients who felt the same and said nothing.
- Record the same few fields for every complaint and code it by theme, stage and cause.
- Root cause analysis should end in a process change, not a named person.
- Review patterns quarterly by team, stage and channel; single complaints rarely show the cause.
- Tell complainants and staff what changed. It is the part most firms skip.
Complaints are the visible part
Complaints about legal services are rising quickly. The Legal Ombudsman received 14,259 new complaints in 2025/26, 37% more than the previous year, and accepted complaint volumes rose fastest in immigration and asylum (49%) and residential conveyancing (41%)[1]. Behind every complaint that reaches a firm are others that never do. Among dissatisfied legal services consumers in 2026, the most common response was to do nothing, at 40%[2].
Source: Legal Ombudsman, 2026[1]
Show the data
| Item | Value |
|---|---|
| Immigration and asylum (accepted) | 49% |
| Residential conveyancing (accepted) | 41% |
| All new complaints received | 37% |
That makes each complaint more valuable than it first appears. It is a free, detailed account of where your service failed someone, often written by a client who cared enough to tell you. Most firms handle complaints carefully one at a time and learn very little from them as a group. This guide is about the second part: turning a pile of individual complaints into a short list of process fixes.
Record the same things every time
You cannot find patterns in complaints that are recorded differently by each person. Agree a short set of fields and make them mandatory in the complaints log, whether it is a spreadsheet or part of your case management system.
- Date received, and the channel: letter, email, phone, review, in person.
- Team and matter type.
- Stage of the matter when the problem happened, such as onboarding, during the matter, billing or closing.
- Theme, from a fixed list (see below).
- What the client wanted: an explanation, an apology, a refund, a change of fee earner.
- Outcome and date closed, including whether it went to the Legal Ombudsman.
- Root cause, completed once the complaint is investigated.
Log informal complaints too. A client who rings reception angry about not getting a call back has complained, even if they never write a letter. If only formal letters are logged, the data shows the most persistent clients, not the most common problems.
A coding framework that stays simple
The Legal Ombudsman says the most common complaints it resolves concern costs, delay and poor information[3]. Those three themes make a sensible core for your own codes. Add a few more that matter in your practice, and resist the urge to create dozens of categories that nobody uses consistently.
| Theme | Examples of sub-codes | Typical root causes |
|---|---|---|
| Communication | No reply, unclear explanation, not told of a change | No update rhythm, workload peaks, no back-up contact |
| Delay | Slow progress, missed internal deadline, waiting on third party not explained | Capacity, poor diary management, no escalation route |
| Costs | Bill above estimate, unclear charges, disbursement surprise | No revised estimate, unclear scope, billing errors |
| Error | Wrong document, wrong name, missed step | No checklist, no second check, rushed work |
| Attitude | Felt dismissed, rude call, lack of empathy | Training, stress, mismatched expectations |
| Access | Could not get through, could not use the website, needs not met | Phone cover, accessibility, adjustments not recorded |
Finding the root cause
The first explanation for a complaint is usually about a person: the fee earner was slow, the receptionist was short with the caller. Sometimes that is right. More often, the person was working inside a process that made the failure likely. Root cause analysis keeps asking why until it reaches something the firm can change.
State the failure precisely
Not "poor communication" but "the client was not told the completion date had moved until two days before".
Ask why it happened
"The fee earner did not know the date had moved." Why? "The other side told the assistant by phone and it was not recorded."
Keep asking until you reach a process
"There is no rule for recording phone messages from the other side on the file." That is fixable.
Check whether it happened elsewhere
Look at other files in the same team for the same pattern before deciding it was a one-off.
Decide one change
A rule, a template, a checklist step, a system prompt or a training point. One clear change beats five vague ones.
Set a review date
In three months, check whether complaints with the same root cause have fallen.
Blame-free does not mean consequence-free. If someone ignored a clear process, deal with it through supervision. But keep the complaints review focused on processes, or people will stop reporting problems and near misses.
Example: one complaint, one process change
Example: a client complains that she was charged for a lease extension she thought was included in her sale fee. The investigation finds that the fee earner did explain it on the phone, but the client care letter listed only "sale of leasehold property". Why was the letter vague? The template has a single line for the matter description. Why? It was written for freehold sales and never updated.
The firm's fix is not to tell the fee earner to be clearer. It is to add a scope section to the leasehold sale template listing what is included and what is charged separately, with lease extensions named. A quarterly review later shows no further complaints of the same kind, and two bill queries in the same team were resolved quickly because the scope was in writing.
Look for patterns, not anecdotes
A single complaint can mislead. Patterns are what justify spending time on a fix. Each quarter, look at the log across these cuts:
- By theme: is communication still the largest category, or has costs overtaken it?
- By team: does one department generate a disproportionate share for its size?
- By stage: are most problems at onboarding, mid-matter or billing?
- By channel: do phone complaints differ from email ones?
- By time: did complaints rise after a staff change, a system change or a seasonal peak?
Use volumes alongside percentages. In a small firm, two complaints in a quarter may be the whole picture; reading those two files closely is worth more than a chart.
Compare complaints with other signals at the same time. A rise in communication complaints that follows a rise in missed calls or files without contact tells you where to look. A rise with no change elsewhere may point to a new client group, a new service or a single difficult matter.
Who should run the review
In a small firm, the COLP or complaints partner usually runs the quarterly review. In a larger one, a practice manager prepares the data and a small group meets: the complaints lead, one head of department in rotation, and someone from reception or the support team, who often sees the start of a complaint before anyone else. Keep the meeting short, look at the patterns first and individual cases second, and leave with no more than two or three agreed changes, each with an owner.
Data protection complaints count too
The Data (Use and Access) Act 2025 requires organisations to handle data protection complaints from individuals, for example by providing an electronic complaint form, and to tell them the outcome[4]. A client who complains that their information was sent to the wrong address or shared without consent has made a service complaint and a data protection complaint. Log both, apply the same root cause method, and bring in your data protection lead where a breach may have occurred.
Close the loop
The SRA Code requires solicitors to tell clients in writing at engagement about their right to complain, and to tell them in writing if a complaint is not resolved within 8 weeks[5]. Meeting those rules is the minimum. What turns complaint handling into improvement is telling people what changed.
- Tell the complainant: "Because of your complaint, we have changed our leasehold client care letter so that it lists what is and is not included."
- Tell the team: share anonymised root causes and fixes at team meetings each quarter.
- Tell partners: include complaint themes and fixes in the monthly client experience report.
- Thank staff who report near misses and informal complaints.
Firms that do this find staff become more willing to log informal complaints, which in turn gives a truer picture of service.
Pitfalls to avoid
- Logging only formal written complaints, so the data reflects persistence rather than frequency.
- Using "other" as a code. If something does not fit, create a code or rewrite the theme.
- Stopping at "fee earner error" without asking why the error was likely.
- Making several changes at once, so you cannot tell which one worked.
- Treating a fall in complaints as success when it may mean fewer are being logged.
Complaint themes are one input to a wider report; see client experience metrics to report monthly. For a worked example of tackling the biggest communication problem in conveyancing, see cutting chaser calls in a conveyancing team.
Frequently asked questions
How should a law firm categorise complaints?
Use a short fixed list of themes, such as communication, delay, costs, error, attitude and access, plus fields for team, stage and channel. Consistency matters more than detail.
What is root cause analysis for complaints?
Asking why a failure happened until you reach a process the firm can change, such as a template, checklist or rule, rather than stopping at the person involved.
Should we log informal complaints?
Yes. Many dissatisfied clients never complain formally, and among dissatisfied consumers the most common response is to do nothing[2]. Informal complaints show the most common problems.
How often should complaint data be reviewed?
Look at new complaints monthly and review patterns quarterly, with a check three months after each fix to see whether it worked.
References
Legal Ombudsman (2026). Legal Ombudsman 2025/26 annual complaints data and insight (opens in a new tab) ↑
Legal Services Consumer Panel (2026). How consumers are using legal services (Tracker Survey 2026) (opens in a new tab) ↑
Legal Ombudsman (2026). Complaints we can help with (opens in a new tab) ↑
GOV.UK (DSIT) (2025). Data (Use and Access) Act 2025: data protection and privacy changes (opens in a new tab) ↑
Solicitors Regulation Authority (2025). SRA Code of Conduct for Solicitors, RELs, RFLs and RSLs (opens in a new tab) ↑