How to write a safeguarding chronology that holds up

A safeguarding chronology is a list of the key events in one child's file, in date order. Each line is short, and together the lines tell a reader what happened, when, and what the school did next.

As the designated safeguarding lead (DSL), you hold the full detail in concern forms and meeting notes. The chronology sits on top as a map, so a deputy, a new DSL or an outside agency can read it in minutes.

One small event may mean little on its own. Ten small events in date order can show a pattern that nobody saw in the moment. The International Taskforce on Child Protection (ITFCP) says in its 2025 record-keeping briefing that seeing patterns over time is key to spotting and answering concerns.

Keeping children safe in education (KCSIE) 2026 is England's statutory guidance. It says schools should record all concerns, discussions and decisions in writing, with the reasons. Many international schools use it as a reference, so check your local law and your own policy too.

A chronology records action and never replaces it. If a child is in immediate danger, call local emergency services first. Follow your school's child protection procedure and tell the DSL the same day.

Use the same fields in every entry, so the list is easy to scan and easy to compare across weeks. Keep each entry to a few lines and point to the full record for the detail.

Use the date the event happened, even when you write the entry later. If you add an entry late, say so in the entry and give the date you wrote it. The ITFCP briefing lists dating an incident with the day it was entered as a mistake to avoid.

Write dates the same way every time. A school with staff from many countries will read 03/04 in two different ways, so spell out the month.

• Date of the event, written in one clear format such as 14 Mar 2026.
• Time and place, if they matter, such as 08:40 at the front gate.
• What happened, in plain words: what was seen or heard.
• Who was involved or present, with full names and roles.
• Source: who told you, and where the full record is kept.
• Action taken, by whom, and on what date.
• Next step and review date, if there is one.

Write what you saw, heard or did, and leave out what you think it means. KCSIE 2026 says safeguarding records should be clear and factual, and should separate observed concerns, professional opinion and historic information.

Sometimes an opinion belongs in the record. The National Society for the Prevention of Cruelty to Children (NSPCC) says to mark it as opinion, name whose opinion it is, and record their exact words.

Use the child's own words in quotation marks, and do not swap them for polite or technical terms. The ITFCP briefing asks schools to avoid euphemisms and to explain slang or idioms.

If the child spoke another language, write their words in that language and add a translation, and note who translated. This matters in a school where staff and students speak many first languages.

• Instead of "seemed upset", write "was crying at the gate and said, 'I do not want to go in.'"
• Instead of "has a nasty bruise", write "bruise about 4 cm across on the left forearm".
• Instead of "is neglected", write what you saw: "arrived without a coat or lunch on three days this week".
• Instead of "disclosed abuse", write the child's exact words and the question you asked.
• Instead of "parent was aggressive", write "parent raised their voice and said, '...'; the meeting ended at 15:10".

The three sample entries below are made up to show the format and the tone. They are not from a real case.

A reader who was not there can follow each one. None of them guesses at a cause, and each one ends with an action or a review date. Compare them with the last entry you wrote.

• 3 Mar 2026, 08:40, front gate. Form tutor saw Student A arrive without a coat. Student A said, "I was cold all night." Source: concern form 12. Action: tutor told the DSL at 09:10.
• 3 Mar 2026, 14:00, by phone. DSL called Parent 1. Parent 1 said the heating at home broke last week. Source: DSL call note. Action: DSL asked the form tutor to log each morning arrival.
• 6 Mar 2026, 09:00. DSL decided to monitor and review on 20 Mar. Deputy DSL agreed. Reason: see decision note 4. Action: review date set.

Add anything that changes what you know or what the school does. A short shared list helps your team agree on what counts, and the list below is a starting point.

Link to the full record instead of copying it. An entry that says "see concern form 12" keeps the chronology short enough to read in one sitting.

• Concerns and disclosures, including small ones.
• Conversations, meetings and calls with the child, parents, staff or agencies.
• Information you shared or received, with whom, and why.
• Referrals to local agencies, and their replies.
• Decisions, including a decision to take no further action, with the reason.
• Safety plans, risk assessments and review dates.
• Good news, such as a calmer week or a trusted adult who helped.

Most of these errors are easy to fix once you can see them, so check your last ten entries against the list below.

If you find an old error, add a dated correction and leave the first entry as it was. The record then shows what the school knew at each point.

• Dating the entry with the day you typed it instead of the day the event happened.
• Writing a label such as "neglect" or "grooming" with no facts behind it.
• Using gentle words that hide what was said or seen.
• Leaving out decisions, especially a decision to wait.
• Copying whole forms into the chronology until nobody reads it.
• Using initials or nicknames that only the writer understands.
• Catching up at the end of term instead of adding entries as events happen.

The DSL or a deputy usually owns the chronology, and anyone can supply the facts. Ask staff to send concerns the same day so you can add the entry while memory is fresh.

Keep one chronology per child, in the same secure place as the child protection file. Only people who need it for the child's safety should have access. Keep it out of email threads and personal chat apps.

Concerns about an adult need extra care. The ITFCP briefing says a child's file should not hold identifying details of an adult conduct concern, so note that the child raised something and point to the separate record. The process is in managing allegations against staff.

Data protection and retention rules differ by country, so ask local counsel or your child protection authority. Log each act of information sharing as an entry too.

KCSIE 2026 asks for the file to move within 5 days for an in-year transfer, with a short summary of current concerns, so a clear chronology makes the handover easier. The steps are in moving schools and transferring records.

Set a regular check, such as monthly for open cases and once a term for closed ones. Look at the dates first, because a gap can mean a missed entry or a missed follow-up.

Run this short check on each chronology, and again before a transfer, a referral meeting or an accreditation visit. A reviewer can then follow what the school did and why. The wider habit is covered in how to record a safeguarding concern.

• Is every entry dated with the day the event happened?
• Can a stranger tell who did what, and when?
• Are opinions labelled, with the name of who holds them?
• Does every action have an outcome or a review date?
• Does each entry point to the full record?
• Is the chronology stored securely, with access limited?