Skip to main content

POST Atlas Education

Teach technology routes without pretending the route is certain.

A controlled pilot for schools, colleges, training providers and apprenticeship teams. It uses POST Atlas to help learners question route advice, read certification claims and turn interest into evidence.

Discuss a controlled pilot View the public sample excerptOpen for controlled pilots. Not generally proven or self-service.
Four facilitated 45 minute sessions
Technology Route Review inside a controlled pilot
Enquiry only. No public checkout

Controlled pilot, public showcase

The public material here is deliberately limited. Live delivery needs an agreed cohort, staff contact, privacy terms and preparation conversation.

The same programme has different jobs for different people. Each audience gets a named artefact and a realistic session outcome, rather than a vague promise of better career confidence.

Subject teachers

Session plans and slide notes
A 45 minute lesson where learners compare a preferred route with the work it actually asks for.

Careers leaders

Pilot evaluation pack
A before-and-after confidence measure and aggregate themes that can be read without ranking learners.

Learners

Technology Route Review
One route, one alternative and one next action they can challenge with a tutor or adviser.

Careers advisers

Adviser handbook
A 1:1 or small-group conversation that tests route claims, estimates and missing evidence.

Apprenticeship teams

Employer activity and handoff
A learner route checked against entry evidence, with exposure separated from competence.
  1. 1

    IT Support

    Tickets, password resets, the first year where you learn how an organisation actually breaks.

    IT Supporton the Atlas, core domain

  2. 2

    Junior SOC Analyst

    Tier-one alert triage on a rota. The realistic way into security work, and it is shift-based.

    Junior SOC Analyston the Atlas, security domain

  3. 3

    SOC Analyst

    Owning investigations rather than passing them on, usually twelve to twenty-four months in.

    SOC Analyston the Atlas, security domain

  4. 4

    Detection Engineer

    Writing and tuning the rules other analysts work from. Fewer seats, and they go to people who can code.

    Detection Engineeron the Atlas, security domain

See this route on the Atlas

Learners see route steps, role evidence and certification status from the same sources as the public Atlas. That matters because a route is not just a title sequence; it is a set of assumptions to test.

Certainty and estimates

Salary and time ranges are labelled as POST estimates. Some route links are authored from specific role evidence; others are marked as inferred until they have a written rationale.

Session 1

Technology is not one career

Technology roles divide by what the work does to a system, not by the job title. Building, operating, analysing and protecting are four different jobs with four different working days.

Learner output: Three role families to investigate, with a reason for each.

Session 2

Preferences, strengths and constraints

Preference, current ability and future potential are three different things. Enjoying something is not evidence you can do it; finding something hard today is not evidence you never will.

Learner output: A personal evidence map, not a personality label.

Session 3

There is no single correct route

Every entry route buys you something and costs you something. Degrees, apprenticeships, certifications and portfolios are not ranked; they trade money, time, supervision and proof against each other.

Learner output: Two entry routes compared, a preferred route and a backup.

Session 4

Challenge the recommendation

An automated recommendation is an argument, not an answer. It can only reason from what it was told, and knowing what it could not know is the skill worth leaving with.

Learner output: A documented 30, 60 and 90 day plan.

  • Explain several genuinely different technology role families and what separates them.
  • Distinguish between preference, current skill and future potential.
  • Compare at least two entry routes using evidence rather than reputation.
  • Critically evaluate an automated career suggestion, including where it is wrong.
  • Produce a realistic next-step plan they can start within a week.

Synthetic learner review

IT support technician

You are part way through a Level 3 IT course, you have rebuilt a home PC and set up a small network at home, and you have no certifications yet. You said you want to work in cybersecurity and that you have about five hours a week outside college. Nothing in that picture is unusual, and none of it rules anything out. It does mean the next year is about turning interest into something an employer can see.

You said you want to be in security within a year. Security teams usually recruit people who have already operated systems somewhere else, so a year is tight. Treat the first technical job as the route into security rather than a detour from it.

What the public sample is

This excerpt is a synthetic, hand-written demonstration of shape and tone. It is not a real learner, not a generated review and not a live cohort record.

Full generated reviews are only available inside a controlled pilot after staff and learner boundaries are agreed.

Boundaries that are already designed

  • Learners use random references, return codes and cohort codes. The public showcase does not collect learner records.
  • Staff cannot read an individual review unless the learner has chosen to share it inside a controlled pilot.
  • Small-group reporting is suppressed so a cohort summary cannot identify a learner by accident.
  • A review that fails the safety checks is held for a person to read. It is not silently released.
  • This is careers education, not safeguarding triage, recruitment screening or a suitability assessment.

What remains controlled

  • No general self-service launch is being claimed.
  • No public outcome claim is being made because no real institution has validated the materials yet.
  • Pilot terms, retention dates and deletion wording are confirmed in writing before any live cohort opens.
  • The full dashboard, cohort tools, learner join flow, generated reviews, fixtures and educator materials remain controlled.

Before a pilot

The institution agrees the audience, session dates, staff contact, safeguarding route, retention period and what will count as useful evidence.

During delivery

Learners complete the sessions and receive reviews through controlled cohort access. Staff see only what the learner or aggregate rules allow.

Afterwards

The pilot is judged against pre-agreed measures, including explicit failure conditions. A single cohort cannot prove broad impact.

No public Education price

Controlled pilot terms are agreed directly before delivery. There is no public checkout and no invented public price.

This starts a conversation, not a checkout. Do not send learner records here; the first step is only to decide whether a controlled pilot is appropriate.

Goes to one inbox. No mailing list, and your details are not passed on.