Pupil Protect

Free tools

Child protection file transfer checklist

Check when a child protection file must reach the new school, then work through the transfer step by step.

  • Based on KCSIE 2026Paragraph 150 and Annex B, with the IRMS toolkit for keeping a copy. Checked 20 October 2026.
  • Nothing you enter leaves your browserThe checker runs on this page. Nothing is sent or stored.

Find the deadline

Weekends are skipped. Add your holidays and closure days for an exact count.

When is the move?
For an in-year move, we count from this date.
One date or range per line, like 26/10/2026 or 26/10/2026 to 30/10/2026. Bank holidays aren’t included automatically.
Transfer deadline

Enter the date the pupil left to see when their child protection file should reach the new school.

The rule: as soon as possible, and within 5 days for an in-year move or within the first 5 days of a new term (KCSIE 2026, paragraph 150).

Guidance, not legal advice. Your local authority or trust may set its own expectations; follow them too.

The rules

Keeping children safe in education 2026 sets the timescale and how the file should travel. It doesn’t say how to count the days.

As soon as possible, and within 5 days

When a child leaves, the DSL or a deputy should make sure their child protection file is transferred to the new school or college as soon as possible, and within 5 days for an in-year transfer or within the first 5 days of the start of a new term, so the new school can have support in place when the child arrives (KCSIE 2026, paragraph 150 and Annex B).

KCSIE doesn’t say whether these are school days or calendar days. The checker shows 5 calendar days as the date to aim for, moved back to the last school day if it falls on a weekend or closure day, and 5 school days as the latest reading. For a move at the start of a term, it counts the first day of term as day 1.

Separately, securely, with confirmation
For schools, the file goes separately from the main pupil file. The DSL should make sure it travels securely and get confirmation of receipt (paragraph 150). KCSIE doesn’t name a method; schools commonly use a secure electronic transfer, or hand paper files over DSL to DSL.
With a structured summary
New in 2026: the school sending the file should include a clear, structured summary of current safeguarding concerns, relevant context and ongoing support needs, and keep current concerns separate from historic information (Annex B).
The common transfer file runs on a different clock
From a maintained school, the common transfer file and educational record must reach the new school no later than 15 school days after the pupil stops being registered (The Education (Pupil Information) (England) Regulations 2005, regulation 9(3)). The checker shows this date too, for comparison. Don’t wait for it to send the child protection file.
If the new school isn’t known
Follow your local authority’s children missing education procedures and help with reasonable enquiries. Schools must tell the local authority when a pupil’s name is removed from the admission register (KCSIE 2026, paragraphs 221 and 223).
Keeping a copy
The IRMS toolkit says the school a pupil leaves should consider keeping a copy. The new school keeps the file, so it usually ends up with the last school the child attended. Use the retention calculator for review dates.

The transfer checklist

Download for Word (.docx)
Pupil ProtectFree template · pupilprotect.co.uk/tools

Child protection file transfer checklist

School: ______________________________

Confidential: child protection record. Keep this checklist on the child’s child protection file.

For the DSL or a deputy when a pupil with a child protection file leaves. The file should reach the new school or college as soon as possible, and within 5 days for an in-year move or within the first 5 days of a new term (KCSIE 2026, paragraph 150).

Pupil’s full nameDate of birth
Date the pupil left the rollType of moveIn-yearNew term
New school or collegeDeadline to send the file
New school’s DSL (name, phone, email)

1. Before you send it

CheckDoneDateBy whom, and notes
The child protection file is up to date, including the chronology.KCSIE 2026, Annex BDone
A clear, structured summary is written: current safeguarding concerns, relevant context and any ongoing support needs.KCSIE 2026, Annex BDone
The summary separates current concerns from historic information, and gives past issues their context.KCSIE 2026, Annex BDone
Considered whether to share other information before the child leaves, for example if they have had a social worker, receive Channel support, or there are concerns about serious violence or weapons.KCSIE 2026, paragraphs 151 and 152Done
Spoken to the new school’s DSL, where there are issues or concerns.KCSIE 2026, paragraph 152 and Annex BDone
If other agencies are involved, considered who else needs to know about the move.Information sharing duty guidance, paragraph 15Done

2. Sending it

CheckDoneDateBy whom, and notes
Sent separately from the main pupil file and the common transfer file.KCSIE 2026, paragraph 150Done
Sent securely. Method: ______________________ (for example a secure electronic transfer, or handed over DSL to DSL)KCSIE 2026, paragraph 150Done
Sent to a named DSL or deputy at the new school, by the deadline.KCSIE 2026, paragraph 150Done
Asked for confirmation of receipt.KCSIE 2026, paragraph 150Done

3. After sending it

CheckDoneDateBy whom, and notes
Confirmation of receipt received, and kept on file. From: ______________________KCSIE 2026, paragraph 150Done
If no confirmation arrives, chased the new school’s DSL (date and how).Good practiceDone
A record kept of what was sent, how, when and to whom.KCSIE 2026, paragraph 74Done
Decided whether to keep a copy. If kept: stored securely, with a review date in line with your retention schedule.IRMS Information Management Toolkit for SchoolsDone

4. If you don’t know where the pupil has gone

CheckDoneDateBy whom, and notes
Followed the local authority’s children missing education procedures, and worked with it on reasonable enquiries.KCSIE 2026, paragraph 221; Children missing education guidanceDone
Told the local authority when the pupil’s name was removed from the admission register.KCSIE 2026, paragraph 223Done
Where there are safeguarding concerns, told children’s social care, and the child’s social worker if they have one, without delay.KCSIE 2026, paragraphs 219 and 221Done
If the pupil is being home educated, followed the local authority’s elective home education procedures.KCSIE 2026, paragraphs 222 to 225Done
Kept the file securely until the new school is known, then sent it.KCSIE 2026, Annex BDone

5. If you are the receiving school

CheckDoneDateBy whom, and notes
A trained member of staff has reviewed the file, so key risks and needs are understood.KCSIE 2026, Annex BDone
Asked the old school for clarification if anything is unclear or incomplete.KCSIE 2026, Annex BDone
Key staff such as the SENCO know what they need to; the DSL has decided what else to share, and when.KCSIE 2026, paragraph 150 and Annex BDone
If the pupil has carried, threatened with or used a weapon, a risk assessment and safety and support plan are in place before they arrive.KCSIE 2026, paragraph 152Done
Confirmed receipt to the old school.KCSIE 2026, paragraph 150Done

Sign-off

DSL or deputy (name)Signature
Date completedRetention review date for any copy kept

Based on Keeping children safe in education 2026 (DfE, statutory guidance, in force from 1 September 2026), paragraphs 150 to 152, 221 to 225 and Annex B; the Children missing education guidance; and the IRMS Information Management Toolkit for Schools. Checked 20 October 2026. Free template from Pupil Protect: pupilprotect.co.uk/tools. Guidance, not legal advice.

Record transfers in Pupil Protect Safeguard

Safeguard moves a pupil’s safeguarding file between Pupil Protect schools through Record transfers, and every step is logged. A request not dealt with in 5 school days is overdue. For schools not on Pupil Protect, the file goes by a secure link that works for 30 days, and the receiving DSL confirms receipt there.

See record transfers in Safeguard

Questions about transferring files

How long does a school have to transfer a child protection file?

Keeping children safe in education 2026 says as soon as possible, and within 5 days for an in-year transfer or within the first 5 days of the start of a new term (paragraph 150 and Annex B). It doesn’t say whether these are school days or calendar days, so the safest course is to count calendar days.

Is it 5 school days or 5 working days?

KCSIE 2026 just says “5 days”. It doesn’t define them. This tool shows both readings: 5 calendar days as the date to aim for, and 5 school days as the latest. The rule is “as soon as possible”, so don’t wait for either.

Should the child protection file go with the common transfer file?

No. For schools, KCSIE 2026 says the child protection file should be transferred separately from the main pupil file (paragraph 150). The common transfer file and educational record from a maintained school have their own deadline: no later than 15 school days after the pupil comes off roll.

What if we don’t know which school the child has gone to?

Follow your local authority’s children missing education procedures and work with it on reasonable enquiries (KCSIE 2026, paragraph 221). Tell the local authority when you remove the pupil from the admission register (paragraph 223). If there are safeguarding concerns, tell children’s social care. Keep the file securely and send it once the new school is known.

Should we keep a copy of a transferred child protection file?

The IRMS toolkit says the school a pupil leaves should consider keeping a copy. If you do, store it securely and review it in line with your retention schedule. The original goes to the new school, which then keeps it.