How to Run Restrictive Practice Review Meetings That Drive Reduction

Restrictive practice review meetings can either become a repetitive “log review” or a genuine reduction engine that changes day-to-day practice. The difference is structure, clarity of purpose and the discipline to turn information into decisions. Within Restrictive Practice Reduction, Review & Governance, and consistent with PBS Principles & Values, this article sets out a practical approach to running restrictive practice reviews that stand up to scrutiny and drive measurable reduction.

What a restrictive practice review meeting is for

A high-quality review meeting should do four things every time:

• Confirm what restrictions are in place (and whether they remain necessary and proportionate).
• Test whether least restrictive options are being used in day-to-day delivery.
• Set actions with ownership (who will change what, by when, and how it will be checked).
• Evidence learning and improvement (what changed since the last review and what the data shows now).

If the meeting cannot show change over time, it is not functioning as governance.

Preparation: what must be brought to the meeting

Reviews fail when people turn up with partial information. Minimum inputs should include:

• A restriction register (current restrictions by person, type, rationale, and review date).
• Incident/ABC summaries linked to restrictions (not just counts).
• PBS plan status (current version, last review, outstanding actions).
• Training and competency risks (who is new, who needs coaching, who has not been signed off).
• Safeguarding and complaints links (any themes where restriction may be a factor).

Bring “real evidence,” not just narrative: sample daily notes, observation findings, and examples of how staff applied proactive strategies.

A workable agenda that drives decisions

A consistent agenda stops drift and ensures repeatable governance:

• 1) Trend review: restrictions and restrictive interventions over time, with context.
• 2) Person-level reviews: highest restriction, highest risk, or longest duration cases first.
• 3) Proportionality test: necessity, least restrictive options tried, and review schedule.
• 4) Actions: changes to practice, environment, staffing, routines, or PBS plans.
• 5) Assurance: how actions will be monitored (observation, audit, competency sign-off).

Operational Example 1: Turning a monthly review into measurable reduction

Context: A supported living service held a monthly “restraint and restrictions” meeting, but minutes showed repeated discussion with limited change. One person had ongoing restrictions around leaving the property and staff were also using reactive holds during community access.

Support approach: The Registered Manager introduced a structured panel format: restriction register first, then proportionality testing, then action-setting with specific monitoring.

Day-to-day delivery detail: The team brought three recent incident timelines and ABC summaries to the meeting. They identified that escalation was occurring at predictable points: transitions to the car, waiting in queues, and when staff changed plans without warning. Actions included rewriting the community routine (shorter trips, predictable “exit plans”), updating the visual schedule, and changing staffing so a consistent key worker supported community access for two weeks. The PBS practitioner set a two-week observation schedule and managers committed to two unannounced practice observations focusing on early de-escalation and staff language.

How effectiveness or change is evidenced: The next meeting reviewed observation findings and incident data: fewer escalation points, fewer reactive holds, and improved time-in-community without restrictions. The restriction register was updated with a planned step-down and a clear review date.

Making proportionality explicit, not implied

Every restriction discussed should be tested against practical questions:

• What harm is being prevented, and what is the evidence of that risk?
• What less restrictive options have been tried in real conditions (not in theory)?
• Is the restriction time-limited with a step-down plan?
• How do staff apply it day-to-day, and how is drift prevented?

Minutes should reflect this logic. If it is not written down, it is difficult to evidence later.

Operational Example 2: Review meeting identifies restrictive practice drift

Context: In a residential service, door sensors and staff shadowing were introduced during a period of high incidents. Months later, the measures remained in place, but the original triggers had reduced.

Support approach: The governance lead required the review meeting to include a “restriction age” check: how long restrictions had been in place and whether they still matched current risk.

Day-to-day delivery detail: The team sampled daily notes for the previous two weeks and found the person was requesting independent time in the garden with no incidents. Staff were keeping the sensor “because it’s easier.” The panel agreed a step-down plan: sensor used only at night for one week while staff introduced a supported “check-in routine,” then removed completely if no issues arose. The manager scheduled three spot checks to confirm the step-down was happening and that staff were not reintroducing control through constant monitoring.

How effectiveness or change is evidenced: The restriction register recorded the step-down and the rationale. Follow-up checks confirmed removal, and the person’s outcomes were recorded as increased autonomy and reduced distress.

Explicit expectations you must design for

Commissioner expectation

Commissioners expect robust oversight and timely reduction. They will look for a clear review cycle, documented rationale, step-down planning, and evidence that restrictions reduce as staff capability and proactive support improve.

Regulator / Inspector expectation (CQC)

CQC expects governance, learning and least restrictive practice. Inspectors will test whether restrictions are reviewed, proportionate, and understood by staff, and whether leaders can evidence action and improvement rather than relying on policy statements.

Operational Example 3: Linking safeguarding and review meetings without creating panic

Context: A safeguarding enquiry raised concerns that a restriction (limiting community access following incidents) was being applied too broadly and without clear review.

Support approach: The provider used the restrictive practice review meeting as the operational control point: one place where the restriction was tested, time-limited, and governed.

Day-to-day delivery detail: The panel reviewed incident narratives and found the main driver was staff uncertainty in busy environments. Instead of blanket limits, the plan introduced staged community exposure, pre-visit planning, and a de-escalation “exit routine.” The service added a requirement that any restriction on community access must include: clear criteria, a maximum duration, and review within seven days. Managers completed two joint shifts to coach staff through proactive strategies and recorded competence in supervision notes.

How effectiveness or change is evidenced: The provider could demonstrate to stakeholders: the restriction was temporary, alternatives were implemented, staff capability increased, and community access resumed with reduced incident severity.

Minutes and actions that stand up to scrutiny

Strong minutes show:

• What was reviewed (data and evidence).
• What decisions were made (including proportionality and step-down logic).
• Who owns actions and the timescale.
• How implementation will be checked (observations, audits, competency sign-off).
• What changed since the last review (trend evidence, not just statements).

This is what turns a meeting into governance and supports continuous reduction rather than reactive defence.

---