Recording and reporting restrictive interventions in schools: what changed from April 2026

From April 2026, schools in England moved from ‘recommended good practice’ to a clearer, statutory expectation for how significant restrictive interventions are recorded and communicated. This matters for pupil safeguarding, staff confidence, and for leaders who need evidence that practice is lawful, necessary, proportionate and reviewed.

This guide explains what schools should record, who should be told, how quickly this needs to happen, and what training and governance processes help you stay consistent across a busy school day.

What changed in April 2026 (and why it matters)

A number of schools have historically had uneven practice around recording incidents: some had robust systems, while others relied on informal notes or memory. Sector summaries of the new Department for Education statutory guidance emphasise that recording and reporting significant incidents is now treated as a legal duty, rather than optional best practice (SSS Learning). A legal update for schools and academy trusts also notes that new rules came into effect on 1 April 2026 and highlights binding duties to record significant incidents, report to parents, and update policies (Browne Jacobson).

In practical terms, leaders should assume that if an incident is significant enough to be reviewed for learning, safeguarding, or potential complaint handling, it needs a consistent written record that can stand up to scrutiny.

Clarifying terms: restrictive interventions, reasonable force, and seclusion

Different schools and local authorities have used different terminology. One reason this guidance matters is that it supports shared definitions, reducing confusion in incident reviews and policy writing.

Restrictive interventions

Restrictive interventions are described as including both physical and non-physical actions used to prevent, restrict, or subdue a pupil’s movement (SSS Learning). In school practice, this can include a range of actions from temporary restriction to keep someone safe, through to more structured holds, depending on risk and context.

Reasonable force

‘Reasonable force’ is the term used in legislation for the limited circumstances where staff may need to use physical contact to prevent injury, serious disorder or damage, or criminal acts. What matters in a record is not just what was done, but why it was judged necessary at that moment, what alternatives were attempted first, and how quickly force was reduced and stopped once risk reduced.

Seclusion

Seclusion is typically described as isolating a pupil in a space they cannot leave (SSS Learning). If seclusion is used, your process should treat it as a restrictive intervention requiring careful safeguarding consideration and record-keeping.

What should be recorded after a significant incident

The strongest records are factual, specific, and include enough detail that a senior leader who was not present can understand what happened and why decisions were made. Sector write-ups summarising the statutory guidance emphasise that significant incidents should be recorded promptly, generally on the same day, with accurate written records of each significant event (SSS Learning).

A practical incident record template (what good schools capture)

Most schools already have behaviour logs, safeguarding systems or incident forms. For restrictive interventions, ensure your form captures at least the following:

• Date, time and location of the incident.
• Pupil(s) and staff involved, plus witnesses.
• Antecedents and triggers: what was happening before things escalated.
• Identified risk: what harm was likely if staff did not act.
• De-escalation attempts: what was tried first, and for how long.
• What restrictive action was used: description in plain language (avoid jargon) and duration.
• Any injury or medical concern (pupil, staff, or others) and what checks were completed.
• Support and repair: what happened afterwards to help the pupil regulate and return to learning safely.
• Parent or carer communication: who was contacted, when, and what was shared.
• Review notes: what needs to change to reduce the likelihood of recurrence (support plan, environment, staffing, timetable, sensory factors, etc.).

Write like you are explaining to an external reviewer

When writing incident records, assume they may be read by parents, governors, safeguarding partners, inspectors, and sometimes solicitors. Aim for neutral language describing observable behaviour and staff actions. Avoid labels and assumptions about intent.

If a pupil is distressed, record that they were distressed. If they calmed after a specific support strategy, record that too. The goal is clarity, not defensiveness.

When should the record be completed?

One summary of the statutory guidance highlights recording promptly, generally on the same day (SSS Learning). That does not mean every detail must be written minutes after the incident, but it does mean the record should be treated as time-sensitive safeguarding documentation.

A workable approach is to:

• Capture a short ‘initial note’ immediately (time, place, who was involved, any injury).
• Complete the full record before the end of the working day wherever possible.
• Ensure a senior leader reviews and signs off the record within your internal timelines.

CTA: If you want a consistent approach across a whole staff team, our physical intervention training can help schools build a shared framework for safer decision-making, recording and reflection.

Who needs to be told (and what should be communicated)

Sector summaries highlight that parents or carers should be informed as soon as practicable after an incident involving their child (SSS Learning). A legal update for schools also highlights a duty to report to parents (Browne Jacobson).

To make this workable in a school day, be explicit in your policy about:

• Who makes contact (for example, a member of SLT for significant incidents).
• How contact is made (phone call plus written follow-up is common).
• What is shared: a brief factual summary, confirmation of the pupil’s wellbeing, and next steps.
• How the contact is recorded (time/date, method, summary, and whether the parent was reached).

Also be clear about how you handle contact where parents are hard to reach, where there is a safeguarding concern about what can be shared, or where the pupil is in care and you need to follow your agreed communication arrangements.

Governance and oversight: using records to reduce future risk

High-quality records allow leaders to spot patterns: particular times of day, specific demands that repeatedly trigger distress, environmental pinch points, or staffing changes that correlate with incidents.

At leadership level, build a regular review cycle. For example:

• Weekly safeguarding review of all significant records.
• Half-termly reporting to governors on themes, not personal detail.
• Termly review of whether behaviour support plans are working for pupils with repeated incidents.

Importantly, the purpose of oversight is prevention and support. Over time, this should contribute to reducing restrictive interventions by improving proactive strategies, consistency, and the learning environment.

CTA: Where schools want to move beyond compliance and towards safer culture change, restraint reduction training supports teams to reduce restrictive interventions through proactive support, de-escalation and reflective practice.

Training implications: what staff need to know to record well

Recording quality improves when staff share the same decision-making language. Even experienced staff can write weak records if they have never been shown what ‘good’ looks like. Consider covering the following in CPD or training refreshers:

• Legal and ethical principles: necessary, proportionate, least restrictive option.
• Recognising early signs of escalation and using de-escalation strategies.
• How to describe distressed behaviour without judgement.
• How to describe restrictive interventions in plain language.
• How to include the pupil’s perspective where appropriate, and how to record welfare checks.

Training should also connect to your systems: staff need to know exactly where to log incidents and who to inform, not just what ‘should’ happen.

CTA: If you work across schools, our children's services training supports teams working with children and young people where risk can escalate quickly and records must be accurate, consistent and safeguarding-led.

Worked examples: turning a busy incident into a clear record

Many records become unclear because staff try to summarise a fast-moving situation in one sentence. A better approach is to structure the narrative in short, factual steps. The examples below are not scripts; they are a way of showing the level of detail that helps reviewers understand decision-making.

Example 1: preventing injury in a corridor

Context: End of lunch, corridor is crowded and noisy. A pupil is visibly distressed, shouting, and moving quickly towards an exit.

• Observed risk: The pupil is pushing past others and attempting to run out of the building. Risk of collision, falls, and serious injury to the pupil or other pupils.
• De-escalation attempts: Two staff use calm voice and simple instructions, offer space, and offer a choice of quieter location. The pupil continues to run and attempts to pull away from support.
• Restrictive action: Staff use the least restrictive physical intervention available to briefly restrict movement and redirect away from the exit until the immediate risk reduces. The record includes duration and how the restriction was reduced as soon as it was safe.
• Welfare checks: Staff check breathing and visible injury, offer water and quiet space, and continue supportive communication.
• Follow-up learning: The team reviews the trigger (noise/crowding) and updates support so the pupil can transition earlier, use a quieter route, or access a calm space before the corridor becomes busy.

This shows that the restrictive action was about immediate safety, that less restrictive options were attempted, and that learning actions followed.

Example 2: seclusion used as a short-term safety measure

Context: In a classroom, a pupil begins throwing objects and attempting to strike peers. The room cannot be cleared quickly due to other pupils needing support.

• Observed risk: High likelihood of injury to other pupils or staff.
• De-escalation attempts: Staff reduce demands, offer time and space, and attempt to create distance. The behaviour continues and objects are still being thrown.
• Restrictive action: The pupil is moved to a supervised space and prevented from leaving for a short period to manage immediate risk. The record explains why this was judged necessary, how the pupil was supervised, and what conditions ended the restriction.
• Welfare checks: Staff record emotional state, signs of distress, and steps taken to support regulation.
• Parent contact: The record includes who contacted the parent or carer, when, and what was shared, plus any follow-up meeting arrangements.

When a restrictive measure involves confinement, documentation should be especially careful: it should show active supervision, a clear safety rationale, and a plan to return to normal movement as soon as it is safe.

Data protection and information sharing: keeping records useful and safe

Incident records are safeguarding documents and may contain special category personal data. As well as being accurate, they should be stored securely with access controlled to those who need it. Avoid unnecessary detail about other pupils; focus on the pupil involved, staff actions, and the safety context.

Where you use digital systems, make sure staff know which log is the ‘single source of truth’. Duplication across multiple places increases the risk of missing information, contradictions, or accidental disclosure.

How to decide whether an incident is ‘significant’ in your setting

Schools benefit from agreeing local thresholds so staff do not make inconsistent judgements under pressure. A practical approach is to treat an incident as significant if any of the following apply:

• The restrictive intervention went beyond brief, everyday contact and was used to prevent injury, serious disorder, or a criminal act.
• Any form of seclusion or confinement was used, even if for a short period.
• Any injury occurred or medical checks were needed.
• The incident is likely to lead to a complaint, exclusion, safeguarding referral, or multi-agency involvement.
• The same pupil has had repeated incidents and this record will contribute to a support plan review.

Once you define the threshold, make it easy to apply: provide staff with a one-page prompt sheet and ensure leaders reinforce it through review and feedback.

Auditing quality: what leaders should look for in records

Even with a form template, quality varies. A simple audit approach is to sample a small number of records each half-term and check for:

• Completeness: time, place, people, duration, and outcomes are all recorded.
• Clarity: a reader can understand the sequence of events and decision points.
• Least restrictive practice: the record shows that less restrictive options were considered and attempted where appropriate.
• Welfare and repair: the pupil’s wellbeing, and any restorative actions, are documented.
• Learning: next steps are specific (for example, changes to support plan or environment), not generic reminders.

Audits should not be used to blame staff. They should be coaching-led: when you find weak records, provide examples of stronger writing, agree an improvement target, and check again.

Common pitfalls that create risk for schools

• Vague language (for example, “pupil was out of control”) without observable detail.
• Missing de-escalation steps, which makes it harder to evidence that restrictive action was a last resort.
• Inconsistent thresholds: two similar incidents recorded differently by different staff.
• Delay in parent contact, with no rationale recorded.
• Records that focus only on compliance and miss welfare, repair and learning.

FAQ

Do all incidents of physical contact need a restrictive intervention record?

No. Normal, appropriate physical contact (for example guiding a pupil away from danger, first aid, or comfort) is not automatically a restrictive intervention record. Your policy should define what counts as a significant incident requiring the more detailed record, and staff should know the threshold.

How soon should parents be informed?

Summaries of the statutory guidance highlight informing parents or carers as soon as practicable after an incident involving their child (SSS Learning). Schools should translate this into a clear internal expectation (for example, same day where possible), with a process for exceptions.

What if a parent disputes what is written?

Take concerns seriously and respond promptly. If a parent shares a different view, record that as part of follow-up, review CCTV or witness statements where available, and consider whether staff need support or coaching to improve clarity and neutrality in records.

Do we need specialist training to comply?

Schools need staff who understand the principles and the school’s policy and systems. While sector commentary emphasises training remains important, compliance depends on consistent practice, clear thresholds and competent recording.

Next steps: a simple implementation checklist

• Update your policy and define what counts as a ‘significant incident’ in your context.
• Align safeguarding, behaviour and incident reporting systems so staff are not duplicating work.
• Train staff on both practice and paperwork: what to do, what to record, and who to tell.
• Review incident data regularly and turn it into prevention actions.
• Audit a sample of records each term for completeness, neutrality and learning.

If you would like help aligning your approach, speak to our team about whole-school training and policy support.