Using Restrictive Practice Data to Drive PBS Reduction Plans

Restrictive practice data should help services understand whether support is becoming safer, more skilled and less intrusive. Within the Positive Behaviour Support knowledge hub, data is not treated as a reporting burden. It is part of understanding the person and improving daily support.

When providers use restrictive practice review evidence well, they can see whether restrictions are reducing, changing shape or becoming normalised. This must stay connected to PBS values in everyday support, so the service measures quality of life as well as incident frequency.

Concept explained clearly

Restrictive practice data is the recorded evidence about when, why and how restrictions are used. It may include physical interventions, locked access, increased observation, restricted community activity, staff-led decisions, environmental controls, medication used in response to distress, or any other limitation placed on a person’s ordinary freedom.

In PBS, the purpose of this data is not simply to count incidents. It is used to understand patterns, test hypotheses and guide reduction planning. The data should help teams ask practical questions: what happened before the restriction, what staff did, what the person may have been communicating, what alternative support was attempted, and what outcome followed.

Why it matters in real services

Without good data, restrictive practice can appear safer than it really is. A service may report fewer incidents because the person goes out less, has fewer choices or is supported in a more controlled way. That is not genuine progress. It may simply mean risk has been contained by reducing the person’s life.

Poor data also weakens decision-making. Staff may rely on memory, assumptions or emotional accounts of risk. Managers may approve restrictions without knowing whether they are still needed. Commissioners may question whether high levels of support remain justified. CQC may find that leaders cannot evidence how restrictions are monitored, reviewed and reduced.

What good looks like

Strong services demonstrate that restrictive practice data is accurate, timely and used. Records show the type of restriction, reason, duration, staff response, early signs, alternatives attempted and impact on the person. Data is reviewed alongside qualitative evidence, including the person’s views, family feedback, staff observations and changes in quality of life.

Good practice means the data leads to action. If restraint increases on late shifts, the rota, handover and staff approach are reviewed. If locked access is used more after cancelled activities, the activity planning system is changed. If community restrictions reduce incidents but also reduce independence, the plan is revised to rebuild safe access.

Operational Example 1: Identifying a pattern in evening restrictions

Context

A supported living service recorded increased use of locked kitchen access between 6pm and 8pm. Staff described the restriction as necessary because the person entered the kitchen repeatedly, opened cupboards and became distressed when asked to leave.

Support approach

The PBS lead reviewed three months of data and found that the restriction was most likely on evenings when the person’s preferred staff member was not working, meals were delayed or the person had limited afternoon activity. The behaviour was understood as communication of hunger, uncertainty and loss of routine.

Day-to-day delivery detail

The team introduced a visible evening plan, earlier snack options, a choice-based meal preparation routine and clearer handover about preferred foods. Staff were coached to offer structured access rather than block entry. The person was supported to prepare simple items with supervision, then gradually with less prompting.

How effectiveness was evidenced

Effectiveness was evidenced through reduced locked access, fewer distress episodes, increased participation in meal preparation and improved staff confidence. The data showed not only a reduction in restriction, but a change in what staff did before restriction became necessary.

Deepening data use beyond incident counts

Restrictive practice data becomes more useful when it captures the circumstances around behaviour. Counting how often a restriction is used is only the starting point. Teams need to understand what happened before, during and after the restriction so they can change the support environment.

This is where services often strengthen their review process by using ABC data to analyse behaviour and staff responses. When antecedents, behaviour and consequences are recorded clearly, the service can see whether restrictions are linked to pain, sensory overload, communication barriers, boredom, transition anxiety or inconsistent staff practice.

Operational Example 2: Reducing door alarms through better evidence

Context

A residential service used door alarms for a person who frequently left the building without staff. The alarm created rapid staff responses, but the person became more distressed when staff ran towards them or blocked the doorway.

Support approach

Data review showed that most door exits happened after long periods without meaningful activity, especially when the garden was inaccessible or staff were completing paperwork. The restriction had become a reactive safety control rather than part of a proactive support plan.

Day-to-day delivery detail

The service introduced planned outdoor access, a visual “outside now / outside later” board, garden checks before preferred times and a calm response protocol. Staff were instructed to approach from the side, use agreed phrases and avoid crowding the doorway. The alarm remained initially but was reviewed weekly against the new support plan.

How effectiveness was evidenced

Evidence included fewer alarm activations, reduced distress after attempted exits, increased planned outdoor time and fewer emergency staff responses. The review showed that the person was not simply “absconding”; they were seeking movement, space and predictable access to outside areas.

Systems, workforce and consistency

Data quality depends on staff confidence and consistency. If staff do not know what counts as a restrictive practice, records will be unreliable. If one staff member records “prompting” while another records the same action as “blocked access”, governance becomes unclear.

Strong services use supervision and team meetings to check recording quality. Staff are supported to describe what happened factually, not emotionally. Handovers include current restriction-reduction goals, early warning signs and agreed alternatives. Managers sample records to check whether the plan is being followed across day shifts, night shifts, agency staff and community support.

Consistency also requires feedback loops. Staff need to see that recording leads to change. When teams understand that data influences rota planning, environmental changes, communication support and review decisions, recording becomes part of practice rather than an administrative task.

Operational Example 3: Reviewing staff proximity restrictions

Context

A person attending a day opportunity was subject to close staff proximity during group activities because of previous incidents of grabbing objects and pushing peers. Staff were instructed to remain within arm’s reach throughout sessions.

Support approach

The provider reviewed incident and observation data. It showed that incidents were more likely during unstructured waiting times than during the main activity. Close staff proximity sometimes increased tension because the person felt watched and corrected.

Day-to-day delivery detail

The team changed the support plan so staff offered structured roles during waiting periods, such as setting out materials or choosing music. Staff stepped back during focused activity but moved closer during known transition points. A consistent cue was introduced to signal when the activity was changing.

How effectiveness was evidenced

Effectiveness was evidenced through reduced peer incidents, increased participation, fewer staff corrections and successful periods with less intrusive support. The data allowed the service to reduce blanket proximity while still managing risk at predictable points.

Governance and evidence

Governance should show how restrictive practice data is collected, checked, analysed and acted on. Providers should be able to evidence an audit trail from daily records into PBS review, from PBS review into action planning, and from action planning into measurable outcomes.

Useful governance does not rely only on dashboards. Data should be tested against lived experience. If restrictions reduce but the person appears withdrawn, less active or less connected, the service must question whether the reduction is meaningful. Strong services demonstrate a clear line of sight from behaviour to action to outcome, with both numbers and narrative evidence supporting decisions.

Commissioner and CQC expectations

Commissioners expect providers to explain how restrictive support is monitored and how reduction is pursued without creating unmanaged risk. They will want evidence that staffing levels, support models and restrictions are based on current need, not historic assumptions.

CQC expectations include effective governance, safe care, person-centred planning, protection of rights and learning from incidents. Inspectors may ask whether leaders know where restrictions are used, whether staff understand them and whether data shows improvement. Providers should be able to evidence that restrictive practice information leads to safer, less restrictive daily support.

Common pitfalls

• Counting restrictions without analysing why they happened.
• Recording fewer incidents while the person’s opportunities have reduced.
• Using inconsistent language across staff teams.
• Failing to record alternatives attempted before restriction.
• Reviewing data too infrequently to influence practice.
• Separating restrictive practice data from quality-of-life evidence.

Conclusion

Restrictive practice data should help services make better decisions for the person. When it is accurate, reviewed and connected to daily support, it shows where restrictions can be reduced and where staff need clearer guidance. Strong PBS governance uses data not to defend control, but to build safer, more skilled and more person-centred support.

---