Insights: see delivery, feedback and review patterns

Leaders ask whether support is working. Inclusion leads ask where it is slipping. The honest answer needs data from the support journey itself: what was agreed, what was delivered, what learners said. This page explains the insights Inclusion Studio is designed to give, and what the prototype shows today.

What problem do insights solve?

Many providers can report how many learners have a plan. Fewer can say whether the agreed support happened, or whether learners think it helps. Reports are often built by hand from spreadsheets, a week before a meeting, with no record of how they were calculated.

Insights should be a by-product of everyone doing their normal work in the system, not a separate reporting chore. They should also be modest. A number is not an outcome, and the product does not pretend it is.

What will insights show, step by step?

1. Data is captured as staff work. Plans, delivery items, missed support, recovery steps, learner feedback and reviews all record dates and outcomes.
2. Measures are calculated from the record. For example the share of agreed actions delivered in a period, the number of overdue reviews and the number of open recoveries.
3. Learner feedback is summarised. The learner’s own words and their rating of whether support helps are shown, not replaced by a score.
4. The view is filtered by permissions. A tutor sees their learners. An inclusion lead sees their remit. Senior leaders see aggregate views.
5. Small numbers are protected. Where a group is too small to be anonymous, the aggregate is suppressed or handled with care.
6. You can click through. Each figure leads to the underlying items for staff with permission to see them.

Which questions should insights help answer?

• Is agreed support being delivered, and where is it not?
• Which actions are missed repeatedly, and is it one course or room?
• Are reviews happening on time and leading to changes?
• What are learners saying helps or does not?
• How long do new requests wait?

These are management questions about a process. They do not measure a learner’s worth, and they are not an assessment of a provider’s quality. The product does not calculate an inclusion score and does not predict inspection judgements.

Who sees what?

Permissions apply on the server, including to aggregates:

See permissions and roles and senior leaders.

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

In the prototype (illustrative figures only):

• An Insights section called “Support in practice”, labelled “Demo insights”.
• A card showing “18 of 20 agreed actions delivered” with a progress bar and a link to outstanding actions.
• A card showing a fictional learner’s feedback with a link to turn it into a next step.
• Header counts such as awaiting action and reviews this week, which update when you save a review.
• A note: “Illustrative figures only. These are not an inclusion score or an inspection judgement.”

None of the numbers describe real learners or a real provider.

Being built for the pilot:

• Delivery, missed support, recovery and review measures calculated from real records.
• Aggregate views by course, campus or cohort.
• Click-through from a figure to its items.
• Protection against identifying individuals in small groups.

To be decided with pilot providers: which measures are genuinely useful. Outcome measures need careful validation and are not claimed.

Who is this for?

Senior leaders who need an honest picture. Inclusion leads who want to spot problems early. Quality and compliance staff who need a trail. See senior leaders and quality and compliance.

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

An inclusion lead at a fictional college opens the insights view before a half-termly meeting. It shows that most agreed actions were delivered, that two actions on one course were missed repeatedly, and that three reviews are overdue. She clicks the course figure to see the items, finds the same workshop each time, and agrees a change with the curriculum manager. She also reads the learner feedback summary, which shows the learners’ own words about what is working. She does not use a score, because there is none. The figures are only a way to find where to look. This is a fictional example.

Related guides and next steps

• Reviewing whether support worked
• Delivery tracking and evidence export
• Join the pilot.