Duty of Candour in Practice: A Step-by-Step Operating Model for Regulated Care Providers

Duty of Candour becomes fragile when it is treated as a one-off apology letter rather than a managed process that starts at incident triage and ends with evidenced learning. In inspection and assurance, providers are expected to show not only that they understand the duty, but that they apply it consistently after harm, with clear records of who was contacted, what was explained, and what changed. This article sits within Notifications, Statutory Reporting & Duty of Candour and connects to how providers demonstrate openness and learning under CQC Quality Statements & Assessment Framework, using practical operational examples.

To better understand expectations around registration and monitoring, it helps to explore the CQC registration, monitoring and compliance hub.

What “good” Duty of Candour looks like operationally

At its best, Duty of Candour is visible in the way a service behaves after things go wrong: immediate safety actions, honest explanations, compassionate communication, and improvements that reduce recurrence. Operationally, it requires a repeatable model:

• Triage: identify whether the incident meets the harm threshold and whether Duty of Candour applies.
• Contact planning: decide who will speak with the person/family, when, and what information is known.
• Conversation: provide a factual explanation, acknowledge impact, and describe immediate actions.
• Written follow-up: confirm what was discussed, what will happen next, and how to raise questions or concerns.
• Learning loop: complete review, implement changes, and evidence effectiveness.

The biggest risk is inconsistency: two similar incidents handled in different ways because the manager on duty had a different personal style or confidence level. Standardising the process protects people and staff.

Build a Duty of Candour pathway that aligns with incident reporting

Duty of Candour should be triggered from your incident process, not bolted on later. Practical controls include:

1) A clear threshold test and a documented decision

For every incident meeting seriousness criteria, record: “Duty of Candour triggered: yes/no” with a short rationale and the name/role of the decision-maker. This prevents retrospective confusion and supports audit sampling.

2) A named “candour lead” for each incident

Assign one person accountable for the candour pathway (often the Registered Manager or delegated senior). Their job is to ensure contact happens, the record is complete, and learning actions are tracked to closure.

3) A standard contact and follow-up template

Use consistent prompts: what happened (facts), impact (known/unknown), immediate safety actions, next steps, how the person/family can ask questions, and what the provider will do to reduce recurrence. Consistency is not “robotic”; it ensures completeness.

4) Governance oversight and evidence capture

Build candour checks into monthly quality governance: a short register of candour-triggered incidents, with status (contact complete, written follow-up complete, review complete, actions implemented, effectiveness evidenced).

Operational example 1: fall with fracture and family concern about response times

Context: A person falls during a transfer and sustains a fracture. The family express concern that staff took too long to call an ambulance and that the care plan was not followed.

Support approach: Immediate clinical escalation occurs and the person is supported to hospital. The service initiates Duty of Candour and a rapid internal review of the transfer plan, moving and handling guidance, and response timeline.

Day-to-day delivery detail: The candour lead schedules an initial conversation within a defined window, using a simple timeline: time of fall, first aid actions, ambulance call time, and hospital transfer time. Staff involved provide factual statements, and the manager checks whether the hoist/transfer plan was available, current, and understood. The service introduces a “post-fall escalation checklist” in the office/on digital system so staff can follow consistent steps under pressure.

How effectiveness is evidenced: The provider documents the conversation, issues written follow-up confirming actions, and evidences improvement by auditing fall response records for the next period (e.g. 8 weeks), showing timely escalation and improved adherence to transfer plans.

Operational example 2: restraint-related injury and restrictive practice governance

Context: During an incident of distress, staff use physical intervention and the person sustains bruising. The person later reports feeling frightened and “held down”.

Support approach: The provider initiates safeguarding consideration, reviews whether intervention was planned/authorised, and triggers Duty of Candour due to harm and the person’s experience.

Day-to-day delivery detail: The manager gathers immediate evidence: incident notes, ABC context, antecedents, staff present, and de-escalation attempts used before intervention. The person is offered a calm, supported debrief using their preferred communication method and trusted staff. The service reviews whether the Positive Behaviour Support plan was current and whether staff were competent in de-escalation and least restrictive options, then updates training and introduces scenario-based reflective practice after restrictive incidents.

How effectiveness is evidenced: The provider tracks restrictive practice frequency and injury rates, records debrief completion, and shows updated PBS guidance and supervision records. The candour record demonstrates openness plus measurable reduction in restrictive incidents or improved prevention indicators (e.g. earlier de-escalation success).

Operational example 3: medication omission leading to deterioration

Context: A critical medicine dose is missed over multiple visits due to a documentation/rota interface error. The person deteriorates and requires urgent GP review.

Support approach: The service escalates clinically, completes medicines incident processes, and triggers Duty of Candour because avoidable harm occurred.

Day-to-day delivery detail: The candour lead explains the facts known (missed doses, how identified, immediate safeguards), acknowledges impact, and confirms how the provider will prevent recurrence. Operationally, the provider implements a “critical medicines verification” step for high-risk medicines: the incoming carer checks the previous administration record and flags any discrepancy to the on-call manager immediately. The rota system is reviewed so late changes do not remove competency-matched staff from critical calls without management approval.

How effectiveness is evidenced: Effectiveness is shown through medicines audit results, reduced missed-dose incidents, competency confirmations in supervision, and governance minutes evidencing changes and monitoring over time.

Commissioner expectation

Commissioner expectation: Commissioners typically expect providers to demonstrate a culture of openness with reliable follow-through: timely communication with people and families, clear written confirmation, and learning actions that reduce recurrence. They also expect candour processes to align with safeguarding, complaints handling, and serious incident review so messages are consistent and risks are controlled.

Regulator / Inspector expectation (CQC)

Regulator / Inspector expectation (CQC): Inspectors commonly look for evidence that the provider is open and transparent when things go wrong, that duty-triggered incidents are identified consistently, and that records show a complete pathway: contact made, written follow-up, review completed, and learning embedded. They also test whether staff understand the process in practice, not just in policy.

Practical assurance checks you can run monthly

• Sample recent serious incidents: is the “duty triggered” decision recorded with rationale?
• Do records show who spoke to the person/family, when, and what was explained?
• Is written follow-up present and consistent with the facts?
• Are learning actions time-bound, owned, and evidenced as effective?
• Can on-call managers describe the process confidently?

When candour is built into incident handling and governance, it becomes a predictable, compassionate operating model—strong for people, strong for staff, and robust under inspection.

---