Basic Logging vs Root Cause Analysis: Complaints Handling Approaches

Overview

Complaints handling is one of the most scrutinised areas of FCA-regulated firms' operations. Every authorised firm must comply with DISP — the Dispute Resolution sourcebook — which sets out requirements for recording, investigating, and resolving complaints. At a minimum, firms must maintain a complaints register, respond within prescribed timeframes, and submit periodic returns to the FCA. For many years, this was treated as a largely administrative exercise: log the complaint, resolve it, move on.

The introduction of the Consumer Duty has fundamentally changed the regulatory calculus. The FCA now expects complaints data to serve as a primary input into outcome monitoring. It is no longer sufficient to demonstrate that individual complaints were resolved fairly. Firms must show that they are analysing complaint data to identify systemic issues, understanding why complaints arise, and taking action to address root causes. The shift is from reactive resolution to proactive prevention — and it applies to every firm, regardless of size.

This creates a meaningful choice for firms. Basic complaints logging — recording each complaint with a category, outcome, and resolution date — meets the minimum DISP record-keeping requirements but provides little analytical value. A root cause analysis programme goes substantially further: it imposes a structured taxonomy, trains staff to identify underlying causes rather than symptoms, aggregates data to reveal patterns, and creates feedback loops that connect complaint insights to business improvement. The investment is greater, but so is the regulatory and commercial return.

The question firms must answer honestly is whether their current complaints handling would withstand scrutiny from the FCA's Consumer Duty supervision team. If the answer involves any hesitation, the case for upgrading from basic logging to root cause analysis is compelling.

When Basic Complaints Logging Makes Sense

Basic complaints logging remains a defensible approach for a narrow category of firms: those with genuinely low complaint volumes, simple product sets, and limited customer interactions. A firm that receives fewer than ten complaints per year across a single product line can arguably identify patterns through direct observation by the compliance officer without needing a formal analytical programme. At this scale, the compliance officer knows every complaint personally and can spot recurring themes without structured data analysis.

Newly authorised firms in their first twelve months of operation may also find basic logging appropriate as a starting point. Before you have complaint data to analyse, building an elaborate root cause programme is premature. The sensible approach is to start with disciplined logging — ensuring every complaint is recorded with sufficient detail — and then introduce root cause analysis once you have enough data to make the analysis meaningful. Typically, this transition point arrives within the first year.

Firms under genuine financial pressure may also defer root cause analysis investment, provided they have a documented plan and timeline for implementation. The FCA applies proportionality, and a small firm that demonstrates awareness of the gap and a credible plan to address it is in a stronger position than one that has not considered the question at all. However, this is a temporary position, not a permanent strategy. The Consumer Duty does not include a small-firm exemption for outcome monitoring.

When Root Cause Analysis Programme Makes Sense

For any firm with meaningful complaint volumes — broadly, more than twenty complaints per year — root cause analysis is not a luxury but a regulatory expectation. At this volume, patterns exist in the data whether or not the firm chooses to look for them. The FCA's view is unambiguous: if patterns exist and the firm failed to identify and act on them, that is a failure of governance and oversight.

Firms operating in sectors with elevated complaint risk should treat root cause analysis as essential from the outset. Consumer credit, general insurance, investment advice, and pension transfers all generate complaint volumes and complexity that demand structured analysis. The Financial Ombudsman Service publishes data showing which sectors and product types generate the highest referral rates, and firms in these sectors face heightened supervisory expectations around complaints handling.

The commercial case is equally strong. Every complaint that could have been prevented but was not represents a direct cost: staff time to investigate and resolve, potential redress payments, FOS case fees if the complaint escalates, and reputational damage. Root cause analysis is the mechanism by which firms convert complaint data into operational improvement. A firm that discovers 40% of its complaints stem from a single unclear clause in its terms of business can fix that clause once and eliminate an entire category of complaints. Basic logging would record each of those complaints individually without ever surfacing the connection.

Consumer Duty annual board reports require firms to present evidence of outcome monitoring across four key areas: products and services, price and value, consumer understanding, and consumer support. Complaints data feeds directly into at least three of these. A root cause analysis programme produces the structured, evidenced insight that makes these board reports substantive rather than superficial. Boards that receive only complaint volume counts cannot meaningfully assess whether customers are receiving good outcomes.

Key Considerations

The FCA's supervisory approach to complaints has shifted materially since Consumer Duty implementation. In thematic reviews and firm-specific assessments, the regulator now routinely asks firms to demonstrate what they have learned from complaints and what changes they have made as a result. A firm that can produce only a flat log of resolved complaints — however meticulously maintained — will struggle to answer these questions. The FCA is looking for evidence of a closed loop: complaint data in, analysis performed, root causes identified, remedial action taken, effectiveness monitored.

The quality of your complaint taxonomy is the foundation of effective root cause analysis. A poorly designed taxonomy — one with too many categories, overlapping definitions, or categories that describe symptoms rather than causes — will produce data that is difficult to analyse and unreliable for decision-making. Investing time in taxonomy design, with input from operational staff who handle complaints daily, is essential. The taxonomy should be specific enough to be analytically useful but simple enough for frontline staff to apply consistently. Most firms find that fifteen to twenty-five root cause categories, organised into four or five thematic groups, strikes the right balance.

Staff training is the second critical success factor. Root cause analysis only works if the people recording complaints are trained to look beyond the customer's stated issue and identify the underlying cause. This requires a different mindset from basic logging, where the goal is simply to capture the facts. Training should be practical, scenario-based, and reinforced through quality assurance of completed complaint records. Firms that invest in the programme design but neglect staff training consistently find that the data quality is too poor to support meaningful analysis.

Board engagement determines whether root cause findings translate into business change. The most effective complaints programmes produce regular management information that is reviewed at board or executive committee level, with named owners for remedial actions and tracked completion dates. Without governance, root cause analysis becomes an academic exercise — the firm identifies the problems but never fixes them, which is arguably worse than not looking at all, because it demonstrates awareness without action.

The Bottom Line

Basic complaints logging served firms adequately in a regulatory environment focused on DISP compliance and individual complaint resolution. That environment no longer exists. The Consumer Duty has raised the bar to outcome monitoring and systemic improvement, and the FCA's supervisory practice reflects this shift in real terms. Firms that continue with basic logging are not just missing a commercial opportunity — they are carrying regulatory risk that increases with every supervisory cycle.

Root cause analysis is not complex or prohibitively expensive to implement. It requires a structured taxonomy, trained staff, a regular analysis cadence, and governance that connects findings to action. For most firms, the investment pays for itself within twelve months through reduced complaint volumes, lower FOS referral rates, and stronger evidence for Consumer Duty reporting. More importantly, it positions the firm to answer the question the FCA will inevitably ask: what have you learned from your complaints, and what have you done about it?