Ask naturally.
Type a question or speak it. Journey turns everyday language into a request for the information you need.
Journey AI, also known as Talk to Journey, answers from the records you’re allowed to see. Speak or type a question and get an answer with evidence to check and a clear place to act.
Explore Journey AdvancedYour questions. Your connected Journey.
Choose a sample question and explore the answer. Open its sources to see the records behind it.
Ask naturally. Journey brings the context.
Built on a proven AI SDK. Connected to your platform, your records and your team’s real questions.
Type a question or speak it. Journey turns everyday language into a request for the information you need.
The AI SDK connects the conversation to Journey’s record tools: learners, delivery, funding and quality.
Journey checks your organisation and permissions before its tools read records. The conversation follows those boundaries.
Open the evidence behind an answer, then follow its link to the relevant learner, queue or workspace. You decide what happens next.
For everyone moving learning forward. Ask about the work you own, with answers shaped by the records you can access.
“Which learners need our attention this week?”
Start with the learners whose reviews or off-the-job hours are behind plan. Open the linked records to see the gap and who can help.
“Which of my learners has a review overdue?”
Check the overdue reviews in your caseload, with their due dates and the relevant learner records. Open a review to plan your follow-up.
“Which quality actions are overdue?”
Bring overdue actions, owners and due dates into one view. Follow the linked quality records to check what has happened and agree the next action.
“Which of my apprentices need attention?”
See your apprentices’ recorded progress, off-the-job learning and reviews awaiting your signature. Open the employer workspace to follow up on the people who need you.
Ask about learners, delivery, funding, quality or gateway. Journey retrieves the permitted facts, explains what they show and includes the relevant evidence references. A tutor’s caseload, an employer’s apprentices and a learner’s own record each have their own access boundary.
Journey AI reads and explains. Follow a link into the right workspace to review the detail and take action. It does not sign reviews, approve a gateway pack or release an assessment result on your behalf.
An answer can only use the facts available to it. Evidence references show the source and when it was read. If model narration is unavailable, Journey can present the retrieved facts directly.
Journey AI is part of Advanced, with the provider’s capacity, AI allowance, onboarding and support agreed in writing. Your learner records remain in the same platform as your provision grows.
Most apprenticeship software gives you screens. Journey AI gives you answers with evidence, inside the signed-in app, scoped to your provider.
Journey AI is built so a leadership team can trust what it reads without trusting the AI blindly.
“What needs my attention today?” Start with a supported operational question, then inspect the available facts and next-step links.
Journey retrieves the supported records your role can access and shows the available source references and as-of context alongside the answer.
The answer links to available supporting records. Check the sources and the recorded context before acting; an AI response can still make mistakes.
Inspect the available sources and recorded context before acting.
Supported answers show source references and an as-of timestamp, with links to the relevant work. Open the source and check the recorded facts before making a decision. Journey records AI usage and audit metadata; an answer is not an immutable snapshot of every source record.
Journey AI is available with Journey Advanced. AI included. Answers cite records; consequential actions stay with a named person. Journey is independent software and does not make funding, gateway, EPA or learner-status decisions.
The same record answers different questions for different people. Illustrative questions shaped around common provider tasks, with synthetic answers.
| Role | A question they ask | What Journey reads | What comes back |
|---|---|---|---|
| Managing director | Show my caseload and their OTJ progress. | Off-the-job log, programme plans, employer records | A supported caseload summary with available OTJ context and source links |
| Head of delivery | Which reviews are overdue this month and who owns them? | Progress reviews, tutor caseloads | Learners, due dates, tutor, employer sign-off status |
| Finance and MIS lead | What is outstanding for the ILR return? | Funding records, ILR draft, funding rules pack for each start date | A supported preparation summary and the available source references |
| Quality lead | Which tutors have not been sampled this term? | Sampling plan, observations, actions | Tutors, last sample date, open actions |
| Gateway coordinator | Who is approaching gateway with an item outstanding? | Gateway readiness, portfolio coverage, English and maths, employer confirmation | Learners, planned gateway date, the item outstanding and who owns it |
| Safeguarding lead | Which learners have an open welfare action older than 14 days? | Safeguarding and wellbeing records (restricted role) | Only what the role is permitted to see, with the owner and age of each action |
Application access controls restrict the tools and records available to the assistant. Human review remains essential.
Answers are read-only. Changing a learner status, a funding record or a gateway decision is a named person's action, recorded in the audit trail.
Answers come from your provider's own records, scoped to your tenant. It does not read other providers' data or the internet.
Journey retrieves the supported records your role can access and shows the available source references and as-of context alongside the answer.
Journey AI inherits the role and site scope of the person asking. A tutor cannot ask it about another tutor's caseload.
AI is included within the agreed fair-use allowance. Usage is metered per provider; confirm the allowance, notifications and behaviour at a limit in your written proposal.
The website offers a guided conversation using illustrative records. Live Journey AI belongs to your signed-in Advanced workspace.
How a director prepares with Journey AI rather than with a pack of exports.
Supported answers show source references and an as-of timestamp, with links to the relevant work. Open the source and check the recorded facts before making a decision. Journey records AI usage and audit metadata; an answer is not an immutable snapshot of every source record.
Ask supported questions about your permitted records. Journey explains the recorded facts and provides the available evidence and next-step links. If the information or capability is unavailable, the response should say so. Check the sources before acting.
Supported answers show source references and an as-of timestamp, with links to the relevant work. Open the source and check the recorded facts before making a decision. Journey records AI usage and audit metadata; an answer is not an immutable snapshot of every source record.
No. It answers and shows its sources. Consequential actions such as changing a learner status, a funding record or a gateway decision stay with a named person in the app, with the audit trail recording who did it and when.
Yes. The website has a guided, scripted demonstration using illustrative learner records. Try the five questions and inspect the sample sources. Questions about your provider’s live records belong in the signed-in Journey platform, subject to the enabled scope and your permissions.
Journey Advanced, with AI included. Journey Core is the connected record without AI features and is free for verified UK training providers with up to 50 counted apprentices, subject to application review.
A walkthrough runs Journey AI on the questions your leadership team actually asks, with controlled data.
“Which learners need attention?” is a useful starting point. A more precise follow-up gives the answer an operational purpose: “Which learners at my site are due for gateway in the next 60 days and still need an employer review?” That question identifies a group, a time window and a missing item.
Use the answer to check the underlying records, understand the context and agree the next action with the responsible team. A count without the relevant learners, dates and evidence is rarely enough to decide what should happen.
A useful answer should make its boundaries visible. Check which learners it covers, the time period it uses, when the information was read and which records support it. If something is absent or ambiguous, clarify the question or review the source. An incomplete record cannot become complete simply because the answer reads well.
Journey AI follows the access of the person asking. A conversational interface does not create a new entitlement to see restricted learner or safeguarding information. The same principle applies when someone changes role or moves between sites.
Journey AI connects the conversation to tools inside Journey. The tools retrieve permitted facts; the AI explains them. This keeps the operational context central to the experience instead of asking your team to paste learner information into a separate general-purpose chat.
The public website uses guided questions and sample records. Your organisation’s live questions belong in the signed-in Journey workspace, subject to your enabled capabilities, required approvals and permissions. Advanced includes AI within fair use, with usage reporting; confirm allowances, notifications and limit behaviour in writing.
For teams who want to understand the technology: Journey AI uses Vercel AI SDK to connect model responses with application-controlled tools. Journey applies provider, role and learner permissions before those tools retrieve record facts. The conversation can then explain the recorded position and return evidence references, so a question has a route back to the underlying work.
The SDK provides the building blocks for the conversation; Journey defines the access boundaries and available tools. It does not give the model unrestricted database access or authority to make funding, safeguarding or assessment decisions. Confirm the workflows enabled for your organisation, including their processing and retention arrangements, during onboarding.