Duty of Candour in Practice: Linking Openness, CQC Notifications and Governance Evidence

Duty of Candour is where values and regulation meet. In practice, providers must act quickly, communicate clearly and keep an accurate audit trail when something goes wrong. CQC does not assess candour as a one-off apology; inspectors look for a repeatable process that links incident response, notification decisions, safeguarding and learning. This article forms part of Notifications, Statutory Reporting & Duty of Candour and shows how candour evidence is best organised against the CQC Quality Statements & Assessment Framework so managers can defend decisions confidently.

For consistent compliance processes, the CQC compliance and quality management knowledge hub provides a useful framework.

What “good candour” looks like under inspection

In strong services, candour is visible in three places at once:

• Front-line practice: prompt, compassionate communication with the person and those important to them.
• Records: clear notes of what happened, what was said, by whom, when, and what follow-up was agreed.
• Governance: oversight that checks consistency, learning and whether the same issues repeat.

Where providers struggle, it is usually because candour is treated as a “conversation” rather than a structured pathway with defined steps, triggers and sign-off.

Building a candour pathway that stands up to challenge

A defensible pathway typically includes:

• Trigger thresholds: what types of harm or near-miss trigger candour review (not only “serious harm”).
• Initial contact standard: when and how the person/family is contacted (including out-of-hours scenarios).
• Written follow-up: what is confirmed in writing, and how the provider records agreement or disagreement.
• Link to notifications: a clear decision record showing if a CQC notification was required and why.
• Learning loop: how review findings become actions, tracked to completion.

This pathway must be usable on a busy day: short prompts, templates, and a central tracker matter more than long policy wording.

How candour links to CQC notifications without becoming a tick-box

Candour and notifications are related but not identical. Providers should avoid two common errors:

• Conflating the two: assuming that notifying CQC is “doing candour”. It is not.
• Separating them completely: treating candour as a purely local conversation with no governance trace.

The most defensible approach is a single incident file (digital or physical) that contains: incident report, immediate actions, safeguarding decision, notification decision record, candour log, review findings and improvement actions.

Operational example 1: medication omission with hospital admission

Context: A medication is omitted due to a transcription error. The person deteriorates and is admitted to hospital. The family are upset and allege poor management.

Support approach: The service escalates clinically, secures medicines records, informs safeguarding where appropriate, and initiates candour steps alongside notification review.

Day-to-day delivery detail: The manager completes an immediate candour call the same day, documents what is known, what is being investigated, and agrees a follow-up time. A written summary is sent and logged. The incident file includes a clear notification decision record and a medicines review timeline (MAR, pharmacy queries, staff statements). Staff involved receive debrief and reflective supervision focusing on accuracy and checking processes.

How effectiveness is evidenced: The provider audits transcription and secondary-check compliance over the next eight weeks, demonstrates improved accuracy, and evidences learning via updated prompts in the medicines process and competency refreshers.

Operational example 2: unexplained bruising and safeguarding escalation

Context: A person is found with unexplained bruising. The family raise concerns about handling and supervision.

Support approach: Immediate safeguarding referral and risk review occur. The provider begins candour communication while facts are uncertain.

Day-to-day delivery detail: Staff record body maps, observations and the person’s account using accessible communication where needed. The manager contacts the family to explain actions being taken, makes clear what is not yet known, and agrees how updates will be provided. The candour log is updated after each contact. The provider documents staffing levels, observations schedules and relevant CCTV/entry data where applicable and lawful.

How effectiveness is evidenced: Outcomes are evidenced through safeguarding feedback, internal audit of recording quality (body maps, observations, escalation), and reduction in repeat “unexplained injury” incidents following targeted training and supervision checks.

Operational example 3: restrictive intervention incident with staff injury and complaints

Context: During an episode of severe distress, restrictive intervention is used. The person sustains a minor injury and staff also report injury. The person’s advocate submits a complaint alleging excessive force.

Support approach: The service takes immediate steps to ensure safety, reviews PBS guidance, and implements candour steps with the person/advocate while initiating a governance review.

Day-to-day delivery detail: The manager documents a clear timeline: antecedents, de-escalation attempts, decision to use restrictive intervention, post-incident health checks, and the complaint handling pathway. Candour communication focuses on what happened, why, and what review will occur, with clear dates for feedback. The provider checks staff training currency, competency sign-off and supervision records for the techniques used.

How effectiveness is evidenced: Evidence includes a reduction in restrictive intervention frequency, improved de-escalation planning documented in support plans, and audit outcomes showing staff competency checks are completed on schedule.

Governance and assurance mechanisms that inspectors recognise

To avoid candour becoming inconsistent across teams, providers typically use:

• a candour/notifications tracker with dates for contact, written follow-up, review completion and actions
• weekly incident review huddles where thresholds and decision rationale are checked
• monthly governance review focusing on themes, repeat issues and overdue actions
• quality sampling of candour records for tone, clarity and completeness

These controls turn “good intentions” into evidence.

Commissioner expectation

Commissioner expectation: Commissioners expect openness and early escalation, with a documented rationale and evidence that learning is embedded. They want assurance that incident handling reduces recurrence and supports safe care across contracts.

Regulator / Inspector expectation (CQC)

Regulator / Inspector expectation (CQC): Inspectors expect a clear, timely candour pathway, accurate documentation of communication, and evidence that the provider learned and improved. They also expect managers to explain thresholds and decisions consistently.

Keeping candour human while staying audit-ready

Candour should never feel like legal compliance performed at families. The strongest providers combine compassion with clarity: a consistent pathway, plain-English communication, and records that demonstrate accountability and learning.

---