One approval. The journey continues.
The learner’s story should stay connected when responsibility moves from provider to assessment organisation. Journey prepares the assessment readiness pack. Your authorised person approves it. The native Meritura connection carries the approved handover forward and brings the released result back.
A complete handover.
Prepare the pack
Readiness, evidence and named approval.
Approve & send
Pack received by the assessment organisation.
Receive the released result
The released outcome joins the learner record.
The Journey–Meritura integration exchanges an approved readiness pack and assessment lifecycle information between connected providers and assessment organisations. It is available where the recipient uses Meritura and the relationship is configured. Journey remains the provider record; Meritura supports the assessment organisation’s operations and independent decisions.
MerituraReady at gateway.
Connected through assessment.
From the provider’s learning record to the assessment organisation’s workspace. One approved handover, with progress and released results coming back.
Training provider
Readiness and evidenceMerituraAssessment organisation
Awaiting the approved packPrepare the evidence
Bring together the learner’s readiness, selected evidence and assessment-plan requirements in Journey.
Approve and send
An authorised person approves the versioned pack. The connected Meritura organisation validates it and acknowledges receipt.
Coordinate assessment
The assessment team accepts or queries readiness, links the case, schedules activity and checks assessor competence and conflicts.
Assure and release
Assessment recommendations pass through quality assurance. An authorised person releases the result.
Bring the result home
Assessment updates and the released result return to the linked Journey record, with receipt confirmation and an audit trail.
Native exchange for organisations using Meritura.
The exchange is implemented. Live use requires an approved connection between your organisations and verified delivery.
How the platforms exchange information
Versioned HTTPS APIs carry the approved pack and ordered assessment updates. Scoped access protects evidence retrieval. Receipt confirmations keep both systems aligned; an event is marked delivered only after acknowledgement. MCP tools are planned separately.
A connected handover needs more than a send button
The first useful outcome is knowing that the correct organisation has received the correct approved pack. After that, both teams need a way to handle questions, track the assessment process and identify the same learner case without repeatedly reconstructing the context.
The native exchange uses a shared reference to connect that sequence. A receipt, a correction request and a released result describe different events. Keeping those distinctions visible helps the provider know whether the next action belongs to its own team or to the receiving assessment organisation.
Three handover situations worth seeing in a demo
The animation on this website illustrates the sequence with sample information. It does not submit a live learner pack or demonstrate that a particular provider-to-assessment-organisation relationship is already active.
| Situation | What the connected process should make clear |
|---|---|
| The pack is accepted | The approved pack reaches the connected recipient, the receipt is recorded and the assessment case is linked. |
| The pack needs correction | The receiving team records a reason. The provider corrects the source record and re-sends with a traceable history. |
| Assessment is complete, but the result is not released | Progress and a formally released result remain distinct. The assessment organisation retains its quality assurance and release authority. |
Share the assessment context, with a clear boundary
The pack should carry what the assessment process needs. That can include the relevant learner and apprenticeship references, the standard and assessment plan, gateway confirmations, required evidence and assessment-related adjustment requests. It should not become an unrestricted copy of the provider’s entire learner record.
This separation matters operationally as well as for information handling. The provider needs its delivery, funding and support history. The assessment organisation needs an appropriate assessment case. Connecting the two does not merge their responsibilities or transfer judgement to the platform.
Check the receiving relationship before planning the rollout
Confirm which assessment organisation receives the pack, whether it uses Meritura, who can approve the provider handover and how the connected relationship will be validated. Include a controlled acceptance and correction scenario in that validation.
Journey can still support gateway readiness, EPA bookings and outcomes where an EPAO uses a different system. The native pack exchange and released-result return are the additional capability for connected Meritura relationships. Meritura itself is an assessment operations platform, not a regulator or awarding body.
When a learner is ready, Journey builds the assessment readiness pack from the record, a named person approves it, and it is sent to Meritura by Journey from the learner record. Meritura runs scheduling, assessor allocation, marking, IQA and result release. The released result comes back to the learner record.
A pack, an approval and a click.
What used to be a zip file and an email is a correlated exchange between two systems of record, with a person at each end.
Illustrative learner and assessment records. The named people, references and timings shown are sample data.
- Readiness checklist cleared
9 of 9 items read from the record - Assessment readiness pack built
Minimised: what assessment needs, nothing more - Approved by a named person
Head of Delivery - Sent to Meritura
Sent from the learner record. Receipt recorded.
- Pack accepted, case created
Tenant-scoped, audit event appended - Scheduled and assessor allocated
Competence and conflict checks before allocation - Assessed, marked, IQA approved
Intelligence assists. People decide. - Result released and synced to Journey
Distinction, back on the learner's record
Nothing re-keyed on either side
The pack is built from the learner record. The result is written back to it. Both sides keep a correlated audit trail.
Minimised by design
Meritura receives what assessment needs and nothing more. Provider data stays in Journey.
Same family, separate boundary
Meritura is by Journey, endorsed not merged. Providers and assessment organisations each keep their own system of record.
Controlled demonstration data. Meritura and Journey are independent software and are not regulators, awarding bodies or certification services.
What is in the readiness pack, and what is not.
The pack is minimised by design: the assessment organisation receives what assessment needs and nothing more.
| In the pack | Why | Stays in Journey |
|---|---|---|
| Learner identity and apprenticeship reference | To create the case and match the result on return | Contact details beyond what the EPAO needs to schedule |
| Standard, level, assessment plan version and planned gateway date | Meritura derives the assessment regime from the plan type and the date | Programme plan history and tutor notes |
| Gateway confirmation: employer sign-off, English and maths status, portfolio complete where required | The evidence gateway was met | Progress reviews, off-the-job logs, quality samples |
| Portfolio or project evidence the assessment plan requires | Assessment methods that assess submitted work | Everything else in the e-portfolio |
| Reasonable adjustment requests | To schedule fairly | The underlying support records |
| Correlation reference and approver name | Both audit trails point at the same hand-over | Funding records and price |
The correction loop
If a coordinator at the assessment organisation returns the pack, it comes back to the same learner record in Journey with the reason and the correlation reference. The provider fixes the record, not a copy, and re-sends. Both sides keep the returned and re-sent events in their audit trails.
What the assessment organisation does with it
Meritura creates the case, schedules the assessment with replay and collision checks, allocates an assessor with competence and conflict checks, records delivery, takes marks, runs internal quality assurance, and releases the result through a human decision. Intelligence assists; people decide. The released result is the only thing that flows back.
Timeline, in practice
- Readiness cleared on the record and the pack built: minutes, because the checklist reads from the record.
- Approval by a named person at the provider: when they are ready, not when a form is finished.
- Receipt from Meritura: typically within a minute of sending.
- Scheduling and allocation: at the assessment organisation's pace, visible in Journey as case events.
- Result released and written to the record: the same day as release.
Any end-point assessment organisation is supported for bookings and outcomes. The hand-over from the learner record and result sync apply where the assessment organisation runs Meritura by Journey. Neither product is a regulator, awarding body or certification service.
About the Meritura hand-over.
What is Meritura?
Meritura by Journey is the assessment operations system for awarding organisations and end-point assessment organisations. It runs readiness-pack intake, assessment cases, scheduling, assessor allocation, marking, internal quality assurance, result release and result sync back to Journey. It is a separate product with its own system of record at meritura.co.uk.
What does Journey send to Meritura?
A minimised assessment readiness pack built from the learner record: the standard and assessment plan, gateway confirmation, the evidence assessment needs and nothing more. A named person at the provider approves the pack before it leaves Journey.
What comes back?
Receipt of the pack, any return for correction with the reason, and the released result once a person at the assessment organisation has released it after independent quality assurance. The result is written to the learner record with the released decision and time.
Does my EPAO have to use Meritura?
No. Journey's gateway readiness, EPA booking and outcome tracking work with any end-point assessment organisation. The hand-over from the learner record and result sync are available where the assessment organisation runs Meritura.
Is the hand-over automatic?
No. Readiness reads automatically from the record, but a named person approves the pack, and a person at the assessment organisation accepts it or returns it for correction. Intelligence assists; people decide.
Related pages.
See the hand-over end to end.
A walkthrough follows one learner from readiness to a released result, on controlled data.
See what changes
when it all connects.
Bring your learners’ journey, your team’s questions and your next ambition.