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

How is Germany's KldB related to ISCO-08?

Germany’s KldB is a German national variant, a classification built for German labour market, survey and administrative use that relates to ISCO-08 through mapping, not by being ISCO-08 in German. A KldB code therefore always needs its KldB label, and any ISCO-08 figure derived from it needs a note saying that a mapping step took place.

German readers often meet KldB alongside other German administrative categories, which makes the labelling task harder rather than easier. When several German systems appear in one dataset, the temptation is to shorten every label to a bare number. That shortening is exactly where a national variant starts to masquerade as an international code.

Why does Germany maintain a distinct system?

Germany maintains KldB because German occupations, training routes and labour market institutions have a shape that an international list alone would flatten. Vocational training traditions, the organisation of skilled trades, and the way German surveys and registers record work all create a need for finer or differently drawn groups. A national variant lets German statistics speak precisely about German work, while a mapping to ISCO-08 lets those statistics enter international comparison when needed.

That dual purpose explains why KldB should not be judged by how closely it copies ISCO-08. Closeness at broad level is useful for comparison, but difference at detailed level is often the point. A variant that copied ISCO-08 exactly would add nothing for national use, and a variant that ignored ISCO-08 entirely would add nothing for comparison. KldB sits between those poles, as a national system with an international link.

How does mapping handle German detail?

Mapping from KldB to ISCO-08 works group by group, comparing tasks, skill and scope. Some KldB groups may map cleanly to a single ISCO-08 unit group. Others may map to a broader ISCO-08 minor or sub-major group, because ISCO-08 does not draw the same fine line. Still others may split across ISCO-08 groups, in which case a simple one to one conversion is impossible and the mapping must record how the split was handled.

The practical lesson is to check the level before reusing a mapped figure. A mapped result that is sound at a broad level can become misleading if it is broken back down into detail that the mapping never supported. Reports should therefore state the level at which mapping was applied, and should not present mapped detail at a finer level than the correspondence allows.

What role does language play?

Language is not a cosmetic issue here. German occupational titles carry meanings tied to training, legal status and workplace organisation that a literal translation may miss. A title translated word by word into English may look like an ISCO-08 title while covering a different set of tasks. Coding should follow the German definition and the published correspondence, not the apparent English equivalent.

This also affects readers who do not work in German. They should be especially careful not to infer scope from a translated title alone. The group definition, the mapping note and the version consulted matter more than whether two titles sound alike in translation.

How can a reader check a KldB to ISCO-08 claim?

A reader can check a claim in four moves. First, find the system name and version for the original KldB data. Second, find the correspondence used, including its version. Third, find the ISCO-08 level at which results are presented, remembering the ILO hierarchy of 10 major groups, 43 sub-major groups, 130 minor groups and 436 unit groups. Fourth, look for any note about groups that could not be mapped cleanly, since an honest mapping will flag its rough edges rather than hide them.

If any of those four pieces is missing, the claim is incomplete, not necessarily wrong, but not yet ready to quote. Asking for the missing piece is better than filling the gap with an assumption.

What has this guide deliberately left out?

No KldB codes, no KldB version, no correspondence entries, no publication dates and no naming of the German publishing body beyond describing it as the German body that publishes KldB are given here, because those details were not verified from a primary source for this guide. For live work, go to that German body for the current KldB structure and correspondence, and go to the ILO for ISCO-08. Keep KldB labelled as a German national variant throughout, and keep ISCO-08 reserved for the ILO classification.

Sources checked

1. ILO, ISCO-08

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