Reviewing Restrictive Practice: How to Evidence Necessity, Proportionality and Reduction

Restrictive practice reviews are often completed routinely but without real challenge. Forms are updated, rationales repeated, and restrictions continue unchanged. Within Restrictive Practice Reduction, Review & Governance and anchored in PBS Principles & Values, this article sets out how restrictive practice reviews should operate as a mechanism for reduction, not reassurance, and how providers can evidence this to commissioners and inspectors.

Why many restrictive practice reviews fail

Common failure points include:

  • Reviews that restate risk without testing alternatives.
  • Over-reliance on historical incidents.
  • Lack of clear reduction goals.
  • No follow-up on agreed actions.

When reviews become procedural, restrictive practices persist by default.

What a meaningful restrictive practice review must test

Every review should explicitly consider:

  • Necessity: Is this restriction still required today?
  • Proportionality: Is it the least restrictive option available?
  • Alternatives: What proactive supports could replace or reduce it?
  • Impact: How does the restriction affect quality of life?

These questions must be answered with current evidence, not assumptions.

Operational Example 1: Challenging long-standing environmental restrictions

Context: A service maintained locked internal doors due to historical absconding risk.

Support approach: PBS plans had evolved, but environmental controls had not been revisited.

Day-to-day delivery detail: A restrictive practice review included recent incident data, observed behaviour patterns, and trial periods of supervised access. Staff were coached to support gradual change rather than default control.

How effectiveness or change is evidenced: Doors were unlocked during defined periods, no increase in risk occurred, and quality of life indicators improved. Reviews documented clear reduction decisions.

Embedding review outcomes into practice

Reviews only matter if outcomes are implemented. Providers should ensure:

  • Actions are assigned with timescales.
  • Staff are briefed and coached on changes.
  • Follow-up reviews test whether change occurred.

Operational Example 2: Reducing medication-based restriction through review

Context: PRN medication was used frequently during periods of distress.

Support approach: PBS plans emphasised proactive sensory regulation.

Day-to-day delivery detail: Reviews compared PRN use with delivery of proactive supports. Gaps were identified and addressed through supervision and routine changes.

How effectiveness or change is evidenced: PRN use declined, and records showed increased proactive support delivery.

Explicit expectations you must design for

Commissioner expectation

Commissioners expect restrictive practice reviews to lead to reduction. They look for evidence of challenge, alternatives tested, and measurable change rather than repeated justification.

Regulator / Inspector expectation (CQC)

CQC expects restrictions to be regularly reviewed and reduced. Inspectors assess whether reviews meaningfully consider rights, choice and proportionality.

Operational Example 3: Using review evidence during inspection

Context: A service faced inspection following safeguarding concerns.

Support approach: Restrictive practice reviews were collated with outcomes.

Day-to-day delivery detail: Leaders presented review timelines, action completion evidence and reduction data.

How effectiveness or change is evidenced: Inspectors noted clear oversight and learning, reducing regulatory concern.

What good review practice demonstrates

High-quality reviews show:

  • Active challenge.
  • Evidence-based decisions.
  • Ongoing reduction.

This positions restrictive practice review as a core assurance process.