Support plan review software: did it help, and what should change?

A review is where support either improves or quietly drifts. Inclusion Studio treats the review as a short conversation with the learner, backed by what was delivered, and ending in a clear decision. Good support plan review software makes that conversation easy to prepare and hard to skip. This page explains how that works and what you can try in the prototype.

What problem does support plan review software solve?

Many support plans are reviewed only on paper, once a year, or when something goes wrong. The learner may not be in the room. Nobody has the delivery record to hand. The outcome is often “continue as before”, whether or not it is helping.

A good review asks one question first: is this helping, according to the learner? Then it checks what actually happened, and decides to keep, change or stop each piece of support. Our guide to reviewing whether support worked covers the practice.

How does a review work, step by step?

1. A review comes due. The plan’s review date arrives and the owner sees it in their priorities.
2. The learner is asked first. Before the meeting, the learner is invited to say whether the support helps. Their answer is stored as learner voice.
3. The record is brought together. The review screen shows the learner’s quote, what was agreed, what was delivered and any missed items.
4. The conversation happens. Staff and learner talk it through. Notes are recorded.
5. A decision is made. For each action: keep, change or stop, with a reason.
6. The next step is set. A named owner, a next action and a next review date.
7. The learner’s involvement is recorded. Was the next step agreed with the learner, still to be discussed, or did the learner ask for a different approach?
8. The plan updates. The change flows back into the support plan, and the review itself becomes part of the evidence export.

What should a review not do?

A review should not become a test the learner can fail. It should not rely on a staff opinion alone. It should not be used to remove support because the learner is “doing well” without asking whether it is the support that is making that possible.

Our support review meeting template and review meeting agenda tool give you a structure for any setting. To invite a learner or confirm the outcome in writing, use the support plan review letter template.

Who sees what?

Server-side permissions by organisation, relationship and field apply:

See permissions and roles.

What is in the prototype today, and what is being built?

In the prototype (fictional learners only):

• A review form from each learner’s summary, showing the learner’s quote, what was agreed and what was delivered.
• Choose “How is the support working?” (Needs a change, Helping, Not yet clear).
• Add review notes, with an optional labelled sample AI draft you can edit. See AI drafts.
• Set the next support action, owner and next review date, and the learner’s involvement.
• Validation if notes or the next step are missing.
• Save, then see the status, next action and outstanding count update. If the learner has not agreed, the status shows “Follow-up planned”, not agreement.

Changes stay in this demo session and reset on refresh. There is no persistence, login or audit history.

Being built for the pilot:

• Review scheduling and reminders.
• Pre-review learner feedback.
• Keep, change or stop per action.
• Permanent, versioned review records with an audit trail.
• Reviews feeding the evidence export.

Who is this for?

Tutors and assessors running reviews. Inclusion leads checking that reviews happen and lead to change. Learners, who should be at the centre. See tutors and assessors and learners.

What does this look like in practice? (fictional example)

Leo, a fictional Level 3 team leader apprentice, has a trial of protected study time. Before the review, he says a regular slot would help him plan his week. The review screen shows his words, the agreed support and two check-ins recorded. In the conversation, Leo says the slot is practical on Tuesdays but not Thursdays. The tutor records the outcome as “Needs a change”, sets the next step to confirm a Tuesday slot with the employer, names an owner, chooses a review date and marks the next step as agreed with Leo. The plan updates and Leo’s words remain in the history. This is a fictional example, not a real learner.

Related guides and next steps

• Reviewing whether support worked
• EHCP annual reviews post-16
• Join the pilot.