Impact of learning support: reviewing whether it worked

A plan is a hypothesis: “if we do these things, this barrier will matter less.” A review tests it. Without one, support carries on out of habit, or stops without anyone deciding to stop it.

This guide covers what a good review checks, how to run one, how to decide, and how to record the outcome so that it can be explained later.

Why review the impact of learning support?

Support should be reviewed because needs change, adjustments can stop being effective, and the people responsible for the support need to be able to show they acted on what they learned.

The SEND Code of Practice describes a cycle of assessing, planning, doing and reviewing. Under section 66 of the Children and Families Act 2014, a further education institution must use its best endeavours to secure the special educational provision a student needs. Reviewing is how you find out whether your endeavours are working.

For disabled learners, the duty to make reasonable adjustments in section 20 of the Equality Act 2010 is about removing substantial disadvantage. If an adjustment is not removing it, you have a reason to change it. Colleges as public bodies also have the public sector equality duty, which requires due regard to advancing equality of opportunity. Take professional advice if you are unsure how these apply to a specific situation.

For learners with an EHCP, the statutory annual review is a separate process. See EHCP annual reviews post-16. A support review inside the college can, and should, feed into it.

What are the three questions every review should answer?

Every review should answer three questions, in this order.

1. Was the support delivered? If not, the review is about delivery, not about whether the support works.
2. Did it help, in the learner’s view? Ask them directly, and ask for examples.
3. What should we keep, change or stop? Make a decision for each item and record why.

Reversing the order is the common mistake. Teams ask “is it working?” before checking “did it happen?”, then draw the wrong conclusion.

How do you check whether support was delivered?

Look at your delivery records before the meeting. Count planned sessions against delivered, missed and recovered. Note any pattern, such as support missed on Mondays, or only in one unit, or after a tutor change.

For each missed item, ask:

• Was it missed because of staffing, timetabling, learner absence or a misunderstanding?
• Was the learner told, and did they get a chance to reschedule?
• Was it recovered, and if so, how?

The next guide, recording support delivery evidence, covers how to keep these records without drowning in admin.

How do you ask the learner whether it helped?

Ask open questions, give a rating only as a starting point, and ask for an example. A scale from 1 to 5 can open a conversation, but the useful part is the answer to “what makes it a 3?”

Sample questions:

• “What has changed for you since we started this?”
• “Which part of the support do you use most? Which part do you forget about?”
• “Is there anything we do that you would rather we did not?”
• “What is still hard?”
• “If you could change one thing, what would it be?”
• “Do you want to keep this, change it or stop it?”

Offer other formats if a meeting is hard for the learner: a short written form, a call, or a message before the meeting. The learner voice guide has more on ways to ask.

What other evidence should you look at?

Use a small number of simple measures that are connected to the barrier, not a dashboard of everything. Choose from:

Be careful about cause. If attendance improves, support may be part of the reason, but so may a change of timetable. Say what the evidence suggests rather than claiming it proves the support worked.

How do you decide to keep, change or stop?

Decide item by item, using four options.

• Keep. The support is delivered and helps. Record why, and set the next date.
• Change. Delivery is fine but the support is not quite right. Agree what to adjust.
• Fix delivery. The support has not been delivered consistently, so you cannot judge it. Fix the cause and review again soon.
• Stop or step down. The barrier has eased or changed. Agree a gradual reduction and a check-in to see whether the barrier returns.

Never stop support silently. If the learner or team decides to stop, the plan should say so, with a date and a reason.

What does a review look like in practice?

Fictional example. Daniel is an apprentice electrician. His plan, agreed six weeks ago, included a weekly 20-minute check-in with his assessor, instructions given in writing for off-the-job tasks, and a quiet space for written work at the training centre.

Before the review the inclusion lead looks at the delivery record: six check-ins planned, four delivered. Both missed sessions were because the assessor was visiting other sites. Written instructions were given for every task. The quiet room was used twice; Daniel says it was booked out on other days.

In the meeting Daniel says the written instructions “changed everything”. He says the check-ins are useful when they happen but he would prefer a short message at the start of the week to a 20-minute call. He has not used the quiet room much because “it feels like a big deal to ask”.

Decisions recorded:

• Written instructions: keep.
• Weekly check-in: change to a short message on Monday, with a call if Daniel replies that he wants one. The assessor’s missed sessions are noted as a delivery issue.
• Quiet room: change so it is booked for him on his regular training days and he does not need to ask.
• Next review: six weeks, or sooner if Daniel misses two sessions.

Notice that the review treats the learner as the expert, separates delivery from effectiveness and ends with dated actions.

What are the common mistakes?

• Reviewing without delivery data. You will not know whether the support failed or never happened.
• Asking “Is everything okay?” Closed questions get “yes”.
• Letting staff talk more than the learner. Start with the learner’s view.
• Treating success as a reason to withdraw support. Success may be because of the support.
• Using one measure. Grades, attendance and satisfaction each tell part of a story.
• Not recording the decision. If the outcome is not written down, the next person starts again.
• Making the review a one-off event. Plan short check-ins in between.
• Promising more than you can deliver. If a change is not possible, say so and offer an alternative.

A checklist for a review meeting

• ☐ Delivery records prepared and shared with the learner beforehand.
• ☐ Learner knows the purpose and can choose how to contribute.
• ☐ The learner speaks first.
• ☐ Each support item has a decision: keep, change, fix delivery, stop or step down.
• ☐ Disagreement is recorded.
• ☐ Actions have owners and dates.
• ☐ The updated plan is shared with the learner in an accessible format.
• ☐ The next review date and early-review triggers are set.

The support review meeting template and the review meeting agenda tool can help you structure the session.

What should you do when a learner disagrees with the team?

Record the disagreement, explore it and decide what happens next, rather than closing it down. Disagreements fall into three kinds.

1. The learner does not want support the team thinks is needed. Ask why. Explain what you are worried about. Agree a trial, a smaller step or a date to look again. Unless there is a safeguarding or legal reason to act otherwise, the learner’s informed choice stands.
2. The learner wants something the team cannot provide. Be honest about what is not possible and why. Offer the nearest alternative, and note the request in case it points to a wider gap.
3. The learner and the team read the evidence differently. Show them the delivery record and outcomes, listen to their reading, and agree what you will watch before the next review.

If a disagreement cannot be resolved, make sure the learner knows how to raise a concern under your complaints or appeals process, and write down that you told them.

Review notes also help with funding conversations and quality assurance. Summarised across a cohort and anonymised, they can show which types of support are most often changed or stopped, and where delivery most often fails. A support plan review letter template can help you invite the learner and confirm the decision in plain English.

How does Inclusion Studio support this?

Reviews are the last step of the Understand, Agree, Deliver, Review journey. In the design, the review looks at delivery records, asks the learner whether the support helped, and ends in a decision to keep, change or stop each item. See the reviews page. Inclusion Studio is pre-pilot, with a clickable prototype using fictional learners, and the production application is in development. It supports your review process; it does not decide anything on your behalf.