Review a school behaviour policy before September by testing how it could fail in practice. Check whether expectations can be taught, routines can be used and staff responses are feasible.
Support must be accessible. Decisions must remain human, lawful and reviewable.
Use recent patterns, staff experience, pupil and parent or carer views, and current support information as prompts for enquiry. Do not turn them into a score, diagnosis or automatic sanction.
This guide is for schools in England and is accurate on 9 August 2026. It is not legal advice. Follow current statutory guidance, local safeguarding procedures and your school's approved governance route.
Why run a behaviour policy pre-mortem now?
A pre-mortem asks a calm question before launch: imagine the policy unravels in September. What made it hard to teach, use or review, and what could the school change while there is still time?
The Department for Education's behaviour guidance asks leaders to build a clear whole-school culture. Its audit tools examine leadership, systems, relationships, staff development, transition and pupil support.
That makes this more than a wording exercise. A policy can be immaculate in a PDF and still become surprisingly shy when the corridor fills. The useful test is whether people can enact it in ordinary, pressured moments.
The headteacher remains accountable for the policy. A behaviour or inclusion lead can own the pre-mortem, with the SENCo, DSL, staff, pupils and governors contributing within their roles.
An eight-part school behaviour policy review checklist
Keep the sample purposeful. Start with aggregated or de-identified patterns, then allow only authorised staff to open individual records when a defined professional question requires it.
| Failure mode | Evidence to test | September repair |
|---|---|---|
| 1. Expectations are vague | Staff and pupils describe the same routine differently | Write observable steps and model them in the real setting |
| 2. Routines cannot be taught | Transitions rely on assumed knowledge or long verbal instructions | Plan practice, prompts, accessible formats and re-teaching |
| 3. The response is not feasible | The named room, adult or follow-up is often unavailable | Create a safe fallback and tell staff who owns it |
| 4. Context disappears | Records describe a label or judgement instead of an observable event | Separate what happened, context, response and uncertainty |
| 5. Support is hard to access | Agreed adjustments or strategies are not usable at the point of need | Test availability, staff knowledge and an alternative route |
| 6. Voices are missing | Pupil, staff or parent or carer accounts are absent or flattened into agreement | Record views, differences, missing evidence and access needs |
| 7. Escalation becomes automatic | A count, flag or prior response appears to decide the next sanction | Require an authorised person to review facts, policy and circumstances |
| 8. Nobody reviews the repair | Actions lack an owner, date or evidence that would change the decision | Name the owner and review after ten school days and at half-term |
Test whether expectations are teachable and accessible
Choose three high-friction moments, such as arrival, lesson transition and social time. Ask a member of staff to explain the routine, show how it is taught and identify the response when the usual plan is unavailable.
Then ask pupils to explain the same routine in an accessible way. Offer speech, symbols, drawing, AAC, a scribe or a quieter setting. The aim is understanding, not a memory test with unusually high stakes.
Record uncertainty and disagreement. If a pupil describes a barrier that staff did not expect, treat it as evidence to explore, not proof of motive, disability, poor parenting or a settled account of every event.
Invite parent or carer knowledge where relevant and lawful. Ask what helps, what changes the situation and what has been misunderstood. Do not imply agreement, or make one account carry more certainty than it can support.
Follow the evidence across records
Consider a fictional composite example. A school's policy expects a quick corridor transition, while aggregated records show more incidents near one route. Staff feedback says the area becomes crowded after lunch.
Accessible pupil feedback adds that instructions are hard to hear there. Support records show that some pupils use visual prompts, but the prompts are kept inside classrooms rather than at the transition point.
The pattern does not prove why any pupil acted, or that one support step will solve every event. It changes the professional question: is the school teaching and supporting this expectation in the place where it must be used?
The behaviour lead owns a two-week trial of clearer positioning, an accessible prompt and a staffed fallback route.
Staff record only the minimum factual information needed. The lead reviews delivery, pupil views and incident patterns after ten school days.
Keep safeguarding, SEND and exclusion decisions in their proper lanes
Behaviour information can sit beside safeguarding information, but a policy audit must never investigate a disclosure, decide whether a pupil is telling the truth or delay action under the school's current safeguarding policy.
If information may indicate abuse, neglect, exploitation, child-on-child harm, self-harm or another concern, take it to the DSL or deputy without delay. Use the appropriate emergency or local safeguarding route where danger is urgent.
Schools must also consider disability and reasonable adjustments where the Equality Act 2010 applies. Review SEND, communication, sensory, health, attendance and provision context without assuming that any one factor explains the behaviour.
SEND does not excuse harm to others, and a sanction does not remove the need to consider adjustments, proportionality, safeguarding information and individual circumstances.
The Cheam reasonable-adjustments guide explains that legal boundary in more detail.
A suspension or permanent exclusion is a formal decision under current England guidance. It must not be triggered automatically by a pattern, described as support, or replaced by an informal request to stay at home.
What behaviour data cannot prove
Counts and clusters can show where to look. They cannot prove intent, cause, disability, parenting, truthfulness, safety, future behaviour or the correct sanction, referral, placement or statutory outcome.
Staff accounts are evidence; it is not neutral camera footage. Pupil and family views may differ from them. Preserve the source, distinguish observation from opinion and state what information is missing.
Apply data minimisation. Keep only adequate, relevant information needed for the stated review purpose. Avoid copying sensitive free text into a policy audit or creating a new spreadsheet of identifiable incidents.
Where Student Radar fits
Student Radar's Behaviour Analytics lets authorised leaders compare time windows and review whole-school patterns by time, location and group before opening detail where it is needed.
Behaviour Playbooks keeps practical support strategies available for staff to use and review. Neither feature diagnoses a pupil, decides a sanction or replaces professional accountability.
The useful connection is modest: compare the policy expectation with observed patterns, staff implementation, pupil context and the support actually available. Then let an identified professional decide what to test next.
Seven actions before pupils return
- Name the headteacher or delegated behaviour lead as owner of the pre-mortem.
- Choose three routines and test them in the settings where they will be used.
- Ask staff, pupils and parents or carers focused, accessible questions.
- Check reasonable adjustments, SEND support and safeguarding routes with the right leads.
- Remove automatic escalation from data, wording and staff scripts.
- Brief staff on the routine, fallback, recording standard and decision authority.
- Review delivery after ten school days, then again at half-term.
Start with one routine and one accountable review. For a closer look at connected patterns and support, explore the pastoral and behaviour workflow or request a focused Student Radar walkthrough.
Sources and further reading
- Behaviour in schools, Department for Education, updated 19 February 2024.
- Creating a school behaviour culture: audit and action planning tools, Department for Education, published 25 April 2024.
- Equality Act 2010: advice for schools, Department for Education, updated 28 June 2018.
- SEND code of practice: 0 to 25 years, Department for Education and Department of Health and Social Care, updated 12 September 2024.
- School suspensions and permanent exclusions, Department for Education, statutory guidance effective 26 July 2026.
- Keeping children safe in education, Department for Education, updated 7 July 2026. The 2025 edition applies until 31 August 2026; the 2026 edition applies from 1 September 2026.
- Principle (c): data minimisation, Information Commissioner's Office, accessed 9 August 2026.