University, degree apprenticeship, apprenticeship, employment with training. Today every student carries a pathway and shares one evidence base; the application workbench for non-UCAS routes is in development.
Working in my school’s peer-mentoring scheme showed me how much I enjoy breaking a hard problem down for someone else — the same instinct that draws me to a technology consulting role…
…
Name one concrete example of working with a team under a deadline — your Duke of Edinburgh expedition is in your evidence bank.
The UCAS applicant gets a workspace, feedback rounds and a deadline. The apprenticeship applicant gets a folder and goodwill. Same student, same school, two different standards of support.
The route-parity gap is not a UCAS problem; it is a visibility and support gap for everyone who is not applying to university. Outleap starts from a principle that already holds today: every student records an intended pathway, and the evidence they gather belongs to them, not to a single application form.
University, degree apprenticeship, apprenticeship, employment with training, or still deciding. Each student carries a pathway field today, and each one appears in the cohort view rather than only the UCAS applicants.
The evidence bank holds what a student has actually done. Today it supports the personal statement and reference preparation; the same entries are built to feed the wider application workbench as it ships.
Staff see who has chosen a route, who is still undecided, and what support has been given, across the whole cohort, not just the students with a UCAS deadline.
An apprenticeship application is real work: a CV, a cover letter, employer questions answered against competencies. We are building a workbench that gives that work the same structure UCAS applicants already have, with staff sign-off before anything is sent. This is in development and is not a live feature.
Planned: a CV workspace that draws on the evidence a student has already banked, with staff sign-off. CV drafting is on the roadmap, not yet built.
Planned: structured guidance for role-specific cover letters that helps a student express their own evidence. Role-specific cover-letter feedback is in development, not live today.
Planned: scaffolding for employer competency questions so students can structure a clear, evidenced answer. STAR-style competency tooling is on the roadmap, not a current capability.
The longer aim is one connected flow for non-UCAS routes, and route-parity reporting so a Careers Lead can answer who is progressing on every pathway. Every step here is on the roadmap, built on the pathway field and evidence base that exist today.
Planned: a supervised radar that surfaces apprenticeships and employment routes a student might not search for, each with a source, a reason it is shown, and a verified date. In development.
Planned: the application workbench above, so the student moves from a saved opportunity to a structured application with staff sign-off. In development.
Planned: route-parity reporting that shows progress across every pathway, so support no longer depends on which route a student chose. On the roadmap, built on today's cohort view.
Draft your “why healthcare?” answer using your hospital-volunteering evidence.
The shared evidence base and the pathway field are live now: each student records an intended route and appears in the staff cohort view, not only the UCAS applicants. The application workbench shown here is captioned as a vision preview and is in development, not a current feature.
See the pathway field and evidence base that work today, and where the application workbench and route-parity reporting are heading. A consultative walkthrough of your process, not a generic feature tour.
Book a walkthrough