Understanding Behaviour Function in PBS: Knowing What the Behaviour Does for the Person
Positive Behaviour Support becomes stronger when services understand what behaviour does for the person, not just what it looks like to staff. The Positive Behaviour Support knowledge hub supports this wider view by linking behaviour, communication, proactive support, rights and reduction of restrictive practice.
In specialist services, understanding behaviour through PBS means asking what need, feeling or outcome may sit behind a behaviour. A person may be escaping overload, seeking connection, expressing pain, gaining control, communicating fear or regulating sensory distress.
This connects directly with PBS principles and values in practice, because behaviour function should never be used to blame the person. It should guide staff to provide safer, clearer and more respectful support.
Concept Explained Clearly
Behaviour function means the purpose a behaviour may serve for the person. This does not mean the person is always consciously choosing the behaviour. It means the behaviour has an effect. It may help the person escape a demand, access a preferred item, receive attention, reduce discomfort, express distress or regain predictability.
Understanding function matters because the same behaviour can mean different things for different people. Shouting may communicate pain for one person, anxiety for another, and frustration about unclear choices for someone else. Property damage may be linked to sensory regulation, loss of control, or inability to communicate that an activity needs to stop.
Why It Matters in Real Services
When function is misunderstood, support becomes ineffective. Staff may keep offering reassurance when the person needs reduced sensory input. They may remove all demands when the person needs clearer communication. They may increase supervision when the person is seeking privacy and control.
This can lead to repeated incidents, increased restriction and staff frustration. It can also weaken assurance. Commissioners need confidence that providers understand why behaviours occur and what support is being changed. CQC may look for evidence that plans are person-centred, proactive and based on the person’s communication and needs rather than generic risk control.
What Good Looks Like
Strong services demonstrate that behaviour function is explored through observation, recording, discussion and review. Staff do not jump to conclusions. They gather evidence across time, settings, activities, health, communication and staff response.
Good PBS plans explain the likely function in plain language and translate that understanding into daily support. Staff know what the person may be communicating, what early signs look like, and what response reduces distress. This creates a clear line of sight from behaviour to understanding, from understanding to action, and from action to outcome.
Operational Example 1: Behaviour Used to Escape Overload
Context: A person in a residential service regularly shouted and left the room during group activities. Staff initially described this as refusal to engage, but the behaviour occurred most often when several people spoke at once.
Support approach: The provider reviewed ABC records, sensory observations and staff notes. The likely function was escape from sensory and social overload. The aim was not to force participation, but to make engagement more tolerable and meaningful.
Day-to-day delivery detail: Staff offered smaller group options, quieter seating, visual activity choices and permission to leave without challenge. The person was invited to join for shorter periods and was not pressured to explain withdrawal during signs of distress.
How effectiveness was evidenced: Records showed fewer abrupt exits, reduced shouting and increased voluntary participation. Staff also recorded improved recovery time after activities. The provider could evidence that understanding the escape function led to environmental changes rather than exclusion.
Deepening the Understanding: Function Is Tested, Not Assumed
Strong PBS practice treats function as a working hypothesis. A team may think behaviour is linked to escape, attention, access or sensory regulation, but they must test this against evidence. If the support response changes and outcomes improve, the hypothesis becomes stronger. If behaviour continues or worsens, the team needs to review its understanding.
Function also changes over time. A behaviour that once helped someone avoid overwhelming activity may later become the only reliable way they can communicate distress. Staff response can unintentionally strengthen this pattern. If the person only receives a break after escalation, the service has not provided an earlier communication route.
The related guidance on seeing behaviour as communication rather than challenge reinforces why function must be understood through the person’s experience, not staff convenience.
Operational Example 2: Behaviour Used to Gain Predictability
Context: A supported living tenant repeatedly asked the same question, became distressed when staff gave different answers, and sometimes threw objects when plans changed. Records described repetitive questioning and agitation.
Support approach: The provider reviewed communication needs and daily routines. The likely function was gaining predictability and reassurance. The behaviour increased when staff answered casually or changed wording.
Day-to-day delivery detail: The team introduced a visual plan, consistent phrases and written confirmation of key events. Staff were trained not to give uncertain promises. If an activity might change, they used a planned explanation and offered two predictable alternatives.
How effectiveness was evidenced: Repeated questioning reduced, object throwing became less frequent, and the person used the visual plan more independently. The service evidenced that the behaviour was linked to uncertainty and that consistent communication improved emotional security.
Systems, Workforce and Consistency
Behaviour function must be understood by the whole team. If one staff member sees behaviour as communication and another sees it as deliberate disruption, the person receives inconsistent support. This inconsistency can increase distress and make behaviour appear more complex than it is.
Strong services build shared understanding through induction, supervision, team meetings and reflective practice. Handovers should include the likely function of behaviour and what staff should do differently. Managers should observe whether staff responses match the PBS plan and correct drift quickly.
Operational Example 3: Behaviour Used to Access Connection
Context: In a specialist service, one person frequently banged on doors during staff handover. Staff saw this as disruption, but records showed the behaviour happened when staff attention moved away from the person for a predictable period.
Support approach: The provider considered whether the function was access to connection and reassurance. Rather than increasing restrictions around handover, the team redesigned the routine so the person did not experience sudden loss of attention.
Day-to-day delivery detail: Before handover, staff spent five minutes with the person, explained what would happen, and set up a preferred activity nearby. A named staff member checked in halfway through handover using a calm, predictable phrase.
How effectiveness was evidenced: Door banging reduced and staff completed handovers with fewer interruptions. The person appeared calmer during the transition. Evidence showed that planned connection reduced behaviour more effectively than reactive correction.
Governance and Evidence
Governance should show how behaviour function is identified, reviewed and translated into support. Providers should be able to evidence ABC records, functional analysis, communication assessments, sensory information, health checks, PBS plan updates, staff briefings and outcome reviews.
Evidence should include both data and narrative. Incident reduction matters, but so does improved quality of life, increased choice, better engagement, reduced restriction and stronger relationships. This creates a clear line of sight between the behaviour, the proposed function, the support response and the outcome achieved.
Commissioner and CQC Expectations
Commissioners expect providers to understand behaviour function because it shows that risk is being managed proactively and intelligently. They need assurance that the provider can explain why support approaches are used, how they reduce distress, and how outcomes are monitored.
CQC will expect person-centred care, safe support and effective leadership oversight. Inspectors may review whether behaviour support plans are based on individual need, whether staff understand communication, and whether restrictions are reduced where possible. Strong services demonstrate that functional understanding shapes real daily practice.
Common Pitfalls
- Assuming function without gathering enough evidence.
- Using labels such as “attention seeking” in a blaming or dismissive way.
- Forgetting that the same behaviour can have different functions in different settings.
- Writing functional analysis into a plan without translating it into staff actions.
- Failing to review function when behaviour changes or support stops working.
- Measuring success only by fewer incidents, without checking quality of life.
Conclusion
Understanding behaviour function is central to effective PBS. It helps teams move beyond surface behaviour and identify what the person may be communicating, avoiding, seeking or regulating. This changes the purpose of support. Staff stop asking how to stop the behaviour and start asking what needs to change around the person.
Strong providers demonstrate that function is tested through evidence, shared across the workforce and reviewed through governance. When this is done well, support becomes more consistent, less restrictive and more closely linked to the person’s quality of life.