Craig Stanley
Home / Work / The ESCO lens

Crosswalking ESCO to O*NET

How to move between ESCO occupations and O*NET profiles so you get ESCO's skills detail and O*NET's task detail for the same role.

10 October 2026 · 2 min read · Craig Stanley
In short, explained

ESCO and O*NET are two big lists of jobs from different places. A crosswalk is like a dictionary that tells you which job on one list matches which job on the other.

A crosswalk links matching jobs in ESCO and O*NET. That lets you combine ESCO's skills list with O*NET's tasks and work conditions for the same role, which gives you a fuller picture than either one on its own.

Use the European Commission's ESCO–O*NET crosswalk to join ESCO occupations to O*NET-SOC codes. Treat matches as candidates. Many are one-to-many, so validate each against local job descriptions before combining task and skill data.

Why bother

ESCO tells you the skills a role needs. O*NET tells you the tasks people do and the conditions they work in. When you want to map decisions and the skills needed to make them, having both for the same role is worth the extra step.

The official crosswalk

The European Commission has published a mapping between ESCO occupations and O*NET-SOC occupations. It's the place to start, rather than matching job titles by hand.

Things to watch for

One-to-many matches. One ESCO occupation can match several O*NET occupations, and the reverse. Pick the closest by reading the descriptions, not just the titles.

Different levels of detail. Some areas are split finely in one framework and grouped broadly in the other. When that happens, note it and work at the broader level.

Local reality wins. Both frameworks describe averages. Use the crosswalk to build a first draft, then check it against your own job descriptions and what people actually do.

A simple workflow

  1. Find the ESCO occupation closest to your role.
  2. Use the crosswalk to find candidate O*NET occupations.
  3. Take the essential skills from ESCO and the tasks and work context from O*NET.
  4. Check the combined profile with people in the role.
  5. Use the tasks to find decisions, as in Map the work, then the decisions.

Read next

A question to take awayCould you list the ten decisions your team makes most often, with how long each takes?

About me

Craig Stanley

Microsoft AI consultant and technical architect, based in Whitley Bay. Over the last few years I've delivered Microsoft 365 Copilot, Copilot Studio agents, Azure AI Foundry work and governance for UK public sector and financial services organisations.

What interests me is the decision underneath the tool: what it costs, what it risks, and whether a small, transparent model can make it better. I write the methods up here and on Substack so anyone can use them.

Find me