How to Track Off-the-Job Training: An Audit-Ready Provider Workflow

Last reviewed: 15 July 2026 against version 1 of the 2026 to 2027 funding rules.

An OTJ tracker is not merely a running total. It should prove that the activity was eligible, show whether delivery is keeping pace with the agreed plan, and surface gaps early enough to act. The hour total is the result of that evidence chain—not a substitute for it.

Use three connected records

A defensible process connects three layers:

1. Baseline: the standard, published minimum, initial assessment, prior-learning adjustment and agreed planned hours.
2. Delivery: individual eligible activities with KSB mapping and participation evidence.
3. Control: monthly exception checks, progress-review actions and final reconciliation to actual ILR hours.

If those records live in separate spreadsheets, assign a stable learner identifier and a named owner for reconciliation. Otherwise a correct total can still be unsupported by the underlying activity or attached to the wrong programme version.

Minimum fields for each learner and activity

Learner baseline

• apprenticeship standard code and version;
• start date and applicable funding-rule year;
• published minimum OTJ hours at enrolment;
• typical planned hours set by the provider;
• evidenced prior learning and the approved reduction, if any;
• adjusted compliance minimum and the eight-month duration check;
• planned delivery model: regular, front-loaded or block release; and
• employer, learner and provider approvals.

Activity log

• activity date and eligible duration;
• clear description of the new learning;
• KSBs addressed and curriculum component;
• delivery method and person or organisation delivering it;
• confirmation that it occurred within normal paid working hours;
• participation evidence or learner output;
• provider verifier, decision and date; and
• rejection reason where an activity is ineligible.

Run a monthly control, not a gateway rescue

For an ordinary delivery model, create a calendar-month exception report. At minimum, flag:

• no planned active learning in the month;
• planned activity that did not occur;
• submitted hours waiting for provider verification;
• activities with no KSB link or no participation evidence;
• delivery outside normal working hours without an agreed compensated exception;
• cumulative delivery materially behind the provider's curriculum plan; and
• a mismatch between the training plan, apprenticeship agreement and ILR baseline.

For an agreed front-loaded or block-release model, configure the three-calendar-month active-learning rule instead. Do not apply that wider interval merely because delivery has become irregular; the model must be agreed with the employer and documented in the signed training plan.

Use a simple evidence-quality test

Before approving a log, the provider should be able to answer five questions:

1. Relevant? Which required KSB did the learner develop?
2. New? What learning occurred beyond ordinary productive work?
3. In time? Did it happen in the practical period and normal working hours?
4. Demonstrated? What proves participation or output?
5. Verified? Who checked the activity and when?

Descriptions such as “project work”, “study” or “shadowing” are categories, not evidence. A stronger entry records the learning objective, relevant KSB, output and eligible time. Evidence should be proportionate: attendance records, tutor notes, a submitted assignment, version history, observed practice or a learner reflection can all contribute when they support the specific claim.

Turn exceptions into owned actions

Record the action in the training plan or progress-review workflow, but remember that a progress review itself is excluded from OTJ hours.

Reconcile before the practical period ends

Run a pre-completion check early enough to resolve genuine gaps:

• verify that every hour included in the total is eligible and evidenced;
• confirm the adjusted minimum has been met and all KSBs have been delivered;
• compare actual delivery with the original planned-hours figure;
• do not overwrite that original ILR planned-hours field except for an initial input error;
• report eligible actual hours when required; and
• where actual hours are below the original plan but still compliant, obtain the employer and apprentice statement required by the rules.

A good tracker therefore supports both curriculum management and funding evidence. It shows the target, the learning behind every approved hour, the exceptions raised and the decisions taken—not just a green percentage on the day before completion.