Skip to content

Science1 publisherNot yet confirmed elsewhere3 min readPublished

Australian labour research runs on O*NET without a crosswalk. One now exists, with a warning attached

No official O*NET-SOC to ANZSCO correspondence exists. The one just published chains three many-to-many joins, and its author says the European Commission's method is probably better.

The Scientist · Science desk

How we use AISend a correction

Illustration accompanying Australian labour research runs on O*NET without a crosswalk. One now exists, with a warning attached
Generated illustration

What happened

  • There is no official correspondence table between the O*NET occupational taxonomy and ANZSCO, even though Australian researchers use O*NET data routinely.
  • An analyst has published one, built by chaining O*NET-SOC through ISCO-08 or ESCO and then OSCA to ANZSCO, with problems appearing at each step.
  • The post tells readers to be suspicious of the table it produces and names the European Commission's approach as the probably better method.

Compiled by The ScientistSomething wrong?How this is made

Why it matters

  • exposure Australian work that borrows O*NET similarity measures is exposed to a mapping decision made by whoever ran the join, since the source says analyst judgement is unavoidable and no agency has ruled...
  • constraint With about 3.5 categories collapsing into each O*NET occupation at the first join alone, fine-grained occupation-level findings are more than the data can carry; group-level claims or hand-checked...
  • decision Anyone starting an Australian O*NET project now chooses between a table its own author recommends against leaning on and rebuilding the European Commission's method from scratch.
  • cost The OSCA transition means this rebuild cost recurs, and it lands on individual researchers rather than on a statistical agency.

The problem is arithmetic before it is taxonomy. The best SOC-to-ISCO correspondence the author could find maps 3,349 categories onto 958 O*NET occupations, and none of the matches are one-to-one [8]. That works out at roughly 3.5 source categories per O*NET occupation [19], and it happens at the first of three joins. ISCO-08 correspondences are published only at unit group level, so OSCA occupations arrive bundled into large groups on the way through [9].

The bundling does not run in one direction, which is what stops the chain being fixed by more careful joining. Engineering Technologist is assigned to several ISCO-08 groupings at once [7]. The ISCO/ESCO category for sports, recreation and cultural centre managers picks up two O*NET jobs, while O*NET's legislators splits across more than one ISCO/ESCO category [10]. On the Australian side, Production Manager (Manufacturing) carries more than one ANZSCO grouping [6]. Many-to-many at every step means the person building the table is deciding, not deriving. The author says so directly: analyst judgement is required to make the match fit the use case, and anyone working on trucking occupations, for instance, should confirm by hand that the data has been sensibly assigned [11].

That instruction is the part with teeth for anyone citing O*NET-derived numbers in an Australian paper. If the mapping requires judgement, the mapping is a result, with as much claim on the methods section as the model that consumes it.

The pointer to the European Commission's approach is unusual enough to sit with [4]. A crosswalk arrives carrying a note from its own author that a better method probably exists elsewhere and has not been reproduced here. Whoever picks up the table inherits that note, whether or not they pass it on.

Then there is decay. OSCA is the new standard and the successor to ANZSCO [12], which the author expects will give this crosswalk a short useful life [13]. The underlying correspondence tables were sourced from O*NET and the ABS on 21 August 2026 [14], so the artefact is pinned to a date and will drift at both ends. The author's own guess at why no official table exists is that OSCA is new and that O*NET-SOC does not match cleanly to ANZSCO or to the intermediate tables anyway [16]. The same mismatch turns up whenever datasets use different definitions of industries, administrative boundaries or products [17].

Worth noting how the work was made: the code was written largely with Claude, while the write-up was left more or less alone [15]. For a data-cleaning and joining exercise, that is the reverse of the usual concern. The thing a reader needs to review is the joins, and the joins came out of a machine. The whole exercise began as groundwork for a 2025 advisory project mapping occupational transition pathways in India [1], where the viability of a move between jobs was judged partly on how similar the two occupations were, conditional on geography, wage differentials and education [2].

What to watch

  • Whether the ABS or O*NET publishes an official correspondence between O*NET-SOC and OSCA, which would retire the ad hoc mappings currently in circulation.
  • The author's promised follow-up replicating ANZSCO-based research, which would show how far the mapping choices move the results.
  • Whether the European Commission methodology the post prefers is documented in enough detail for someone else to apply it to OSCA.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence55
Adoption12
Hype gap−20
Incentives30
Confidence58
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    In 2025 the author served as an adviser for a project to map occupational transition pathways in India.

    ReportedSupportedView cited source
  2. [2]

    The India project's methodology leaned heavily on studies using O*NET occupational profile data, with the viability of a transition pathway determined in part by how similar two jobs are, conditional on geography, wage rate differentials and education.

    ReportedSupportedView cited source
  3. [3]

    There is no official crosswalk between the O*NET occupational taxonomy and ANZSCO, despite Australian researchers frequently using the O*NET database.

    ReportedSupportedView cited source

Sources

1 independent publisher whose own reporting we read for this story.

  1. r-bloggers.com

    1 article · August 20, 2026

    The boring part first: Building a crosswalk from O*NET-SOC to ANZSCO

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Topics

  • AI-assisted data engineeringFollow
  • Occupational classification crosswalksFollow
  • Reproducible research in RFollow
  • Labour market data infrastructureFollow
Loading related stories