Apprenticeship Units Evidence Pack Checklist: What Providers Need to Keep in 2026

Last updated: 30 May 2026

Why Apprenticeship Unit Evidence Is Different

Apprenticeship units are now a live funding product under the Growth and Skills Levy. They give employers and providers a shorter route for targeted skills development, but they are not mini apprenticeships. That distinction matters most in the evidence pack.

The unit funding rules require providers to prove that the learner exists, is eligible, has a legitimate learning need, receives eligible delivery hours, completes the required assessment, and is reported correctly. Those controls will feel familiar to any apprenticeship provider. The risk is assuming that familiar means identical.

Full apprenticeships are built around an apprentice employment relationship, a training plan, off-the-job training, progress reviews, KSB mapping, gateway evidence, and end-point assessment. Apprenticeship units have a different structure. Providers need evidence that matches the unit rules, not a copied apprenticeship file with labels changed.

The Core Record Every Unit Learner Needs

Start with a clean learner-level record. For each learner, the provider should be able to show the unit title, unit code or reference, employer, learning start date, planned end date, agreed delivery hours, assessment requirement, funding route, and current status.

This is the spine of the evidence pack. Every other document should connect back to it. If a delivery register, eligibility check, assessment record, or change-of-circumstance note cannot be tied to the learner and the unit, the pack will be difficult to audit.

The record should also identify whether the learner is funded through a levy-paying employer account, non-levy reservation, transfer, or co-investment route. The funding route affects the commercial and reporting trail, so it should be visible from the start rather than reconstructed later.

Eligibility Evidence: Learner, Employer, and Programme

The initial assessment is not just a sales conversation. It is the point at which the provider confirms that the learner, employer, and programme are eligible for funding.

For the learner, keep evidence of age, employment status, residency eligibility, working location, and any restriction that could prevent completion. The rules include important exclusions, including learners who are self-employed as sole traders, already undertaking an apprenticeship or another apprenticeship unit, or using another funding source for overlapping training.

For the employer, keep evidence that the employer is connected to the learner and is entitled to use the relevant funding route. For levy-funded learners, the employer account and funding authorisation trail should be retained or referenced. For non-levy employers, keep the reservation or co-investment trail.

For the programme, keep the approved unit specification, the planned content, planned delivery hours, assessment method, and evidence that the learner has a learning need. The prior learning check is particularly important. A learner is not eligible if their existing knowledge and skills overlap with the majority of the planned unit content.

Delivery Hours: The Evidence Area Most Likely to Fail

Delivery hours are the most important operational difference between apprenticeship units and full apprenticeships. The unit rules define delivery hours tightly. The hours must deliver new knowledge and skills, be directly relevant to the unit, take place during the learner's normal working hours, and involve the tutor and learner being in the same physical or virtual space.

This means providers need more than a learning activity log. A robust delivery hours record should show the date, time, duration, tutor, learner attendance, delivery mode, unit content covered, and whether the session took place during normal working hours.

Providers should be careful with asynchronous materials. Self-directed learning, assignments set outside a taught session, revision, examinations, and other testing do not count as delivery hours under the unit definition. They may still support learning, but they should not be included in the funded delivery total unless the rules allow it.

Virtual delivery is acceptable where the tutor and learner are present at the same time. Keep attendance evidence that shows live participation, not just access to a recording or resource.

Assessment Evidence

Each unit needs assessment evidence that proves the learner has acquired the required knowledge and skills. The assessment method will depend on the unit specification, but the evidence pack should normally include the assessment brief, learner submission or performance evidence, assessor decision, date of assessment, result, feedback, and any resit or reassessment record.

Assessment evidence should be separated from delivery evidence. A taught session can contribute to delivery hours. An examination, test, or assessment activity should not be counted as delivery hours unless the unit rules explicitly permit it. Mixing the two creates avoidable funding risk.

Providers should also retain internal quality assurance evidence where it applies. Shorter provision still needs credible assessment decisions, especially where funding is attached to completion or achievement.

Change of Circumstance Evidence

Short programmes still need change controls. A learner may change employer, working hours, location, contract status, planned end date, or eligibility status during the unit. Any of those changes can affect funding.

The evidence pack should include the date the provider became aware of the change, the nature of the change, the funding impact, the action taken, employer confirmation where relevant, and the reporting update made in the provider system. If the learner becomes ineligible, the provider should record the withdrawal decision and the date used for reporting.

Because units are shorter than full apprenticeships, delays in recording changes matter. A provider that waits until monthly reconciliation may discover that the unit has already ended and the evidence trail is incomplete.

System Controls Providers Should Put in Place

Good unit delivery needs system separation. The provider system should distinguish apprenticeship units from full apprenticeships, foundation apprenticeships, Skills Bootcamps, commercial courses, and compliance training. The evidence fields, hours definitions, assessment stages, and reporting outputs should match the product.

At minimum, providers should configure programme templates for unit delivery, live delivery hour capture, eligibility checks, employer approval, prior learning notes, assessment records, and change-of-circumstance tracking. Managers should be able to report on missing evidence before the funding return is submitted.

The most useful dashboard is simple: learners started, eligibility complete, employer agreement complete, planned hours, delivered hours, assessment status, exceptions, and reporting status. If the provider cannot see those fields in one place, operational risk will sit in spreadsheets and inboxes.

Provider Checklist

• Learner record: learner identity, employer, unit, start date, planned end date, funding route, status.
• Eligibility: age, employment, residency, working location, exclusion checks, funding route, and employer connection.
• Initial assessment: learning need, programme fit, prior learning check, support needs, and employer discussion.
• Programme evidence: approved unit specification, planned content, planned delivery hours, assessment method, price, and funding band where applicable.
• Employer agreement: confirmation of participation, working-hours arrangements, funding authorisation, and any co-investment requirement.
• Delivery hours: date, time, tutor, learner, mode, live attendance, duration, normal working hours confirmation, and unit content covered.
• Assessment: brief, evidence, assessor decision, result, feedback, quality assurance, and resit records.
• Change controls: changes to employment, eligibility, dates, withdrawal, completion, or funding status.
• Management information: reporting status, errors, reconciliations, funding claims, and audit exceptions.

Frequently Asked Questions