Off-the-job training hours: a complete guide for apprenticeship providers

What the OTJ requirement actually says

ESFA funding rules require that every apprentice spends a minimum average of 6 hours per week — or at least 20% of their contracted working hours — on off-the-job training throughout the planned programme duration. This training must take place within their contracted working hours, must be directly related to the apprenticeship standard, and must be distinct from their normal day-to-day job duties.

The “6 hours or 20%, whichever is higher” formula means the requirement scales with the apprentice’s contracted hours. An apprentice on a 30-hour week needs at least 6 hours of OTJ per week. An apprentice on a 40-hour week needs at least 8 hours (20% of 40). Part-time apprentices working fewer than 30 hours per week can apply to ESFA for a modified OTJ calculation — this requires prior approval and must be documented.

The calculation is made across the full planned programme duration, excluding any approved breaks in learning. This means the total minimum OTJ hours is not a fixed number — it varies by contract type, programme length, and any breaks in learning that were approved during delivery.

What counts as OTJ training — a practical reference list

ESFA provides a list of activity types that qualify as off-the-job training. Understanding this list — and being able to categorise logged activities against it — is essential for audit compliance.

Activities that count:

• The teaching of theory (for example, lectures, role playing, simulation exercises, online learning, manufacturer training)
• Practical training (shadowing, mentoring, industry visits, and participation in competitions)
• Learning support (time spent with learning support workers when the learning is directly related to the apprenticeship standard)
• Writing assessments or assignments
• Completing projects directly related to the apprenticeship standard
• Time with the provider for taught sessions, workshops, or reviews that include a formal learning component

Activities that do not count:

• English and maths initial assessment and teaching (these are counted separately)
• Progress reviews (unless there is a substantial taught or reflective learning component beyond the standard review format)
• Normal work duties, even if the apprentice is developing through them
• Overtime hours (OTJ must take place within contracted hours)
• Any training the employer was providing before the apprenticeship started

The boundary between “training delivered through work” and “normal work duties” is the most common source of audit disputes. A useful test: if the activity would have been part of the role whether or not the person was on an apprenticeship programme, it is probably a work duty, not OTJ.

Calculating minimum OTJ hours: worked examples

Calculating the minimum is more involved than it appears, particularly for part-time workers, long programmes, or learners who take a break in learning.

Standard example: An apprentice on a 37-hour week completing a 15-month (65-week) programme. Minimum OTJ = 20% of 37 hours = 7.4 hours per week. Total minimum = 7.4 × 65 = 481 hours.

Lower contracted hours: An apprentice on a 25-hour week. 20% of 25 = 5 hours, which is below the 6-hour minimum floor. Minimum OTJ is therefore 6 hours per week. For a 15-month programme: 6 × 65 = 390 hours.

Break in learning: The same 37-hour-week apprentice takes an approved 8-week break in learning due to illness. The programme is extended by 8 weeks, and the OTJ calculation is recalculated against the revised planned end date. The break weeks are excluded from the minimum hours calculation, but the total minimum hours remain based on the full planned duration post-extension.

Providers managing multiple cohorts across different contract types and programme durations need a system that calculates the correct minimum automatically per apprentice — not a standard figure applied universally across the cohort.

The four OTJ tracking failures that fail audits

ESFA compliance audits consistently identify the same four failure modes in OTJ tracking. Each is avoidable with the right process.

1. Retrospective logging. Hours logged at the end of the month or just before a progress review, reconstructing activities from memory or a tutor’s diary. Auditors look at the timestamp on each log entry relative to the date of the activity. Consistent same-day or same-week backdating is treated as evidence of unreliable records. The standard is contemporaneous logging — entered on the day of the activity or within a very short window.

2. Vague activity descriptions. Log entries that read “online training” or “learning activity” without specifying the content, duration, activity type, and connection to the apprenticeship standard. These cannot be verified against the ESFA definition of OTJ and will be challenged in audit. Each entry should specify the activity type (from the approved list), what was covered, how it relates to the standard, and how long it lasted.

3. No employer sign-off. The employer is a signatory to the commitment statement and shares responsibility for OTJ delivery. Without employer confirmation that logged activities took place, the provider’s record is a single-party claim. In an ESFA audit, unverified hours are at risk of being discounted. A structured employer sign-off workflow — not an email chain or a box ticked during a progress review — is the minimum required.

4. Shortfall discovered at gateway. The most operationally damaging failure. Without a running total tracked against the minimum target, shortfalls accumulate invisibly until the gateway calculation is done — often too late to recover. A provider that reaches gateway and discovers an apprentice is 80 hours short with three months remaining faces an impossible remediation timeline. Automated alerts at 80% of the minimum threshold give enough runway to recover.

Building a robust OTJ tracking process

Effective OTJ tracking combines system design, workflow discipline, and employer engagement. No single element is sufficient on its own.

Real-time logging by apprentices. Requiring tutors to log all OTJ hours centrally is a bottleneck that produces delays and inaccuracies. The most reliable approach is apprentice-led logging at the point of activity, with a structured form that requires activity type, description, duration, and connection to the standard. The tutor’s role is oversight and approval, not data entry.

Employer sign-off built into the workflow. Employer confirmation should be a step in the logging process, not an afterthought. The platform should notify the employer contact when new OTJ entries are submitted and require their digital sign-off before hours are counted toward the running total. This creates a contemporaneous, employer-verified record automatically.

Monthly compliance checks. At the end of each month, the tutor or programme manager should check the running total against the minimum target trajectory. This is not the same as waiting for the quarterly progress review — monthly monitoring gives earlier warning of shortfalls and more time to respond.

Documented remediation for shortfalls. When an apprentice falls below the minimum trajectory, the remediation plan must be documented: what additional OTJ activities are planned, by when, and how the shortfall will be recovered. This documentation is as important as the hours themselves — ESFA auditors look for evidence that the provider identified the issue and acted on it.

How automated platforms change OTJ management

The difference between managing OTJ in a spreadsheet and managing it in a purpose-built platform is the difference between finding out about a shortfall at gateway and finding out three months before gateway when there is still time to act.

Purpose-built OTJ tracking software gives apprentices a simple interface to log activities in real time, routes entries to employers for sign-off automatically, calculates the running total against the correct minimum for each individual apprentice, and sends alerts when the accrual rate falls below the level needed to meet the minimum by the planned gateway date.

At audit, the platform generates a structured export of every OTJ log entry — with timestamps, activity types, descriptions, employer confirmations, and running totals — that satisfies the ESFA’s contemporaneous record requirement without any manual assembly.

The operational benefit extends beyond compliance. Tutors who can see OTJ accrual rates in real time can intervene earlier, have more specific conversations with employers about delivery planning, and build OTJ activities more deliberately into the learning programme rather than treating them as something that happens incidentally alongside the main delivery.

What ESFA auditors look for specifically

ESFA compliance audits of OTJ hours focus on five questions:

1. Does the provider have a contemporaneous record of OTJ activities for each apprentice?
2. Do the recorded activities meet the ESFA definition of off-the-job training — i.e., are they genuinely distinct from normal work duties?
3. Has the employer verified the logged activities?
4. Does the running total meet the minimum required for each apprentice?
5. Where shortfalls exist, is there a documented remediation plan?

Providers who can answer yes to all five questions with documentary evidence — produced quickly, not assembled over several days — pass OTJ audits. Those who cannot answer yes to all five are at risk of audit findings, funding clawback, and in serious cases, enhanced ESFA monitoring.

Practical checklist

• Calculate the correct minimum OTJ hours for each apprentice individually, accounting for contracted hours and programme duration
• Enable apprentice-led real-time logging with activity type and description as required fields
• Implement employer sign-off as a step in the logging workflow, not an optional extra
• Track running totals against minimum targets with automated alerts at 80% threshold
• Conduct monthly OTJ compliance checks, not just quarterly at progress reviews
• Document all remediation plans for learners falling below minimum trajectory
• Generate an audit-ready export monthly so you are never assembling records from scratch under audit conditions