A missed SEND review rarely looks like a dramatic failure on the day. It looks like a plan that is still marked "current" even though the support has changed. A parent waiting for an update. A teacher using an old strategy. A SENCO discovering three overdue actions while trying to prepare for the next meeting.
The fix is not another reminder written on a sticky note. It is a review-date workflow that makes four things obvious:
- what is due
- who owns it
- what needs to be prepared
- what happened after the review
**A reliable SEND review system combines one current pupil record, visible due dates, named owners and a short follow-up step.** If one of those is missing, dates drift and the record stops being useful.
Why review dates disappear
Schools rarely miss reviews because nobody cares. They miss them because the information is split across systems.
One date may sit in a spreadsheet. Another is in a calendar. The latest support plan is in a shared drive. Actions from the last meeting are in an email. A staff change then creates the final bit of confusion: nobody is sure which date or document is the one to trust.
There is also a predictable human problem. A review date with no preparation work attached feels less urgent than the daily demands in front of the team. By the time the meeting arrives, the school is rushing to gather information rather than using the review to make a decision.
The answer is to treat a review as a short process, not a date in isolation.
Step 1: Create one review list
Start with a single list of pupils who have a planned SEN Support review, an EHCP annual review or another formal support review. Keep the fields deliberately plain:
- pupil identifier
- type of review
- due date
- lead person
- class or setting
- parent or carer contact needed
- status
- next action
Do not add every piece of information to the list. The list is for control. The pupil record is for context.
Use a consistent set of statuses, such as:
- upcoming
- preparation needed
- meeting booked
- actions overdue
- completed
Avoid a free-text status field if several people maintain it. "In progress", "nearly done", "waiting" and "to sort" may make sense to one person and mean nothing to the next.
Step 2: Set the due date from the last decision
The next review date should come from the decision recorded at the previous review, not from a rough annual guess.
At the end of every review, record:
1. the date of the meeting
2. the date or window for the next review
3. what evidence should be checked then
4. who will arrange it
5. what would trigger an earlier review
For example, "review in six weeks after the new morning routine starts" is more useful than "review next term". It links the date to the reason for the review.
For an EHCP annual review, the school must still follow the relevant local authority process and timescales. The internal tracking system should support that process, not pretend to replace it.
Step 3: Give every review an owner
A review date without an owner belongs to nobody. The SENCO may coordinate the process, but that does not mean the SENCO should personally chase every piece of evidence, invite every person and write every follow-up.
Name the person responsible for each part that matters:
- meeting arrangement
- pupil view
- family contact
- teacher feedback
- outside professional input, where relevant
- updated plan
- follow-up communication
One person can own several tasks, but each task needs a clear name. "The team" is not an owner.
A simple owner rule is useful: if the person is absent, another member of staff should be able to see what is outstanding and take over without starting again.
Step 4: Use a short preparation checklist
Preparation should be enough to make the meeting informed, not so heavy that staff avoid doing it.
A practical review pack might ask for:
- the pupil's view, in their own words where possible
- the family's main update or concern
- what support has actually been delivered
- what has changed since the last review
- evidence of progress against the agreed outcome
- what has not worked
- the decision needed at the meeting
The last two fields matter. If every form only asks what went well, the meeting becomes a polite status update. A good review gives permission to stop, change or increase support when the evidence says that is the right call.
Do not copy a whole history into every new plan. Keep the current information easy to find and retain the previous decision trail where it helps explain the change.
Step 5: Protect the pupil and family voice
A review is about the pupil's support, not just the school's paperwork. Ask a direct question before the meeting:
**What is making school easier or harder at the moment?**
The answer can be brief. It might identify a lesson, transition, social situation, sensory factor or communication problem that attendance figures and attainment data will not show.
Families may describe a different pattern at home. Record what they said accurately and make it clear whether the school agreed an action, needed more information or decided that no change was required.
That distinction prevents a common problem: a record that says "parent happy" when the actual conversation included a request that still needs a response.
MeritDocs can keep the current support documents and review information together so staff do not have to reconstruct the last conversation from separate files. The important outcome is not simply faster administration. It is a record that makes the agreed next step hard to lose.
Step 6: Make overdue actions visible
Most schools track meetings better than they track what happens afterwards. That is backwards. A review has little value if the updated plan never reaches staff or a promised call never happens.
After each meeting, record:
- the decision
- the action
- the owner
- the deadline
- who needs to be told
- the date the action was completed
Use one overdue view. Do not rely on people remembering to open every pupil folder and check old meeting notes.
A useful weekly routine takes 15 minutes:
1. filter for reviews due in the next four weeks
2. filter for actions past their deadline
3. assign anything without an owner
4. contact the person responsible for the next step
5. close completed actions
The point is not to create a new meeting. It is to keep the existing process from quietly dying between reviews.
Step 7: Keep the current plan obvious
A school can have an excellent review calendar and still give staff the wrong information. The current plan needs a clear home and a clear date.
When a document is updated, make sure the record shows:
- when it was updated
- what changed
- which version is current
- the next review date
- any immediate instruction staff need to follow
Do not make staff choose between six files with almost identical names. If old versions need to be retained, label them clearly and keep them out of the normal current-record view.
MeritDocs keeps SEND documents in one searchable hub. Staff can filter by pupil, see review dates and export the current document when needed. That is a better control than asking everyone to remember which shared-drive file has the latest edits.
A simple review-date audit
Run this audit at the start of each half term:
Check the list
Are all active SEN Support and EHCP reviews on the same control list? If a date is only in an individual calendar, it is not part of the school's reliable process.
Check the dates
Are the next review dates specific enough to act on? Replace "next term" with a date or a short date window.
Check the owners
Does every upcoming review have someone responsible for arranging it and preparing the evidence?
Check the actions
For the last five completed reviews, can you see what was agreed, who owned it and whether it was completed?
Check the record
Could a teacher or senior leader find the current plan without asking the SENCO to search for it?
If the answer is no, fix that step before adding a new template.
What about reminders?
Reminders still help. They are not the system.
Use calendar reminders for people who need a prompt, but keep the underlying review list and pupil record as the source of truth. A reminder can tell someone that a review is due. It cannot tell them which plan is current, what the family said or whether last month's action was completed.
Frequently asked questions
How often should SEN Support be reviewed?
The SEND Code of Practice expects schools to review support regularly as part of the assess, plan, do, review cycle. The exact timing should reflect the pupil's needs, the support being tested and the evidence available. A fixed annual date is not enough for every pupil.
Who should track EHCP annual review dates?
The school should have a clear internal owner, usually coordinated by the SENCO, while following the local authority's process. The important thing is that the date, preparation and follow-up do not depend on one person's private calendar.
What should happen when a review is overdue?
Record the delay, name the person responsible for the next action, contact the relevant family or professional and set a new date. Do not quietly move the date without recording why. A visible delay is easier to manage than a missing history.
The practical takeaway
Review dates are not an admin detail. They are the point at which a school checks whether support still matches the pupil in front of it.
A workable process needs one control list, specific dates, named owners, a short preparation pack and visible follow-up. Patchwork calendars and old documents will keep going until a staff absence or urgent family conversation exposes the gaps.
MeritDocs helps schools keep the current SEND record, review dates and follow-up information together. That means the next review starts with the right information instead of another round of detective work.