How Providers Use Informal and Withdrawn Complaints in CQC Risk Profiles
Not every concern becomes a formal complaint. Some people raise an issue informally, accept a quick response, or withdraw a complaint because they feel it has been resolved. Even so, the concern may still contain important risk intelligence.
Strong provider risk profile intelligence from informal complaints helps leaders identify early themes before they become formal dissatisfaction or regulatory concern.
This depends on CQC evidence and assurance from complaint learning, including feedback records, care records, audits, staff practice and governance review.
The CQC compliance and governance knowledge hub supports providers to connect concern handling with governance, assurance and inspection-ready monitoring.
Why this matters
CQC and commissioners may ask how providers learn from concerns, not only formal complaints. If informal issues are resolved locally but not recorded as intelligence, the provider may miss repeated themes.
A withdrawn complaint can still show that something went wrong. The fact that the person no longer wants to pursue it does not remove the provider’s responsibility to learn from it.
Informal concerns are especially important where people may feel reluctant to complain. This can include family hesitation, fear of damaging relationships, communication barriers or uncertainty about the complaints process.
Good governance captures learning without making the process feel heavy or defensive.
A clear framework for informal complaint intelligence
Providers should define how informal concerns, withdrawn complaints and early dissatisfaction are recorded. The record should capture the issue, service area, person affected, response given, evidence checked and any learning required.
Risk profiles should include informal concerns where they repeat, affect safety or suggest a wider service issue.
Managers should avoid treating informal resolution as the end of the matter. Resolution answers the person’s concern. Governance asks whether the provider needs to change anything.
Good governance records the concern, action taken, pattern review, evidence checked and outcome of learning.
Operational example 1: Informal concern about poor mealtime support
Baseline issue: A relative informally raised concern that mealtime support felt rushed, but did not want to make a formal complaint. The measurable improvement target was improved mealtime support assurance within six weeks, evidenced through care records, audits, feedback and staff practice.
Step 1: The deputy manager records the informal concern, identifies the mealtime support issue, and logs the concern in the feedback intelligence tracker.
Step 2: The nutrition lead reviews food and fluid records for the person affected, checks support evidence, and records findings in the nutrition assurance note.
Step 3: The senior carer observes mealtime support on the relevant unit, checks pace and dignity, and records findings in the practice observation log.
Step 4: The Registered Manager briefs staff on mealtime support expectations, clarifies dignity standards, and records the discussion in the staff communication file.
Step 5: The governance group reviews six-week mealtime evidence, checks whether further concerns reduced, and records assurance in governance minutes.
What can go wrong is that the concern is treated as resolved after reassurance to the relative. Early warning signs include rushed support, incomplete food records, people leaving meals unfinished or repeated informal comments. Escalation may involve dietetic advice, staffing review or focused mealtime monitoring. Consistency is maintained through dignity-focused observation.
Governance audits check food records, observation findings, staff briefing evidence and feedback themes. The nutrition lead reviews weekly during the monitoring period. Action is triggered by repeated mealtime concerns, poor intake evidence, rushed practice or no measurable improvement after staff briefing.
This example shows that informal concern can reveal a wider quality risk. The provider should respond kindly to the person raising the concern, while still testing whether practice needs to improve.
Operational example 2: Withdrawn complaint about missed communication
Baseline issue: A family member withdrew a complaint after receiving an apology about missed updates, but the issue reflected repeated communication gaps. The measurable improvement target was improved family update reliability within eight weeks, evidenced through communication records, feedback, audits and staff practice.
Step 1: The complaints lead records the withdrawn complaint, captures the original concern, and enters the theme in the complaints learning log.
Step 2: The service manager reviews communication records for the person involved, checks update frequency, and records findings in the service assurance note.
Step 3: The team leader checks whether staff understand family update responsibilities, confirms expectations, and records findings in the supervision summary.
Step 4: The provider quality lead samples similar communication records across the service, identifies repeat gaps, and records findings in the assurance report.
Step 5: The provider governance group reviews eight-week communication evidence, confirms learning actions, and records decisions in governance minutes.
What can go wrong is that a withdrawn complaint is removed from learning systems because the person is satisfied with the apology. Early warning signs include missing call notes, families chasing information, unclear responsibilities or repeated apology-based resolution. Escalation may involve revised communication standards, manager oversight or commissioner update. Consistency is maintained through complaint learning logs.
Governance audits check complaint records, communication notes, supervision evidence and sampled assurance findings. The complaints lead reviews monthly for emerging themes. Action is triggered by repeat communication concerns, weak records, unclear ownership or repeated withdrawn complaints on the same theme.
This example protects learning from being lost. A complaint can be resolved for the person and still remain useful intelligence for provider governance.
Operational example 3: Informal staff-reported concern about family dissatisfaction
Baseline issue: Staff reported that several relatives seemed dissatisfied during visits but had not complained formally. The measurable improvement target was improved early concern capture within one quarter, evidenced through feedback, care records, audits and staff practice.
Step 1: The team leader records staff-reported concern themes, identifies families mentioned, and logs the intelligence in the early concern tracker.
Step 2: The engagement lead contacts selected relatives for feedback, checks whether concerns exist, and records responses in the feedback system.
Step 3: The Registered Manager reviews care records linked to concerns raised, checks whether evidence supports the feedback, and records findings in the assurance note.
Step 4: The provider quality lead compares staff-reported intelligence with formal complaints and feedback, identifies themes, and records conclusions in the risk profile.
Step 5: The provider board reviews quarterly experience intelligence, checks whether early concerns are captured, and records challenge in board minutes.
What can go wrong is that staff observations about dissatisfaction are dismissed because no formal complaint exists. Early warning signs include relatives avoiding discussion, repeated staff comments, low survey response or increasing informal tension. Escalation may involve targeted engagement, advocacy support or senior manager contact. Consistency is maintained through early concern capture.
Governance audits check early concern logs, feedback responses, care record evidence and board challenge. The engagement lead reviews monthly during active monitoring. Action is triggered by repeated staff-reported dissatisfaction, poor feedback coverage, formal complaints emerging later or unresolved experience themes.
This example recognises that frontline staff may notice concern before systems do. Provider governance should value that intelligence while checking it fairly and sensitively.
Commissioner expectation
Commissioners expect providers to learn from the full range of concerns. They may ask how informal dissatisfaction, withdrawn complaints and early feedback are monitored.
They will look for evidence that providers do not hide behind low formal complaint numbers. Low complaint volume may mean people are satisfied, but it may also mean concerns are being resolved informally without organisational learning.
Commissioners may also examine whether providers can identify themes across complaint types. A pattern of informal concerns can be as important as a smaller number of formal complaints.
Strong informal concern monitoring reassures commissioners that providers listen early, respond proportionately and use concern intelligence to improve care before dissatisfaction escalates.
Regulator and inspector expectation
CQC inspectors may ask how providers encourage people to raise concerns and how learning is captured. They may compare complaint records with feedback, care records, staff interviews and family comments.
If informal concerns are not recorded, inspectors may question whether the provider has a complete view of people’s experience.
The provider should evidence concern capture, response, learning review, theme analysis, action taken and outcome monitoring.
Inspectors may also assess culture. A strong service does not treat concerns defensively. It records them, responds respectfully and uses them to strengthen assurance.
Conclusion
Informal and withdrawn complaints are important sources of provider risk intelligence. They may show early dissatisfaction, weak communication, practice gaps or emerging themes before formal complaints increase.
Outcomes are evidenced through feedback records, care records, communication logs, audits, staff practice, supervision records and governance minutes. Improvement is shown when mealtime support is checked, communication gaps reduce and staff-reported concerns lead to better engagement.
Consistency is maintained through early concern trackers, complaint learning logs, theme review and governance challenge. Providers should not lose learning simply because a concern was resolved informally or withdrawn.
For CQC and commissioners, strong use of informal concern intelligence demonstrates listening governance. It shows that provider leaders value early feedback, learn from lower-level concerns and act before experience risks become serious complaints.