Mapping AI to real work

We broke all 923 US occupations into more than 270,000 steps and searched over 2,700 AI benchmarks for the ones that test them.

16 November 2026 · By the HeyMilo Labs team

Atlas exposes the gap between what benchmarks test and the work people actually do. It maps every occupation down to the steps of its real work and shows which of those steps any benchmark covers.

Other efforts go deep on a small set of jobs with human verifiers. Atlas goes wide first: every occupation, broken down to every step, with the evidence behind each judgment attached. Then it opens the map so experts can deepen it.

Benchmarks are our best way to measure what AI can do. But as they've turned into leaderboards to win, we've drifted from why we benchmark in the first place: to test whether a model understands, reasons, and can justify its work, rather than just pattern-matching its way to an answer.

Atlas is an open, public map shaped by the people who use it. It's built to help anyone understand where AI meets human work, and to turn its blind spots into benchmarks and environments with real economic value and impact. We go deeper into our findings below and explain what we’re building towards.

How do we know it’s real work? Every task comes from O*NET, the US government’s catalogue of what people do in each job, and every judgment cites the papers, datasets and code behind it. An AI judge makes each judgment and a second pass checks it (see how). On top of that, human experts are now reviewing Atlas domain by domain. That takes time, so if you know a field, help us review it or get in touch.

Benchmark coverage at launch

Atlas maps all 923 occupations, nearly 19,000 tasks and more than 270,000 steps. Here's how much of that work today's benchmarks test.

Occupations 613of 923 covered 143 fully covered
Tasks 3,808of 18,829 covered 282 fully covered
Steps 23,954of 271,399 covered 733 fully covered

2,721 benchmarks analyzed

What we’re building towards

The goal is a score for every job that reflects the real work, with model performance weighted by each step, its share of working time and its wages. Atlas already links coverage, time and wages to every step, and nearly 20,000 steps have a published model score. What stands in the way:

  1. Most work isn’t measured yet. Only 9% of steps are known to have a benchmark testing them, even partly, and over half haven’t been judged yet. Unmeasured work can’t be scored, so we’ll turn the gaps into benchmarks and RL environments with HeyMilo Labs but we can’t do it alone.
  2. Scores are for whole benchmarks. A model’s result covers the whole benchmark, not the step. We’ll tie item-level results to the steps they test.
  3. Expert validation. Every judgment so far comes from AI. We’re bringing in domain experts and the people who do the work to check it, fix what’s wrong and add what’s missing, and we’ll publish how often they agree.
  4. Unknown steps. About 151,000 steps still need judging, mostly in the mapped occupations.
  5. Work O*NET doesn’t list. We’ll add new and changing tasks as real work evolves.
  6. Physical work. Hands-on steps are the least measured of all, and will need benchmarks of their own as robotics matures.

Working on any of these? Contribute or get in touch.

Methodology Brief

Atlas starts from O*NET's list of tasks for every US occupation. A single task can hide a lot of different work, so we break each one down into the individual steps a worker actually performs. We then judge every step against the benchmarks that might test it, reading each benchmark's own paper, code and task files rather than just its description, and a second, independent pass checks every coverage claim.

It's worth being clear about what coverage means. It tells you whether a benchmark tests a piece of work, not whether AI can do it, which is why model scores are shown separately. A few words in Atlas carry a specific meaning, explained on the Terminology tab, and the full method is on the Methodology tab.

Limitations

This is our initial release. Read the findings below with these in mind.

One AI judge
Every judgment comes from one model and is checked by an independent second pass. We’re having experts review judgments, tasks and more.
Machine-written steps
Tasks are split into steps by the same model, and experts are validating those steps.
Two depths of search

We screened 153 occupations against every candidate benchmark. For the remaining 770 occupations, which account for 81% of all tasks, we used a benchmark-to-task map to select a narrower set of candidates. When tested against the fully screened occupations, the map recovered 80% of full matches and 47% of partial matches covering at least 30% of task steps.

Some apparent gaps in the second group therefore reflect missed matches rather than missing benchmarks. Its measured coverage is a lower bound, and comparisons between the two groups should be treated with caution.

Model-shortlisted candidates
Atlas draws on over 2,700 public benchmarks. For the 153 screened occupations, a language model shortlists the first batch of candidates by matching what each benchmark sets out to test against the occupation. A benchmark left off that shortlist is not judged there.
Uneven evidence
When only a benchmark's metadata can be read its judgments default to unknown. Unknown makes up 23.2% of all judgments.
Scores skip unknowns
A coverage score averages only the judged steps. A task with 5 covered and 5 unknown steps scores 1.0 while half of it is unassessed, so read scores alongside their evidence completeness.
Benchmark-level scores
A model's score is for the whole benchmark and not the single step it covers. A model can score 99% on a benchmark and still fail the one item that tests a step.
Estimated economics
Each task's share of working time is estimated from O*NET ratings and some occupations have none. Specialties that share one BLS row split its employment equally.
Relative to O*NET
Shares of working time count time on O*NET's tasks. Work that O*NET does not list is not measured at all.

Each of these shrinks as people contribute: expert workflows check the steps, new benchmarks and sources resolve unknowns, and reviewers check the judgments. See What we’re building towards and the Contribute tab.

Findings

Landscape

Most occupations are touched by at least one benchmark but coverage thins out quickly at the level of tasks and steps where the actual work happens. An occupation or task counts as covered here if a benchmark tests at least one of its steps, even partly.

2,721 benchmarks were analyzed and 1,930 were checked against at least one task.

One occupation task up close

Software Developers are among the best-covered jobs in Atlas, yet even their everyday work is only partly tested. Take the O*NET task “Modify existing software to correct errors, adapt it to new hardware, or upgrade interfaces and improve performance.” Atlas splits it into four paths of six steps each, and the coverage varies a lot between them. Fixing errors is fully covered and improving performance nearly so, but adapting software to new hardware and upgrading interfaces and integrations are only partly tested, and keeping older hardware supported has no benchmark at all.

Fix the reported error
1.00
Adapt it to new hardware
0.42
Upgrade interfaces and integrations
0.50
Improve performance
0.92
CoveredPartly coveredNot coveredRows are paths and squares are steps. Hover for the benchmark. Scores on the right are out of 1.

If one of the most measured occupations still has evaluation gaps like these, there is a lot of work to be done for every other occupation. Every occupation in Atlas is broken down the same way into tasks, paths, subtasks and steps, with the benchmark behind each judgment.

Benchmarks

To see where benchmarks focus, we gave every task a dollar value: what the US pays for that work each year, based on how many people do it, their median wage and the share of their time it takes. Benchmark builders clearly lean toward the work that pays most. Among the most valuable quarter of tasks, 35% have at least one tested step, compared with just 9% of the least valuable.

Even so, most high-value work is still untested. 65% of the most valuable tasks have no tested step at all, and only 3.6% have a step that is fully tested. That thin slice of measured work is what claims about AI’s economic impact rest on today, and the gap around it is where a new benchmark or RL environment would pay off most.

Tasks with a tested stepFrom least to most valuable, four groups of about 4,400 tasks
Fully coveredAt least partly covered
Value = BLS OEWS May 2025 employment × median annual wage × the task's estimated share of working time. Occupations sharing one OEWS row split its employment equally. A task counts when any one of its steps is covered.

For Atlas we chose breadth, reading over 2,700 benchmarks, so that “untested” means no benchmark we could find tests the work and not just that it is missing from a short list. That breadth also lays the foundation for Atlas to build on. The Benchmarks tab shows which of them cover the most steps.

Coverage by job family

Benchmarks are built around desk work. Computer, maths and legal jobs are the best covered yet even there fewer than three in ten steps are tested. Hands-on trades come last and most of their work has never been near a benchmark. This is not only a robotics gap though. Most work done on a computer is untested too and benchmarks tend to go where AI is already expected to help. The work we know least about is the work nobody expected AI to touch.

Steps by best coverage foundShare of each job family's steps, sorted by share at least partly covered
CoveredPartly coveredNot coveredUnknown
All 923 occupations, grouped by SOC major group. Each step takes the best judgment any benchmark received. Unknown includes steps no benchmark was judged against. Step counts on the right.

Model scores

Many benchmarks publish AI scores, such as a model’s pass rate on a coding benchmark. Atlas can link a published score to only about 20,000 of its more than 270,000 steps. For the other 93% there is no score at all so nobody knows how AI would do on that work.

All steps in Atlasn = 271,399

What to build next

Atlas contains about 574,000 judgments: 1,520 found full coverage and about 61,000 found partial coverage. The fully covered steps come from 281 benchmarks and 22 of them account for half. They are led by a teaching-workflow benchmark, Terminal-Bench 4.0, ERP-Bench and DeepSWE 1.1. See the top 10 on the Benchmarks tab.

Every partial judgment names the missing part in a sentence and so becomes a specification for the next benchmark. Each one can be checked: 98.8% of judgments cite a passage from the benchmark verified word for word and every judgment, quote and missing part can be opened in Atlas.

Extend
851 tasks could be covered by extending a benchmark that already exists.
Rebuild or research
Of the roughly 8,500 tasks checked against a benchmark, 34% need one rebuilt and 56% need more research. None can use a benchmark as it is.
Where it pays
The Build opportunity lens in Atlas ranks valuable work that benchmarks cover weakly. It is the starting point for new benchmarks and RL environments.
Atlas map of occupations as 3D blocks coloured by benchmark coverage, with map controls for 2D view, dark mode, zoom and fullscreen
Navigable in 3D

Explore what to build next

Mission

Our mission is to help the world understand where AI meets human work. A built out Atlas lets people in every industry see where they stand, support each other and move forward together, so that no one gets left behind.

Our methodology laid the first foundation of Atlas and we will keep building on it until the map reflects the work people really do and how AI compares to it. From there, we’ll continue to push and evolve Atlas to help the world understand the AI landscape.

Our background at HeyMilo Labs, understanding human workflows and skills across occupations, gives us a head start in mapping human work to AI. Read more on the HeyMilo Labs tab.

No single team can map work at this scale alone. We need researchers, engineers, domain experts and workers to help keep Atlas accurate for everyone. Your work won't go unnoticed, and we'll make sure it gets the credit it deserves. Learn more on the Contribute tab, or talk to us directly through the Contact us tab. We’re also open to collaborating across the RL development lifecycle, from data and benchmarks to environments and training.