How to Evidence Complaints Handling, Feedback Systems and Duty of Candour Readiness During CQC Registration

A strong CQC registration submission must show that complaints, concerns and feedback will be handled through a live operational system rather than an aspirational policy. Inspectors will expect providers to demonstrate how concerns are received, recorded, investigated, responded to and translated into measurable improvement. That must also align clearly with CQC quality statements, because responsiveness, openness and learning are tested through how services act when people are dissatisfied, worried or affected by poor outcomes. Providers therefore need to evidence not only that they welcome complaints and feedback, but how they use them to strengthen practice, fulfil duty of candour obligations and maintain service credibility from the start.

Providers reviewing how governance influences inspection outcomes may find the adult social care inspection quality and governance resource hub particularly helpful.

Why complaints readiness matters during registration

Complaints handling is often presented as an administrative function, but CQC is likely to view it as a test of leadership, culture and responsiveness. A provider that cannot explain how concerns move from first contact to recorded action may appear under-prepared even if a formal complaints policy is in place. Strong registration readiness means showing how the service will distinguish low-level concern from formal complaint, how timescales are managed, who reviews responses and how learning is embedded.

This is particularly important for new services, because early complaints often expose weaknesses in communication, consistency, staffing and expectations. A provider that can evidence a clear response pathway from day one is better placed to demonstrate openness, accountability and continuous improvement.

What effective complaints and feedback readiness looks like

Effective readiness means the provider can show how verbal concerns, written complaints, compliments, surveys and informal feedback are all captured and reviewed proportionately. It also means leaders can evidence how the organisation responds where people have experienced avoidable harm, poor communication or service failure. Duty of candour should not sit outside this process; it should connect directly to incident review, apology, explanation and improvement.

Operational example 1: receiving and escalating a complaint safely and consistently

Context: A new domiciliary care provider needed to evidence that concerns raised by people using the service or families would be handled consistently across office staff, coordinators and managers. The baseline challenge was showing that complaints would not be lost in informal communication or treated differently depending on who received them.

Support approach: The provider created a structured complaint intake and escalation process because registration readiness depends on demonstrating consistent handling at the first point of contact. The aim was to ensure all concerns were recorded, categorised and reviewed appropriately.

Step-by-step delivery:

• Step 1: When a complaint or significant concern is received by phone, email or in person, the receiving staff member records the date, complainant details, issue raised, immediate risk level and preferred response route in the complaints intake form on the same working day.
• Step 2: The office coordinator reviews the intake form within the same working day, records whether the matter is an informal concern, formal complaint or safeguarding-linked issue and logs the classification decision in the complaints tracker.
• Step 3: If the matter involves immediate risk, repeated service failure or potential harm, the coordinator escalates it to the Registered Manager immediately, recording the escalation reason, time and interim action in the escalation section of the tracker.
• Step 4: The Registered Manager reviews the complaint within 24 hours, records the investigation lead, response deadline, required evidence sources and whether duty of candour or safeguarding processes must also be activated.
• Step 5: The complaint is then tracked through investigation and response, with each contact, action and timescale update recorded in the complaints log so the provider can evidence continuity, openness and closure.

What can go wrong: Concerns may be handled informally without record, leaving the provider unable to evidence patterns, timescales or whether the issue was resolved properly.

Early warning signs: Repeated verbal complaints with no tracker entry, unclear classification between concern and complaint, or office staff escalating issues inconsistently.

Governance: The Registered Manager reviews the complaints tracker weekly and samples classification decisions monthly. Any complaint with missed response timescale or unclear categorisation is escalated through governance review.

Outcomes: Effectiveness is evidenced through full same-day logging of complaints, improved response timeliness and clearer audit trails showing how concerns moved into action. Evidence is triangulated through intake forms, complaint logs, escalation records and governance review notes.

Operational example 2: investigating complaints and meeting duty of candour expectations

Context: A supported living provider needed to evidence how it would respond when a complaint involved avoidable distress, poor communication or possible service failure. The baseline issue was demonstrating that apology, explanation and improvement would be structured rather than ad hoc.

Support approach: The provider linked complaint investigation to duty of candour because open communication is a core part of regulatory credibility. The aim was to show that the service could investigate fairly, respond transparently and record learning.

Step-by-step delivery:

• Step 1: Once the complaint is allocated, the investigating manager gathers care notes, call records, medication records, staff statements or communication logs as required, recording all evidence sources and dates requested in the investigation record.
• Step 2: The investigating manager interviews relevant staff and, where appropriate, the person affected or their representative, recording factual accounts, discrepancies and any immediate remedial action in the complaint investigation template.
• Step 3: If the complaint identifies avoidable harm, distress or a notifiable service failure, the Registered Manager records whether duty of candour applies, what apology has been offered, what explanation is available and what further communication is required.
• Step 4: The written response is drafted within the recorded timescale, setting out the issue raised, findings, apology where required, action taken and review route, with the final approved response saved in the complaint closure file.
• Step 5: The Registered Manager reviews whether the promised actions were completed, records closure evidence in the complaints and action tracker and escalates unresolved or disputed matters to provider leadership where necessary.

What can go wrong: Providers may respond defensively, apologise without investigating properly or investigate without linking findings to candour obligations and service change.

Early warning signs: Delayed responses, responses that describe events without findings, or repeated complaints about communication and lack of openness.

Governance: All complaints involving harm, missed care, medicines or safeguarding themes are reviewed monthly by the Registered Manager and quarterly by provider leadership. Any case with incomplete duty of candour documentation is treated as a governance concern.

Outcomes: Effectiveness is measured through improved response quality, completion of promised actions and reduced repeat complaints on the same theme. Evidence is triangulated through response letters, action logs, complainant feedback and governance minutes.

Operational example 3: turning feedback and complaint themes into service improvement

Context: A residential care provider preparing to register wanted to show how routine feedback, compliments and complaints would feed into governance rather than sit in separate systems. The baseline challenge was evidencing learning, not just response.

Support approach: The provider integrated complaints and feedback into quality assurance because registration readiness requires proof that the service learns from what people say, not just that it replies to them.

Step-by-step delivery:

• Step 1: The administrator collates weekly feedback, complaints and compliments, recording source, issue type, service area, timescale performance and sentiment in the feedback and complaints dashboard.
• Step 2: The Registered Manager reviews the dashboard weekly, records emerging themes such as communication delay, missed call timing or staff attitude and notes whether the pattern is isolated or systemic in the governance summary.
• Step 3: Where a theme is confirmed, the Registered Manager opens a quality improvement action, records the root issue, named owner, deadline, expected outcome and measurement method in the action tracker.
• Step 4: Managers implement the agreed change, such as updated communication standards, rota review, staff briefing or supervision focus, and record completion evidence in supervision records, briefing logs or audit files.
• Step 5: At the next monthly governance meeting, leaders compare the new feedback and complaint trend data to baseline, record whether improvement is evidenced and either close, extend or escalate the action depending on results.

What can go wrong: Feedback may be collected but treated as anecdotal, preventing leaders from identifying themes early and weakening assurance that the service is learning.

Early warning signs: Repeated low-level dissatisfaction, compliment and complaint themes never discussed in governance, or actions closed without measurable review.

Governance: Weekly dashboard review, monthly complaints-theme analysis and quarterly provider oversight of unresolved or repeated service concerns.

Outcomes: Effectiveness is evidenced through faster response times, reduced repeat complaint themes and improved satisfaction feedback after action plans are implemented. Evidence is triangulated through dashboards, action logs, survey returns and governance review records.

Commissioner expectation

Commissioner expectation: Commissioners will expect providers to demonstrate that complaints and feedback systems are open, timely and capable of driving service improvement. They are likely to look for evidence that concerns are not minimised and that recurring themes are acted on at management level.

Regulator / Inspector expectation

Regulator / Inspector expectation: CQC is likely to test whether complaints handling is consistent, transparent and linked to learning. Inspectors may compare logs, response letters, duty of candour records, action trackers and governance minutes to assess whether the service is genuinely responsive.

Governance and oversight

Strong complaints readiness should include same-day recording, clear classification, response timescales, complaint investigation templates, duty of candour decision routes and governance review of themes and closure evidence. The Registered Manager should be able to show how concerns become actions and how actions are checked for impact. That is what turns a complaints policy into an operational assurance system.

Conclusion

Complaints handling, feedback systems and duty of candour readiness are evidenced through clear intake, structured investigation, transparent communication and measurable learning. Providers must show that concerns are recorded consistently, reviewed proportionately and translated into operational change where needed. A Registered Manager should be able to demonstrate to CQC how complaint information is tracked, how openness is maintained and how recurring themes are escalated and resolved through governance. When response systems, managerial oversight and improvement actions are aligned, complaints handling becomes a strong indicator of provider readiness rather than a risk point at registration.

---