A useful apprenticeship compliance plan makes it clear where the provider is exposed, who is responsible for putting things right and how leaders will know the action has worked.

For MIS and quality leaders, the difficult part is often joining up the evidence. Learner records, funding data, quality reviews and management actions can each look reasonable on their own while telling different stories when brought together.

This guide explains how apprenticeship providers can build a practical compliance improvement plan that supports funding assurance, Ofsted inspection preparation and day-to-day operational oversight.

Scope: apprenticeship provision in England. Official guidance checked on 7 October 2026. Use the funding rules, provider agreement and inspection guidance that apply to your provision; the planning method below is a recommended management approach.

What is an apprenticeship compliance plan?

An apprenticeship compliance plan is a working record of the risks, controls and improvement actions needed to meet the provider’s responsibilities. It connects each identified issue to an accountable owner, a deadline, supporting evidence and a decision about whether the risk has been resolved.

It should answer five questions:

  1. What responsibility or expectation are we checking?
  2. What does the evidence tell us about current practice?
  3. What needs to change, and who will do it?
  4. How will we verify that the change has happened?
  5. How will we check that it continues to work?

A compliance plan can sit alongside your quality improvement plan (QIP), or form a clearly identified part of it. Choose an arrangement that allows staff to find the current action and avoids maintaining competing versions.

Keep funding assurance and Ofsted preparation distinct

Funding compliance and the quality of apprenticeship provision are connected, but they require different assurance questions. A funding check examines whether the relevant requirements are met and evidenced. A quality review examines what apprentices are learning, the support they receive and the effect of leadership decisions on their experience and outcomes.

The 2026 to 2027 apprenticeship funding rules apply to apprenticeships starting between 1 August 2026 and 31 July 2027. Earlier starts may fall under earlier rules. Record which rules apply before assessing a learner file.

For inspection preparation, use the current Ofsted further education and skills toolkit and operating guidance. The guidance was updated for September 2026; check that internal inspection checklists reflect the current version.

Bring findings into one management view while retaining their source, purpose and verification criteria. A complete set of documents alone cannot establish the quality of learning.

Step 1: map your responsibilities and evidence sources

Start with a responsibilities register. For each area, record the applicable source, the internal process that implements it, the person responsible for the control and the evidence used to check it.

Use your provider agreement, relevant funding rules and current inspection guidance as source material. Add other obligations relevant to your organisation, including safeguarding, data protection and subcontracting where applicable.

A practical starting scope includes:

  • Enrolment and eligibility: initial assessment, prior learning, relevant eligibility evidence and agreements.
  • Training and progress: individual training plans, delivery records, off-the-job training evidence and progress reviews.
  • Funding and data: consistency between source records, the individualised learner record (ILR), apprenticeship service records and financial information.
  • Changes and completion: how changes in circumstances, breaks, withdrawals and assessment requirements are recorded and checked.
  • Quality and learner support: curriculum, assessment, internal quality assurance (IQA), feedback, inclusion and the effectiveness of support.
  • Leadership and oversight: safeguarding oversight, subcontractor assurance where relevant, escalation and management follow-through.

These are review areas, rather than a substitute for the detailed requirements. Give each control a reference to the relevant source so reviewers can explain the basis for their judgement.

Step 2: establish a baseline you can trust

Bring together recent audit findings, quality sampling, data exceptions, complaints, learner and employer feedback, and outstanding management actions. Record the period covered and the limits of the evidence.

Use a mix of risk-based sampling and broader coverage. If you only review the records already flagged as problematic, you can investigate those exceptions but cannot assume the rest of the provision is sound.

For every finding, capture the affected process or cohort, the evidence checked and whether the issue appears isolated or recurring. Keep “not checked” visible as a separate state. An empty result is not evidence of compliance.

Where a dashboard identifies an exception, trace it back to the source. Confirm that the reporting period, learner status and rule version are correct before asking delivery staff to act. For a wider approach to reconciliation, see how to manage apprenticeship data across systems.

Step 3: prioritise by risk and establish the cause

Assess findings against potential harm to apprentices, funding exposure, the scale of the issue and the likelihood of recurrence. Urgent safeguarding concerns should follow the provider’s safeguarding procedures immediately; they should not wait for the next plan review.

Separate immediate containment from the change needed to prevent recurrence. Correcting an individual record may resolve that exception, while leaving the process that created it unchanged.

Ask where the control broke down. Was the responsibility unclear? Did staff lack access or training? Was information recorded in one system but missing from another? Did a check run without anyone reviewing its results? Test the explanation against the available evidence before deciding on an action.

Where funding exposure is suspected, assign someone to assess its scope and determine the appropriate response under the relevant rules and agreement. Record unresolved questions explicitly.

Step 4: write actions that can be verified

“Improve documentation” gives an owner little direction and gives a reviewer no clear basis for closure. Describe the change, the affected scope and the evidence needed to demonstrate completion.

Use the following structure for each action:

  • Finding and source: what was observed, when it was checked and which requirement or expectation applies.
  • Risk and scope: why it matters and which records, teams or processes need attention.
  • Cause: the supported explanation, with any remaining uncertainty.
  • Immediate response: what is needed to contain the current risk.
  • Improvement action: the specific change to the process or control.
  • Owner, deadline and dependencies: who is accountable, when it is due and what they need.
  • Verification and impact: who will check the result, what evidence they will use and what improvement they expect to see.
  • Status and follow-up: progress, closure decision, residual risk and the next check date.

For example, if sampling finds inconsistent review records, the action could specify the affected records to review, the recording process to clarify and a follow-up sample of newly completed reviews. The follow-up should check the quality of the review and resulting actions as well as whether the record exists.

Set targets from your actual baseline and agreed risk tolerance. Record the rationale so the team can explain why the target is appropriate.

Step 5: give MIS, quality and operations clear responsibilities

Assign one accountable owner to each action, even when several teams contribute. Shared work still needs a person responsible for reporting progress and resolving dependencies.

A useful division of responsibilities is:

  • MIS and data teams: validate reporting definitions, trace exceptions and reconcile records.
  • Quality teams: test practice through sampling, observation and feedback, then evaluate the effect of improvements.
  • Operations teams: implement changes in delivery and make sure staff understand the process.
  • Compliance and finance teams: assess funding requirements, evidence and financial exposure within their remit.
  • Senior leaders and governors: challenge progress, resolve resource constraints and oversee significant residual risks.

Adapt this to your organisation. Where staffing allows, use someone other than the action owner to verify closure, particularly for higher-risk findings.

Step 6: build a proportionate evidence trail

Link actions to controlled source records rather than copying documents into several folders. A reviewer should be able to follow the finding, the decision, the change and the subsequent check.

Record the date and scope of verification. If an action is only partly implemented, show what remains open and what temporary control is in place. Keep sensitive learner and safeguarding information within the appropriate access arrangements; management summaries should contain only the detail needed for oversight.

For inspection preparation, Ofsted’s information for providers says it does not expect additional work specifically for inspection or information in a prescribed format. Maintain useful working evidence through normal operations. Our guide to Ofsted evidence trails explores how to connect practice, oversight and impact.

Step 7: review improvement, not just completed tasks

Agree a review rhythm that reflects the risk. As a starting management approach, teams might review urgent exceptions weekly, the overall plan monthly and strategic themes at their normal governance meetings. Adjust the frequency when the evidence warrants it.

Track overdue actions, repeated exceptions, unresolved dependencies and findings reopened after verification. Measure improvements using consistent definitions and comparable periods. Explain changes in the population being reviewed so apparent progress is not simply the result of a different sample.

Keep implementation and effectiveness visible separately. Updating a procedure is an implementation milestone. Staff applying it correctly, and the identified problem becoming less frequent, provide evidence of effectiveness.

A suggested 90-day approach

This is an implementation sequence for your team, rather than a regulatory timetable. Deal with urgent risks immediately.

  1. Days 1–30: establish the baseline. Confirm responsibilities and applicable sources, review existing findings, test priority controls and agree the action register.
  2. Days 31–60: implement improvements. Address priority exceptions, clarify processes, support staff and resolve dependencies between teams and systems.
  3. Days 61–90: verify and challenge. Check newly completed work, assess recurrence, review residual risks and report what has improved and what remains unresolved.

Continue the cycle after the initial period. New starts, rule changes and changes in delivery can create new risks even when earlier actions have been closed.

When apprenticeship compliance consultancy can help

Apprenticeship compliance consultancy can be useful when leaders need an independent view of recurring findings, help interpreting requirements or additional capacity for a focused improvement programme.

Agree the scope before commissioning support: the questions to answer, evidence to review, outputs to deliver and how your team will maintain the controls afterwards. Audit support is most useful when findings lead to clear, owned actions and a follow-up check.

AiVII’s consultancy services cover funding compliance and audit readiness, Ofsted preparation, quality improvement planning and operational reviews. The AiVII provider management platform brings reporting, quality activity and governance workflows into the management of provision. Your team remains responsible for interpreting requirements and making assurance decisions.

Need a clearer starting point? Explore AiVII’s apprenticeship compliance consultancy and discuss the risks, evidence gaps and improvement priorities your team needs to address.

Frequently asked questions

Is an apprenticeship compliance plan the same as a QIP?

They can share actions, but their purposes differ. A compliance plan makes responsibilities, controls and exceptions explicit. A QIP normally covers wider improvements to provision. Connect the two so owners and closure decisions remain consistent.

How often should the plan be reviewed?

Choose a frequency based on risk and your governance arrangements. Review significant new findings promptly, and bring forward a review when a rule change, delivery change or repeated exception affects the plan.

What evidence should close an action?

Use the verification criteria agreed when the action was set. Check that the change was implemented, test whether it addresses the finding and record any residual risk or later effectiveness check.

Does a compliance plan guarantee a successful audit or inspection?

No. It helps leaders manage responsibilities and demonstrate their response to findings. The underlying practice and evidence still need to stand up to scrutiny.