Learning From Incidents: Using Post-Incident Review to Strengthen Reactive Behaviour Support

Reactive strategies are intended to be used rarely, proportionately and only when preventative approaches have failed. When incidents do occur, how organisations respond afterwards is a critical indicator of quality, governance and learning culture. Within Positive Behaviour Support, post-incident review is not an administrative task but a safeguarding mechanism that ensures reactive strategies remain lawful, effective and progressively reduced over time.

This article sits alongside work on reactive strategies and incident response and the wider principles and values of Positive Behaviour Support, focusing specifically on how services convert incidents into measurable improvement rather than repetition.

Providers also need to demonstrate that incident responses are consistent with proactive planning and least restrictive practice. This is examined further in effective reactive strategies within Positive Behaviour Support frameworks. The objective should never be simply to demonstrate that an intervention was performed correctly; it should be to understand what happened, whether it could have been prevented and what needs to change before the next period of distress.

The purpose of post-incident review in PBS

Post-incident review serves several functions simultaneously. It supports the individual by ensuring their experience is understood, supports staff by providing reflective learning, and protects the organisation by evidencing lawful decision-making. Critically, it tests whether reactive strategies remain necessary, proportionate and the least restrictive option available.

Effective review processes go beyond incident forms. They triangulate staff accounts, environmental factors, support plan accuracy, and the person’s communication and presentation before, during and after the incident. Where restrictions have been used, this should connect directly with restrictive practice reduction, review and governance.

The review should therefore ask not only, “Was procedure followed?” but also, “What does this incident tell us?” A technically compliant intervention can still reveal weaknesses in communication, environment, staffing, formulation, escalation or proactive support strategies.

Operational example: Reducing repeat restraint in supported living

In a supported living service supporting a man with autism and a history of physical aggression, incident frequency had plateaued despite a PBS plan. Post-incident reviews identified that staff were consistently applying the reactive strategy correctly, but antecedent signs were being missed during shift transitions.

The review process led to changes in handover structure, visual prompts in the environment, and refresher coaching. This was reinforced through PBS coaching, supervision and practice competency so that the learning was translated into staff behaviour rather than remaining an action on the incident record.

Within eight weeks, incidents reduced by over 40%, without altering the reactive strategy itself. The improvement came from recognising earlier indicators and changing the conditions around the incidents rather than increasing the intensity of the response.

Operational example: Safeguarding-led review following injury

In a residential service, a staff member sustained a minor injury during an incident. The post-incident review was conducted jointly by the manager and safeguarding lead. Analysis showed the reactive strategy was proportionate, but staffing deployment at the time increased risk.

Actions included rota adjustments, clearer escalation thresholds and updated risk assessments. The review outcome was shared transparently with commissioners, demonstrating learning rather than blame.

This distinction matters. A strong learning-from-incidents culture does not assume that every adverse event proves individual failure. It examines the interaction between the person, staff practice, deployment, environment, systems and management controls, then identifies what can reasonably be improved.

Operational example: Reviewing restrictive practices in crisis services

A crisis support service identified increased use of physical intervention during night hours. Post-incident reviews highlighted environmental triggers, limited access to senior decision-makers overnight, and inconsistent de-escalation approaches.

The service introduced on-call clinical consultation and revised night-time routines. Subsequent reviews showed both reduced incident severity and shorter duration of reactive interventions.

Importantly, the service did not treat the reduction in incidents as sufficient evidence on its own. It continued reviewing whether restrictions remained necessary, whether staff responses were becoming more consistent and whether the changes were improving the person’s wider experience and quality-of-life outcomes.

From individual review to thematic learning

One of the most important governance tests is whether providers can move from reviewing individual incidents to identifying patterns across time, teams, locations and people. Repeated incidents may appear unrelated when considered separately but reveal a systemic issue when analysed together.

Useful themes may include particular times of day, staff transitions, environmental conditions, communication demands, staffing combinations, missed early indicators, types of restrictive intervention or delays in management escalation.

The Quality Dashboard Builder can help providers bring together incident frequency, severity, restrictive-practice use, repeat patterns and action completion so that managers and leaders can see whether learning is translating into measurable change.

This is where post-incident review becomes part of root cause analysis and thematic learning, rather than a sequence of isolated incident investigations.

Commissioner expectation: Evidence of learning and reduction

Commissioners expect providers to demonstrate that incidents lead to tangible change. This includes clear records of review, actions taken, and evidence that reactive strategies are being reduced or refined over time rather than normalised.

Services unable to evidence learning may face increased monitoring or contractual challenge, even where incidents themselves are unavoidable. The important assurance question is whether the provider understands the pattern, has responded proportionately and can demonstrate whether agreed changes have made a difference.

The Commissioner Evidence Builder can support providers in translating incident learning, corrective action and measurable improvement into clearer evidence for contract monitoring, tenders and commissioner assurance.

Regulator expectation: Governance and assurance

CQC expects providers to have effective systems for learning when things go wrong and for leaders to understand significant risks within their services. In PBS settings, providers should therefore be able to demonstrate meaningful oversight of incidents, restrictive practices, patterns, actions and subsequent improvement.

Reviews should show how individual incidents inform wider service learning, training and policy development. Evidence should also demonstrate that actions have been completed and tested for effectiveness rather than simply recorded as closed.

The CQC Evidence Gap Analyzer can help providers test whether their claims about incident learning, restrictive-practice oversight and improvement are supported consistently across incident records, audits, supervision, action plans and frontline practice.

Senior oversight and accountability

Repeated or high-risk incidents should not remain solely within frontline management systems. Leaders need sufficient visibility to understand whether patterns indicate weaknesses in staffing, clinical or behavioural support, service design, training, risk management or organisational culture.

The Governance Maturity Assessment can help organisations examine whether incident information travels effectively from frontline services into management and board-level assurance, and whether leaders can demonstrate that identified risks result in accountable action.

This strengthens the connection between PBS practice and wider quality assurance, governance and oversight. Senior leaders do not need operational detail about every incident, but they do need sufficient intelligence to identify deteriorating patterns, recurring restrictions and actions that are failing to produce improvement.

Embedding effective post-incident review

Strong systems typically include structured review tools, defined timescales, involvement of the individual where possible, and clear accountability for follow-up actions. Reviews should be psychologically safe for staff while remaining robust and transparent.

Effective systems also distinguish immediate review from deeper learning. Some actions may need to happen immediately after an incident, while recurring patterns may require multidisciplinary review, behavioural reformulation, changes to the environment, revised staff competency arrangements or wider service improvement.

Providers should be able to trace a clear sequence:

• the incident and immediate response;
• the person’s experience and recovery;
• review of what happened before, during and after the event;
• identification of contributory factors and learning;
• agreed actions with named accountability;
• changes to plans, environments, staffing or practice where required; and
• subsequent evidence showing whether those changes reduced risk or improved outcomes.

That final stage is critical. Closing an action is not the same as demonstrating improvement. Effective embedding of learning into day-to-day practice requires providers to return to the evidence and establish whether the intended change actually occurred.

When embedded well, post-incident review becomes a driver of quality, safeguarding and continuous improvement rather than a reactive compliance task. Its value lies not in producing more documentation after something has gone wrong, but in progressively making future distress, escalation and restrictive intervention less likely.

---