After a bullying concern, compare each attendance session with the actual arrival or departure, the reason recorded, the safety arrangement and its delivery. Keep the register accurate while checking what education and protection the pupil received. An authorised adult must resolve discrepancies and own the next action. A session mark can't establish that the pupil stayed all day, felt safe or received agreed support.
This reconciliation method is for attendance, pastoral and inclusion leaders, DSLs and SENCos in England. It isn't a coding shortcut or permission to shorten a pupil's education. Follow the school's safeguarding policy immediately where there is a concern: speak to the DSL or deputy without waiting for a data review. Use emergency services for immediate danger and the appropriate local safeguarding route when required.
Start with one day and five separate entries
Choose a day that needs clarification. The attendance lead coordinates the record check; the DSL owns safeguarding decisions. Agree who contacts the family and who checks support delivery. Those responsibilities can sit with different adults. Keep access within each person's role and leave sensitive narrative in its restricted source record.
- Session evidence. Read the morning and afternoon marks, registration times and supporting information. Identify the source and any unresolved correction. Don't translate a percentage into a claim about hours of education.
- Departure evidence. Record the confirmed departure time, who arranged it and the attributed reason. Distinguish a family request, a school request and an account that hasn't been confirmed. An office entry saying collected doesn't explain why the collection happened.
- Education expected and received. Check the timetable and what learning was available after departure. Separate an agreed arrangement from an improvised response. Record a gap honestly; don't infer provision from a plan or an email attachment.
- Protection and access. Identify the arrangement promised for the relevant time, the responsible adult and evidence of delivery. A staffed safe space, accessible reporting route or supported transition needs confirmation from the people involved. An allocated task doesn't establish delivery.
- Decision and review. Record the question that remains, who will answer it and when. Keep the register decision, support decision and safeguarding decision distinguishable. Note who has acknowledged each handoff and how unresolved actions will be escalated.

Two records can agree and still leave a question
The following day and records are entirely invented. They describe no pupil, school or customer. A pupil has a present morning mark and an office entry recording collection before lunch after a reported peer incident. The afternoon mark records absence. The family says staff asked them to collect; an internal note calls the departure a family choice. Neither account should silently replace the other.
The attendance lead checks the session evidence and asks the relevant staff member to clarify who requested collection. The pastoral lead checks the safety arrangement: a supported lunchtime transition was planned, but staff cover hasn't been confirmed. The professional question now includes whether agreed protection was available and how the pupil can access education safely. Attendance data alone didn't supply that question.
Offer the pupil a private conversation with a trusted adult using their established communication method, processing time and support. Ask what they experienced, what remains difficult and what would help them reach an adult. Record uncertainty or disagreement. Don't ask them to investigate peers or prove the report. Seek parent or carer knowledge where safe, relevant and lawful, following the DSL's communication decision.
For this invented review, the attendance lead checks the register evidence that day. The pastoral lead confirms adult cover before the next lunchtime, and the DSL reviews safeguarding actions through the school's procedure. The team agrees a next-school-day check with the pupil and family on access and delivery. New harm, missing protection or another unplanned departure brings action forward. These are suggested review arrangements, not statutory deadlines.
The record doesn't establish that bullying caused the absence, explain the pupil's intentions or demonstrate that a support measure worked. It can't diagnose a need, predict future absence or select a sanction, referral or placement. Differing accounts need attributable clarification and professional judgement. A quieter incident log doesn't establish safety.
A code can't authorise a reduced timetable
The DfE attendance guidance limits temporary part-time timetables to very exceptional circumstances in the pupil's best interests; they mustn't be used to manage behaviour. They require agreement, review and an intended end point. C2 applies only where its criteria are met. It isn't a general mark for leaving early after a concern.
Have the attendance lead apply chapter 8 to the established session facts. Keep departure details alongside the register. Don't retrospectively create an agreement to make the records look consistent. The register-mark guide covers the broader coding check.
A school mustn't use collection as an informal exclusion, even with parental agreement. Suspension and permanent exclusion have formal procedures and distinct consequences; neither is equivalent to lesson removal or a managed move. If staff asked a pupil to leave, leadership must examine the actual decision and lawful route. Don't hide it under a convenient attendance label.
The Equality Act advice for schools and Equality Act 2010 inform reasonable-adjustment duties. The SEND Code of Practice supports reviewing needs and provision with pupil and parent participation. SEND doesn't excuse harm, and disciplinary action doesn't remove equality, SEND or safeguarding responsibilities. This method isn't legal advice.

Close the discrepancy without closing the concern
Finish with separate outcomes: the register entry and reason for any correction; the safety or support action and its owner; and the evidence still missing. A coding correction doesn't resolve a bullying concern. Follow Keeping children safe in education 2026 and local safeguarding procedures. Keep safeguarding and disciplinary processes distinct, coordinating authorised adults where both apply.
In Student Radar, Attendance Analytics can support attendance review, while Safeguard supports authorised concern work where enabled. Staff must still inspect the relevant source records and decide what follows. This isn't a claim of automatic reconciliation, unrestricted access or a system choosing an attendance code.
Use the protective-arrangements review for the ongoing safety task. For this record check, take one unresolved day to the responsible adults, agree what must happen before the next relevant session and record when you will check delivery.
Sources
- DfE: Working together to improve school attendance, July 2026 edition, paragraphs 65 to 70 and chapter 8.
- DfE: Keeping children safe in education 2026, publication page updated 17 November 2026.
- DfE: Suspension and permanent exclusion guidance, effective 26 July 2026.
- DfE: Equality Act advice for schools, May 2014 advice; publication page updated 28 June 2018.
- DfE and DHSC: SEND Code of Practice, January 2015 code; publication page updated 12 September 2024.
