Sample policy · Reg 20

Duty of candour policy template

Statutory anchor: Regulation 20 (duty of candour), Health and Social Care Act 2008 (Regulated Activities) Regulations 2014 (SI 2014/2936). This policy also engages Regulation 12 (safe care and treatment) and Regulation 17 (good governance), and sits alongside Regulation 16 of the Care Quality Commission (Registration) Regulations 2009 (notification of death) and the other statutory notifications. · primary source

Download the PDF

The PDF version of this template is the same content, formatted for adaptation in your document control system. The disclaimer above is repeated on the PDF cover.

Verivius pack version v1, 2026-06-10

1. What the regulation says

As soon as reasonably practicable after becoming aware that a notifiable safety incident has occurred a registered person must notify the relevant person...

The notification... must include an apology.

The notification given under paragraph (2)(a) must be followed by a written notification given or sent to the relevant person...

harm that requires a moderate increase in treatment, and significant, but not permanent, harm.

a permanent lessening of bodily, sensory, motor, physiologic or intellectual functions, including removal of the wrong limb or organ or brain damage, that is related directly to the incident and not related to the natural course of the service user's illness or underlying condition.

an expression of sorrow or regret in respect of a notifiable safety incident.

The full text of the regulation is at https://www.legislation.gov.uk/uksi/2014/2936/regulation/20. Where this policy and the regulation diverge, the regulation wins.

A notifiable safety incident is a specific legal term, and the threshold that triggers the duty differs by provider type. Regulation 20 sets one definition for health service bodies and a separate definition for other registered persons. The service must apply the correct Regulation 20 definition for its own provider type, and must not assume that the wording used by another type of provider applies to it.

2. Plain-English summary

When something goes wrong that meets the Regulation 20 notifiable safety incident threshold for your provider type, you must tell the relevant person (the patient, or the person acting on their behalf) in person as soon as reasonably practicable, give a truthful account, offer support, apologise, and follow up in writing. The threshold itself differs by provider type: Regulation 20 sets one notifiable safety incident definition for health service bodies and a separate definition for all other registered providers, so the service must apply the correct definition for its own type rather than assume another provider type's wording applies. The regulation does not set a number-of-days deadline for the written stage; any specific deadline you see in Verivius is an operational default, not a legal duty.

Regulation 20 is the duty to the patient. It sits alongside the duty to notify the regulator under the Care Quality Commission (Registration) Regulations 2009 (for example, notification of death under Regulation 16), but it is a separate obligation. Honouring one does not satisfy the other.

3. Scope

This policy applies to all clinical and care staff at , every regulated activity the provider is registered for, every service-user pathway, and every incident that meets the Regulation 20 notifiable safety incident threshold for the service's provider type. It applies regardless of whether the incident was preventable; the regulation is triggered by the harm threshold, not by blame.

(Tenant updates the angle-bracket placeholder.)

4. Roles and responsibilities

(Tenant updates the named role-holders.)

5. Procedure

The duty-of-candour procedure operationalises Regulation 20 across the lifecycle from harm identification to written-notification closure. It runs as a sub-lifecycle inside the source incident record in Verivius.

  1. Harm assessment at incident logging. Every incident's initial harm assessment is reviewed against the Regulation 20 threshold for the service's provider type. The harm categories and threshold must be checked against the current Regulation 20 wording before opening or declining the duty-of-candour lifecycle. The triage decision is recorded on the incident.
  2. Open the duty-of-candour panel. Where the threshold is met, the candour panel opens on the source incident. The deadline clock starts ("as soon as reasonably practicable" in the regulation; the tenant SLA layer sets the operational target).
  3. Identify the relevant person. The patient is the default. Where the patient cannot consent or is bereaved, the relevant person is identified per Regulation 20(6): a person lawfully acting on the patient's behalf, the bereaved family per the priority list.
  4. Verbal notification. A face-to-face conversation (where reasonably practicable) or a phone call (where face-to-face is not). The conversation captures: an accurate factual account of what happened so far as known at the time, what further enquiries the provider considers appropriate, the apology, the offer of support. The conversation is recorded on the candour panel with date, time, attendees, location, summary of what was said. The apology is not "we are sorry that you feel"; it is "we are sorry that this happened".
  5. Written follow-up. A written notification follows the verbal as soon as reasonably practicable. The written must contain the matters discussed verbally, the results of further enquiries (or a statement that they are ongoing), an apology, the steps the provider is taking. The letter is drafted, reviewed (typically by the Registered Manager), sent through a channel the recipient has agreed (post, email, in-person hand-over).
  6. Record evidence of sending. The written notification is attached to the candour record (an email confirmation, a printed-letter scan with date stamp, a hand-over signature). The send timestamp and the sending user are captured.
  7. Track outcomes. Where the relevant person responds, the response is recorded against the candour record. Where further enquiries produce new information after the initial written, a supplementary written notification is sent.
  8. Closure. The candour record closes when the duty has been honoured end-to-end (verbal done; written sent; any outcome captured). The closure paragraph names what was done and the closing user.
  9. Cross-link to the statutory notification. Many Regulation 20 incidents also meet a statutory-notification trigger under the Care Quality Commission (Registration) Regulations 2009 (for example, notification of death under Regulation 16). The two records are linked but run their own lifecycles. The Registration Regulations notification does not satisfy Regulation 20 and vice versa.
  10. Pattern review. The aggregate candour pattern (count, harm-distribution, time-from-incident-to-verbal, written-letter quality) is reviewed at the monthly governance meeting.

6. Training requirement

Training records are held in the tenant's training matrix register.

7. Audit

Compliance with this policy is monitored by the Registered Manager:

Audit findings recorded in the tenant's audit register; actions logged in the improvement-actions register.

8. Record-keeping

Duty-of-candour records (sub-lifecycle inside the source incident) are held for a minimum of 8 years from the date of the last entry, aligned to the NHS Code of Practice on Records Management and the related clinical record. Written-notification copies and any reply correspondence are attached to the candour record and travel with it.

Verivius preserves the per-record audit trail indefinitely while the workspace is active.

9. Related policies in this pack

10. Sources and further reading

This template is based on CQC's guidance for providers and managers, the Health and Social Care Act 2008 (Regulated Activities) Regulations 2014, and other topic-specific legislation and guidance listed below. It is a starting point for adaptation, not a substitute for legal, clinical, HR, safeguarding or specialist professional advice.

11. When to seek further advice

Seek specialist advice where the issue involves serious harm, safeguarding, deprivation of liberty, restraint, children, professional misconduct, controlled drugs, radiation, termination of pregnancy, infection outbreak, water safety, employment dismissal, DBS barring referral, or regulatory enforcement.

12. Document control

Version Date Author Changes
v1 2026-05-19 Verivius (sample) Initial sample template.
v1.1 2026-06-01 Verivius (sample) Filled out Sections 3 to 8 with concrete content. Section 4 names the typical role allocation (Registered Manager sign-off, Clinical Lead in-the-room responsibility, Designated Candour Drafter). Section 5 expanded to a 10-step lifecycle (harm assessment, panel open, identify relevant person, verbal notification, written follow-up, evidence of sending, outcome tracking, closure, statutory-notification cross-link, pattern review) tied to the platform's candour sub-lifecycle on incidents. Section 6 names the training tiers (awareness for all clinical staff, delivery training for the Manager + Clinical Lead + Drafter, apology-language training). Section 7 names the per-incident sign-off audit and the quarterly candour-record review. Section 8 references the NHS Code of Practice.
v1 (2026-06-10) 2026-06-10 Verivius (sample) Re-conformed to the current Verivius policy standard, preserving the original content. Restored the original verbatim Regulation 20 quotes in Section 1 exactly as first issued; added the provider-type clarification that the notifiable safety incident threshold differs by provider type and the service must apply the correct Regulation 20 definition for its own type; corrected the Section 2 summary so it applies the provider-type threshold consistently rather than stating "moderate harm or worse" as a universal trigger; added the header policy owner / applies-to line, the Sources and further reading section, and the When to seek further advice block.

This sample policy template was issued by Verivius. It is a template, not a substitute for legal advice or the tenant's own policy-development process. Where this template and live law or regulator guidance diverge, the live source wins.

What a CQC inspector checks

The same requirement seen through an ex-CQC-inspector's eyes: what they actually ask to see, and the gap they are testing for.

  1. How you decided which incidents crossed the Regulation 20 notifiable-safety-incident threshold for your provider type: a defined statutory bar (moderate or severe harm, death, or prolonged pain or psychological harm), tested per incident, including the ones ruled out.

    Evidence: The threshold decision recorded on the incident with the provider-type definition and the legal source checked, and the not-opened decisions explaining why the threshold was not met.

  2. For a sampled above-threshold incident, the verbal notification: when it happened, who was present, and the exact apology wording.

    Evidence: A conversation note recording that it was done as soon as reasonably practicable, the attendees, and a genuine apology captured in the record (an expression of sorrow or regret, not "sorry you feel").

  3. The written follow-up for that incident, and proof it was actually sent, not just drafted.

    Evidence: The written notification that reflects the conversation and includes an apology, with the evidence of sending stored.

  4. How the relevant person was identified where the service user had died, was under 16 and not competent, or lacked capacity, with the authority recorded.

    Evidence: The relevant-person identification note with the capacity or bereavement and representative-status record.

  5. That the Regulation 20 duty is discharged to the person and is not itself a CQC notification; where the same incident is separately notifiable, that notification is opened or ruled out as its own record.

    Evidence: The separate CQC statutory-notification record and decision (under the CQC Registration Regulations), cross-linked to but distinct from the candour record.

  6. That openness with the person is the norm for any safety incident affecting them, not reserved for the high Regulation 20 threshold; a service candid only at the statutory line reads as a well-led and person-centred concern.

    Evidence: A lower-harm incident where the person was still told what happened and offered an apology, recorded alongside the Regulation 20 cases.

Audit this policy

Duty of candour procedure checklist

A policy is the intent; the evidence is what a CQC inspector actually asks to see. This matching checklist turns the policy above into the records to keep, the audit to run, and the places small services most often fall short.

Open the Duty of candour procedure checklist

Related Verivius content

Want help adapting this to your service?

A Verivius consultant can read your adapted policy against the live regulation and your service shape. The work fits inside a Mock Inspection engagement or a shorter consulting brief. A 20-minute conversation is the fastest way to find out whether the fit is right.

Get started free

Free to start, no card. A 14-day trial when you subscribe.

Last reviewed 10 June 2026