Field entry, published 2026-11-03T00:00:00.000Z, updated 2026-11-03T00:00:00.000Z. Group: National variants, labelled as variants

How is the United States SOC related to ISCO-08?

The United States SOC is a national occupation classification for the United States, and it relates to ISCO-08 as a separate national system that can be mapped to the ILO classification, not as a copy of ISCO-08 and not as a part of it. A SOC code therefore needs its SOC label in full, and an ISCO-08 code needs its ILO label, even when a published correspondence connects the two.

Thinking of SOC as an American dialect of the same idea helps, provided the metaphor is not pushed too far. Both systems group jobs by the kind of work performed, but SOC was built for United States surveys, agencies and labour market reporting, so its titles, boundaries and level of detail answer United States needs first.

What is SOC for, in its own terms?

SOC organises United States occupations so that different United States sources can talk about the same kinds of work in a consistent way. That consistency is valuable inside the United States, where employers, surveys and administrative records all need a shared vocabulary. It does not automatically make SOC figures comparable with figures from another country, because another country may split, merge or name the same kind of work differently.

This guide deliberately avoids quoting SOC codes, SOC titles in a correspondence table or a SOC revision date. Those details belong to the current United States publication, and they change between versions. A guide that froze them here would soon mislead a reader who trusted the frozen copy instead of the live source. For any live use, check the publishing United States body and its current correspondence material, alongside the ILO structure for ISCO-08.

How does the relationship to ISCO-08 actually work?

The relationship works through mapping, not through identity. Mapping means that a SOC group is linked to one or more ISCO-08 groups, or that several SOC groups together correspond to a broader ISCO-08 group, according to a published correspondence. The link is a judgement recorded in that correspondence, based on task similarity and skill, and it can be revised when either system changes.

Three consequences follow. First, a SOC code and an ISCO-08 code are not interchangeable, even where the titles look alike. Second, a mapping may be one to many or many to one, so converting in one direction may lose detail that cannot be recovered by converting back. Third, the version matters on both sides. A correspondence built for an older SOC version may not fit a newer SOC version, and the same caution applies to any future ILO revision. Always record which versions were used.

Where do readers most often slip?

One common slip is to copy a SOC title into a table headed ISCO-08 because the title sounds international. Another is to compare a United States SOC total directly with another country’s ISCO-08 total, without asking whether both totals came from the same level and the same mapping. A third slip is to treat a near match in wording as an exact match in scope. Titles can be similar while the tasks included, the boundary with a neighbouring group or the treatment of supervisors and helpers differs.

A useful habit is to pause at any United States figure and ask three short questions. Which system produced the original code? Which correspondence, if any, was used to reach ISCO-08? At which level, major, sub-major, minor or unit, is the comparison being made? If any answer is missing, the comparison is not ready to publish.

What does good practice look like in a report?

Good practice keeps both names visible. A table note might state, in the report’s own words, that the underlying data were coded in SOC, as a United States national variant, and then mapped to ISCO-08 for international comparison, naming the correspondence version used. A chart that mixes United States data with data from other countries should carry the same note, not bury it in an appendix that a reader may never open.

Where only SOC data are available and no mapping has been applied, the honest presentation is a SOC table labelled as SOC, with no ISCO-08 heading. That is not a failure. It is clearer than a forced conversion, and it lets a later analyst apply the correct correspondence when one is available.

What is left unverified here, on purpose?

This guide does not state the current SOC version, the publisher’s correspondence entries, or any date on which SOC was revised, because none of those details was verified from a primary source for this guide. Readers who need them should go to the United States body that publishes SOC and to the ILO pages for ISCO-08, and should cite the versions they actually consult. The relationship described here, a national variant mapped to an international reference, is the stable point. The version specific entries are the moving parts, and they belong in the primary publications, not in a summary that cannot keep them current.

Sources checked

1. ILO, ISCO-08

Back to the National variants, labelled as variants group or browse all occupations.