Role

Learner support software for senior leaders and governors

Learner support software for senior leaders and governors: aggregate patterns in learner support, not individual stories, and what it does not claim.

Updated
Illustration with fictional data
In short

Senior leaders see patterns across learner support, such as requests, outstanding actions and review rates, without needing individual learner detail. Inclusion Studio does not calculate an inclusion score or predict inspection outcomes.

Principals, directors of curriculum, heads of apprenticeships and governors are accountable for learner support without being close to day-to-day delivery. You need confidence that the process works, early signs when it does not, and honest information to give boards and inspectors. This page explains what Inclusion Studio is designed to provide, and what it does not.

What does a senior leader’s day look like?

You scan reports, take questions from governors and hear about individual cases when they have gone wrong. You know support matters, because it affects retention, achievement, complaints and inspection. But the information you get is often anecdotes and a one-off report assembled for a meeting, rather than something you can rely on to be consistent.

What do senior leaders need from learner support software?

  • A reliable view of whether the support process is operating: are requests answered, plans agreed, reviews done?
  • Early warning when support is being missed or delayed in a team, site or programme.
  • Evidence that learner voice is heard and acted on.
  • Answers you can explain, without exposing individuals’ personal information.
  • Realistic claims. A false picture of strength is worse than a clear picture of gaps.

What do you see in Inclusion Studio?

The design gives leaders aggregate and process views, for example:

  • volumes and age of open support requests;
  • how many agreed plans are overdue for review;
  • missed support and whether it was recovered;
  • learner feedback on whether support helped, in summary;
  • patterns by site, course or team, where numbers are large enough to avoid identifying individuals.

See insights. In the prototype these are illustrative figures for fictional learners; the production reporting is in development, and what exactly it includes will be validated in the pilot. Reports are a view of the process records, so they are only as complete as the records staff enter.

What do you not see?

Leaders do not need individual diagnoses, notes or documents to oversee the process, and by default they do not see them. Access is checked on the server by organisation, relationship and field. If a leader needs to see a case, for example during a complaint, that should be a role-based decision, with access that is logged. See permissions and roles.

What does Inclusion Studio not claim?

This matters because leaders are asked for assurance.

  • It does not calculate an inclusion score.
  • It does not predict or improve inspection outcomes.
  • It does not make your organisation compliant.
  • It does not decide who gets support.
  • It has no customers, outcome statistics or certifications yet.

Software supports a process. The provider remains responsible for its duties.

How does it relate to inspection and equality duties?

Ofsted’s renewed FE and skills inspections began on 10 November 2025 and include an inclusion evaluation area covering support for disadvantaged learners, those with SEND and those known to children’s social care. Inspectors will make their own judgement from what they see and hear. Records of what was agreed, delivered and reviewed can help your staff explain their practice. See Ofsted inspection and learner support.

Colleges and many providers are also subject to the public sector equality duty in section 149 of the Equality Act 2010, which requires due regard to eliminating discrimination, advancing equality of opportunity and fostering good relations. Whether it applies to your organisation depends on its status. See public sector equality duty. This is general information and not legal advice.

What should leaders ask of their team?

Start by asking whether your learning support policy matches what staff actually do.

A few questions work whatever system you use:

  1. How long does a new request wait before someone sees it?
  2. What percentage of agreed plans have been reviewed in the agreed time?
  3. How do we know support happened, and what do we do when it does not?
  4. How do we know learners find it helpful?
  5. Who can see a learner’s record, and how do we know?

What is the current status?

Inclusion Studio is pre-pilot and uses synthetic data only. The pilot starts with FE colleges and apprenticeship providers in England. If you lead one and want to discuss the pilot, see the pilot page or contact us. For the people who prepare your evidence, see quality and compliance and inclusion leads.

Frequently asked questions

Will senior leaders see individual learners' records?

Not by default. The design gives leaders aggregate views suited to oversight. Access to individual records depends on role and relationship and is checked on the server.

Does Inclusion Studio give an inclusion score?

No. It does not calculate an inclusion score, predict inspection outcomes or claim to improve grades. Prototype figures are illustrative.

Can governors use it for assurance?

It can provide consistent information about the support process for governors to question. Judging quality remains a leadership and governance task.

Is this live?

No. It is pre-pilot. The prototype uses fictional learners and illustrative aggregate metrics, and the production application is in development.

Sources and further reading

Official guidance changes. Check the source before relying on any detail, and take professional advice for individual cases.

Help shape the pilot

We are working with a small number of England FE colleges and apprenticeship providers first. Tell us about your learner support and we will be in touch.