How to record and report reasonable force incidents in schools (UK guide)

When a situation escalates at school and a member of staff uses reasonable force, it is rarely the incident alone that determines what happens next. The quality of the recording, the speed of the internal review, and the tone of the communication with families often shape trust, staff confidence, and the likelihood of repeat incidents.

This article sets out a practical workflow for schools in the UK. It focuses on making incident recording consistent, proportionate and usable, not bureaucratic. It also explains how to align recording with training, safeguarding processes and data protection expectations.

What counts as “reasonable force” and why records matter

School staff have a legal power to use reasonable force in certain circumstances, but it is always context dependent. Detailed records help you show how staff balanced safety, dignity and proportionality, and help leaders identify patterns and prevent avoidable recurrence.

The Department for Education has published specific guidance on the use of reasonable force, and it is being updated through the transition to new statutory expectations from April 2026. The key practical point for recording is simple: if it was significant enough to intervene physically, it is significant enough to log clearly and review.

A simple incident recording workflow (the “same day, next day, next week” model)

Many recording systems fail because they try to do everything at once. A more reliable approach is to separate immediate facts from later analysis and learning.

Same day: secure the facts and safeguard everyone

• Confirm immediate safety: check the pupil, other pupils, and staff for injury; record any first aid and who provided it.
• Capture the basics while it is fresh: time, location, who was present, what prompted staff concern, and what de-escalation steps were attempted first.
• Describe the hold/contact neutrally: use plain language about what staff did and why, avoiding emotive labels. Record duration and whether any restrictions on breathing, circulation or communication occurred (and if not, state that clearly).
• Record outcomes: what changed as a result (for example, harm prevented, pupil moved to a safer space, dangerous item removed).
• Preserve any relevant evidence: CCTV clip reference, radio logs, or contemporaneous notes. If another policy applies (for example, a search and confiscation policy), reference it.

For staff capability and consistency, align the expected language and thresholds in your behaviour and safety policies with your training programme. If you need a refresher on safe approaches to intervention and prevention, see our physical intervention training page.

Next day: complete statements and complete the “why”

The next day is where schools often either over-write (adding opinions) or under-write (missing key context). A good standard is: facts first, then structured reflection.

• Staff statements: brief, consistent statements from the lead staff member and any witnesses.
• Pupil voice: record the pupil’s account when they are regulated and able to engage, including what they found difficult and what helped.
• Trigger and function notes: what was happening immediately before, what need the pupil may have been communicating, and what early interventions might reduce repeat incidents.
• Reasonable adjustments: if the pupil has SEND needs, record what adjustments were in place and whether any additional adjustments are required.

CTA: If your team wants a consistent, school-friendly format for recording and post-incident review, ask us about tailoring a recording template alongside training so documentation supports learning rather than blame.

Next week: review trends, not just this incident

Incidents often recur because the system learns slowly. A short weekly or fortnightly review meeting can make a major difference.

• Look for patterns: particular times, environments, tasks or transitions.
• Check consistency: are different adults recording in comparable ways?
• Confirm follow-up actions: parent communication, pastoral support, risk assessment updates and any staff support actions.
• Update plans: adjust support plans, risk assessments and de-escalation strategies.

What to include in an incident log (a practical checklist)

A strong record helps a reader understand the event without guessing. It should also make clear that the intervention was the last resort within that moment.

1) The lead-up

• What was happening in the lesson or environment, and what changed?
• What did staff observe that indicated increasing risk?
• What de-escalation strategies were attempted?

2) The decision point

• What risk was staff responding to (harm to self, harm to others, serious property damage, severe disruption)?
• Why was force judged necessary at that moment?
• Why were less intrusive options not sufficient in that moment?

3) The intervention

• Exactly what staff did, in plain language.
• Duration and how the intervention ended.
• Any change in risk level during the intervention.

4) Immediate aftercare

• First aid (if needed) and welfare checks.
• Calm, restorative support for the pupil.
• Staff debrief and welfare check.

Recording language: write so the record is usable and fair

Incident records are frequently read by people who were not there. To keep records professional and defensible:

• Use observable language: describe what you saw and heard.
• Avoid labels: focus on behaviour, not character.
• Use consistent terms: a shared vocabulary reduces misunderstandings.
• Record distress and support: if a pupil showed distressed behaviour, record what support was offered and what helped.

Parent and carer communication: what good looks like

Families usually want two things: reassurance about safety and a clear explanation of what will happen next. The way schools communicate also affects the likelihood of complaints escalating.

Timing and approach

• Contact promptly: where appropriate, make contact the same day, even if you cannot share every detail yet.
• Be factual and calm: explain the risk that staff were responding to and what action was taken.
• Offer next steps: confirm how the incident will be reviewed and how the family can share information that may help prevention.

CTA: If your incident communication often feels reactive, consider building a short “parent contact checklist” into your process so every call covers safety, learning and support.

What to avoid

• Speculating about motives or making clinical claims.
• Over-sharing information about other pupils or staff.
• Using disciplinary language when the pupil was in distress.

Data protection and record access: plan for subject access requests

Incident logs, emails and behaviour records can be requested by pupils or families. The Information Commissioner’s Office explains that there are different routes to access pupil information, including subject access rights under UK GDPR and separate education regulations for education records.

This is another reason to record clearly and professionally: you should assume that what you write may be read outside the immediate staff team. Clear records reduce the risk of misunderstandings and help you apply redaction consistently where third-party information is included.

How to connect recording to prevention and restraint reduction

Recording is not the end of the process. The goal is to reduce the likelihood that physical intervention is needed again. If incidents cluster around the same pupils or contexts, consider a targeted plan that strengthens early intervention, environmental adjustments and staff confidence.

Many schools find it helpful to make restraint reduction a visible part of their learning culture. See our restraint reduction training page for approaches that support prevention and safer outcomes.

Safeguarding, dignity and vulnerable pupils

In some cases, an incident is part of a wider safeguarding picture. Your recording should connect with safeguarding processes without turning the incident log into a safeguarding referral itself. Keep the record factual, then signpost any safeguarding concerns through the appropriate channel.

If you work with younger pupils, ensure your approach fits developmental needs and trauma-informed practice. Our work with children’s services teams often highlights that consistency and calm adult responses are as important as the written record.

Common pitfalls (and how to avoid them)

Pitfall 1: Recording becomes a blame document

If records read like a defence statement, they may lose credibility. Use structured fields that prompt facts, decisions and reflections in that order.

Pitfall 2: Inconsistent thresholds for what gets logged

Agree a clear threshold. For example: any physical guiding that goes beyond ordinary contact, or any situation where a pupil’s movement is restricted, should be recorded.

Pitfall 3: Records live in isolation

Link the incident log to follow-up actions such as risk assessment updates, pastoral support, and training refreshers. This makes records useful for improvement, not just storage.

Citation hooks and where to check the official position

For school leaders, it is useful to periodically cross-check your recording expectations against official guidance. The Department for Education publishes guidance on the use of reasonable force in schools and has updated it ahead of new expectations from April 2026. The Information Commissioner’s Office provides guidance on routes for accessing pupil information and explains how education records differ from wider personal data requests.

Example incident record (what “good” can look like)

Schools often ask what level of detail is “enough”. The aim is to create a record that someone else could understand without being present, while staying proportionate. The example below is deliberately generic, but it shows the structure that tends to stand up well in internal reviews.

Context

• Date/time/location: Tuesday 11:05, corridor outside Year 6 classroom.
• Staff present: class teacher, teaching assistant, senior leader called via radio.
• What was happening: transition from break to lesson; pupil asked to line up.

Lead-up and de-escalation

• Observed risk indicators: shouting, pushing objects off a shelf, moving quickly towards another pupil.
• Steps attempted: clear instruction, offered space to calm, offered choice of two regulated routes to class, asked supporting adult to swap in.

Decision and action

• Why intervention was necessary: staff judged there was an immediate risk of injury to another pupil in a narrow corridor.
• What staff did: one adult positioned side-on, used open hands to guide pupil away from peers and towards an empty room; once in the room, staff released contact when pupil stepped back and breathing/voice remained unrestricted throughout.
• Duration: approximately 15 to 20 seconds of contact.

Aftercare and review notes

• Medical: no injury observed; pupil offered drink and quiet time; staff welfare check completed.
• Reflection: transition was a known pressure point; earlier pre-warning may reduce escalation. Consider adjusting staffing and providing a calm arrival routine.

How long should schools keep incident records?

Retention is often set through your school or trust retention schedule. The practical goal is to retain records long enough to evidence patterns, safeguarding decision-making and learning, without keeping data for longer than needed. If you are unsure, take advice from your data protection lead and align retention periods across incident logs, safeguarding records and staff records, rather than having contradictory timeframes.

Supporting staff after an incident

Recording should not only protect the organisation; it should also support staff. A short, routine debrief helps adults regulate, reduces hindsight anxiety, and improves record quality. Consider including:

• what staff noticed early and what helped (even briefly);
• what they would do the same next time;
• what they would change, including any environmental adjustments needed;
• whether any staff member needs additional support following the event.

FAQ

Should every use of reasonable force be recorded?

As a rule, yes. A consistent threshold protects staff and pupils, supports learning, and reduces disagreement later about what happened and why.

How quickly should parents be informed?

Where appropriate, contact on the same day so families hear a calm account from the school. If more information is needed, explain what will be confirmed after internal review.

What if staff disagree about what happened?

Record separate witness accounts and avoid forcing a single narrative. A short debrief meeting can identify any gaps and confirm agreed learning actions.

What should we do if an incident record includes information about other pupils?

Keep third-party information to what is necessary, and anticipate that information may need to be handled carefully if an access request is made.

How can we use incident data to reduce future interventions?

Look for patterns in triggers, locations and times, and then test small changes. Pair those changes with staff coaching and prevention-focused training.

CTA: If you want to strengthen confidence and consistency, we can help you align training, recording templates and review routines so your process supports safer outcomes for everyone.