Before You Write a PBS Plan, Ask This One Question

July 27, 2025

Most behaviour support plans jump straight to what to do. But effective Positive Behaviour Support (PBS) starts by understanding why. If your service is anchored in PBS principles and values, then curiosity comes before control. And if you apply ethical PBS frameworks consistently, you avoid the common drift into restrictive, “containment-first” approaches that may suppress behaviour without addressing distress.

There’s one question every team should ask before writing any strategy, setting any goal, or assigning any intervention:

“What is this person trying to communicate through their behaviour?”

🧠 Behaviour Has Meaning

In PBS, we don’t treat behaviour as a “problem to eliminate”. We treat it as information — a message shaped by context. When someone has limited ways to communicate stress, pain, fear, frustration or unmet needs, behaviour may become their most reliable way to be heard. Labelling behaviour as “challenging” often tells us more about the service experience than the person.

That message might be:

I’m overwhelmed by noise, lighting, touch or unpredictability.
I don’t understand what’s expected of me, or the demand feels too hard right now.
I feel unsafe, rushed, ignored, or controlled.
I’m in pain, unwell, exhausted, hungry, or anxious.
I need a break, but I don’t know how to ask or I’m not being allowed one.

If we jump to solutions without understanding meaning, we fix the surface — not the cause. That is how services end up repeating the same incidents for months, escalating restrictions over time, and losing sight of quality of life.

📌 Commissioner expectation

Commissioner expectation: commissioners increasingly expect providers to demonstrate function-based behaviour support that is proactive and outcome-led. In practice, this means the provider can evidence that behaviour support plans are informed by functional understanding (not generic “de-escalation” statements), that preventative strategies are implemented consistently, and that there is a learning loop showing what was tried, what changed, and what impact was achieved over time.

🔎 Regulator / Inspector expectation (CQC)

Regulator / Inspector expectation (CQC): inspectors look for person-centred care that is safe, responsive and least restrictive. In PBS terms, they will expect to see that staff understand the person’s triggers and needs, that behaviour is approached as communication, and that restrictive practice is not used as the default response. Where restrictions are used, CQC will expect clear rationale, review, and evidence that less restrictive alternatives have been attempted and strengthened.

📋 Functional Assessments Aren’t Just Paperwork

Analysing what happens before, during and after behaviour (ABC charts, functional assessments, incident mapping) isn’t a tick-box task. It is an act of respect. It says: “We believe there’s a reason, and we care enough to find it.”

Function-based understanding is also a risk management tool. When a team can reliably identify patterns — time of day, environment, health changes, demand levels, staffing patterns, sensory load, communication breakdown — the service can prevent escalation rather than simply respond to it.

However, functional assessments only work when they are done with real discipline. Poor-quality ABC charts often capture only the “behaviour” and ignore the context. Good functional work captures:

Setting events: sleep, pain, illness, medication changes, bereavement, trauma triggers, disrupted routines.
Antecedents: noise, crowding, requests, transitions, demands, staff tone, denied access, waiting.
Behaviour detail: what actually happened (not labels), how long it lasted, how it escalated, how it ended.
Consequences: what changed immediately after (attention, escape, access, sensory relief, reduced demands).

The more curious and precise the assessment, the more person-centred the support becomes — and the less likely the team is to rely on restrictions.

🧩 Operational example 1: “Aggression” driven by communication and demand confusion

Context: In a supported living service, a person hits out when asked to attend appointments or complete certain daily tasks. Staff describe it as unpredictable, but incidents cluster around demand-heavy periods and time pressure.

Support approach: Functional assessment identifies that behaviour is linked to uncertainty and demand overload: staff give multi-step instructions, change plans at short notice, and keep prompting when the person shows early distress.

Day-to-day delivery detail: Staff introduce a simple visual routine and reduce verbal instruction. Requests become single-step and paced. The person is offered structured choices (“now or in 10 minutes”; “walk or taxi”). Staff agree a consistent script and a “pause and reset” protocol when early signs appear (fidgeting, withdrawal, raised voice). A quiet preparation period is built into the routine before leaving the home.

How effectiveness is evidenced: Incidents reduce in frequency and intensity, and staff report fewer “standoffs”. The provider tracks incident timing, triggers and recovery, and reviews progress in supervision. The plan is updated with clear proactive strategies and evidence of reduced escalation.

🧩 Operational example 2: Distress as a response to sensory overload in shared spaces

Context: A residential service experiences repeated incidents in the lounge: shouting, pushing objects and attempts to leave. Staff report “refusal to engage” and increase supervision, which escalates further.

Support approach: Mapping shows a pattern: incidents occur during busy communal times (shift change, meal preparation, visitors). The behaviour functions as escape from sensory overload and crowding.

Day-to-day delivery detail: The team adjusts the environment: reduce noise sources, use calmer lighting, and create a predictable access route to a quiet space. Staff stop approaching from behind, give more processing time, and offer a planned sensory break before peak periods. The daily routine is adapted so the person can use shared areas at quieter times, with a preferred activity available as an alternative.

How effectiveness is evidenced: Incident duration shortens and recovery improves. Staff logs show earlier intervention using proactive strategies rather than reactive containment. Restrictive interventions reduce because escalation is prevented sooner, and the provider can evidence least-restrictive practice through incident reviews and supervision notes.

🧩 Operational example 3: “Attention seeking” reframed as connection and predictability

Context: A person repeatedly shouts, interrupts staff, and escalates when staff are busy supporting others. The behaviour is labelled as “attention seeking”, and the service responds with firm boundaries and reduced engagement.

Support approach: Functional assessment identifies that behaviour increases when the person lacks predictable connection and feels uncertain about when support will be available. The function is access to reassurance and social connection.

Day-to-day delivery detail: The service introduces planned, predictable engagement: a short check-in at set times, visual prompts that show when staff are available, and a simple “waiting strategy” with an agreed activity. Staff are trained to respond consistently with brief reassurance and a clear time cue (“I’ll come back in 5 minutes”) rather than escalating verbal conflict. The person is supported to request connection using an agreed phrase or prompt card.

How effectiveness is evidenced: Interruptions reduce because connection is predictable. The provider tracks the number of escalations during busy periods and reviews the plan weekly. Staff confidence improves, evidenced in supervision and reduced reactive incidents.

✅ Tips for Practice: Turn Curiosity Into Reliable Delivery

Curiosity matters — but services also need a repeatable method so understanding doesn’t disappear when staff change. Good practice includes:

Ask function questions: “What does the person gain or avoid through this behaviour?” (escape, access, attention, sensory relief, control, predictability).
Involve the right people: family, keyworkers, advocates, clinicians and anyone who knows the person’s history and communication style.
Test assumptions: treat your hypothesis as a working theory and trial one change at a time to see if behaviour shifts.
Build health checks into PBS: pain, constipation, infection, sleep, medication side effects and menstrual health are common hidden drivers.
Record early indicators: so staff can act before escalation peaks (tone shifts, pacing, withdrawal, refusal patterns).
Link learning to governance: post-incident reviews should lead to plan adjustments, not just “actions completed”.

Understanding does not slow services down. It saves time, reduces incidents, improves outcomes, and lowers reliance on restrictive practice in the long run.

🧭 What to Include in Tenders and Provider Assurance

Providers often state “we use PBS” in tenders but fail to evidence functional understanding. Strong submissions show the mechanism and the evidence trail. For example:

How functional assessments are completed, quality checked and reviewed.
How ABC data informs proactive strategies and environmental adjustments.
How teams evidence reduction in restrictive interventions over time.
How supervision and competency checks confirm staff can apply PBS thinking in real situations.
How outcomes are tracked (frequency, duration, recovery time, quality of life indicators, stability).

This approach signals maturity: the provider is not relying on individual staff skill alone, but has built a system that produces consistent, least-restrictive support.