The short version
A SEND risk register is a working record of what might go wrong, what is already starting to slip, and who is responsible for putting it right.
It is not there to add drama.
It is there to stop quiet problems from turning into bigger ones.
That might mean a review date is drifting. It might mean attendance is falling. It might mean a reasonable adjustment has stopped happening in practice. It might mean a staff change has broken the handover.
The register only works if it stays current and short.
The moment it becomes a long spreadsheet nobody trusts, it has failed.
MeritDocs helps schools keep SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. That matters because any risk register is only as good as the live record behind it.
What a SEND risk register is for
A good register gives leaders and SENCOs an early warning system.
It should help you answer four questions quickly:
What is at risk?
How serious is it?
Who owns the next action?
When will we check it again?
If the register does not answer those questions, it is too vague.
If it tries to answer everything, it becomes unusable.
The sweet spot is a small, live list of the things most likely to affect support.
The risks worth tracking
Not every issue needs a place on the register.
The best entries are the ones that need attention soon and have a clear owner.
Common SEND risks include:
missed review dates
support that is written down but not happening in practice
attendance that is drifting down
parent or carer concern that has not been resolved
a key adult leaving or being absent for a long period
a planned intervention with no clear impact evidence
external advice that has not yet been acted on
a change of class, phase, or setting that needs a fresh handover
equipment, medical, or access arrangements that are not fully in place
These are the problems that tend to look small at first and expensive later.
What to include in each entry
Keep each entry short enough to scan.
A useful risk register row should include:
pupil name or identifier
the risk in one sentence
what evidence shows it is a concern
the owner
the immediate action
the date by which it should be reviewed
status
brief outcome note
That is enough.
You do not need a paragraph of background history in every row.
You need a record someone else can act on.
A simple structure that works
The easiest version is a table with five core columns:
risk
owner
action
due date
review note
Some schools add a severity flag.
That can help, as long as people use it the same way.
What matters more than the exact format is consistency.
If one SENCO writes one kind of entry and another writes a different kind, the register stops being a shared tool.
How to keep it useful week to week
The register should not be reviewed only when something goes wrong.
It should be part of a regular rhythm.
A short weekly or fortnightly review is usually enough.
That review should ask:
has the risk changed?
has the action been done?
is the owner still the right person?
should this risk be closed, escalated, or kept open?
If you do not review the register, it quickly becomes a list of old worries.
And old worries do not help anyone.
The difference between a risk register and an action log
These two tools are related, but they are not the same.
An action log records what was agreed.
A risk register records what might fail, what is already slipping, and what needs watching.
That matters.
A school can have a full action log and still miss the fact that a pupil’s attendance is sliding, or that a support strategy is no longer being delivered.
The action log says what should happen.
The risk register says what could stop it happening.
What makes the register fall apart
Most bad risk registers fail for the same reasons.
1. Too much detail
If every entry turns into a case note, nobody will update it.
2. No owner
If nobody is clearly responsible, the risk stays open by default.
3. No review rhythm
A risk register has to be checked. Otherwise it just records old uncertainty.
4. It sits away from the live record
If the register is separate from the documents that explain the pupil’s support, staff have to work twice as hard.
That is where schools start losing trust in the system.
Patchwork systems work until they do not. Shared drives, old Word documents, email threads, and handwritten notes can keep a school going for a while. They are much less good at showing one dependable version of what is current.
A practical way to build it
Start small.
Step 1: Pick the top risks
Choose the handful of risks that most often affect support in your school.
Do not start with dozens of entries.
Step 2: Define the trigger
Be clear about what makes something a risk.
For example, you might log attendance only when it drops below an agreed threshold or when the pattern changes suddenly.
Step 3: Assign an owner
Every entry needs one named owner.
Not a team. One person.
Step 4: Set a review date
If there is no date, the item will drift.
Step 5: Close properly
When a risk is resolved, close it and say why.
That stops the register from filling up with dead entries.
A small example
A Year 8 pupil has a support plan in place, but their attendance has started to dip after lunch on three days a week.
That may not look dramatic on its own.
On a risk register, it becomes visible early.
The entry might say:
risk: attendance dip linked to afternoon fatigue and anxiety
owner: SENCO
action: speak to parent, check timetable pressure, review adjustments
due date: Friday
review note: pattern confirmed, adjust afternoon support
That is the kind of entry that helps a school act before the problem hardens.
Where MeritDocs fits
A risk register is much easier to trust when the current record is easy to find.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. That means the risk register can be built from live information instead of memory, old attachments, or half-remembered meeting notes.
The real gain is not just speed. It is a record people can actually rely on when support starts to drift.
A useful summary for busy staff
A SEND risk register should track the few things most likely to slip, assign one owner to each risk, and be reviewed regularly. Keep it short. Keep it current. Tie it back to the live record. If it is not helping staff act faster, it is too heavy.
Frequently asked questions
Who should own the risk register?
Usually the SENCO or inclusion lead, with named owners for individual entries.
How often should it be reviewed?
Weekly or fortnightly works for most schools, provided the review is short and focused.
Should every pupil have one?
No. It is usually best for pupils where support is changing, a review is overdue, attendance is wobbling, or the school needs tighter oversight.
Is this just another spreadsheet?
It should not be. A good risk register is a live working tool, not a storage place for old concerns.
Final thought
Schools do not usually lose SEND work because nobody cared.
They lose it because the warning signs were scattered, and nobody had one clear place to see them.
A small, disciplined risk register helps fix that.
And when the live record sits in one searchable hub, the register becomes much easier to keep honest.