How to choose apprenticeship software, step by step.

Most apprenticeship software decisions go wrong before the first demo. The provider asks suppliers to show what they have, rather than deciding what the record must do. This guide starts from the record.

1. Write the requirements from the record outward

Every apprenticeship generates the same record: an enrolment, a programme plan, off-the-job hours, progress reviews, evidence against knowledge, skills and behaviours, a funding record and ILR returns, quality checks, gateway readiness and an end-point assessment result. Five teams write to it. The first question is whether the system keeps that as one record or as several that someone reconciles.

Write one line per team describing what it must be able to do on the record without leaving the system:

• Delivery. Programme plan with planned end date, off-the-job hours logged against the requirement, progress reviews every twelve weeks signed by the employer, breaks in learning and withdrawals recorded correctly.
• Funding. Agreed price and levy or non-levy route on the record, funding rule checks against the versioned rules for the start date, ILR returns R01 to R14 built from the record, apprenticeship service reconciliation.
• E-portfolio. Evidence mapped to KSBs, assessor feedback, learner journal, employer observations, coverage reporting.
• Quality. Sampling plan, observations, actions with owners and dates, self-assessment and quality improvement evidence, IQA and EQA readiness.
• Gateway. Readiness checklist that reads from the sections above, EPA booking and outcome, achievement and destination, and a hand-over to the assessment organisation that is not an email with attachments.
• Leadership. Questions answered from the record with sources, not dashboards to decode. Ask what happens when a director asks "which learners are due for gateway without a signed employer review?"

2. Score suppliers on ten criteria

Score each criterion 0 (absent), 1 (partial or manual), 2 (present) or 3 (present and evidenced on the supplier's own pages or in a walkthrough on your data). A supplier that scores under 20 of 30 will cost you the missing points in staff time.

3. Run walkthroughs on your own questions

A demo shows the supplier's best path. A walkthrough follows yours. Send three things a week ahead: the standards you deliver most, the number of sites and employers, and the two problems you most want to stop paying for. Then ask for these four moments in the session:

1. One learner from enrolment to a released result, with the audit trail visible.
2. An ILR return built from the record and validated in front of you.
3. Gateway readiness reading from the record, and the hand-over to the assessment organisation.
4. A leadership question answered from the data, with the sources it used listed.

Take notes against the ten criteria during the session. If a capability is "on the roadmap", score it 0.

4. Check governance and security before price

Learner records are personal data about young people and adults in employment. Before negotiating price, have written answers to: where data is hosted and by which sub-processors; how tenants are isolated; how roles are scoped and how access is reviewed; what the audit trail records and for how long; how the supplier handles a subject access request; what the accessibility statement commits to; and, for any AI feature, where answers come from, whether the AI can change a record, and whether every answer shows its sources.

5. Price the total cost of ownership

The licence is one line of six. Add implementation and configuration; migration of history from the current system; training for tutors, assessors, admin and employers; integrations with finance, HR and the apprenticeship service; ongoing support; and the internal hours the system will remove or add. A system that saves an MIS officer two days per ILR return saves roughly 28 days a year, which is often worth more than the licence difference. The total cost of ownership checklist lists the questions to ask.

6. Plan the migration around an ILR return

Export learners, employers, programmes, reviews, off-the-job logs and evidence with dates and authors preserved. Import into the new system while the old contract is still running. Build one ILR return in both systems and reconcile the differences; they will show you every field the old export was fudging. Only then switch. Keep the export as an archive: funding audits and inspections reach back several years.

Where Journey sits

Journey keeps the five teams on one connected learner record, builds the ILR from it, reads gateway readiness from it, hands the pack to Meritura in one click, and answers leadership questions from it with sources through Talk to Journey. Journey Core is free forever for verified UK providers with up to 50 counted apprentices subject to application review; Journey Advanced is priced per provider. Score us on the same ten criteria, on your own data.

Questions providers ask

• How long does it take to choose apprenticeship software?

  Providers that run a structured evaluation typically take six to ten weeks from requirements to signed terms: two weeks to write requirements and score criteria, three to four weeks of walkthroughs and reference calls, and two to four weeks for due diligence and contracting. Rushing the requirements stage is the most common cause of a poor fit.

• Should the MIS and the e-portfolio be the same system?

  If they are separate, someone reconciles them: the ILR says one thing, the portfolio says another, and the funding audit finds the gap. One connected learner record removes that reconciliation. Where a provider keeps a separate system for a good reason, insist on a named integration with a documented field map rather than a manual export.

• What should we ask a supplier about AI?

  Four questions: where the answers come from (your data or the open web), whether the AI can change any record on its own, whether every answer shows its sources, and how usage is metered and priced. A supplier that cannot answer all four in a sentence each has not governed the feature.

• How do we migrate without losing evidence?

  Export learners, employers, programmes, reviews, off-the-job logs and evidence from the current system with dates and authors preserved, import into the new system before the old contract ends, and run both for one ILR return. Keep the export as an archive; funding audits reach back several years.

• What does apprenticeship software cost?

  Published prices are rare. Suppliers quote per learner per month, per user, or per provider. The licence is usually a third to a half of the total cost once implementation, migration, training, integrations and internal staff time are counted. Journey Core is free forever for verified UK providers with up to 50 counted apprentices subject to application review; Journey Advanced is priced per provider.