A missed special educational needs (SEN) Support review rarely announces itself. The date passes, the old plan still looks current and staff keep using support that may no longer fit. The problem usually appears later, when a parent asks what changed or a teacher needs an answer that should already be in the record.
The fix is a review workflow, not a busier calendar.
Key points: Set a clear review date when support is agreed. Give preparation and follow-up tasks named owners. Gather pupil, parent and staff evidence before the meeting. Record the decision against the previous plan, publish one current version and keep overdue actions visible until somebody closes them.
What does the special educational needs and disabilities (SEND) Code of Practice require schools to review?
The SEND Code of Practice says SEN support should follow the assess, plan, do, review cycle. When support is planned, the teacher and special educational needs coordinator (SENCO) should agree the expected impact and a clear date for review with the pupil and parent. The effectiveness and impact of that support should then be reviewed on the agreed date.
The Code is specific about the purpose. Review is where the school evaluates the support, considers the pupil's progress and views, listens to the parent, then agrees what should change. It is not a diary exercise.
The same guidance says schools should meet parents of pupils receiving SEN support at least three times each year. That does not create one universal timetable for every support plan. A new intervention may need checking after six weeks. A stable adjustment may follow the school's termly cycle. The date should match the decision and the evidence the school expects to review.
Education, Health and Care Plan (EHCP) annual reviews are different. The local authority must review an EHC plan at least every 12 months, and schools must cooperate with that process. Keep EHCP annual review tracking in the same oversight view if that helps, but do not blur the two processes or their responsibilities.
Why do SEN Support Plan review dates slip?
Dates slip when the SENCO's spreadsheet, a teacher's calendar, the current plan, parent views and previous actions live in different places. A reminder can prompt a person. It cannot show whether the plan is current, whether evidence has arrived or who still owes an action. Staff absence exposes the gap quickly.
MeritDocs addresses this by keeping SEND documents, review context and current versions in a governed workflow. Staff can filter documents, see review dates and export the record, rather than rebuilding the position from separate files.
What should a review-date workflow contain?
Keep the control view short. It should show what needs attention, not reproduce the pupil's history.
For each review, record:
- pupil identifier
- document or review type
- agreed review date
- reason for that timing
- lead owner
- preparation status
- decision required
- follow-up status
Use a small set of statuses: upcoming, evidence needed, meeting booked, decision recorded, actions overdue and complete. Avoid labels such as "nearly done" or "waiting" because they hide the next action.
Set the date from the decision
Record the next review date while the support is being agreed. Tie it to the expected impact.
"Review on 12 November after six weeks of the new morning transition routine" is useful. "Review next term" is not. The first version tells staff when to act, why that date was chosen and what evidence to bring back.
Also record what would trigger an earlier review. A sharp attendance change, a new professional report, a failed adjustment or a concern raised by the pupil or family may mean the school should not wait for the planned date.
Give preparation work an owner
The SENCO may coordinate the process, but that does not mean every task belongs to the SENCO.
Name who will gather:
- the pupil's view
- the parent's update or concern
- teacher feedback
- evidence about the agreed outcome
- information from outside professionals, where relevant
- the provision delivered since the last review
"The team" is not an owner. Another authorised colleague should be able to see and take over the task if needed.
Why should review timing sit outside artificial intelligence (AI)-generated text?
AI can help turn recorded evidence into a structured draft. It should not invent the school's review timetable in a fluent paragraph.
The Department for Education (DfE)'s guidance on generative AI in education says professionals remain responsible for the quality and content of final documents, and that AI output requires critical checking for accuracy and appropriateness. A review date is exactly the sort of operational decision that needs clear ownership.
Good SENCO software should therefore keep review scheduling in the product workflow. The date should come from an agreed cycle, a manual choice or a documented school decision. If draft wording conflicts with the saved date, the controlled value should win.
MeritDocs keeps review scheduling inside the application workflow so generated wording does not quietly create its own timetable. Staff still choose and approve the arrangement. The software keeps that decision attached to the document and visible for later work.
This matters beyond AI. Copying an old plan can carry an old date into a new document just as easily. The control should sit with the live record, not with whichever paragraph was copied last.
What evidence should be ready before the review?
Collect:
- the support that was delivered
- the pupil's view, in their own words where possible
- the parent's main update
- staff observations linked to the agreed outcome
- progress from the recorded baseline
- what has worked
- what has not worked
- the decision needed next
Bring forward the information that affects the current decision rather than copying the pupil's whole history into every review.
The Office for Standards in Education, Children's Services and Skills (Ofsted) Supporting SEND research found that gaps in staff understanding of pupils' needs and starting points could damage pupils' experiences, learning and development. That small-scale study is not a review-date standard, but its practical lesson fits: a meeting date is of little use if the adults arrive without a dependable picture of the pupil.
What should happen after the meeting?
A review is unfinished until the decision reaches the current record and the relevant people.
Record:
- what the evidence showed
- what will continue, stop or change
- who owns each action
- the deadline for each action
- who needs the updated information
- the next review date
Then update the plan. Preserve the previous approved version, but make the new current version obvious. Staff should not have to choose between six files with similar names.
Keep overdue follow-up actions visible until somebody closes them.
How can schools audit the process each half term?
Choose five current SEN Support Plans and run this check:
- Is there a specific next review date?
- Can staff explain why that timing was chosen?
- Does preparation have a named owner?
- Are pupil and parent views included?
- Can staff find the previous approved plan?
- Is one version clearly current?
- Can they see what changed?
- Are overdue actions visible?
If the answer to several questions is no, fix the workflow before adding another template. The failure is not a shortage of forms.
Frequently asked questions
How often should a SEN Support Plan be reviewed?
The SEND Code of Practice says support should be reviewed on the agreed date and schools should meet parents at least three times each year. The interval for a plan depends on the pupil's needs, the support being tested and the evidence needed next.
Is a SEN Support Plan review the same as an EHCP annual review?
No. SEN Support reviews are part of the school's graduated approach. An EHCP annual review is a statutory local authority process that must happen at least every 12 months. Track both clearly without treating them as interchangeable.
Who owns a SEN Support review?
The class or subject teacher remains responsible for daily teaching and works with the SENCO on assessment and review. Name an owner for arranging the review and owners for evidence, family contact, plan updates and follow-up.
What should a school do when a review is overdue?
Record the delay rather than silently changing the date. Name the next action and owner, contact the family where appropriate, gather missing evidence and set a realistic new date. Keep the missed date in the history.
Keep the decision attached to the date
A review date is useful only when it carries the reason, evidence, owner and follow-up with it. That is what turns a calendar entry into an Assess, Plan, Do, Review control.
MeritDocs helps schools keep that chain together: the current document, the review arrangement, the previous version and the next action. The practical gain is a plan that staff can trust after the meeting, with timeliness and follow-through covered.
Sources and related reading
- SEND Code of Practice: 0 to 25 years
- DfE guidance on generative AI in education
- Ofsted: Supporting SEND
- Assess, Plan, Do, Review: building a SEND evidence trail
- Writing the next SEN Support Plan after a review
- How to evidence SEN support in school
- SENCO software for UK schools