The short version
A chronology and a support plan are not the same document.
The chronology is the story of what happened, when it happened, and who was involved. The support plan is the working document that tells staff what to do now.
Schools get into trouble when those two jobs are mixed together. The chronology becomes too long. The support plan becomes too vague. Staff stop trusting either one. The SEND Code of Practice pushes schools towards clear planning, review, and a single current record.
The answer is not to merge everything into one giant file. It is to keep both documents current, separate, and linked.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. That makes it much easier to keep the story and the action in the right place.
What each document is for
The chronology
A chronology is a running record of important events.
It should capture:
key conversations
assessment dates
referrals
reviews
changes to provision
parent concerns
outside-agency input
decisions and outcomes
It should answer one question clearly: what has happened over time?
The support plan
A support plan is the current working summary.
It should capture:
the pupil's main needs in plain English
what helps day to day
what staff should do consistently
current adjustments
current targets or focus areas
review date
owner of the next step
It should answer a different question: what should staff do now?
If the two documents try to do each other's job, the school loses clarity.
What goes where
This is the easiest way to stop the record drifting.
Keep in the chronology
Put the following in the chronology:
dates of parent meetings
dates of reviews
dates of referrals or assessments
changes in attendance patterns
significant incidents if they affect support
agreement changes
handover points between staff
outcomes of specialist input
The chronology does not need to explain every detail. It needs to preserve the trail.
Keep in the support plan
Put the following in the support plan:
current need
current strategies
what to do in lessons
what to do around school
what to avoid
who is responsible for what
what success looks like
when the plan will be reviewed
The support plan should be short enough that staff can use it quickly.
Keep out of both where possible
Do not bury either document in:
repeated email text
copied and pasted meeting minutes
speculative language
old versions that are no longer current
background detail that no one will act on
Those things may matter somewhere. They do not all need to live in the same place.
A useful rule of thumb
If the sentence helps someone answer "what happened?", it belongs in the chronology. If it helps someone answer "what should I do next?", it belongs in the support plan.
That simple test prevents a lot of duplication.
How schools usually get this wrong
1. The chronology becomes a dumping ground
Staff paste every email, call, and note into the chronology because they do not know where else to put it.
The result is a long file that looks detailed but is hard to use.
2. The support plan becomes a history lesson
Instead of current actions, the support plan tells the full story of the last two years.
New staff cannot find the working guidance quickly enough.
3. Nobody knows which one is live
A parent sees one version. A class teacher sees another. The SENCO has a third.
At that point, the problem is not the wording. It is the system.
The Documents Hub means every pupil's current support information is findable, filterable, and exportable. The real gain is not just speed. It is that people can trust they are looking at the live record.
A simple structure that works
You do not need a complicated method.
Chronology structure
Use short dated entries:
18 March: parent raised concern about mornings
22 March: SENCO called home and agreed short check-in
2 April: class teacher trialled visual start-of-day cue
16 April: review held with parent and TA
23 April: outside professional joined next meeting
That is enough to show the story.
Support plan structure
Use a stable set of headings:
Current need
What helps
What staff should do
What to avoid
Review and owner
That is enough to tell staff what to do now.
If the headings change every time, staff have to relearn the format every time they open the file.
How to keep the two documents linked
Separation only works if the documents still talk to each other.
A good setup does three things.
1. Link the chronology to the current plan
The chronology should point to the current support plan so staff can move from the history to the live action quickly.
2. Put the review date on both
If the review date appears only in one place, someone will miss it.
3. Keep the live version obvious
There should never be confusion about which plan is live and which chronology is current.
That is where patchwork systems fall apart. Shared drives, email chains, and old files can keep a school going for a while. They are much less good at giving staff one dependable version of the truth.
The Documents Hub means every pupil's current support information is findable, filterable, and exportable.
What to do when a case becomes complex
Complex cases often tempt staff to add more and more detail.
Usually, that is not the fix.
Instead, tighten the structure.
Ask three questions
What happened?
What is current?
What happens next?
If the record can answer those three questions quickly, it is doing its job.
If it cannot, the record needs simplifying.
Split the work by purpose
The chronology holds the trail.
The support plan holds the current guidance.
The action list holds what still needs doing.
That split makes the record easier to maintain, especially when more than one adult is involved.
MeritDocs is built for this kind of working record. Schools can keep the chronology, plan, and live support information in one searchable hub, then pull what they need without rebuilding the story from scratch.
A small example
Imagine a pupil whose attendance has dipped after a change in class routine.
A weak record might mix everything together:
history of previous concern
current attendance worries
old meeting notes
strategies that no longer apply
new actions that have not been separated
A better record would split it:
Chronology
7 May: class routine changed
9 May: parent reported increased stress
11 May: attendance lead and SENCO met
14 May: trial adjustment agreed
Support plan
calm start-of-day check-in
clear visual routine
named adult for morning handover
review in two weeks
Now the school can see both the story and the response.
FAQ
Is a chronology the same as a case note?
Not quite. A case note is often a single entry. A chronology is the running sequence of important entries over time.
Should the chronology replace meeting minutes?
No. It should summarise the useful parts of the meeting history, not copy every word.
How long should a support plan be?
As short as possible while still being useful. If staff will not read it, it is too long.
Who should update the documents?
Usually the person closest to the live case, with oversight from the SENCO or SEND lead. The main thing is that one clear owner exists.
The takeaway
The school does not need one giant SEND document. It needs the right documents doing the right jobs.
The chronology should keep the story. The support plan should tell staff what to do now.
When those two things stay separate but linked, staff move faster, families get clearer answers, and the record becomes easier to trust.
That is the point of better workflow software. MeritDocs keeps SEND documents in one searchable hub, so schools can separate the story from the action without losing either one.