In customer meetings this year, one exchange has repeated more than any other. A provider describes its complaints function, and it is a real function: a dedicated team, a case management system, target dates, an escalation route. Then the board asks what the recurring themes are, whether last year's lessons have been applied, and why the same issue keeps arriving from the same estate. Nobody in the room can answer.
That is not a capacity problem, and it is rarely a competence one. The teams we meet are diligent and under pressure. It is a design problem. The systems these organisations bought were built to log and track individual cases, and they do that well. They were not built to tell anyone what the cases add up to. So the record grows, and nothing reads it.
Logging is not analysis, and the Code asks for both
The Complaint Handling Code does not stop at timeliness. It expects complaints to produce learning, and it expects that learning to reach the governing body through the Member Responsible for Complaints. The Regulator's Consumer Standards go further and expect a provider to use complaint data to identify and act on systemic issues, not simply to close cases one at a time.
Both of those duties assume somebody is looking across the file rather than down it. In practice the question we are asked most often is whether complaints cluster by postcode, by contractor, or by issue type, and the honest answer in most organisations is that nobody knows, because finding out means reading individual case notes by hand. The data to answer it already exists. It sits in free text, in the wrong shape, across several thousand records.
The same gap shows up at the other end. Complaints generate learning points, those learning points go into a report, and the report is filed. Whether the learning was ever completed, whether it was any good, and whether it prevented anything are questions almost nobody tracks. A learning point that is logged and not followed through is indistinguishable, in the record, from one that changed the service.
The real process is often a spreadsheet
The second pattern is more uncomfortable, and it is more common than the sector admits. In several organisations the official case management system holds the bare minimum, while the process that actually runs the department is a spreadsheet maintained by hand: the live case list, the target dates, the escalation monitoring.
Alongside it, Stage 1 and Stage 2 deadlines are frequently tracked through somebody's personal diary reminders rather than automated alerts. Near-miss timing then becomes a pattern, and when you look at which cases nearly slipped, they are not the complicated ones. They are the ones that landed in a busy week.
Both arrangements work, right up until they do not. The Code's statutory clocks are 10 working days at Stage 1 and 20 at Stage 2, and the evidence that they were met has to survive the person who was holding it. An audit trail that depends on spreadsheet discipline is only ever as good as the discipline, and it does not survive a leaver, a reorganisation or an inspection asking to see the underlying records.
The resident feels the missing analysis first
This is where it stops being an internal reporting inconvenience. Three of the patterns we hear are, from the resident's side, the same experience.
Where most Stage 1 responses are escalated, and the remedy has to be improved at Stage 2, the question is not whether Stage 2 is working. It is whether Stage 1 was ever resourced and empowered to resolve the thing properly the first time. The Code's early resolution principle asks landlords to put things right within their own procedure. A high escalation rate says that, for most residents, the first answer was not the real answer, and they had to push to get one.
Where a complaint raises three things and the response addresses one, the resident does not read a partial response as an oversight. They read it as being managed. The Code requires every point raised to be answered, and staff in the organisations we meet are aware of that and still need repeated reminders, because nothing in the system checks it.
And the quality and tone of responses is, almost universally, not measured at all. Whether a letter reads as empathetic or as heavy-handed, whether it acknowledges what the household actually went through, is invisible at scale, even though the Ombudsman's guidance on putting things right treats the manner of a response as part of the remedy and not a garnish on top of it. Tone is one of the more reliable drivers of escalation, and it is the one no dashboard shows.
None of those three is caught by a system that tracks whether a case was closed inside the deadline. All three are caught by reading across cases, which is the thing nobody has time to do by hand.
The question worth asking in the room
There is a simple test for whether this applies to your organisation. At the next board or committee meeting, ask what the top three recurring complaint themes were last quarter, who produced that figure, and what changed as a result. Then ask how long the answer took to assemble.
A confident answer is genuinely reassuring. A slow one is more useful, because it tells you the analysis is being done by a person, on request, rather than by the system, continuously. That is a fragile arrangement to rest a regulatory position on, and it is the arrangement most providers currently have.
Where the record should start
The fix is not another internal reporting layer bolted to the top of the same unstructured data. Analysis is only as good as the shape of what went in, and most complaint records are shapeless because the first contact was a phone call transcribed into a free-text box by somebody with the next call waiting.
That is the thinking behind TenantSafe, which ThinkTribal provides free to residents. It gives a resident a plain-language read on their issue, the statutory reference and timescale that apply, and a dated copy of the record they keep. What reaches the landlord is a complaint that already knows what it is: categorised, staged, and tied to the right part of the Code from the first minute. That is easier to answer, easier to evidence, and, for the first time, easier to count.
A landlord that cannot describe its own complaint themes is not failing its residents through indifference. It is reading a filing cabinet and calling it a report. The residents in those files told you what was wrong, patiently, one case at a time. The least any of us can do is add them up.