Gateway evidence: a clear route from ready to accepted

Start with the apprentice’s actual assessment route

Record the standard reference, version, option, assessment-plan version and the assessment organisation’s current instructions before assembling documents. Two apprentices with similar job titles can have different requirements. Skills England’s revised approach includes gateway to completion; older end-point assessment routes retain their applicable gateway arrangements. Do not move an apprentice between versions merely because a newer webpage exists. Confirm the route with the provider’s compliance lead and the assessment organisation, then retain the confirmation alongside the pack.

Build one index with a named owner

Give each required item a row: requirement, evidence reference, location, owner, reviewer, due date and current status. Use precise links rather than instructions such as “in the portfolio”. Separate an uploaded document from an accepted document; a file can be present but illegible, unsigned, out of scope or inaccessible. One coordinator should maintain the index while tutors, employers and apprentices own their actions. This makes the pack easier to review without replacing the employer’s judgement about occupational competence.

Check evidence quality, not just document count

Open the files as the reviewer will see them. Check that the evidence belongs to the correct apprentice, covers the correct period and is readable without specialist access that has not been arranged. Where an evidence item refers to a workplace activity, identify the apprentice’s personal contribution and the relevant assessment requirement. Use a focused selection that meets the actual instructions; more pages can make a weak pack harder to navigate. Redact unnecessary personal and client information while preserving enough context to understand the work.

Make the readiness conversation meaningful

Before a sign-off meeting, give the apprentice and employer the current checklist and any unresolved issues. Ask what work the apprentice can now complete independently, which areas still require support and whether the planned assessment conditions create any access barriers. Capture disagreement rather than forcing a green status. If someone is not ready, record the specific gap, the learning or evidence action, the responsible person and the next review date. A delayed submission with a clear recovery plan is more useful than an unsupported readiness declaration.

Run a practical submission check

Test the actual submission route with a permitted sample or an approved test process. Confirm file size limits, accepted formats, naming conventions and who receives acknowledgements. Keep version numbers consistent across the index and the documents. An email saying a pack was sent is not the same as confirmation that the recipient can open it. For documents requiring signatures, check the organisation’s accepted signature process. Arrange access support early and use the assessment organisation’s secure route for sensitive information.

• Confirm applicable English, maths and mandatory qualification requirements individually.
• Check declarations and employer decisions are complete, dated and attributable.
• Record adjustment approval separately from an adjustment request.
• Use restricted access for health information and identity documents.

Close the loop on queries

When a reviewer raises a query, copy it into the action log using its original reference. Assign an owner and a realistic response date. Answer the point directly, identify the amended evidence and state which previous version it replaces. Avoid quietly changing several files without explaining the change. Once resolved, retain the acceptance or decision reference. At weekly cohort meetings, look for repeat causes such as missing permissions, unclear employer declarations or inconsistent file formats; improve the process at source rather than repeatedly chasing individual apprentices.

Use the template as a working control

The downloadable checklist is editable in a browser and printable. Replace its example requirement rows with the exact requirements for the apprentice’s route. Keep the working copy in your organisation’s authorised record system and apply your retention rules. The checklist supports preparation; it does not make a gateway decision or confirm an assessment booking. Review its owner, version and open actions whenever dates change, and give the apprentice a clear explanation of what happens next and who to contact.

Worked example: resolve a pack before it becomes a booking delay

A provider expects an apprentice to be ready on 14 January. The programme coordinator opens the route-specific checklist six weeks earlier and finds that the employer declaration is unsigned, an English requirement is still recorded as “to check”, and the adjustment request has no decision reference. The coordinator assigns the employer declaration to the workplace manager, asks the compliance lead to confirm the individual English position, and routes the adjustment through the assessment organisation’s published process. The forecast date remains a forecast until each item has an evidenced decision; nobody marks the pack complete merely because files exist.

The common errors are ownership and status errors: using “uploaded” to mean “accepted”, copying a generic requirement list across versions, storing identity or health evidence in the open tracker, and silently replacing a queried file. The provider’s programme owner controls the version; the employer signatory owns the accuracy of workplace declarations; the learner-support owner coordinates access information; the coordinator maintains the action log. The apprentice receives one plain-language update rather than several conflicting chasers.

Use the checklist at three decision points: first to identify missing requirements, then to decide whether the pack is ready for formal submission, and finally to close any query with a reference to the accepted replacement. If an item cannot be confirmed, record the blocker, owner and next review date and revise the forecast. A checklist is useful when it exposes an uncertain decision early; it becomes unsafe when green ticks are used to imply approval or a confirmed assessment date.