A SEND chronology should do one job well.
It should let the next adult in the room understand what happened, what changed, and what still needs doing.
If it does not do that, it becomes another file with dates in it.
That is the real problem with chronologies in schools. They often start with good intentions and then drift into a pile of meeting notes, copied emails, and half-helpful summaries that no one opens again.
A useful chronology is shorter than people expect. It is current, ordered, and written for action.
The short version
A good SEND chronology keeps the key dates, the main decisions, the support that was tried, the family’s view, and the next action in one place. It should be quick to scan, easy to update, and clear enough that a new member of staff can use it without asking the same questions all over again.
That matters because SEND support is not static. Needs change, staff change, families move, and priorities shift through the year.
If the chronology does not keep pace, the school ends up relying on memory. Memory is helpful, but it is not a system.
What a SEND chronology is for
A chronology is not the same as a pile of notes.
It is a working record that shows the sequence of events and the school’s response.
Used well, it helps with:
annual reviews
SEN Support planning
parent meetings
handover between staff
complaints and challenge
transition between year groups or settings
In other words, it reduces the amount of story-building the next person has to do.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. That makes the chronology easier to maintain because the live record is not split across half a dozen places.
What to put in it
You do not need every detail.
You need the details that explain the school’s decisions.
A good chronology should include:
the date
the event or conversation
the concern raised
the support that was offered or changed
the family’s view
the pupil’s view, where relevant
who owns the next action
the review date or follow-up date
If the chronology is about a pupil with an EHCP, SEN Support, or a fast-changing need, this structure gives the school enough clarity to act without reopening old questions.
A simple format
A lot of schools find this format easiest:
Date What happened.
So what? Why it mattered.
Next step Who is doing what, by when.
That is enough to keep the chronology readable.
What to leave out
Chronologies go wrong when people try to make them do everything.
Leave out:
duplicate copies of the same email
long extracts that no one will read again
vague phrases like “ongoing support” without detail
every minor observation that does not change the plan
notes that belong in a separate document
If the chronology becomes a dumping ground, staff stop trusting it.
That is when they go back to hunting through inboxes and old files instead.
How to keep it current
A chronology only works if it stays live.
A sensible rule is to update it soon after a meeting, call, or decision. If the school waits until term ends, the chronology starts to behave like a history project rather than a working tool.
1. Update it while the event is fresh
Write the note when the conversation is still fresh enough to be accurate.
If that is not possible on the same day, do it as soon as possible after.
2. Use the same fields every time
Consistency matters more than clever formatting.
If one entry has a date, a support note, and a follow-up, every entry should have a date, a support note, and a follow-up.
3. Keep one owner
One person should be responsible for the chronology.
That does not mean only one person contributes. It means one person makes sure the chronology stays clean, current, and complete.
4. Link it to the live plan
The chronology should not float on its own.
It should sit alongside the current SEN Support Plan or the current summary record so staff can move from the timeline to the action without guessing which document is current.
5. Archive the dead weight
Old working notes should not hang around forever.
If they no longer add value, archive them under policy so the live chronology stays readable.
Why schools struggle with this
Most schools do not struggle because they lack information.
They struggle because the information is fragmented.
A chronology in one folder, the current plan in another, parent emails in a personal inbox, and meeting notes in a shared drive is not a system. It is a search problem.
That is why people say things like, “I know the answer is somewhere.”
A chronology should remove that sentence from school life.
MeritDocs helps schools run this properly by keeping SEND documents in one place, with current information easier to find, review dates visible, and exports straightforward. The real gain is not just speed. It is a record people can actually trust when they need to act quickly.
A practical example
Imagine a Year 6 pupil whose support changed after a move in staff and a difficult spring term.
A weak chronology might say:
meeting held
parents concerned
some support discussed
review to follow
That is not much use.
A better chronology would say:
date of the meeting
the specific concern raised
what support had already been tried
what changed after the review
what the family asked for
who was responsible for the next step
when the school would check back
That version gives the next teacher or SENCO something real to work with.
Why this matters for handover
Chronologies often get tested at the worst possible moment.
A SENCO leaves. A class teacher changes. A pupil moves year group. A parent asks what has been done already.
If the chronology is useful, the handover is calmer.
If it is not, the school starts from zero.
That is expensive in time and tiring for families.
The point is not to write more. It is to write enough, in the right order, so the next person can continue the work.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. The Documents Hub means every pupil’s current support information is findable, filterable, and exportable.
What good looks like in practice
A good chronology has four habits.
Clear dates
Every entry has a date, not just a vague term label.
Plain English
It should be readable by anyone who needs the information.
One version of the truth
There should be one current chronology, not several competing copies.
Visible next actions
If the chronology does not show what happens next, it is only half useful.
FAQ
How long should a SEND chronology be?
Long enough to be useful, short enough to read quickly. If staff stop opening it, it is too long.
Is a chronology the same as a case note?
Not quite. A case note may capture detail. A chronology should capture the sequence and the decision trail.
Who should own it?
Usually the SENCO or a delegated SEND administrator, with input from teachers and support staff.
Does every pupil need one?
Not necessarily in the same format. But any pupil with ongoing SEND support, changing needs, or frequent review points benefits from a clear chronology.
The takeaway
A SEND chronology should make school life easier, not heavier.
If staff can scan it, trust it, and update it without friction, it becomes one of the most useful records the school has.
If it lives in inboxes and broken folders, it will fail the first time someone needs it in a hurry.
The simplest fix is to keep one current record in one searchable place.
That is what MeritDocs is for. It keeps SEND documents in one hub so schools can see what is current, export what is needed, and keep the chronology useful long after the meeting has ended.