A weekly SEND triage meeting should not feel like a catch up for the sake of it.
It should be a short, structured decision point. What needs attention now? Who is doing what? When will we look again?
If the meeting cannot answer those questions, it is just another slot in the calendar.
The short version
A useful triage meeting is small, repeatable, and boring in the best way. It should cover only the pupils or cases that need a decision, then leave with clear owners and dates.
If a case leaves the meeting without an owner and a next review date, the meeting has not finished the job.
Why weekly triage helps
SEND work can drift when everyone is busy. A plan gets updated, then forgotten. A parent call happens, then the note sits in an inbox. A support adjustment is agreed, then nobody checks whether it happened.
A weekly triage meeting gives the team one place to look at the live picture. It works best when it is used to unblock stalled cases, decide which pupils need a fuller review, check whether actions from last week actually happened, spot new risks before they turn into a bigger problem, and keep the record current.
The meeting is not there to replace professional judgement. It is there to stop the work fragmenting.
Who should attend
Keep the group tight. The meeting usually works best with the SENCO or SEND lead, a pastoral or year lead, someone who owns attendance or behaviour if those are relevant, an admin or case support person who can update the record, and a senior leader if decisions need signing off.
Do not invite everyone just because the case touches their area. The more people in the room, the harder it is to decide anything.
What the agenda should look like
Keep the agenda fixed. Change the cases, not the structure.
Review last week's actions first. What was done? What was not done? What slipped? Why? This is not about blame. It is about whether the plan is moving.
New cases should only come in if they need triage. If a case does not need a decision, it can wait for the next routine review or be updated outside the meeting.
Cases that are not moving deserve attention because they often get stuck. The family is waiting. The school is waiting. The record says work is happening, but nothing has changed in two weeks. Those are the cases that need a named next step.
If you do only one useful thing in the meeting, write down who is doing what and when the team will look again.
A simple triage template
A good template keeps the meeting short. For each case, capture the pupil, the issue, the current support, the decision needed, the owner, the deadline, and the review date.
That is enough to keep the conversation focused. If you start writing paragraphs, the meeting will drift.
What a good decision sounds like
A good triage decision is concrete. The SENCO will check the current plan and update the parent by Friday. The year lead will speak to the form tutor today and report back. The admin lead will pull the latest review dates and flag overdue items. The pastoral lead will arrange a check in after lunch each day for two weeks.
Those are actions, not intentions. The bad version sounds polite but goes nowhere: look into it, touch base next week, keep an eye on it, see how it goes.
How to keep the meeting from becoming a talking shop
Limit the number of cases so the room can make decisions. If there are too many, split the list or shorten the scope.
Use the same order every week. People work faster when they know what comes next.
Stop repeating the same discussion. If a case has not changed, record that and move on.
Make the update happen live. Do not leave the notes to memory. If the action is agreed in the room, the record should reflect that before the meeting ends.
MeritDocs keeps SEND documents in one searchable hub, so staff can filter by pupil, see what is current, and export when needed. That matters in triage because a meeting only works when the team can see the live record instead of reconstructing it from scraps.
What to do before the meeting
A little preparation saves a lot of time. The chair or coordinator should send out a short list beforehand with any cases that need decisions, plus enough detail for the room to act: what has changed, what the block is, what decision is needed, and who needs to be involved.
If the team gets a mystery item with no context, the meeting turns into detective work.
What to do after the meeting
The job is not done when people leave the room. The actions need to be updated in the live record the same day if possible.
That usually means updating the current note or plan, recording the decision, setting the review date, telling the relevant staff member what they need to do, and checking that nothing got lost between the meeting and the classroom.
If the record stays stale, the meeting has not really happened. MeritDocs helps schools run this properly by keeping SEND documents in one place, with current information easier to find, review dates visible, and exports straightforward. The real gain is not just faster admin. It is a live record that still makes sense by the time the next meeting starts.
A weekly rhythm that actually works
Monday: gather the cases that need attention. Tuesday: share the agenda and any documents people need. Wednesday: hold the meeting and make decisions. Thursday: update the record and send any follow-up messages. Friday: check the actions are visible in the right place.
This sounds basic because the basics are usually the bit schools skip.
Common mistakes
The meeting tries to cover every pupil. That is not triage. That is a long review meeting with a new label.
The same unresolved case comes back every week. That usually means the group has not made a real decision, or the decision was never recorded properly.
The notes live somewhere separate. If actions sit in a notebook, a WhatsApp thread, or one person's memory, the school has not got a reliable process.
Nobody owns the next step. This is the most common failure. An action without an owner is not an action.
FAQ
How long should a weekly SEND triage meeting take?
Short enough to stay useful. For many schools, 30 to 45 minutes is enough if the agenda is tight.
Should every pupil be discussed?
No. Only the cases that need a decision or a check on progress.
What is the most important output?
A clear action, a named owner, and a review date.
The takeaway
A weekly SEND triage meeting is only worth the time if it helps the team decide what matters now.
That means fewer cases, clearer actions, and one live record that stays current after the meeting ends. MeritDocs is useful here because it keeps SEND documents in one searchable hub, so staff can see the current version, update it quickly, and stop relying on memory to hold the plan together.