EPA gateway software: arrive at gateway with the whole story ready.
Gateway should be the point where connected delivery becomes a clear, approved handover. Journey brings the readiness position, required evidence, employer confirmation and named approval together before the learner moves into assessment.
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.
EPA gateway software helps providers organise and review the evidence and confirmations needed before end-point assessment. Journey connects readiness to the learner record, supports EPA bookings and outcomes with any EPAO, and provides a native approved-pack handover where the receiving assessment organisation uses Meritura and the relationship is connected.
Start with the requirement, then follow the evidence
The gateway position depends on the applicable standard, assessment plan and learner circumstances. A generic percentage cannot explain whether the necessary conditions are satisfied. Your team needs to see the specific item being checked, the evidence used and the person responsible for reviewing it.
Bring delivery progress, portfolio requirements, employer confirmation and relevant English and maths information into that review. Where an item is missing or needs clarification, give the follow-up a named owner. The readiness view should help your team find the work, not conceal it behind a green status.
A practical pre-handover review
Use these questions to structure the operational review alongside the exact requirements for the apprenticeship. They are intended to help a provider organise its process, not to provide a universal gateway checklist.
- Are the standard and relevant assessment plan identified correctly?
- Can the reviewer open the evidence behind each required readiness item?
- Is the required employer confirmation recorded and attributable?
- Have assessment-related support or adjustment requests been considered through the appropriate process?
- Does the pack include the evidence the assessment organisation needs, with unrelated provider information kept out?
- Has an authorised, named person reviewed the pack and approved the handover?
The handover needs a return path
Sending a pack is one event in a longer process. Your coordinator also needs to know whether it was received, whether a correction is needed and when the assessment organisation releases an outcome. With a configured Journey–Meritura relationship, these exchanges remain linked to the learner through a shared reference.
If a pack is returned for correction, review the reason, correct the underlying learner record and re-send through the agreed process. Retaining the history of the return and correction gives both teams a clearer account than replacing an attachment without explanation.
Meritura is assessment operations software, not an awarding body. The responsible assessment organisation retains its assessment, quality assurance and result-release decisions.
Track gateway readiness, EPA bookings and outcomes across every learner, with the audit trail attached at each step.
Approaching
Priya Shah
Business Admin L3
Marcus Reed
Team Leader L3
In Gateway
Sarah Jenkins
Software Dev L4
EPA Booked
Liam O'Connor
Data Analyst L4
12 Dec 2025
Achieved
Emma Watson
HR Support L3
Illustrative gateway and EPA pipeline with sample data.
Definition
What is EPA gateway readiness?
Traditional EPA takes place after training and gateway. The employer confirms readiness with the provider and the apprentice’s involvement against the applicable plan. Revised plans may include assessment during the programme and use gateway to completion. Journey’s workflow must be evaluated against the actual plan your provision uses.
Does Journey track EPA and gateway readiness?
Yes. Journey tracks gateway readiness, sign-off, EPA bookings and outcomes through to achievement and destinations, with concurrency-safe transitions so each state change has a single, audited owner. Journey is independent software and is not DfE or Ofsted approved. It does not guarantee funding or inspection outcomes.
Brings together what used to be separate tools
Gateway readiness
Readiness criteria and sign-off are tracked per learner before they enter gateway.
EPA bookings & outcomes
Bookings and outcomes are recorded against the standard, with the evidence behind each step.
Achievement & destinations
Outcomes flow through to achievement and destination data for reporting.
Lifecycle & breaks in learning
Breaks in learning, withdrawals and reinstatements are handled as first-class lifecycle events.
Meritura handover contract—activation required
Journey has an implemented, approval-gated handover contract, but it remains locked until an authorised provider–AO tenant binding is active. Only then, after formal gateway submission, readiness checks, approved evidence and provider approval, may Journey queue a versioned handover; completion requires Meritura acknowledgement.
Gateway as a controlled state, not a checklist
Gateway is the point where funding, evidence and quality all have to line up at once, and it is easy for a learner to be pushed through before they are genuinely ready. Journey treats readiness as a tracked state per learner: the criteria and sign-off are recorded before the apprentice enters gateway, so the decision is evidenced rather than assumed.
Gateway submit, EPA outcome and lifecycle changes use transactions and row locks to manage concurrent actions. Attributable audit events record the person associated with each completed state change.
From booking to achievement and destinations
EPA bookings and outcomes are recorded against the standard, with the evidence behind each step, and outcomes flow through to achievement and destination data. That destination information matters for both your own reporting and the wider picture inspectors and funders expect providers to be able to show after completion.
A controlled handover path for Meritura
Journey's implemented Meritura handover contract is designed to reduce manual repacking after gateway without bypassing provider or AO control. The route remains unavailable until an authorised provider–AO tenant binding is active. Only then must formal gateway submission, readiness checks, approved portfolio evidence and authorised provider approval all be present before Journey may queue a versioned handover.
A queued handover is not a completed transfer. The handover completes only after Meritura acknowledges it. No provider should assume this route is active: the exact provider and AO binding must be confirmed during evaluation and activated before use.
Breaks in learning and withdrawals handled properly
Breaks in learning, withdrawals and reinstatements are first-class lifecycle events rather than ad-hoc edits. Because they are modelled explicitly, they feed correctly into funding and the ILR, and the audit log records who made each change and when — so the learner's journey through gateway and EPA stays defensible end to end.
Built so your team can trace evidence, decisions and actions
Tenant-scoped access controls
Tenant-scoped access controls are designed to keep each provider's records separate on reads and writes.
Controlled audit history
Significant application state changes are recorded against the person who made them, supporting a traceable history.
Published funding-rule packs
Journey applies supported, versioned DfE funding-rule packs selected from the apprentice's start date, including 2026/27 version 3, to support provider review.
Bounded AI assistance
Journey AI can help identify recorded readiness gaps. A named person reviews the learner evidence and approves the pack; the receiving assessment organisation retains its assessment and release authority.
Evidence-led security controls
Tenant isolation, access controls, audit records and governed operations are designed into the platform.
Your data and employers stay yours
Export options are available under the applicable terms, and employer relationships remain with the provider.
Journey is independent software and is not DfE or Ofsted approved. It does not guarantee funding or inspection outcomes.
Questions providers ask
Is the gateway sign-off safe under concurrent edits?
Yes. Gateway submit, EPA outcome and lifecycle transitions run in a single transaction with row locks, so concurrent writers collapse to one winner and a clean conflict for the rest.
Does it capture destinations?
Yes. Achievement and destination data are recorded so providers can report on outcomes after completion.
Is the Meritura handover live automatically?
No. Journey has an implemented, approval-gated handover contract, but it is unavailable until the provider and AO authorise and activate the exact tenant binding. Only a bound route may queue a handover, and completion still requires Meritura acknowledgement. Confirm activation during evaluation.
Related pages.
See Journey on your own questions.
A guided walkthrough of the connected record and the questions your leadership team actually asks.
See what changes
when it all connects.
Bring your learners’ journey, your team’s questions and your next ambition.