Stage 1
Map one operational workflow, its roles, evidence and current system boundaries.
Apprenticeship management software
Journey
Journey is apprenticeship management software for UK training providers. Journey Core is free forever for verified UK providers with up to 50 counted apprentices, subject to application review. Journey Advanced adds Journey AI, also known as Talk to Journey.
Journey is published at journeyapp.co.uk. Journey Core and Journey Advanced are the two published editions, and Journey Core eligibility is established through an application review.
Discuss Journey
An operational workspace, shown through the actual interface.
01
Audience and operating context
A product direction for a specific kind of work.
Journey is for UK training providers delivering apprenticeships: the delivery, quality, review and management roles that coordinate apprentices, evidence and decisions across a programme.
A service can be busy without being controllable. People may know that a case, learner, customer request or operational commitment exists, yet struggle to see the current owner, the evidence behind a decision, the next action or the exceptions that need review. In that setting, more reporting can add noise rather than accountability. Journey explores a clearer operating view: work arranged around roles, visible ownership and the evidence needed to move a decision forward.
02
Workflow before feature list
Start with one workflow that can be observed and evaluated.
A delivery lead begins with a queue of work that needs attention. A contributor records the relevant action or evidence; a reviewer sees what requires a check and can return an exception for clarification; the accountable owner can see whether the operational state is moving, blocked or awaiting a decision. The point is not to automate every judgement. It is to make the route from work item to review and accountable next step inspectable. The exact workflow must be mapped with the organisation before any configuration or build is proposed.
03
Architecture decisions
Questions about data and integration come before a deployment promise.
- 01
Which system remains the source of record for people, work items, documents and status?
- 02
What evidence may be surfaced, linked, copied or retained, and for how long?
- 03
Which existing systems need a read, write or export relationship, if any?
- 04
What data classification, residency, retention and access constraints apply to the proposed workflow?
04
Control and assurance
Responsibility needs to be designed into the operating route.
- 01
Which roles can create, review, approve, reopen or close work?
- 02
What must be attributable to a person, and what needs an audit trail or evidence reference?
- 03
Which exceptions require human review rather than automatic progression?
- 04
What availability, continuity, support and incident responsibilities are required for the intended use?
05
Evaluation
Evidence that should decide whether the direction moves forward.
- 01
Can each role find its next meaningful action without relying on a parallel spreadsheet or inbox?
- 02
Can a reviewer understand the evidence, decision and owner behind an operational state?
- 03
Are exceptions visible early enough for an accountable person to act?
- 04
Does the proposed product reduce ambiguity without creating a duplicate source of record?
06
Implementation route
Move from a bounded question to an accountable decision.
Stage 2
Agree the smallest useful workspace and the acceptance criteria it must meet.
Stage 3
Confirm data, access, integration and assurance decisions before a pilot or deployment route is selected.
Stage 4
Run a controlled evaluation with a named owner, then decide whether to extend, integrate, redesign or stop.
07
What can be inspected now
Current first-party evidence and its limits.
The public record distinguishes product work that can be inspected from capability, availability or outcome claims that still need project-specific evidence.
Available evidence
Journey is published at journeyapp.co.uk, including an apprenticeship-software overview and a pricing page setting out Journey Core and Journey Advanced.
Available evidence
A TechGeek-controlled Journey operational-workspace image is shown on this site; it is not a generated customer mock-up.
Available evidence
The Journey operational workspace has a public first-party build record describing the build and its evidence limits.
Explicit limitation
The public evidence is first-party product evidence, not a client case study, endorsement or adoption metric.
Explicit limitation
Journey Core eligibility is decided by application review; being a UK provider with up to 50 counted apprentices does not by itself create an account.
Explicit limitation
Edition contents and prices are those published at journeyapp.co.uk/pricing and should be read there before a commercial decision.
Source discipline
Primary guidance and technical references
Direct answers
Questions about Journey
01What is Journey?
Journey is apprenticeship management software for UK training providers.
02What does Journey Core cost?
Journey Core is free forever for verified UK providers with up to 50 counted apprentices, subject to application review.
03What does Journey Advanced add?
Journey Advanced adds Journey AI, also known as Talk to Journey.
04What is Talk to Journey?
Talk to Journey is the other name for Journey AI, the capability included in Journey Advanced.
05Where are the editions and prices published?
Journey's editions and prices are published at journeyapp.co.uk/pricing.
A practical next step
Decide whether Journey belongs in the work.
Bring the workflow, users, source systems, constraints and the evidence a first evaluation must create. We will confirm current capability, availability and the appropriate next step before proposing a delivery route.
Start a product conversation