Field entry, published 2026-11-03T00:00:00.000Z, updated 2026-11-03T00:00:00.000Z. Group: From ISCO-88 to ISCO-08, and revision
What is the ILO revision work toward a successor?
| Major group | All major groups |
|---|---|
| Skill level | General |
| Code ladder | General |
Classification only, not a job decision
This guide describes ILO revision work in general terms only, and it does not forecast a group, title, or code for any reader's job.
ILO revision work toward a successor means the ongoing research, consultation, testing, and drafting through which the ILO prepares a future edition to replace ISCO-08 when the current edition no longer fits observed work well enough. That work is in progress, and it does not mean that a finished successor already exists, or that ISCO-08 has stopped being the current standard. Revision is a process with stages, and a reader who understands those stages will be less likely to mistake a discussion paper, a pilot structure, or a reported aim for a published classification.
What triggers revision work in the first place?
Revision work begins when evidence accumulates that existing groups misdescribe a growing share of jobs. Evidence comes from several directions at once. Statistical offices report groups that are hard to code, because job titles no longer match group definitions. Researchers point to new tasks, such as platform mediated work, data related roles, green transition roles, and care roles that have changed shape. Countries report national occupations that have no comfortable home in the international structure. None of those signals alone forces a revision, but together they show where the map is fraying. The ILO then weighs whether smaller updates, such as clarified definitions or better coding guidance, can repair the fraying, or whether a fuller revision is needed. A successor edition is chosen only when the second answer becomes clear.
What stages does revision work usually pass through?
Early work is mostly listening and mapping. Experts review how ISCO-08 is used, where coders struggle, and which occupations have grown, split, or merged since 2008. Draft structures follow, with proposed groups tested against real job titles and survey responses from different countries. Testing is crucial, because a group that works for one labour market may fail in another where the same work is organised differently. Consultation then widens, involving governments, employers, workers, statisticians, and researchers, so that the draft reflects varied labour markets rather than a single national picture. Only after that cycle of drafting, testing, and revising does a formal adoption step become possible, through the kind of expert meeting and governing body process that produced ISCO-08. Each stage takes time, and a delay at any stage moves the whole timetable.
How does revision work differ from everyday updates?
Everyday updates keep a classification usable without changing its structure: a new job title is added to an index, a coding note clarifies a boundary, or an example is refreshed. Revision work, by contrast, can change the structure itself, by splitting a group, merging two groups, moving a group to a new home, or rewriting a definition so that its scope changes. That structural power is why revision needs formal adoption and a new edition label, while everyday updates do not. A reader should therefore treat index additions and guidance notes as maintenance, and reserve the language of a new edition for a formally adopted successor. Confusing the two leads to false claims that the classification has already changed when only its guidance has improved.
What questions should a reader ask about any reported successor?
Four questions cut through most speculation. First, what is the source, and is it an ILO publication or a secondary report about ILO work. Second, what stage has been reached: research, draft, testing, consultation, or formal adoption. Third, what has actually been decided about structure, as opposed to proposed or debated. Fourth, what timetable is stated, and is it framed as an aim, a plan, or a confirmed release date. A report that answers all four questions clearly is far more trustworthy than a headline that names a successor without evidence. This guide deliberately gives no new version name and no new code, because inventing either would fail the third question at once. Until the ILO publishes a successor, ISCO-08 remains the edition to cite.
Why does slow revision protect statistics rather than hinder them?
Slow revision can feel frustrating to a reader who sees new work every day, yet speed would damage the very comparability a classification exists to provide. Countries need stable groups to run censuses and long surveys, and researchers need stable groups to build time series. A successor rushed into use before testing would produce noisy coding, divergent national practice, and broken comparisons. A successor prepared through testing and consultation, even if it arrives later than enthusiasts wish, gives countries a structure they can adopt with confidence. Patience here is not bureaucratic delay for its own sake. It is the price of a shared map that many different users can trust at the same time.
Revision work is therefore best understood as preparation, not as a replacement already in force, and its progress should be judged by published ILO material, stage by stage, rather than by rumour about a new edition.
Sources checked
Back to the From ISCO-88 to ISCO-08, and revision group or browse all occupations.