Lifecycle
Complaints management for CQC-regulated providers
What a CQC inspector actually reads in a complaint is the trail: when it was received and acknowledged, how far the investigation reached, whether the response answered the real concern, and what changed in the service afterwards. Regulation 16 of the Regulated Activities Regulations 2014 sets that duty across every CQC-registered service; the NHS Complaints Regulations 2009 add a statutory acknowledgement-and-response timeline on NHS-funded episodes. This page covers what CQC expects and the records you need to evidence it.
Start with Regulation 16 in plain English, the complaints policy template, and the complaints handling checklist.
What the regulation expects
For private episodes, the legal anchor is Regulation 16 of the Health and Social Care Act 2008 (Regulated Activities) Regulations 2014: any complaint received about the carrying on of the regulated activity must be investigated and necessary and proportionate action taken in response. Reg 16 is non-prescriptive about the timeline. The 2009 Complaints Regulations set the NHS timeline (acknowledgement within three working days, response as soon as reasonably practicable) but do not apply to private-only providers.
For NHS-funded episodes at any provider, the 2009 Regulations apply: the three-working-day acknowledgement window and the structured response duty are statutory. Most independent providers receive a mix of private and NHS-funded episodes; Verivius tags funding source per complaint so the right timeline and response shape apply per record rather than tenant-wide.
The Reg 17 (good governance) reading layer sits above both. Patterns across complaints (theme tagging, severity grade, recurrence rate) feed into the well-led question inspectors ask about whether the service is learning from the complaints it receives, not just closing them individually.
What providers most often miss
Across the inspection portfolio Klaudiusz worked over thirteen years inside CQC, three complaint-trail gaps showed up repeatedly.
One: the acknowledgement clock starts later than it should. The complaint arrives by email or verbal on a Friday afternoon. The team takes it as received on the Monday. The three-working-day NHS clock (for NHS-funded episodes) already feels tight; starting it 72 hours late effectively halves the response window. The original receipt date and the formal log date need to be the same date, even if the substantive response takes longer.
Two: the response covers what happened but not what changed. The response letter rebuilds the timeline, acknowledges any errors, and apologises where warranted. What it often omits is the specific change to practice that followed. The complainant reads the letter, cannot see what the provider will do differently next time, and either escalates or simply does not trust the service. The follow-up complaint volume on the same theme is the leading indicator of this gap.
Three: the pattern view does not exist. Each complaint is investigated and closed in isolation. The quarterly question (are we seeing a theme on communication at discharge, or wait times in clinic, or consent quality in elective surgery?) does not get asked because the data lives in 15 separate file folders and a spreadsheet. Verivius surfaces the pattern view by default; the platform's job is to make the aggregate visible without a separate audit project.
What a CQC inspector looks for in complaint records
The standard CQC complaints sample is the provider's complaint log over the last twelve months plus the individual records for five to ten complaints chosen non-randomly. The chosen records are usually a mix of severity grades and a stratified pick of themes (clinical, communication, waiting times, billing) so the inspector reads across the spectrum.
The reading test on individual records: was the acknowledgement timely, did the investigation reach into the underlying clinical record where relevant, did the response address the complainant's actual concern (not a reformulation of it), and did the closure carry a named change to practice. Records that have all four read as evidence of working systems. Records that close on a generic apology and a procedural recap read as performative closure.
The aggregate test: across the twelve months, do the complaint themes converge with the incident themes, the safeguarding themes, and the staff supervision themes. A service where complaints surface a theme that incidents do not surface, or vice versa, is a service where one evidence channel is under-functioning. That cross-channel inconsistency is a Reg 17 well-led concern and the single biggest pattern CQC inspectors comment on in independent secondary care inspections.
For Health Service Ombudsman referrals (the next-stage escalation when an NHS-funded complaint is not resolved at provider level), the inspector reads the provider's response to the Ombudsman investigation alongside the original complaint closure. Significant divergence between the two suggests the original closure underplayed what actually happened.
How Verivius handles complaints
Verivius runs complaints as a closed lifecycle: log (with the original receipt date, not the formal log date), acknowledge, investigate, respond, close. The three-working-day NHS clock applies automatically when funding source is tagged as NHS-funded; private complaints carry the tenant's own operational SLA. The response letter is drafted against the record so the evidence cited is verifiable. The closure paragraph requires a specific change-to-practice entry; closure without it is a guarded step the platform makes deliberately visible. Aggregate views show quarterly theme patterns, severity mix, and recurrence rates so the well-led answer to a recurring theme is visible without a separate audit project. For the full feature walk-through see what Verivius actually does.
See also the Day-to-day use section on the FAQ for the short answers across every lifecycle.
Common questions on complaints management
Do the NHS Complaints Regulations apply to my private clinic?
Only for the episodes you deliver under NHS funding. A pure-private clinic that takes no NHS contract work is not subject to the 2009 Regulations on those private episodes; Reg 16 of the Regulated Activities Regulations 2014 still applies to every complaint. Mixed providers (private + NHS-funded) carry both regimes simultaneously on the relevant episode types. Verivius distinguishes funding source per complaint so the right rules apply per record.
How long should a complaint investigation actually take?
The NHS Regulations expect the response as soon as reasonably practicable and in any event no later than six months from the date of receipt of the complaint, with the complainant kept informed of progress in writing if the investigation runs longer than the initial response window. Reg 16 sets no statutory clock. Most providers aim for a substantive response within 20 to 25 working days and use the longer ceiling only for genuinely complex cases.
What if the complainant escalates to the Ombudsman or the Independent Sector Complaints Adjudication Service?
NHS-funded complaints escalate to the Parliamentary and Health Service Ombudsman. Private-paying clinic complaints in the independent healthcare sector typically escalate to the Independent Sector Complaints Adjudication Service (ISCAS) where the provider subscribes. The platform records the escalation route against the source complaint so the Ombudsman or ISCAS submission carries the verifiable evidence trail the original investigation produced.
Should every complaint be linked to a duty of candour conversation?
No. Duty of candour applies to notifiable safety incidents that meet the moderate-harm-or-above threshold under Reg 20, not to complaints as a category. A complaint that surfaces a notifiable safety incident may trigger both lifecycles simultaneously; the platform links the records so the two response trails stay visible without contaminating each other. Most complaints do not trigger duty of candour; the threshold is about clinical harm, not about complainant dissatisfaction.
How do we handle complaints that mention staff by name?
The complaint investigation focuses on what happened and what changes; staff names go into the investigation record but not the public-facing response letter unless the response specifically requires it. If the complaint alleges staff misconduct, the staff-allegation track opens in parallel (see the safeguarding-reporting page for the parallel-track pattern). The two tracks run separately so a complaint investigation does not prejudice or compromise the staff process.
Related sample policies
Verivius-authored templates that pair with this page. Verbatim statutory text plus plain-British summary and adoption sections; for adaptation, not adoption unchanged.
- Complaints policy template · Reg 16
- Service user guide template · Service user guide
See how the complaint lifecycle works inside Verivius
A 20-minute conversation walks through your service shape, your current complaint trail, and the Reg 16 patterns inspectors are most likely to sample in your sector. No demo deck. The founder logs into a demo workspace, walks through it, answers what you actually want answered.
Worth reading alongside: the incident-reporting page for how complaints and incidents interlock, the duty of candour page for how Reg 20 sits inside the complaint trail when a notifiable safety incident is involved.
Related sample policy template: Complaints handling (Reg 16).
Free to start, no card. A 14-day trial when you subscribe.
Last reviewed 14 July 2026