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

When might a successor to ISCO-08 appear?

A successor to ISCO-08 might be implemented around 2030, according to ILO reporting on revision work, but that timing should be read as an aim rather than as a fixed release date. No confirmed publication day is stated here, and no new version name is assumed, because a successor edition does not exist as a published standard until the ILO formally adopts it. A reader who treats around 2030 as a guaranteed launch will plan badly, while a reader who treats it as a planning horizon will use it well: as a signal that preparation is under way and that change, when it comes, will need correspondence work, retraining, and careful handling of series breaks.

Why is around 2030 a planning horizon rather than a promise?

Revision timetables depend on stages that cannot all be fixed in advance. Drafting may reveal a boundary dispute that needs more testing, consultation may surface a labour market pattern that a draft missed, and formal adoption requires agreement through bodies that meet on their own schedules. Any of those steps can shift a timetable by months or longer, and a shift at one stage compounds through later stages. ILO reporting that points to implementation around 2030 therefore describes direction and ambition, not a contract. Treating it as an aim also protects statistical producers, who would otherwise face pressure to promise users a switch date before the structure is stable enough to adopt. A planning horizon invites preparation without forcing premature commitment, which is the right balance for a standard used by many countries.

What would need to happen before a successor could appear?

Several milestones would need to be visible in ILO publications before a successor could be treated as imminent. A draft structure would need to be published and tested against real job data from varied countries. Consultation results would need to show broad agreement on contested boundaries, such as new technology roles, platform work, and evolving care and green roles. A formal adoption step, comparable to the expert meeting and governing body endorsement that produced ISCO-08, would need to take place. After adoption, the ILO would need to publish the full structure, definitions, and correspondence material linking the new edition to ISCO-08. Until those milestones appear in order, a successor remains a project, however advanced, rather than a standard ready for coding. Readers can track progress by watching for those publications, not by watching headlines.

How should countries and data users prepare in the meantime?

Preparation in the meantime is practical, not speculative. Statistical offices can review where ISCO-08 coding is hardest, keep records of national titles that fit poorly, and preserve task detail in survey responses so that future recoding is possible. Researchers can document which edition they used, keep their code lists, and avoid building a long series that silently mixes editions. Publishers of statistics can plan for dual coding samples around any future switch, so that users can see the effect of reclassification separately from real employment change. None of that preparation requires guessing the final structure. It only requires good documentation now, which will pay off whenever a successor arrives, whether near 2030 or later.

What happens to ISCO-08 figures if a successor arrives later than expected?

If a successor arrives later than the reported aim, ISCO-08 figures simply continue as the current standard, and no crisis follows. Classifications are designed to be used for years, and a longer life for ISCO-08 would mean that its groups still serve most coding needs well enough, even if some newer roles fit awkwardly. Users would continue to note awkward cases, and revision work would continue to address them. The risk of a later arrival is modest: some new work remains roughly classified for longer. The risk of an early, untested arrival would be larger, because it would break comparability across countries that adopt at different speeds. A timetable that slips is therefore less damaging than a timetable that forces adoption before testing is complete.

How should this guide be cited by a careful reader?

A careful reader should cite the timing as ILO reporting pointing to implementation around 2030 as an aim, and should add that no fixed release date and no new version name are confirmed here. That wording is deliberately cautious, and its caution is the point. It lets a reader plan, discuss, and prepare without overstating what is known. When the ILO publishes firmer material, this guide should be updated to reflect it, with the new source stated and the old aim wording replaced rather than quietly overwritten. Until then, around 2030 remains a horizon to watch, not a date to promise.

Sources checked

1. ILO ISCO-08

Back to the From ISCO-88 to ISCO-08, and revision group or browse all occupations.