Regulation 13: Safeguarding service users from abuse and improper treatment

Reg 13(1) sets the principle: service users must be protected from abuse and improper treatment. Reg 13(2) requires the provider to establish and operate effective systems to prevent abuse. Reg 13(3) requires effective systems to investigate, immediately upon becoming aware of, any allegation or evidence of abuse. Reg 13(4) sets out the operational standards: care must not be provided in a way that includes acts intended to control or restrain a service user disproportionately, that is discriminatory, that includes degrading treatment, or that significantly disregards the service user's needs.

Reg 13(5) prohibits any deprivation of liberty for the purpose of receiving care or treatment without lawful authority. The lawful-authority route is the Deprivation of Liberty Safeguards (DoLS) under Schedule A1 of the Mental Capacity Act 2005 for care-home and hospital settings; the Court of Protection route for other settings. The DoLS regime is being replaced by Liberty Protection Safeguards (LPS); LPS implementation remains deferred at the page review date and DoLS remains in force.

CQC expects providers to have a named safeguarding lead, a clear written policy that staff can find and follow, training appropriate to role (Level 1 for any staff with service-user contact, Level 2 for clinical and direct-care staff, Level 3 for the named lead), and a working route from concern to local-authority referral to outcome to closure. The provider does not decide whether a Section 42 enquiry should run; the provider refers concerns that may meet the s42 threshold and the local authority decides. The provider's job is the threshold reasoning at log-time, the referral submission through the LA channel, the outcome capture, the change-to-practice that follows.

Inspectors do not expect zero safeguarding concerns in a complex service. Presence of concerns on the register is read as recognition operating; the inspector reads the response pattern (threshold reasoning, referral timeliness, outcome capture, aggregate themes) for the well-led signal.

The Reg 13 patterns that recurred across thirteen years of CQC inspections: threshold reasoning recorded after the fact, with the audit trail showing the reasoning paragraph dated weeks after the concern was logged; the referral submitted but the local-authority outcome letter never attached, so the concern sits indefinitely in the LA-referred state; no record of a staff-allegation fork where one was needed, leaving the LADO referral or the equivalent adult-allegation process undocumented; closure with “no further action required” and no learning recorded; and the aggregate-pattern miss, where three concerns in six months at the same site about the same staff team never surfaced as a well-led concern because no one was reading the aggregate. Each of these is a Reg 13 finding on its own; the aggregate pattern is the culture finding that drives ratings on the well-led key question.

Verivius drives this regulation through the safeguarding-reporting lifecycle. Threshold reasoning is captured at log-time. The local-authority referral track runs as a sub-lifecycle with deadline visibility. The staff-allegation fork opens as a parallel record so the two response processes stay distinct. Aggregate patterns surface on the quarterly safeguarding view at the governance meeting.

Sample policy template: Reg 13 Safeguarding from abuse. Companion lifecycle marketing page: safeguarding reporting.