01 / The bundleStart with everything the job contains
O*NET lists each occupation as a set of task statements. Laid out flat they are just a bundle — no ordering, no weighting, and nothing yet said about which of them a machine could take.
Every square is one documented task
02 / What staysSome of it a model cannot touch
Work needing hands on a patient, presence in a room, or a judgement someone has to own. These stay grey at every setting — no scenario moves them, because the constraint is not capability.
Grey at every scenario
03 / What gets helpSome gets faster rather than taken
A model drafts, summarises, plans or checks, and a person keeps the work. This is the largest category in the middle scenario — the least dramatic result in the dataset, and the most plausible.
The largest group under Substantial
04 / What gets takenAnd some of it goes
High exposure, little accountability attached: retrieval, formatting, routine documentation, scheduling. Move the scenario and watch this category eat into the middle one. That movement is the whole argument.
21% → 45% → 69% of all tasks
05 / What arrivesNew work appears too
Not modelled — observed. O*NET flags newly emerging task statements, 121 of them across these occupations. For a nurse midwife: evaluating patients’ mental health, screening for gynaecologic conditions.
121 new tasks recorded in O*NET
06 / What is leftThe job is not smaller, it is different
What remains gets more room. The tasks a model touched carry more volume per hour of human attention; the ones it cannot touch are what the job becomes. Whether that is a better job is not a question this data can answer.
Scale shows capacity, not headcount