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

How is Canada's NOC related to ISCO-08?

Major groupNational variant, not ISCO-08 itself, see text
Skill levelSee text, ISCO-08, ILO
Code laddergeneral

Classification only, not a job decision

This guide compares classification systems. It never sorts a reader's own work into NOC or into ISCO-08, and it offers no coding verdict.

Canada’s NOC is a Canadian national variant, a system built for Canada that relates to ISCO-08 through mapping rather than by being ISCO-08 under another name. A NOC code quoted without the NOC label, or slipped into an ISCO-08 table without a mapping note, loses the very information that makes it interpretable.

Canadian readers meet NOC in many places, from census and survey outputs to employment and training material. That familiarity can create a false sense of universality. Familiar inside Canada does not mean identical outside Canada, and the task of this guide is to keep the Canadian system visible while explaining its link to the ILO reference.

Why would Canada need its own system at all?

Canada needs a vocabulary that fits Canadian jobs, Canadian institutions and Canadian survey respondents. A purely international list, however well designed, would miss local titles, local ways of organising work and the level of detail that Canadian policy and research require. NOC answers that need by providing a Canadian structure that can still be related to ISCO-08 when international comparison is wanted.

The trade off is built into the design. More local fit means more local difference. A Canadian group may be finer than the nearest ISCO-08 group, broader than it, or drawn around a boundary that ISCO-08 draws elsewhere. Those differences are not errors. They are the reason a variant exists, and they are also the reason a mapping step is needed before comparison.

What does mapping between NOC and ISCO-08 involve?

Mapping links a NOC group to the ISCO-08 group or groups that best match its scope, using task similarity and skill as the guide. The result is a correspondence, a published link between two systems, not a renaming of one system as the other. A correspondence can be straightforward at a broad level and messy at a detailed level, because fine Canadian distinctions may collapse into one international group, or one Canadian group may span more than one international group.

Version discipline matters here as much as in any other variant. NOC changes over time, ISCO-08 has its own history, and a correspondence tied to one pair of versions may not hold for another pair. A report that names the systems but not the versions has left out a key part of the method, and a later reader may apply the wrong correspondence without realising it.

How should a Canadian figure be read beside an international figure?

Start by separating the stages. First, the Canadian figure was produced in NOC. Second, it may have been mapped to ISCO-08, or it may not have been. Only the second stage supports an international comparison, and only at the level where the mapping is reliable. A detailed NOC breakdown that collapses neatly at major group level may still be unreliable at unit group level after mapping, because detail is lost in the collapse.

Language adds a further check in Canada. Titles exist in more than one language, and a translation that looks equivalent may carry slightly different scope in practice. The safe approach is to trust the coded group and its published definition, not the title alone, and to note the language version consulted where that could affect interpretation.

What mistakes are worth watching for?

Watch for a NOC title used as if it were an ISCO-08 title, especially in short briefing tables where system notes are often dropped. Watch for a trend that mixes NOC versions, since a change in the Canadian system can look like a change in employment when it is really a change in classification. Watch also for a comparison that uses a NOC group at one level and an ISCO-08 group at a different level, which can exaggerate or hide a difference.

None of these mistakes requires bad faith. They usually come from copying a number without its label, which is why labelling discipline, repeated in every guide in this cluster, is a practical safeguard rather than pedantry.

Which details has this guide left to the primary sources?

No NOC codes, no NOC version number, no correspondence entries and no revision dates are given here, because they were not verified from a primary source for this guide. That omission is intentional. For live work, consult the Canadian body that publishes NOC for the current structure and correspondence, and consult the ILO for ISCO-08 itself, with its 10 major groups, 43 sub-major groups, 130 minor groups and 436 unit groups. Cite the versions you actually used, and keep the NOC name attached to every NOC figure.

Sources checked

  1. ILO, ISCO-08

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