How to Evidence PBS in Your Tender Responses

July 18, 2025

When commissioners ask for “evidence of PBS”, they are rarely asking whether you have a policy. They are asking whether Positive Behaviour Support is consistently delivered, aligned to PBS principles and values, and governed through ethical PBS frameworks that protect rights and reduce restrictive practice. In bid evaluation, the safest position is to assume that statements without data, examples, and assurance mechanisms will be treated as weak. The strongest submissions show a repeatable operating model: how staff understand behaviour, what proactive strategies look like day-to-day, how you measure impact, and how leaders check that practice remains least restrictive and person-centred.

This area forms part of a wider framework covering tender planning, response development and evaluation readiness. You can explore these themes in our health and social care tender planning and bid development hub.

Commissioner expectation

Commissioner expectation: commissioners expect you to demonstrate that PBS is embedded as a day-to-day practice system, not a reactive incident response. They typically want to see (1) credible evidence of outcomes and quality-of-life impact, (2) restraint and restriction reduction as a governed priority, (3) staff competence and refresh, and (4) a clear audit trail showing learning cycles (record → analyse → adapt → re-check) across services and shifts.

Regulator / Inspector expectation (CQC)

Regulator / Inspector expectation (CQC): inspectors will look for safe, person-centred, least restrictive practice that is demonstrably understood by frontline staff and managed through oversight. Evidence is strongest when it shows: staff can describe triggers and proactive strategies; restrictions (if ever used) are lawful, proportionate and time-limited; incidents lead to learning and improvement; and governance processes (supervision, audits, quality meetings) actively reduce the likelihood of recurrence.

What ‘Evidence’ Really Means

Commissioners don’t want vague statements about Positive Behaviour Support (PBS) — they want proof that your service delivers it consistently and effectively. This means providing clear examples, data, and outcomes that show PBS is more than just a policy — it’s embedded in practice. Evidence is also about credibility: can a reviewer see how the data was generated, how often it is reviewed, who is accountable, and what changes were made as a result?

In practical terms, the best evidence sets show three things at once:

Operational reality: what staff do on an ordinary day to prevent distress and support communication.
Assurance and governance: how leaders check fidelity, reduce drift, and challenge restrictive practice.
Impact: measurable changes (incidents, restrictions, quality-of-life indicators) tied to specific PBS actions.

Strong Evidence for PBS Might Include

Case studies demonstrating PBS in action, the functional learning behind decisions, and outcomes achieved.
Data showing reductions in restrictive practices, PRN use (where applicable), or incident frequency/duration/intensity.
Training records confirming staff competence in PBS approaches (including refresh, coaching and competence checks).
Quality assurance outputs showing PBS principles in daily practice (plan audits, observations, supervision sampling).
Voice and experience evidence from people supported and families (accessible feedback, co-production records).
Commissioner / MDT feedback that recognises effective PBS delivery and partnership working.

What makes evidence “strong” rather than “present”

Many providers can provide items (a policy, a training slide deck, a template). Fewer can show a coherent evidence chain. Strong evidence is usually characterised by:

Traceability: you can trace a decision from assessment to plan to staff action to outcome, with dates and review points.
Consistency across shifts: evidence reflects practice on evenings/weekends as well as weekdays.
Specificity: examples describe context, triggers, proactive strategies, staff language, and how success was measured.
Learning cycles: you show what changed after review, not just that review occurred.
Least restrictive emphasis: restrictions (if present) are framed as last resort with reduction plans and clear authorisation.

What to measure (and why commissioners trust it)

Commissioners tend to trust data sets that are simple, repeatable, and consistently applied. Typical PBS-aligned measures include:

Frequency: incidents per week/month (by type and setting).
Duration: average minutes from trigger to calm (and trend over time).
Intensity/risk rating: a consistent scale (e.g. 1–3) that relates to harm likelihood and severity.
Restrictive practice indicators: restraint episodes, seclusion (if applicable), restrictions register entries, PRN for behavioural reasons (where relevant).
Quality-of-life indicators: engagement in meaningful activity, community access, choice points achieved, relationship stability, participation rates.
Plan fidelity: % of plans reviewed on time; % of staff observed delivering proactive strategies correctly.

Evidence improves when you include baseline → intervention → follow-up trends, rather than a single snapshot. Even short cycles (4–8 weeks) can be persuasive if the method is clear.

Operational example 1: Reducing escalation through transition planning

Context: In a supported living setting, a person escalated during morning transitions (personal care → breakfast → leaving for day activity). Incidents were most likely when staffing changed or the routine ran late.

Support approach: The team used ABC recording across different shifts to test patterns and developed a functional hypothesis: distress was driven by unpredictability and processing overload (escape/avoidance function), compounded by rushed prompts and unclear finish points.

Day-to-day delivery detail: Staff introduced a consistent visual sequence (same format used across the week), two scheduled choice points (“now or in two minutes”), a clear finish signal, and a planned regulation break. Staff practised using the same prompt style and tone and avoided multiple staff “layering” instructions at once. Supervision included quick sampling: “talk me through the transition plan and early indicators”.

How effectiveness is evidenced: Frequency reduced from 8–10 incidents/month to 2–3 incidents/month within eight weeks. Average duration reduced from ~10 minutes to ~4 minutes. Restrictions were avoided entirely; the restrictions register showed no new entries. Quality-of-life indicators improved: the person attended more planned activities and required less “last-minute” cancellation due to distress.

Operational example 2: Environmental adaptation to reduce restrictive responses

Context: In a residential service, incidents increased in communal areas at predictable times (handover overlap, mealtimes). Staff sometimes responded by limiting access to reduce risk, which created an informal restriction pattern over time.

Support approach: PBS review identified sensory overload and crowding as consistent antecedents. The function hypothesis was sensory avoidance and escape from high-arousal environments. The ethical risk was that “keeping people safe” was drifting into routine restriction.

Day-to-day delivery detail: The service created a clearly signposted calm space with predictable access, adjusted noise and lighting at peak times, and introduced structured alternatives during high-arousal periods. Staff were coached to spot early indicators (withdrawal, pacing, increased agitation) and to offer regulation options before escalation. Governance included a monthly restriction review: any “informal limitations” had to be recorded, justified, and time-limited with a reduction plan.

How effectiveness is evidenced: Incident frequency during peak times reduced by more than half over a quarter. The restrictions register showed a reduction in “controlled access” entries, with clear rationales and removal dates. Staff observation audits showed improved plan fidelity (more consistent proactive offers and fewer reactive controls). Family feedback noted the person had more choice and less conflict around communal access.

Operational example 3: Turning incident learning into measurable improvement

Context: A community outreach team supported a person whose distress escalated during appointments and unfamiliar journeys. Incidents were recorded, but learning was inconsistent and depended on which staff were on duty.

Support approach: The service introduced a standard PBS learning cycle: incident debrief within 24–48 hours, ABC summary, agreed proactive changes, and a re-check date. The functional hypothesis was anxiety linked to uncertainty and communication mismatch (attention/reassurance needs and escape from perceived threat).

Day-to-day delivery detail: The team created a “predictability pack”: visual itinerary, a simple script used by staff, and a clear exit plan (“if overwhelmed, we step out and use the quiet plan”). Staff used consistent language, reduced rapid questioning, and offered a planned pause before high-demand steps. Supervision included reflective questions: “What did we change? What moved in the data? What do we keep or stop?”

How effectiveness is evidenced: The service tracked appointment attendance (completed vs cancelled), distress duration, and early-exit use. Over 10 weeks, completed appointments increased, early-exit use became planned rather than crisis-led, and incident duration reduced. The evidence set included the debrief template, the plan update log, and a short trend summary that showed practice changes were directly tied to outcomes.

How to structure PBS evidence in a tender response

When you write PBS sections for tenders, it helps to avoid listing documents and instead present a short, defensible evidence chain. A strong structure is:

What PBS means in your service: behaviour as communication; prevention; quality of life; least restrictive practice.
How you operationalise it daily: proactive strategies, communication support, environment adaptation, consistent staff approaches.
How you evidence it: data measures, plan fidelity checks, co-production records, training competence, restrictions monitoring.
How you govern it: who reviews data, frequency of review, escalation routes, MDT input, how you address drift.
What impact looks like: trends, examples, and quality-of-life outcomes, not only incident counts.

This approach makes it easy for evaluators to score because they can see the operating model, the assurance mechanisms, and the outcomes in one coherent narrative.

Why this strengthens your bid

Strong evidence builds commissioner confidence because it shows your PBS approach is not dependent on one good practitioner or one good manager — it is supported by systems. It demonstrates that your service is:

Aligned with key priorities (restraint reduction, human rights, least restrictive practice).
Focused on person-centred outcomes (quality of life, participation, stability, choice and control).
Competent and well-led in embedding PBS across operations (training, supervision, audit, governance).

In procurement, this matters because commissioners need evidence they can defend internally: they want to be confident that performance is repeatable, measurable, and robust under pressure (staff turnover, high risk, complex needs).

Common pitfalls (and how to avoid them)

Pitfall: “We train staff in PBS” without competence checks. Strengthen by showing refresh cycles, observations, coaching, and supervision sampling.
Pitfall: Incident reduction as the only outcome. Strengthen by including quality-of-life indicators and least restrictive impact (freedoms increased, community access enabled, choices expanded).
Pitfall: Restrictive practice described defensively. Strengthen by showing governance, authorisation, time limits, review frequency, and a clear reduction plan.
Pitfall: Case studies with no measurement. Strengthen by including baseline and trend data (frequency, duration, intensity) plus what specifically changed in practice.

What “good” looks like in a single paragraph of evidence

As a benchmark, a strong PBS evidence paragraph usually includes: a short function hypothesis, the proactive strategy implemented, the governance mechanism used to ensure fidelity, and a measurable outcome. For example: “ABC analysis identified transitions and sensory overload as triggers; the plan introduced visual preview, choice points, and a calm-space protocol. Managers sampled practice through monthly observations and supervision prompts. Over 12 weeks, incidents reduced from 9 to 3 per month, average duration reduced from 12 minutes to 5 minutes, and no restrictive interventions were used.”