Engineering Council Accreditation in the UK: A Guide to AHEP Requirements

The Engineering Council does not accredit individual degree programmes. It sets the overall standard, the Accreditation of Higher Education Programmes framework, in line with UK-SPEC, the Standard for Professional Engineering Competence and Commitment. Actual accreditation is carried out by professional engineering institutions that the Engineering Council has licensed for this purpose. A university sends its accreditation application to one or more of these licensed institutions, and that institution conducts the review, including an accreditation visit, and makes the accreditation decision.

AHEP is currently in its fourth edition. According to the Engineering Council's guidance for higher education providers, accredited status typically runs for five years from the first-year student intake date of the programme, and institutions are expected to reapply for re-accreditation well before that period ends, ideally at least twelve months ahead. Accreditation can apply at bachelor, honours, integrated master's, and other postgraduate levels.

It matters just as much to be precise about what accreditation does not do. An accredited programme supports some or all of the underpinning knowledge, understanding, and skills a graduate needs to pursue professional registration, such as Chartered Engineer or Incorporated Engineer status. It does not automatically grant that status. Registration still requires the individual to apply separately and meet the relevant competence requirements under UK-SPEC.

Once a programme understands who it is actually being reviewed by, the harder problem comes into view. AHEP accreditation rests on whether a programme can show that its intended learning outcomes are genuinely taught, assessed, and achieved, not simply listed in a validation document.

The chain that matters runs from programme learning outcomes through curriculum design, into teaching, into assessment, into evidence of student achievement, into academic review of that evidence, and into whatever improvement action follows. Programmes run into trouble when these pieces live apart from each other. Learning outcomes sit in a curriculum document that was last touched at validation. Assessment evidence sits in module-level records that nobody has mapped back to those outcomes. Programme committee minutes record that an issue was discussed, but there is no link showing what changed in the curriculum or assessment as a result.

An accreditation visit tends to surface exactly this kind of disconnection, because a reviewing panel will typically ask not just what the learning outcomes are, but how a programme knows students are achieving them and what happens when they are not. A programme that can only produce the learning outcomes document, without the assessment and review trail behind it, has a much harder case to make than one that can show the full path.

Accreditation evidence becomes stronger when a programme can trace how its intended learning outcomes are taught, assessed, reviewed, and improved.

 

Many programmes only test whether this evidence chain actually holds together when an accreditation visit is approaching. That timing works against them. A gap between what the curriculum says and what assessment actually measures is far easier to fix a year in advance than during the weeks before a panel visit.

A steadier approach keeps this evidence connected as part of normal programme delivery. Learning outcome mapping stays attached to live curriculum design rather than a frozen validation record. Assessment results get tied back to specific outcomes as they are marked, not reconstructed afterward. Programme review decisions get logged with a clear link to the evidence that prompted them, so a panel, or the programme team itself, can trace a finding through to whatever action followed.

This is an institutional operating comparison, not an official Engineering Council or AHEP model, and it does not change what any specific licensed institution requires for its own review.

Accreditation preparation becomes lighter when the evidence trail already exists.

 

Creatrix Campus helps engineering programmes keep curriculum mapping, learning outcomes, assessment evidence, and programme review connected to the workflows that produce them. Outcome attainment data stays linked to the assessments and curriculum decisions behind it, and improvement actions remain traceable to the review findings that prompted them, reducing the need to reconstruct those relationships when accreditation evidence is required. This does not guarantee Engineering Council accreditation, AHEP approval, or professional registration outcomes, all of which rest with the relevant licensed institution and the Engineering Council.