Recording learner support delivery: evidence that stands up

An agreed plan only matters if the support actually happens. Delivery records are how you know, how you fix it when it does not, and how you show a learner, a funder, an auditor or an inspector what you did.

Done badly, recording becomes a second job that nobody finishes. Done well, it takes a minute and gives a clear picture. This guide shows how.

Why does recording learning support evidence matter?

You record delivery because it lets you review support honestly, catch problems early, and explain what you did if anyone asks. It also protects staff, who can show they delivered what was planned.

There are three practical reasons.

1. Reviews. You cannot judge whether support worked until you know whether it happened. See reviewing whether support worked.
2. Duties. A further education institution must use its best endeavours to secure the special educational provision a student needs (Children and Families Act 2014, section 66). Disabled students are also entitled to reasonable adjustments (Equality Act 2010, section 20). Records are how you evidence what you did. They do not make you compliant on their own, and a record of poor delivery is still a record of poor delivery.
3. Continuity. A new tutor, a placement or a cover teacher can pick up where the last one left off.

What is the minimum you should record?

Record six things for each support item. This is a sensible minimum, not a legal list.

Two optional fields are often worth adding: the learner’s response in a few words (“said it helped”), and any change to suggest at the next review.

How do you record missed support?

Record it as plainly as delivered support. Missed support is information, not a failure to hide. The pattern is what helps you improve.

For each missed item, note:

• What was missed. The plan item and date.
• Why. Use a short list of reasons so you can see patterns: staff absence, timetable clash, room or equipment, learner absence, learner declined, communication failure, other.
• What happened next. Rescheduled, replaced with an alternative, escalated or left for review.
• Whether the learner was told. A learner who finds out support has lapsed on their own loses trust quickly.

If a learner declines support, record that as a choice, not a fault. Ask why. It may tell you the support is wrong, not that the learner is difficult.

What does recovery look like?

Recovery means the learner gets what they were owed, or an agreed alternative, as soon as practicable. Three rules help.

1. Set a recovery window. For example, within five working days for weekly support. Choose a time that makes sense for the support.
2. Offer the learner a choice. Make-up session, alternative support or skip it this time.
3. Escalate repeated misses. If the same item is missed three times, it goes to the inclusion lead, whatever the reason.

The missed support recovery plan template can help you set this out.

What does a good entry look like?

Good entries are short, factual and specific. They describe what happened, not what you think about the learner.

Fictional examples.

Good: “14 Oct. Written step cards given for the sauce practical. Learner used them for all four stages. Said the numbering helped. Delivered in full.”

Good: “21 Oct. Planned 20-minute check-in not delivered: assessor at employer site. Learner told by message at 9am. Rebooked for Thursday 23 Oct.”

Poor: “Learner difficult today and refused to use the cards.”

Better: “Learner chose not to use cards. Said they felt visible on the bench. Suggest discussing a smaller format at review.”

The poor entry judges the learner and gives the next reader nothing to act on. The better one records the same event with a reason and a suggestion.

Who should record, and when?

The person who delivers the support should record it, as close to delivery as possible. A one-minute note at the end of a session is more accurate than a reconstruction on Friday afternoon.

Make this realistic:

• Use a form that takes under a minute, with dropdowns for outcome and reason.
• Allow a bulk “delivered as planned” for routine items, with exceptions noted separately.
• Do not ask for the same information in three places.
• Give tutors and assessors a short weekly view of what is due, so they are not hunting for plans.
• Agree how workplace-based delivery is recorded, and by whom, with the employer contact.

How do you keep delivery records lawful and proportionate?

Treat delivery records as personal data, often special category data, and apply the same principles as for the plan. The ICO’s data protection principles include data minimisation, accuracy, storage limitation and security. In practice:

• Minimise. Record the support and the response, not a medical history. Health information is special category data.
• Keep it accurate. Correct errors, and date any changes.
• Restrict access. Tutors need to know the support, not the reason in detail.
• Set retention. Agree a period in your retention schedule with your data protection officer, and delete or archive when it ends.
• Write for the reader. Assume the learner may see it. Individuals have a right of access to their data, subject to exemptions, and your DPO should handle any request.
• Be careful with employers. An employer contact should see the workplace adjustments and their own actions, not the full record. See working with employers on adjustments.

The guide on special category data in education explains the legal framework in more detail. Nothing here is legal advice; ask your DPO or legal adviser if in doubt.

What does an evidence export need?

If you need to give evidence to an auditor, funder, local authority or inspector, assemble it deliberately rather than sharing raw records. A good evidence pack:

• Covers a defined period and group of learners, with a stated purpose.
• Shows plans, delivery, missed support, recovery and review outcomes together.
• Uses anonymised or pseudonymised data where individual identity is not needed.
• Excludes content the recipient has no need to see.
• Records who produced it, when and what was included.

Ask your DPO before sharing identifiable records externally. Evidence is a report on your process, not a promise about results.

What are the common mistakes?

• Recording only successes. A log that never shows a miss is not believable.
• Writing essays. Long entries are rarely read.
• Free text only. Without structured fields you cannot see patterns.
• Recording opinions as facts. Describe observed behaviour and the learner’s words.
• No link to the plan. Entries should refer to a specific plan item.
• Leaving entries until the end of term. Memory fades; accuracy falls.
• Storing records in personal email, notebooks or shared drives with open access.
• Keeping everything forever. Retention should be decided, not default.

A checklist for your delivery recording

• ☐ Every entry links to a plan item.
• ☐ Outcome and reason fields use agreed lists.
• ☐ Missed support has a recovery date or reason.
• ☐ Learners are told about missed support.
• ☐ Access is limited to those who need it.
• ☐ A retention period is set and applied.
• ☐ Repeated misses are escalated.
• ☐ Records could be read by the learner without causing harm.

Start from the delivery log template if you do not yet have a standard format.

How do you audit your own records?

Check a small sample each half-term, so problems surface before an external audit does. Pick ten plans at random and ask five questions of each.

1. Can I see each planned support item in the delivery record?
2. Is there a clear outcome for each date, including missed sessions?
3. For each miss, is there a reason and a recovery or decision?
4. Does the record agree with what the learner says?
5. Is access limited to the right people, and is there anything recorded that should not be?

Share what you find with the team, in a way that treats gaps as process problems. If one tutor or one course has far more misses than others, look at workload, timetabling and communication before looking at people. Agree one or two changes and check again next term. This is a modest routine that gives you real evidence of how your process works, and it is far easier than reconstructing events later.

How does Inclusion Studio support this?

In the Inclusion Studio design, staff record delivered and missed support against the agreed plan, with the reason and how it recovered, and those records feed the review and a controlled evidence export. See delivery tracking. Permissions are intended to be enforced on the server by organisation, relationship and field. Inclusion Studio is pre-pilot: the clickable prototype uses fictional learners and the production application is in development using synthetic data only. Software supports the process; your organisation remains responsible for its records.