Restrictive Practice Reduction Through Reviewing Refusal Responses in PBS

May 15, 2026

Positive Behaviour Support requires providers to review how staff respond when a person refuses support, activity, care, food, medication prompts, appointments or routines. The Positive Behaviour Support hub for rights, behaviour and restrictive practice reduction supports services to connect safety with communication, dignity and autonomy.

In specialist services, restrictive practice review and reduction should include repeated prompting, pressure, blocked choices, staff-led persuasion, delayed access and routines where refusal is treated as behaviour to overcome rather than communication to understand.

This reflects PBS principles focused on voice, dignity and person-led support, because refusal can be meaningful communication. Strong services demonstrate how refusals are explored safely rather than managed through unnecessary control.

Concept Explained Clearly

Refusal responses become restrictive when staff react to a person’s “no” by increasing pressure, removing alternatives, repeating instructions or limiting future access. This may happen during personal care, meals, appointments, medication support, community activities, transitions or household routines.

Some refusals involve real risk. A person may decline essential care, health support or safety-related action. PBS does not ignore those responsibilities. It asks whether the response is proportionate, respectful and designed to understand why the person is refusing.

Refusal may communicate pain, fear, sensory discomfort, lack of understanding, loss of control, trauma memory, tiredness, dislike, confusion or mistrust. A strong PBS response treats refusal as information before deciding what action is needed.

Why It Matters in Real Services

When staff respond to refusal with pressure, distress can escalate quickly. The person may feel unheard, cornered or punished. Repeated staff prompts can turn an ordinary “not now” into a crisis.

Services may also misread compliance as success. A person may eventually complete the task, but only after losing control, becoming distressed or learning that refusal is not respected. Commissioners and CQC will expect providers to evidence that refusals are understood, risks are managed and responses remain least restrictive.

What Good Looks Like

Strong services define how refusal should be recognised and supported. Plans explain what refusal looks like for the person, what staff should check, what choices can be offered, what delay is safe and when escalation is required.

Providers should be able to evidence refusal response plans, communication profiles, PBS updates, incident analysis, staff supervision and outcome records. This creates a clear line of sight from refusal to support action, and from support action to reduced distress and safer engagement.

Operational Example 1: Responding Differently to Refused Personal Care

Step 1 – Context: A person regularly refused morning washing support, and staff responded by repeating prompts until the person shouted and pushed the bathroom door closed.

Step 2 – Support approach: Review identified that the person disliked cold water, fast speech and being approached before breakfast. The refusal was linked to timing and sensory discomfort.

Step 3 – Day-to-day delivery detail: Staff changed the routine to offer breakfast first, warmed the bathroom, used one visual prompt and gave the person a clear “later” option.

Step 4 – Restriction reduction: Repeated verbal prompting stopped. Staff used a planned pause and returned within an agreed care window when the person was more ready.

Step 5 – How effectiveness was evidenced: Personal care completion improved, shouting reduced and staff recorded fewer door-closing incidents. The provider evidenced that respecting refusal reduced restrictive pressure and improved dignity.

Deepening the Approach

Refusal review should examine what happens immediately before the refusal, how staff respond and what consequence follows. A refusal may be maintained by escape from pressure, avoidance of pain, need for control or lack of accessible information.

Good analysis prevents staff from using one response for every refusal. Using ABC data to understand behaviour in PBS can help teams identify whether refusal follows demands, unclear communication, environmental discomfort, waiting, staff change or previous negative experiences.

Operational Example 2: Reviewing Refusal of Community Activities

Step 1 – Context: A person began refusing a weekly community gardening group. Staff initially interpreted this as lack of motivation and stopped offering the activity.

Step 2 – Support approach: PBS review found the person still liked gardening but disliked the crowded minibus journey and uncertainty about who would be present.

Step 3 – Day-to-day delivery detail: Staff introduced a photo preview of attendees, quieter transport, a clear activity role and a return-home plan if the person became overwhelmed.

Step 4 – Restriction reduction: The activity was reintroduced as a supported choice rather than removed after refusal. The person could attend for a shorter period at first.

Step 5 – How effectiveness was evidenced: Attendance resumed, anxiety before travel reduced and the person chose gardening on their weekly planner. The provider evidenced that understanding refusal restored meaningful activity access.

Systems, Workforce and Consistency

Refusal responses must be consistent across staff teams. If one worker respects a pause while another pushes for immediate completion, the person may become less trusting and more defensive.

Supervision should review whether staff understand the difference between risk-based escalation and unnecessary pressure. Handovers should record what was refused, what might have contributed, what response was used and what happened next. Strong services demonstrate that refusal is part of PBS learning, not simply recorded as non-engagement.

Operational Example 3: Managing Medication Prompt Refusal Without Pressure

Step 1 – Context: A person sometimes refused medication prompts in the evening. Staff became anxious and repeated reminders, which led to arguments and delayed bedtime routines.

Step 2 – Support approach: Review showed the person disliked being interrupted during a television programme and became worried when staff used urgent language.

Step 3 – Day-to-day delivery detail: The service agreed a medication prompt window, used a calm visual reminder, avoided repeated verbal prompting and involved clinical advice on safe timing.

Step 4 – Restriction reduction: Staff stopped escalating immediately after the first refusal and used an agreed pause, re-offer and recording process within safe parameters.

Step 5 – How effectiveness was evidenced: Medication was accepted more consistently, arguments reduced and MAR notes showed clearer recording of refusal and re-offer. The provider evidenced safer support without coercive pressure.

Governance and Evidence

Governance should show how refusal-related restrictions are identified, reviewed and reduced. Providers should be able to evidence PBS plans, communication profiles, risk assessments, clinical guidance where relevant, incident analysis, refusal records, supervision notes and feedback from the person or representative.

Strong governance creates a clear line of sight from behaviour to communication, from communication to staff response, and from staff response to outcome. Providers should be able to evidence that refusal is neither ignored nor overridden without justification, but understood within a structured support framework.

Commissioner and CQC Expectations

Commissioners expect providers to balance safety, choice and positive risk management. They need assurance that services do not treat refusal as failure, but use it to improve support design and reduce unnecessary restriction.

CQC will expect care to be person-centred, respectful, safe and least restrictive. Inspectors may review whether consent, choice and refusal are understood, whether staff use pressure, and whether restrictive responses are recorded and reviewed. Strong services demonstrate that refusal responses are part of PBS governance and rights-based practice.

Common Pitfalls

Repeating prompts until the person becomes distressed.
Treating refusal as non-compliance rather than communication.
Removing future opportunities because the person refused once.
Failing to check pain, sensory discomfort, fear or confusion.
Using urgent staff language when calm re-offer would be safer.
Recording refusal without reviewing staff response or outcome.

Conclusion

Restrictive practice reduction through reviewing refusal responses helps PBS services protect dignity while managing real risks. Refusal should lead to better understanding, not automatic pressure or control.

Strong providers evidence how refusals are interpreted, how staff responses change and how outcomes improve. This gives commissioners and CQC confidence that PBS is supporting voice, consent and least restrictive practice in everyday service delivery.