A complaint rarely begins when the complaint is written

Bob is woken at 7am every morning.

He never got up this early until he moved into the care home. He had always been a later riser — 9am, a cup of tea in the kitchen, the radio on quietly. His daughter mentioned it in passing on one of her visits. “Bob is woken at 7am? Are you sure? Dad never used to get up until 9am.” The care worker smiled and said something about the morning routine of the home. His daughter nodded. Nothing changed.

A few weeks later, she noticed his appearance. Bob had always been clean-shaven — a point of pride for him. Now he had two or three days of stubble, some mornings more. She mentioned it to the team leader. The team leader said shaving could be difficult with some residents, that Bob had been a bit resistant lately, that they would try again tomorrow. His daughter nodded. Nothing changed.

Then she noticed his clothes. A stain on his jumper one week, the same jumper the following week. Bob had always been particular about how he looked. His daughter raised it, gently, in the visitors’ book and again with the senior on duty. She was told the laundry had been under pressure, that staff were doing their best. His daughter nodded. Nothing changed.

Three months later, a formal complaint arrived at the registered manager’s desk. It referenced Regulation 9, Regulation 10, the Mental Capacity Act, and the freedom to speak up quality statement.. It was polished, formal, and several pages long. It did not read like a daughter worried about her father. It read like a legal document.

The complaint, of course, did not begin when the complaint was written.

It began the morning Bob was first woken at 7am when he would have chosen 9am. It continued each time his daughter mentioned something and nothing changed. By the time it arrived on the registered manager’s desk, the substance of the complaint was rarely what the complaint said. The substance was the accumulated experience of not being heard.

This is the most important thing registered managers can know about complaints. And it is the thing sector guidance most often misses.

Readers of the forthcoming book How Leaders Know What’s Really Happening in Adult Social Care will recognise Bob from a chapter that tells his story from inside the experience. What arrives as a complaint, from the outside, began much earlier — from the inside.

The Unheard Person

Most complaint guidance focuses on process. Acknowledge quickly. Investigate thoroughly. Respond proportionately. Follow Regulation 16. These things matter — they are the legal floor.

But beneath the process question sits a diagnostic question that most services never ask: what did this person try to tell us before they wrote this?

Behind many complaints is a person who has not felt listened to. The complaint is the moment the unheard experience became formal. The legalistic tone, the careful formatting, the references to regulations or statutes — these are not the person being aggressive. They are the person reaching for tools they hope will finally get them heard.

When services respond to the surface of the complaint — its formality, its length, its legal references — they miss the substance. They investigate what the complaint says rather than what the person has been trying to say for longer than the complaint itself records.

This is not about being more sympathetic. It is about being more accurate. The diagnostic question what has this person been trying to tell us? produces different answers than what does this complaint allege? — and the difference is where improvement lives.

The psychological cost of complaining

Before going further, it is worth naming something that rarely gets said in sector guidance: most people don’t want to have to complain.

Complaining is psychologically uncomfortable for almost everyone. It requires confronting a service or a professional, naming what was wrong, and risking that the relationship sours as a result. It requires choosing to be the person who raised the issue, often in a context where they are not sure their complaint will be taken well.

In adult social care, the discomfort is sharper still. The person raising the complaint — or their family member complaining on their behalf — often depends on the service for ongoing care. They worry, consciously or otherwise, that complaining might affect how their loved one is treated afterwards. They worry about being seen as difficult. They worry that the staff they see every week will resent them. They worry that making a fuss will cost them something they cannot afford to lose.

Most complaints in adult social care, therefore, have already been weighed and hesitated over. By the time someone sits down to write a formal complaint, they have usually concluded that the cost of staying silent is greater than the cost of speaking up. That is a significant conclusion. It says the issue mattered enough to overcome the psychological barrier to raising it.

Services that receive complaints as confrontation miss this entirely. Services that receive complaints as something a person chose to do despite the cost — that is a different reception, and it changes how the service responds.

And the cost of receiving one

There is another side of this that deserves to be named honestly, because it rarely is.

Complaints are difficult to receive. Especially for registered managers who care. The first reaction when a complaint arrives is rarely calm professional curiosity. It is often something closer to hurt. I didn’t know Bob’s daughter felt like this. We do our best. He is well cared for. The team works so hard. These are not defensive thoughts from bad managers. They are honest thoughts from good ones, because the work is hard and the hours are long and the care is real.

There is also a more primal response underneath the thoughts. A complaint goes against the grain of how we are wired. Our bodies read it as a threat — chest tightens, shoulders rise, the mind starts building arguments before the letter has even been fully read. This is fight-or-flight doing what fight-or-flight was designed to do. It is not a character defect. It is biology responding to what feels, in that moment, like an attack.

The discipline is to notice the response and not be governed by it. The body reacts as though the complaint is a threat. The work is to consciously reframe it as something else: as constructive feedback, as an opportunity to learn, as a signal that the service has missed something it needs to see. Not all complaints will turn out to be fully right. Some will be misdirected. Some will name symptoms rather than causes. But every complaint carries information, and the job of the manager is to receive that information rather than repel it. The reframe from threat to feedback is the single most important move a registered manager can make in the minutes after a complaint arrives.

A complaint sits badly because it seems to contradict the truth the manager has been living with every day: that her service tries, that her staff care, that the person the complaint concerns has been genuinely held in mind. To receive a complaint saying otherwise can feel like an accusation, not just of a specific failure but of the whole effort. Managers who care will often feel it personally before they feel it professionally. That reaction is not a flaw. It is a sign that the work matters to them.

But feelings, honoured, still need to be held alongside a second truth: that the manager’s experience of the service is not the same as the person’s experience of the service. Both are real. Both can be true. A service can genuinely care and still not be hearing the person who lives within it. A team can work hard and still miss the pattern a daughter has been trying to name for three months. The manager’s effort and the complainant’s experience are not in competition. They are two facts about the same situation, and the job of good complaint handling is to hold both.

Services that hold only the first truth — we tried, we care, we do our best — will respond to complaints by defending the effort. Services that hold only the second — the person felt unheard, so we must have failed — will respond with excessive self-blame that helps no one. The services that do this well hold both, and respond from the middle: we care, we worked hard, and this person was still unheard. Both things are true. Now what needs to change?

This is a harder emotional position than either defence or self-blame. It is also the only position from which genuine learning is possible.

Why Well-Led depends on listening, not processing

A service rated Requires Improvement or Inadequate under Well-Led rarely gets there because of one unmanaged complaint. It gets there because a pattern emerges across complaints that the service didn’t recognise as a pattern.

Inspectors reading complaint records look for two things. First, whether individual complaints were handled procedurally well. Second — and more importantly — whether the service used complaints to understand what was not working for the people it supported. The second question is about whether the service listens, not whether it processes.

Services that handle complaints only at the procedural level can tick every Regulation 16 box and still fail Well-Led. Because the complaints keep arriving about the same things, and the service keeps investigating them as isolated events, and the pattern that would tell the leadership something important about their service is never seen.

The services that do this well treat each complaint as evidence about a person — and the cumulative complaints as evidence about the service. They ask not only was this complaint resolved? but what is our complaints pattern telling us about what people are experiencing?

That is the Well-Led question. Process does not answer it. Listening does.

The False Assurance Problem in complaints

Carevia has written elsewhere about the False Assurance Problem — the pattern where governance artefacts look complete while masking the inadequacy beneath them. Audits are completed but don’t identify what inspectors find. Actions are recorded but never embedded. Policies exist in folders but not in practice.

Complaints are a fourth place where this pattern appears, and where the consequences are more personal.

The first manifestation: a service receiving no complaints can give a registered manager or provider false assurance that everything is fine. Low or zero complaint numbers are often presented to boards and inspectors as evidence of good service. They might be. They might also be evidence that the service has not made it easy to complain, or that people are too afraid to raise concerns, or that complaints are being absorbed informally without ever reaching the register. The absence of complaints is not the presence of satisfaction. Then one day a complaint arrives that completely changes the picture — and the leadership discovers that what looked like calm was silence.

The second manifestation: complaints being received and handled within policy can give false assurance that the service manages complaints correctly. The procedural box gets ticked. The acknowledgement goes out within 24 hours. The investigation concludes. The response is sent. Regulation 16 is satisfied.

But that procedural completion does not mean anything has changed. It does not mean the person complaining is satisfied with the outcome. It does not mean the service has learned anything. It does not mean the next complaint about the same thing won’t arrive next month. A complaints process that runs smoothly can be running smoothly because it is well-designed — or because it is absorbing complaints without producing change.

The diagnostic question in both cases is the same: what would the evidence look like if this assurance were false? A service with no complaints should be able to answer: we know people feel safe to complain, and we know they are choosing not to. A service with a well-running complaints process should be able to answer: we know complaints are producing real changes in practice, and we know complainants feel heard.

If those answers are not available, the assurance is unearned.

RAOF™ applied to the complaints process

RAOF — Read, Ask, Observe, Feedforward — was developed as a reflective leadership framework for registered managers in adult social care. Applied to complaints, it shifts complaint handling from a procedural exercise into a listening discipline.

The nature of the complaint will determine how RAOF is applied in practice. What follows is not a checklist — it is a way of thinking through what listening actually requires when a complaint arrives.

Read. Read the complaint itself, carefully. Read the care plans and records of the person the complaint concerns. Read your own complaints process and ask whether it was followed — not just procedurally, but with genuine attention. Read earlier entries: supervision notes, daily records, previous communications with the family. The complaint document is the latest word from the person, not the first.

Ask. Ask staff what they observed. Ask the complainant what outcome they need — many complaints escalate because services respond with investigations the complainant never asked for. If the complainant is not the person using the service, ask the person themselves — where it is appropriate and safe to do so — what their experience has been. Their experience is the primary evidence, not a secondary check.

Observe. Observe the experience of the person the complaint concerns, in the days and weeks that follow. Has anything changed? Does the person still appear distressed or withdrawn? Are staff approaching the person differently, perhaps more cautiously? Observation after a complaint is often more revealing than observation before one — because the service has now been alerted to something, and what happens next is diagnostic.

Feedforward. Feedforward what you have learned, to the team and to the complainant. Tell the team what you found and what it means for practice — not just the specific issue raised, but the wider lesson. Tell the complainant what will change and how you will know it has changed. Feedforward closes the loop. It is also the step most services omit, which is why complaints about the same things keep arriving.

RAOF applied this way takes a complaint from a process to be completed into an enquiry to be worked through. The procedural requirements of Regulation 16 are still met — but they are met as a byproduct of the listening, not as the point of the response.

What listening looked like for Bob

When Bob’s daughter’s complaint arrived on the registered manager’s desk, the first reflex was to read it for allegations. Which regulations were being cited. Which incidents specifically. What the service was being accused of. The letter was formal, several pages long, and carried an implicit threat of escalation to CQC.

The registered manager paused before responding.

She read the complaint again, this time for what the daughter was actually saying. Not the legal framing. The substance. Her father was being woken at a time he had not chosen. His appearance no longer matched who he was. His clothes had stopped being cared for. Behind the formal language was a daughter who had tried, three times, to raise these things informally. She had been listened to politely each time. Nothing had changed.

The manager read Bob’s care records. She found the daughter’s earlier mentions noted briefly in handover logs, each one accompanied by something short like “family raised concern about wake time, discussed routine with team” or “daughter commented on appearance, will monitor.” The observations had been recorded. They had not been acted on.

She asked the care team what they had observed. Staff had noticed Bob was often tired in the mornings. They had assumed this was age, or medication, or the natural settling pattern of a newer resident. No one had connected it to the wake time. The shaving had been attempted each day, but a couple of mornings Bob had pulled away, and the carer had decided not to pursue it. The stained jumper had been noted, but laundry had been running behind schedule, and it had felt too small a thing to flag upward.

She asked Bob’s daughter what outcome she needed. Not what resolution the complaint formally demanded — but what she actually needed. The answer was simpler than the complaint letter had suggested. She wanted to know her father was being seen as himself, not as a set of tasks. She wanted the staff who cared for him to know who he had been before he came into care. She wanted to feel that when she raised something small, it would be heard.

The manager observed Bob over the following week. Quietly. Without announcement. He did seem tired in the mornings. His affect brightened noticeably around mid-morning. In conversation about his life before the home, he mentioned his old routines more than once — the late start, the tea, the radio. He was not hiding who he was. Staff, busy with the pace of the home, had not had time to notice.

The changes that followed were proportionate, not transformative. Bob’s wake time was renegotiated with him — 8.30 most mornings, earlier only for medical appointments. The shaving conversation was handed to the carer Bob was closest to, and framed as a preference to check in with, not a task to complete. Laundry got a small schedule adjustment to prioritise residents who had raised clothing concerns. A new section was added to the care plan template: “What does this person take pride in?” — completed with input from the person and their family, reviewed quarterly.

The manager also fed forward to the team. Not just the specific changes, but the broader lesson: that three mentions from Bob’s daughter had been logged and not actioned, and that the complaint had arrived because the informal channel had stopped working. The team received this honestly and uncomfortably. Good staff who care are not easy to tell that they missed something. But the conversation produced a shared agreement: observations noted in handover now include a small flag for “mentioned by family more than once” — a signal for a supervisor to look at, not just a record to keep.

The manager wrote back to Bob’s daughter. The letter was not a legal response. It acknowledged what had happened, what she had raised and how it had been received, what had now changed, and what would be different next time. She also offered to meet.

Bob’s daughter accepted. The meeting was not adversarial. It was the first time she had felt her concerns were being met on the substance, not on the form.

None of this meant the service had been failing before. It meant that the service, like most services, had been running at the pace of its own routine rather than at the pace of the people it supported. A complaint had arrived not because anyone was negligent, but because three quiet mentions had not been enough to slow the routine down. The complaint was what finally got through.

This is important to name clearly, because the service could easily have chosen differently.

The procedural path was available the whole time. The complaint could have been acknowledged within 24 hours. An investigation could have been opened in line with policy. Each allegation could have been examined and a point-by-point response drafted, addressing Regulation 9, Regulation 10, and the Mental Capacity Act references the letter had cited. A response could have gone back within the 28-day window. Regulation 16 would have been satisfied. The complaints register would have recorded a closed case. An inspector reading the file months later would have seen every procedural box ticked.

And nothing would have changed. Bob would still have been woken at 7am. His shaving would still have been attempted each morning and abandoned some mornings. His jumpers would still have carried yesterday’s stains. His daughter would have received a letter that addressed her allegations without addressing her experience. The service would have been compliant and the person would still have been unheard. From the outside, this is what good complaint handling looks like. From the inside, it is the False Assurance Problem in its most personal form.

This is what good complaint handling actually looks like. Not a polished defence. Not a faster acknowledgement. A genuine reopening of the service’s attention to the person the complaint was about. Complaints aren’t about winning. They are about learning, changing, and making the experience of the people supported better. Let’s redefine winning — in the context of a complaint — as improving outcomes because of what the complaint revealed.

It is hard to admit that someone was unhappy with care. Especially when you care so much about the work and the people. The discomfort of that admission is real and it is worth honouring, not dismissing. But discomfort is not the same as wrongness. A complaint that makes you uncomfortable is often a complaint that is telling you something important.

The services that do this well are not the ones that receive no complaints, or the ones that handle complaints with the most polished responses. They are the ones where a complaint produces genuine change in practice — even when the service believes it did everything right. Because the measure of good complaint handling is not whether the service was correct. It is whether something improved for the people the service supports.

A brief note on AI-drafted complaints

A recent sector article explored the rise of AI-assisted complaints — complaints drafted or polished using tools like ChatGPT that sound more formal, more legalistic, and more authoritative than handwritten ones. The practical guidance in that piece was sound: acknowledge AI-drafted complaints in the normal way, do not mirror their formality defensively, focus on substance over style, respond proportionately.

The Carevia view agrees with all of that. The additional point worth making is this: AI lowering the barrier to complaint drafting does not change what complaints actually are. It changes how they look. The underlying truth — that behind the complaint is a person who did not feel heard — is older than ChatGPT and will outlast it.

If anything, AI-drafted complaints are useful evidence of how hard some people have found it to be heard through ordinary channels. The person reaches for the most authoritative-sounding language they can access. That is not a threat to services. It is a signal that ordinary listening was not happening — and a chance to hear what should have been heard sooner.

Services that respond to AI-drafted complaints by mirroring their formality confirm the complainant’s suspicion that informal channels don’t work. Services that respond by hearing the person behind the formality close the gap that drove the escalation.

The fresh-eyes exercise for registered managers

This is an exercise worth doing now, before moving on.

Take a look at the last complaint you received. If it is too recent to look at with distance, look at the one before that. Open the file. Read the complaint, your investigation, and your response.

Then, honestly, ask yourself two questions:

A simple truth applies here: if we always do things the way we’ve always done them, we will always get the same results. A complaint is an invitation to change the way you do something. If no change followed, the invitation was declined.

This exercise is uncomfortable. It is meant to be. Most complaints arrive feeling unfair — because they arrive at services and managers who care. Doing the exercise honestly means holding the discomfort of recognising that a person who received your care felt, at the time, that your care was not enough. That is a hard thing to sit with. It is also the only place real improvement begins.

How Carevia supports this way of working

Carevia was built around the belief that good leadership in adult social care is a reflective discipline, not a procedural one. That belief shapes every tool we build and every article we publish.

Carevia Pro+ includes the full suite of RAOF™-integrated tools for registered managers — including Ask Carevia+, which simulates inspection-style questioning across all five CQC domains, and the Inspection Readiness Dashboard, which builds governance evidence as a natural consequence of daily leadership. For the work of hearing concerns earlier, before they escalate, Pro+ is the natural home.

Carevia Pro includes the Governance & Assurance Schedule Planner and visible-leadership tools designed to help registered managers stay connected to the daily experience of their service — so that concerns are seen and addressed at the earliest opportunity, before they become formal complaints.

Both memberships include Ask Carevia for sector-specific AI guidance on complaints, governance, inspection, and leadership questions.