Glossary

Apprenticeship standard

An apprenticeship standard is the official blueprint for a specific occupation, set by Skills England, defining the knowledge, skills and behaviours an apprentice must demonstrate, plus the funding band, minimum duration and assessment method for that role.

Last updated

Part of our topic guide on Data & AI Apprenticeships.

An apprenticeship standard is the official blueprint for a specific occupation (set by Skills England, not by any training provider) that defines the knowledge, skills and behaviours (KSBs) an apprentice must demonstrate, and fixes the funding band, typical duration and end-point assessment method for that role. Every apprenticeship you can fund through the levy sits inside one of these standards; there's no version of "we'll just write our own apprenticeship". The standard is the fixed spec everyone builds to.

What a standard fixes

Each standard is built and maintained by Skills England, which approves standards against occupational input from employers in that sector (Skills England replaced the former Institute for Apprenticeships and Technical Education, IfATE, in June 2025). Open any standard and five things are already decided for you:

  • The occupation and level: e.g. Data Analyst, Level 4; Data Technician, Level 3, pitched against a defined level of seniority and complexity.
  • The KSBs: the specific knowledge, skills and behaviours the apprentice must be able to demonstrate by the end.
  • The funding band: the maximum the government will put towards training and end-point assessment for that standard. This is what your levy funds, co-investment, or a levy transfer from another employer actually pay against.
  • Minimum duration: at least 8 months for any apprenticeship (reduced from 12 months for starts from 1 August 2025), though a given standard can require longer.
  • The assessment plan: how the apprentice is finally assessed. Most standards use a portfolio or project review plus a professional discussion on real work; a written knowledge test appears only where that standard's own assessment plan specifically requires one. It's the exception, never the default.

What a standard deliberately does not fix

Job titles. Standards are written around the substance of a role, not the label on the door, and this is where most selection mistakes happen. The error we see most often is employers screening candidates by title: our view is that fit is about whether the day-to-day work matches the KSBs in the standard, not whether the person's job title says "data analyst". One Data Analyst or AI & Data Specialist standard covers analysts, coordinators, ops leads, whatever the business calls the role, because what counts is the substance of the work.

How to read one, in the order that protects you

Start at the KSBs and check them against the actual day-to-day of the role you have in mind. The test is whether someone's primary job role is materially aligned to the standard and gives them real opportunity to develop and apply its KSBs. That rules in more people than a title screen suggests, and it rules out anyone whose data work is occasional, adjacent, or a stretch project bolted onto an unrelated role. A role can't be relabelled or topped up to fit a standard.

That bar protects the apprentice more than it constrains the employer. End-point assessment reads real work, so a role that can't generate that evidence produces a learner who can't pass, however willing everyone was at the start. The honest answer to "can we fit this person in?" is sometimes no. You choose the standard that matches the job, not the other way round.

Related terms