What an apprenticeship management system should do.
An apprenticeship management system runs the whole apprenticeship, not just the records. This page sets out the nine components, how the system differs from an MIS and an e-portfolio, and what to check before you call a product an AMS.
One record. A shared direction.
Give every part of the record a clear owner.
An apprenticeship management system is an operating choice as much as a software purchase. Decide who maintains the learner’s core details, who approves plan changes, who closes quality actions and who submits the return. A connected system makes those responsibilities easier to follow; it does not remove them.
Where a college retains a wider MIS, define the authoritative system for each field. Agree how learner identifiers, programme dates and funding changes move between the systems, how rejected updates are handled and when reconciliation takes place.
- One learner identifier across records and imports.
- A named owner for each correction and approval.
- A record of changed dates, reasons and affected sessions.
- A clear reconciliation point before a funding return.
Follow a change all the way through.
Consider an apprentice whose delivery timetable changes. The tutor needs revised sessions and materials; the employer needs visibility of the agreed plan; the quality lead needs to understand the effect on progress. The funding team must separately review whether an ILR change is required under the applicable rules.
Use this example to test an AMS. Ask the supplier to change the delivery plan, show the learner and employer views, and explain the effect on funding records. A calendar edit should not silently become an official funding decision.
Publish programmes with the right people and the right assessment plan.
Only a Tenant Admin or Director can publish and lock a programme. When a programme manager has a draft ready, Journey says who can publish it and offers a Request publication button. The request appears in the approvers’ queue and notifies each of them, so a finished programme never sits unnoticed.
Journey imports the assessment plan alongside the standard’s duties and KSBs. It reads the published formats from Skills England automatically, including older plans and plans with options or pathways, and it never uses AI to do so. Where a plan cannot be read automatically, a programme manager opens the official document beside the programme’s KSBs and records how each one is assessed. A second person then approves the plan, so every standard can have an assessment plan on record.
An apprenticeship management system is software that holds the learner record a training provider uses to run delivery, funding, evidence and quality from enrolment to end-point assessment. A system earns the name when the ILR, portfolio, quality sample and gateway checklist all read from the same record.
The phrase covers a lot of software that does a little. A system earns the name when the record it keeps is the one the ILR, the portfolio, the quality sample and the gateway checklist all read from.
Definition
An apprenticeship management system (AMS) is the software a training provider uses to run apprenticeships from enrolment to achievement. It holds the learner record; plans and evidences delivery; logs off-the-job hours; runs progress reviews with the employer; captures evidence against the knowledge, skills and behaviours of the standard; calculates funding and builds the ILR; supports internal quality assurance; and manages gateway and end-point assessment. In England it must also carry the versioned funding rules and the return calendar.
AMS, MIS and e-portfolio: the difference
| System | Holds | Typical gap |
|---|---|---|
| Management information system (MIS) | Learners, employers, contracts, funding, ILR returns, reporting | Evidence, off-the-job logs and reviews live elsewhere; the ILR and the portfolio disagree |
| E-portfolio | Evidence mapped to KSBs, assessor feedback, learner journal, off-the-job hours | Funding, ILR and quality are separate; gateway readiness is assembled by hand |
| Apprenticeship management system | All of the above on one learner record, with quality and gateway reading from it | Only a gap if the "system" is two products with an export between them |
The nine components
1. Enrolment and eligibility
Eligibility checks against the funding rules version in force on the start date, the apprenticeship agreement and training plan signed by learner and employer, prior learning recorded, English and maths status, and the ILR fields captured once at enrolment.
2. Programme planning
A plan per learner with milestones and planned end date, mapped to the standard, and adjusted for recognition of prior learning.
3. Off-the-job training
Hours logged by learner and tutor against the requirement, with shortfalls flagged before they become a funding problem.
4. Progress reviews
Tripartite reviews on a cadence, signed by the employer in the system, with the review and the signature as one entry on the record.
5. Evidence and e-portfolio
Evidence mapped to KSBs with assessor feedback and coverage reporting, so gateway readiness can be read rather than compiled.
6. Funding and ILR
Agreed price and route, funding rule checks against the versioned pack, ILR returns R01 to R14 built from the record, employer levy position recorded against each employer.
7. Quality assurance
Sampling plans, observations, actions with owners and due dates, self-assessment and quality improvement evidence, IQA and EQA readiness, all on the record the tutor uses.
8. Gateway and end-point assessment
A readiness checklist that reads from the components above; a hand-over to the assessment organisation as a minimised pack with an approval and a receipt; the result written back to the record; achievement and destination recorded.
9. Leadership questions
The reason the record exists: a director asks which learners are behind plan, which funding records would fail the next return, which learners are approaching gateway with an item outstanding, and gets the answer with sources. In Journey that is Journey AI.
Five checks before you call it an AMS
- Change a progress review and watch whether the ILR and the portfolio both reflect it without an export.
- Ask which funding rules versions the system holds and how the version is chosen for a learner.
- Ask what is typed twice between the portfolio and gateway readiness. The answer should be nothing.
- Ask how the pack reaches the assessment organisation and how the result comes back.
- Ask a leadership question and look for the sources.
How Journey does it
Journey is an apprenticeship management system built around one connected learner record. Delivery, funding, e-portfolio, quality and gateway write to it with a named audit trail. The ILR is built from it. Gateway readiness reads from the record; after named approval, a pack can be handed to an assessment organisation using Meritura. Journey Advanced adds Journey AI with AI included. Journey Core is free for verified UK training providers with up to 50 counted apprentices, subject to application review.
Questions providers ask
What is an apprenticeship management system?
An apprenticeship management system (AMS) is the software a UK training provider uses to run apprenticeships end to end: enrolment and eligibility, programme planning, off-the-job hours, progress reviews, evidence against the standard, funding and the ILR return, quality assurance, gateway and end-point assessment. Journey is an AMS that keeps all of that on one connected learner record.
Is an apprenticeship management system the same as an MIS?
No. A management information system (MIS) is the record-keeping and reporting core: learners, employers, contracts, funding and returns. An apprenticeship management system includes the MIS and adds the delivery and evidence side: e-portfolio, off-the-job, reviews, quality and gateway. Many providers run an MIS and a separate e-portfolio and reconcile them; an AMS avoids that.
Do colleges need an apprenticeship management system if they already have an MIS?
It depends on the college’s existing capability. Assess whether its MIS and connected tools already support the apprenticeship’s delivery, employer reviews, evidence, off-the-job activity and assessment handover. Journey can be evaluated alongside that environment with an agreed import and reconciliation plan.
What does "one connected learner record" mean in practice?
Every team writes to the same record for each apprentice, with a name and a time on every change. The evidence portfolio, the quality sample and the gateway checklist read from those entries, and the ILR return is prepared from the same learner record, so nothing is typed twice.
Related pages.
See Journey on your own questions.
A guided walkthrough of the connected record and the questions your leadership team actually asks.
See what changes
when it all connects.
Bring your learners’ journey, your team’s questions and your next ambition.