Journey workflow
One learner record. A clearer next step.
A connected record is useful when it helps the next person act. Follow the relationship between the plan, the activity, the evidence and the review, then use the scenario to evaluate Journey against your provider’s needs.
Published product · edition and implementation scope confirmed during evaluation
The product website describes Journey today. Website demonstrations use illustrative records; confirm the required edition, configuration and supported workflow in a current walkthrough.
UK-hosted, GDPR-compliant
Illustrative workflow
Follow the work through Journey.
Prepare the context
Open the learner record, planned activity, recent evidence and outstanding review actions.
What belongs together
Keep the plan and what happened distinguishable.
The learning plan describes intended activity. Attendance and learning records describe activity that took place. Evidence and feedback help the team judge progress. An agreed review records the decision and the action to follow. Connecting them should make those differences clearer, rather than blur them into a single completion percentage.
Journey’s published delivery workflow places the selected programme, delivery dates, resources, evidence and reviews around the same learner context. In a walkthrough, open the underlying items and inspect their status, date, owner and relationship to the learner.
| Working question | Context to inspect |
|---|---|
| What is meant to happen next? | Approved plan, scheduled activity and relevant resources. |
| What actually happened? | Attendance, learning activity and submitted evidence. |
| What needs a judgement? | Feedback, quality questions and review context. |
| Who acts now? | Agreed action, accountable person and next review point. |
A practical walkthrough
Follow the case through a change.
Use a fictional apprentice whose workplace availability changes before a planned review. The provider needs to keep the delivery plan usable, retain the reason for the change and give the learner and employer a clear next step. This tests continuity more effectively than opening unrelated dashboards.
The steps below are an evaluation scenario. They do not claim that an automated change is appropriate for every provider or that the product decides the funding consequences.
Prepare the context
Open the learner record, planned activity, recent evidence and outstanding review actions.
Review the change
Identify which session or action needs changing and who must agree the revised arrangement.
Keep the evidence visible
Check that recent work, feedback and any gap remain understandable after the plan changes.
Record the next action
Confirm who will act, what the learner and employer need to know and when progress will be reviewed.
Check downstream work
Ask the responsible team to review any funding, quality or readiness implications through the supported route.
Different views, shared context
Test with the roles that will use it.
A useful provider evaluation needs more than an administrator’s account. The learner needs to find their own work, the tutor needs the right caseload context and the employer needs the information relevant to their apprentice. Quality and funding colleagues need the records appropriate to their responsibilities.
Ask what each role can read, change, sign or export. Include a person who should not have access to the example learner. Request a demonstration of the boundary rather than treating a role name as proof that permissions match your organisation.
- Learner: find the next activity and the feedback that explains it.
- Tutor: prepare the review using relevant delivery and evidence.
- Employer: contribute to the progress conversation and agreed actions.
- Quality or funding owner: trace the source behind a finding without relying on a summary alone.
At the assessment boundary
A readiness decision needs more than a full folder.
The purpose of an assessment handoff is to send appropriate, reviewed information to the right organisation. The provider should establish what is needed for the learner’s applicable route and which person can authorise the handoff.
Where the Meritura connection is configured, test a complete readiness case and a case with a missing item. Confirm the acknowledgement, query route and ownership of any correction. The assessment organisation’s decision remains separate from the provider’s preparation.
What a useful evaluation leaves behind
Write down what was shown.
Keep a small evaluation record: scenario, roles, records inspected, decisions demonstrated, gaps and next actions. Separate what is visible in a website demonstration from what was shown in the configured application.
Use anonymised or synthetic data until the intended processing arrangements and access are agreed. A product evaluation can begin with a clearly described task; it does not require personal learner information in a public enquiry.
Questions before the next step
A clearer view of Journey.
Does a connected record mean every user sees everything?
No. The shared record and a person’s permitted view are different things. Ask Journey to demonstrate the permissions needed for your learner, tutor, employer and administrative roles.
Can a planned session prove that learning happened?
No. Plans, attendance, learning activity, evidence and review judgements describe different parts of the process. Use each for the question it can actually answer.
Can we use this scenario before moving systems?
Yes. It is a practical evaluation scenario using fictional data. Keep a record of what was demonstrated, what needs configuration and what still requires confirmation.
Make the next conversation useful
Start with the work.
Explore the fit.
Bring your workflow, the people involved and the decisions you need to make.