Built from the reality of running a provider.
Journey began with a provider’s experience of paying for a platform and still relying on spreadsheets, shared drives and people chasing evidence. Karan’s response was to bring the record, the teams and the questions they ask into one connected apprenticeship journey.
One record. A shared direction.
Journey is a connected apprenticeship platform founded by Karan, drawing on his experience of running a training provider. Its product direction brings delivery, evidence, funding, quality and gateway around the learner, with Journey AI adding a conversational way to understand authorised records.
The problem was the work between the systems
In Karan’s account, his provider paid roughly £36,000 a year for its platform, yet the team was still using Excel and chasing evidence across shared drives when an inspection came. That figure describes his own experience. It is not a claim about every provider’s costs or a promise of the savings another organisation will make.
The experience shaped the central question behind Journey: how can the record stay useful to every team as the learner moves forward? Enrolment information should support delivery. Learning evidence should remain available to quality. Gateway preparation should build on the work already done. The result should return to the learner’s story.
The principles behind the product
| Principle | What it means in the working day |
|---|---|
| The learner stays at the centre | Teams work with the same learner context as responsibilities change. |
| An answer should keep its evidence | People can open the records behind a status or a Journey AI response. |
| Responsibility remains visible | Actions, approvals and consequential decisions belong to named people. |
| The next stage should stay connected | The approved gateway pack and released assessment result have a traceable handover. |
| Starting well should be accessible | Core offers eligible providers the operational foundation with no licence fee. |
Judge Journey by the work it helps you complete
A founder’s experience explains why a product exists. Your own provision determines whether it is the right fit. We encourage you to bring the workflows, difficult handovers and recurring questions that your team deals with today.
Ask to see a learner move through the connected record. Open the evidence behind an answer. Examine a correction as well as a successful handover. Review the edition, migration plan and support scope in writing. Those practical checks provide a stronger basis for your decision than a broad promise about transformation.
Journey is the operating platform for UK apprenticeship training providers. It brings delivery, evidence, funding, ILR, quality, safeguarding and EPA onto one connected product record so teams can act on the same truth.
Built from the experience of running training provision.
Journey was founded by Karan Kumar, drawing on his experience running a training provider. The aim is practical: connect the learner record, the people working with it and the evidence behind the next decision. The founder’s experience informs the product; it is not presented as an independent customer study or a guaranteed result for another provider.
Who is responsible for the information here?
Journey’s editorial team maintains the website. Product explanations are checked against documented implementation and release scope. Regulatory guidance links to primary sources and identifies relevant dates or start-year rules. Comparisons link to supplier evidence and distinguish a missing public statement from a missing feature.
AI-assisted drafting can help organise and explain material, but it does not create a qualification, expert endorsement or independent proof. The published content must remain consistent with the product, the source and the stated boundaries. No review by an external specialist is implied unless the reviewer and scope are named.
To raise a correction, contact Journey with the page, the statement and the supporting source. If you are choosing a platform, bring your own workflow to the demonstration and ask to inspect the evidence. If you need learner support, use the learner guidance pages and your provider’s named contacts.
One product, one accountable record
Most providers have a learner in several systems and a monthly reconciliation job to make those records agree. Journey replaces that fragmentation with tenant-scoped workflows and a history attributed to the real person who acted.
- Audience
- UK apprenticeship training providers
- Scope
- Enrolment through achievement and destination
- Access
- Reviewed Core applications; role and tenant controlled
- Built in
- Around UK apprenticeship delivery
How we work
Product truth before product theatre
Journey is developed against the workflows, evidence and controls apprenticeship providers actually need. We publish what is live, qualify what is limited and leave unsupported claims out.
Built around the whole provider
Journey connects leaders, delivery teams, quality, funding, employers and apprentices on one governed record instead of asking each team to reconcile a different system.
Evidence before claims
Product claims are tied to documented implementation, release scope and the evidence available for the proposed workflow. Regulated guidance is dated and linked to primary sources, and comparisons say when a competitor capability is not publicly stated.
Safe boundaries are part of the product
Tenant-scoped access, role permissions, attributable audit history and governed AI are architectural controls. Journey is independent software and does not guarantee funding or inspection outcomes.
Evidence-led product delivery
The people and principles behind Journey
Journey documents its product controls and makes current, scope-specific assurance evidence available during procurement where applicable. It is independent software and does not guarantee funding or inspection outcomes.
Access and audit controls
- Provider-scoped accessTenant-scoped access checks apply within the authorised workspace
- Attributable historySignificant actions are recorded against the person
Review the current control evidence for your proposed Journey scope during procurement.
Documents for your review
- Security informationCurrent controls and operating boundaries
- Data processingSubprocessors, privacy and agreed terms
We share scope-specific assurance evidence so your team can complete its own checks.
See whether Journey fits your provision
We will show the real workflows, answer due-diligence questions and be clear about what is ready now and what would need configuring for your organisation.
Content reviewed 9 September 2026.
Related pages.
See what changes
when it all connects.
Bring your learners’ journey, your team’s questions and your next ambition.