Role

Learner support quality and compliance: records and evidence for quality teams

How quality and compliance teams can use learner support records and controlled evidence exports for audits, funding queries and inspection preparation.

Updated
Illustration with fictional data
In short

Quality and compliance teams use Inclusion Studio for a consistent trail of what was agreed, delivered, missed and reviewed, and for controlled evidence exports. It supports your process; it does not make a provider compliant.

Quality managers, compliance leads and funding officers are asked to show that support happened, not only that it was planned. This is hard when the evidence is scattered across mailboxes and spreadsheets. This page describes what Inclusion Studio is designed to provide for you and what you should still check yourself.

What does a quality lead’s day look like?

You might be preparing a self-assessment, sampling learner files, answering a funding query, responding to a complaint or getting ready for inspection. Each needs the same thing: a trustworthy account of what was agreed with the learner, who was meant to do what, what actually happened, and whether anyone checked it worked. You often find gaps only when someone asks.

What do quality and compliance teams need from learner support records?

  • Records that were made at the time, not reconstructed afterwards.
  • A consistent structure across teams, sites and programmes.
  • Visibility of gaps: missing agreements, overdue reviews, support missed with no recovery.
  • Exports that include what is needed and nothing more.
  • Clarity about who accessed or changed what.

What do you see in Inclusion Studio?

Following Understand, Agree, Deliver, Review, a quality role would see:

  • Agreements. Whether a plan was agreed with the learner, or disagreement recorded. See support plans.
  • Delivery. Support delivered and missed, and how missed support was recovered. See delivery tracking and missed support recovery.
  • Reviews. Whether the learner was asked if support helped, and what was decided. See reviews.
  • Exports. A controlled evidence export. See evidence export.

Good evidence practice is covered in our guide to recording support delivery evidence. The point is a record that is contemporaneous, specific and tied to the learner’s agreed support. Aggregate patterns are covered on insights.

What are the limits?

  • Records show entries, not truth. If staff do not record, the system cannot know. Sampling and conversation still matter.
  • No scores. Inclusion Studio does not calculate an inclusion score, predict inspection outcomes or claim to improve grades.
  • No compliance guarantee. The provider decides whether it meets its duties.
  • Access is limited. Permissions are enforced on the server by organisation, relationship and field. A quality role sees what its role allows, and exports are controlled by those permissions. See permissions and roles.

How does it relate to funding evidence?

DfE guidance on apprenticeship learning support sets conditions for claiming, including that the learner agrees support arrangements in writing, that costs are evidenced and that needs are reviewed at least every three months with the first review a month after adjustments start. It also notes that free adjustments cannot be claimed and that workplace adjustments are the employer’s responsibility. Rules are set for each funding year, so check the current version. Inclusion Studio can hold the agreement, delivery and review records that such conditions point to, but you remain responsible for the claim. See learning support funding for apprenticeships.

How does it relate to inspection?

Ofsted’s renewed FE and skills inspections started on 10 November 2025 and include an inclusion evaluation area. Inspectors judge what they see, so records are only part of the picture. A consistent trail helps staff explain their practice. See Ofsted inspection and learner support. This is general information and not legal advice.

What should you check before relying on any system for evidence?

  1. Can you see who created and changed an entry, and when?
  2. Can you export what an inspector or funder asks for, and nothing more?
  3. Who can see the export, and where is it stored?
  4. What happens to evidence when a learner leaves?
  5. Has the supplier explained its data protection and security position? See the trust pages.

What might a fictional example look like?

This is a fictional example, not a real provider. A quality manager is asked to show how one learner’s support was handled. She opens the record and sees the learner’s words at the start, the agreed plan with the learner’s response, six weeks of delivery with two missed sessions and how each was recovered, and a review in which the learner said the support helped and asked for one change. She exports the evidence the learner’s record allows her role to export, checks it with the inclusion lead, and keeps her own notes on what she saw in observation, which the system does not replace.

What is the current status?

Inclusion Studio is pre-pilot and uses synthetic data. Evidence export formats and audit features are still being specified, and no real learner data is used. The pilot starts with FE colleges and apprenticeship providers. To help define the evidence you need, see the pilot page or contact us. For senior leaders, see senior leaders.

Frequently asked questions

What evidence can quality teams produce?

The design includes a controlled evidence export drawn from the recorded journey: agreed plans, delivery and missed support, recovery and reviews. Exports are limited by the permissions of the person producing them. Export formats are still being specified.

Does it prove we are compliant?

No. Records show what your staff entered. Compliance is a judgement your organisation makes against its duties, and Inclusion Studio does not guarantee it.

Can it help with apprenticeship learning support claims?

It helps keep records that funding rules ask for, such as written agreement, delivery and regular reviews. It does not calculate or submit claims.

Is an audit log available?

Audit metadata is part of the production design. What is exposed to customers, and how, is still being defined, and the prototype has no audit history.

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.