What a chronology is, and why the guidance insists on it
Newcastle Safeguarding Children Partnership’s practice guidance gives the definition most partnerships use: “Chronologies are a record of key events, in sequential order. Events that are significant for the child could be positive or negative. Chronologies are fundamental to good practice as they improve understanding and insight into individual cases including the child’s lived experiences and cumulative harm.” They are “an essential analytical and reflective tool that should be used in assessing, planning, working with families, understanding, and responding to cumulative harm … and in evidence-based decision making”, and “the chronology of the child’s significant events should also be a reliable ‘go to place’ for practitioners and managers who need to get a quick understanding of the child’s experiences and harm”.
The reasons the guidance gives are the reasons reviews keep finding. A chronology “shows the child’s lived experiences and family history”; “shares information that might otherwise not be known by other agencies”; “helps identify gaps”; “helps to prevent significant information becoming ‘lost’ within records”; “supports the practitioner and family to identify and make sense of what we are worried about, patterns, themes, cycles, increases or decreases in events or behaviour”; “makes it easier to identify the build-up of harm/cumulative harm”; and helps everyone “understand the frequency, severity, first, worst, and most recent harm”. Working Together to Safeguard Children 2026 makes the same point about the system as a whole: information sharing “is also essential for the identification of patterns of behaviour” (paragraph 31), and a pattern is a chronology someone has read.
There are two kinds. The single-agency chronology is the one a school, a youth charity, a GP practice or a care provider keeps about a child or an adult from its own records. The multi-agency chronology is compiled by the lead practitioner – usually the social worker – from every agency’s contributions once a child is subject to a child in need plan, a child protection plan or a review; Newcastle’s guidance is explicit that “it is the responsibility of the lead practitioner to create the chronology and the responsibility of partner agencies to contribute relevant and succinct information directly and regularly to be included”. The single-agency chronology is what makes that contribution possible; an organisation that has to build one from scratch when asked contributes late and incompletely.
What counts as a significant event, and what does not
The hardest judgement in a chronology is what to leave out, and the guidance gives the test: “Does this decision, event, occurrence, or omission hold significance for the child, why and what is the impact or potential impact on them, positive or negative, and how do we know this?” Newcastle’s illustrative list of significant events includes births, bereavements and deaths, a safeguarding referral, a child becoming a young carer, a change of address, GP or school, a change in the parents’ relationships, a domestic abuse incident, worrying or positive weight change, “when a child tells you or someone else something that is a safeguarding concern”, urgent care attendances and hospital admissions, chronic or significant illness in the child or a carer, and events like a pandemic lockdown that affect the family. For a school the list also includes exclusions and suspensions, prolonged absence, missed medical appointments, a disclosure, a bruise or injury noticed and whether it was explained as accidental, a child-on-child incident, a change in behaviour or presentation, signs of neglect or emotional abuse, a parent’s disclosure or request, the involvement of another agency, and the outcome of each referral and the actions taken. The entry is about the individual child or young person – their welfare and wellbeing – not about the school’s process. For an adult at risk in a care setting it includes falls and injuries, hospital admissions, changes in capacity, safeguarding concerns and enquiries, changes in who visits and who handles money, and the person’s own expressed wishes.
What does not belong: “Don’t clutter the chronology of the child’s significant events with processes, routine information and insignificant events that detract and hide what is important to know.” A chronology “will include some but not all processes such as Strategy Meetings, Team Around the Family meetings … Remember to include the ‘person centred’ part, which could be the reason the meeting was needed, the decisions made, following actions and the impact on the child.” The test the guidance offers for the difference is that a chronology is “fundamentally different from case notes, or an ‘audit’ chronology”: it “tells the story of the child and family, not of the agencies working with them”, and it “can be used as an ‘index’” that points to the detail in the case record rather than repeating it.
Positive events are in scope on purpose. The guidance asks for a chronology that “identifies existing safety as well as worrying events” and “provides evidence of change (or lack of change) over time”, because a plan built only on harm cannot see what is working.
The format: the columns and the rules for filling them
A chronology is a table, and most partnerships publish a chronology template; Swindon’s and Darlington’s are typical. Whatever the template, keeping it up-to-date is the discipline: the DSL or lead practitioner should update it as each event is known, not collate it later, and should use professional judgement about what to highlight rather than record everything. The columns that every workable version has:
- Date of the event – the date it happened, not the date it was recorded. Newcastle’s rule: “Enter event as the date they happen on (and put when and how they were first reported/first known about in brackets). If the actual date of the significant event is unknown, use the 1st of the month and explain in the details.”
- The event, in a sentence or two of plain language: what happened, to whom, who was present, in the child’s or adult’s own words where there are any. “Written in plain language with no abbreviations, or these are explained in the first instance they are used.”
- Source – who reported it and where the full record is (the case note, the concern form, the referral, the letter), so the chronology works as an index.
- Action taken and by whom – the referral, the conversation with the parent, the decision not to refer and the reason.
- Impact or significance – why this matters for the child or adult, positive or negative, and the emerging picture it contributes to; this is the column that makes the document analytical rather than clerical.
- Entered by and date entered, so the record shows who knew what and when.
And the rules for the whole document, from the guidance: events “in the order they happened, not in the order they came to professional attention”; “up to date, accurate, use straightforward language that is non-blaming and succinct”; started early – “starting a chronology of the child’s significant events should be one of the first actions for both emergency and non-emergency cases” – and built in both directions, “backwards by adding in historical events as you learn about them … and forwards by adding new events as they happen”; and subject to professional review: “chronologies cannot be automated or treated as an administrative task or something that is done at case closure”. The factual standard is the one Keeping children safe in education sets for every safeguarding record: “clear, factual, and distinguish between observed concerns, professional opinion, and historic information.”
Who keeps it, in each setting
Schools and colleges. The designated safeguarding lead, as part of the child protection file KCSIE Annex B requires, which should contain “a clear and comprehensive summary of the concern, details of how the concern was followed up and resolved, and a note of any action taken, decisions reached and the outcome”. The chronology is the front sheet of that file and the document that makes the 2026 transfer rule workable: when a child moves, KCSIE says the exporting school should transfer the file as soon as possible: within five days for an in-year transfer or within the first five days of the start of a new term and “include a clear, structured summary identifying current safeguarding concerns, relevant context, and any ongoing support needs”, taking “particular care … to distinguish between current safeguarding concerns and historic information”, because “where a file contains extensive historical information, a concise summary of current risk and relevant context is likely to support more effective safeguarding than the transfer of unstructured records alone”. An up-to-date chronology supports that summary, but the receiving school still needs a clear account of current risks, relevant context and ongoing support needs.
Charities, youth groups and sports clubs. The safeguarding lead, in the child’s separate child protection file, from the concern records the NSPCC’s guidance describes, and contributed to the multi-agency chronology when the local authority asks. A small organisation rarely sees the whole picture of a child’s life, which is exactly why its dated record of what it did see matters to the agency that does.
Care providers. For an adult at risk, the registered manager or the safeguarding lead, alongside the care record Regulation 17 requires; in a section 42 enquiry under the Care Act 2014 the provider’s chronology of falls, injuries, concerns, capacity decisions and contacts is the enquiry’s starting point, and the Care and Support Statutory Guidance’s instruction to “look beyond single incidents or individuals to identify patterns of harm” is a chronology by another name.
Children’s social care. The allocated social worker owns the multi-agency chronology and, in Newcastle’s words, should “have ‘updating child’s chronology’ as an agenda item for Core Groups, Team Around the Family meetings and Care Team Meetings”, asking “other professionals, the child and family if they know something significant to add”. In every setting the chronology is reviewed in supervision – it “is useful in supervision and can act as a summary of events to facilitate review, reflection, and work out what might be going on and why” – and it is the “starting point for internal and external auditing” and “a legal requirement for some cases”, including care proceedings.

How it is used: assessment, transfer, reviews and the courts
A chronology does not decide anything; it makes decisions possible. “A chronology doesn’t give you all the answers for your analysis, but gets you asking some of the right questions.” In assessment it front-loads the history so that the practitioner is “better prepared” and “better able to challenge (but not pre-judge) and to be curious”; in planning it shows “frequency, severity, first, worst, and most recent harm”; in a strategy discussion it is the shared account every agency reads before the meeting; in supervision it is the document the manager and the practitioner reflect on together.
At transition it is the document that travels: KCSIE’s structured summary at transfer, the handover from a primary to a secondary school, the referral from a charity to children’s social care, the care home’s account to the hospital. In reviews – a rapid review or child safeguarding practice review under Working Together, a safeguarding adults review under the Care Act – the first request to every agency is for its chronology, and the review’s findings are, in large part, a reading of the merged chronologies against what each agency knew at the time. In care proceedings and in the criminal courts a chronology is disclosed and tested; the guidance’s insistence on events “in the order they happened” with the date first known in brackets is what allows a court to see both what happened and when the organisation could have acted.
Which is why the chronology has to be contemporaneous. A chronology that is accurate because it was reconstructed from case notes at the end is evidence of good filing; a chronology that was kept as events happened is evidence that someone was watching the pattern form.
The events that only ever existed in messages
Look again at the list of significant events and ask where each one first became known. “When a child tells you or someone else something that is a safeguarding concern”: the child told a teaching assistant on the playground, and the teaching assistant told the class teacher in a message at half past three. The bruise was noticed by a lunchtime supervisor and mentioned in the staff group chat. The parent’s disclosure came as a text to the family support worker’s personal phone. The change in presentation that three members of staff each noticed was discussed between them, by message, before anyone told the DSL. In a care home the fall at two in the morning was reported to the on-call manager by text and the escalation and subsequent care arrangements were discussed in the reply.
The chronology’s date column asks for the date the event happened and, in brackets, when it was first known. For most of the events above, the honest bracket would read “first known by a member of staff on a personal phone, on a date the organisation cannot verify, in words it cannot produce”. The event enters the chronology when it reaches the DSL or the manager and is written down, which is later, and shorter, and in someone else’s words. The frequency, severity and “first, worst, and most recent” the guidance asks the chronology to show are built from those entries, and the gap between when something was first noticed and when it was first recorded is invisible to every review that later reads it. The organisation cannot close the gap afterwards: the messages are in apps it does not run, on handsets it does not own, and it needs a lawful, proportionate process for obtaining relevant work messages while protecting unrelated personal information.
Use a restricted reporting route, with access limited to the people who need the information. A recorded message is not proof that someone has read or acted on a concern: follow the safeguarding procedure, contact the responsible person directly when action is urgent, and use the local authority or emergency route when required. Add the relevant information and decisions promptly to the formal safeguarding record.
The remedy is not to forbid staff from telling each other what they noticed; that is the culture of listening every review asks for. It is to give those first tellings a channel the organisation runs, reachable from a personal phone on a playground or a night shift, where the DSL or the manager is in the conversation from the first message, where everyone in it has been told it is on the record, and where the date, the time and the words are kept as they happen and can be entered in the chronology as they were. The question for the safeguarding lead is simple: for the last five events on the chronology, how many were first known in a message the organisation could not now produce?
Official guidance and your next step
The practice guidance quoted above is Newcastle Safeguarding Children Partnership’s guidance on chronologies; most local safeguarding children partnerships publish their own version and a template, and yours is the one to use. The statutory frame is Keeping children safe in education 2026 (Annex B on the child protection file and its transfer), Working Together to Safeguard Children 2026 (information sharing and reviews), the NSPCC’s child protection records retention and storage guidelines, and, for adults, chapter 14 of the Care and Support Statutory Guidance.
This guide is a summary of published guidance for England, not a substitute for it and not legal advice. Chronologies for care proceedings follow the Public Law Outline and the court’s directions; take advice on those.
Then do one thing: take one open child protection file, read its chronology, and for each of the last five entries write in the margin how the organisation first learned of the event. That margin is the record you do not have.
We build ComplyChat for the work conversations organisations need to keep. The organisational archive described here is available on paid plans, with a connected Microsoft 365 tenant and retention configured by the organisation. A chronology is only as good as the first telling of each event, and that is what ComplyChat is for: a channel the organisation owns, on a compatible phone including a personal one, on the record from the first message with everyone in it told so, filing into the organisation’s own Microsoft 365 once the tenant is connected and kept under its own retention rules, so that the date, the time and the words of the first concern are there when the chronology is written and for as long as the file is kept. Families, volunteers and visiting professionals join as guests without an account on your systems. It is not a case-management system and does not keep the chronology; it keeps the conversation the chronology is built from. A member of staff’s own messages stay in their own apps. There is no WhatsApp, Signal or Meta anything in the path.
How it works · Why us · Pricing · FAQ



