A pupil's SEND provision is not supposed to stay frozen because a document has been signed.
A strategy may stop working. A timetable may change. A pupil may return after a long absence, move class, receive new advice, or begin to manage a skill with less adult support. When that happens, the school needs to update the provision and the record.
The trouble is that provision changes often happen in conversation. Someone agrees a different approach after a meeting. A teacher tells a colleague in the corridor. A parent receives an email. The support changes, but the main record does not.
Then the next adult opens the old plan and follows yesterday's instructions.
A good provision change record prevents that. It does not need to be long. It needs to answer four questions:
- What changed?
- Why did it change?
- Who needs to know?
- When will the school review it?
What is a SEND provision change record?
A provision change record is a short, dated entry that links a decision to the pupil's current support. It sits alongside the support plan or wider SEND record. It is not a replacement for the plan, a running diary, or a collection of unfiltered meeting notes.
Its job is to make change visible.
A useful entry might say that a pupil will now receive a visual task sequence at the start of independent work, because the previous verbal prompt was not helping them begin tasks. It should name the person responsible for putting the change in place and give a date to review whether it worked.
That is much more useful than writing "support updated" in a spreadsheet.
Why do provision changes get lost?
Most schools do not lose information because staff do not care. They lose it because the information is spread across too many places.
A decision may sit in an email thread, an annual review document, a paper folder, a shared drive, or a staff member's memory. Each location can be reasonable on its own. Together, they create uncertainty.
The risk grows when staff change. A new teacher may find the old plan but miss the later decision. Cover staff may receive a handover that describes the pupil but not the change in provision. A SENCO may know that support was altered but spend time searching for the reason.
This is a version-control problem. The school needs one current record, not one more place to type.
What should a provision change entry include?
Keep the structure consistent. A short entry should include:
The date and decision owner
Record when the change was agreed and who owns the follow-up. This matters when several adults contribute to support. A date without an owner creates a task that belongs to everyone and therefore nobody.
The provision before the change
State what was in place. This gives the reader a baseline and stops the new entry becoming detached from the previous plan.
The provision after the change
Describe what staff should do differently. Use observable language. "Offer a reduced first task and check understanding before independent work" is clearer than "increase scaffolding".
The reason for the change
Link the decision to evidence. This might be a review of progress, pupil feedback, parent communication, attendance information, advice from a specialist, or a change in classroom context.
Do not claim that support worked just because it was delivered. Record what was observed and what decision followed.
Who needs to know
List the people who need the current information. This may include the class teacher, subject teachers, teaching assistants, pastoral staff, attendance staff, the family, or the next setting.
Keep this focused. The point is to make the right handover happen, not to create a distribution list that nobody checks.
The review date
Every change needs a point at which the school will ask whether it should continue, change again, or stop. A review date turns a good intention into a manageable process.
A simple example
A weak record might say:
Support changed after discussion with staff.
A useful record might say:
14 July: The pupil will now receive a written first-step prompt and a two-minute check-in at the start of extended writing. This replaces repeated verbal reminders, which were increasing frustration and were not helping the pupil begin. The English teacher will use the prompt from 15 July. The SENCO will review work samples and pupil feedback on 29 July. Parent update to be sent after the review.
The second version is not much longer. It is simply specific enough for another adult to use.
How should schools manage changes through the year?
Use a clear trigger for an update
Agree the events that should lead to a provision record update. These might include a formal review, a significant change in attendance, new advice, a transition between classes, a parent concern, a change in risk, or evidence that an intervention is not having the intended effect.
Not every minor adjustment needs a formal entry. But if the change affects what another adult is expected to do, it should be visible in the current record.
Write the change close to the decision
Do not leave it until the end of term. The longer the gap, the more likely the school is to forget the reason or rely on a version that has already been replaced.
A five-minute update after a decision is cheaper than a reconstruction exercise after a complaint, absence, or handover.
Keep the current instruction easy to find
Staff should not have to read every previous document to work out what applies today. Keep the current provision clear, then retain the history underneath it so the school can understand how the decision developed.
A chronology can explain what happened over time. The current support plan should explain what staff need to do now. Those are related records, but they solve different problems.
Close the loop after review
When the review date arrives, record the outcome. Continue the support, adjust it, stop it, or gather more evidence. A change record that never gets closed becomes another form of clutter.
What should staff avoid?
Avoid vague phrases such as "monitor as required", "continue support", or "review in due course". They hide the action and make it difficult to tell whether anything happened.
Avoid copying the whole plan into every update. That creates several documents that look current and increases the chance that staff use the wrong one.
Avoid treating the record as a punishment or compliance exercise. Its purpose is practical. It should help the next adult act correctly without needing a private briefing.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see the current record and review dates, and export information when needed. That makes a provision change easier to connect to the document staff actually use, rather than leaving the update in an email thread.
A five-minute provision change checklist
Before closing the update, check:
- Is the date recorded?
- Is the old provision clear enough to understand the change?
- Does the new instruction describe what staff should do?
- Is the reason linked to evidence rather than assumption?
- Is there a named owner?
- Does the right group of staff know?
- Is the family communication recorded where relevant?
- Is there a review date?
- Will the current record show the new instruction without a search through old files?
If the answer to any of these is no, the change is probably not finished.
How does this support UK SEND practice?
The SEND Code of Practice expects schools to involve children, young people, and parents in decisions and to review support. A clear provision change record helps the school show what was decided, what informed it, and what happened afterwards.
It also supports continuity. If a pupil moves class or a member of staff leaves, the next adult can see the current instruction and the reason behind it. That is safer than expecting a handover conversation to carry the whole story.
MeritDocs helps schools keep the live document findable and current, so the change can be used by the people responsible for support. The value is not a longer audit trail. It is less confusion about what happens next.
Final takeaway
A SEND provision change is not complete when someone agrees it. It is complete when the current record tells the next adult what changed, why it changed, what to do, and when to review it.
Schools do not need another sprawling spreadsheet. They need a dependable way to keep the current record ahead of the old one.
That is where a proper documentation system earns its place. MeritDocs gives schools one searchable home for SEND documents, with current information easier to find and export when the situation demands it.
FAQ
Does every small classroom adjustment need a formal record?
No. Record changes that affect planned support, another adult's responsibilities, family communication, risk, or the next review. Minor moment-to-moment teaching decisions do not all need a separate entry.
Should provision changes replace the support plan?
No. The support plan should show current provision. A dated change entry should explain how and why it changed. Keeping the history separate from the current instruction avoids confusion.
How often should schools review a provision change?
Set a date that matches the change and the available evidence. A short trial may need a review within weeks. A longer-term adjustment may be reviewed at the next planned cycle, unless new concerns appear sooner.