How do you read a four digit ISIC code?

A four digit code in ISIC Rev. 5, UN Statistics Division, is read from left to right as a path through the hierarchy, not as a single number. The first two digits give the division, the third digit narrows it to a group, and the fourth digit narrows it again to a class. Reading it that way matters because neighbouring codes are not necessarily neighbours in meaning: closeness in digits does not always mean closeness in activity.

What does each position in the four digits actually narrow?

Read a four digit code from left to right as a path, not as a single number to be memorised. The first two digits give the division, the broad field inside a section. The third digit narrows that division to a group, a cluster of related activities inside the field. The fourth digit narrows the group again to a class, the finest level of the international classification. Each digit therefore adds a decision: first the field, then the cluster, then the specific kind of work. A reader who skips a step, jumping straight from the full code to a guessed meaning, misses the checks that each level is meant to provide.

That stepwise reading also explains why the code is written as digits rather than as a word. Words carry everyday associations that pull a reader toward familiar meanings, while digits force the reader back to the structure: find the division, read its note, find the group, read its note, find the class, read its note. At each level, the question is the same and deliberately narrow: does the definition still fit the activity described in words, and does an excludes list redirect the activity elsewhere? If the answer at any level is unclear, the honest step is to stay at the broader level that is clearly correct and to record the question, rather than to pick a finer category that the evidence cannot justify.

How does a reader move from digits back to words?

Start by stripping the code back to its levels. The first two digits name the division, the third adds the group, the fourth adds the class. Then, for each level, read the explanatory note, the includes list and the excludes list, rather than relying on the title alone. Titles invite quick guesses, because everyday words are given technical definitions in Rev. 5, and the definitions, not the familiar words, decide what is counted where. A reader who can explain the category in words, without using its title as a definition, has understood it. A reader whose explanation leans on the title alone needs more reading before quoting the code.

A practical illustration, kept deliberately general, shows the habit in action. Imagine a statistical analyst preparing a table for readers who did not collect the data. The analyst writes the activity in plain words, traces it through the UNSD Rev. 5 structure reading each note, and only then records a category. A colleague later asks why a neighbouring category was not chosen, and the analyst points to the excludes list that decided the matter. The table is published with its version label visible, so a reader in another country can check the same structure and reach the same understanding. That chain, from words to notes to a labelled result, is the whole method in miniature, and it works because each level was checked in turn rather than guessed from the digits.

When is stopping at two or three digits the honest choice?

Detail is not a virtue on its own. If the evidence describes a field clearly but does not distinguish between the classes inside it, a division or group figure is the correct figure, and a class figure would dress uncertainty up as precision. Statistical honesty favours a correct broad figure over a detailed figure that cannot be defended, and a methods note that says plainly why the broader level was chosen will earn more trust than a fine figure with no supporting note. The same logic applies in reverse: where the evidence does support class detail, and the question needs it, stopping at division level would hide variation the reader was asking about.

Writers should therefore choose the level by matching two things: the question being asked, and the evidence available. A sector overview often stops at division level. A specialist table often begins at group level and goes to class level where the notes support it. In both cases, the level should be named in the heading or footnote, the version label should travel with the code, and any break in series should be flagged where figures from different revisions appear together.

This guide explains how digits are read inside a statistical classification, and it makes no decision about any reader’s own situation. For reading a four digit ISIC code, read this guide as statistical classification only: it assigns no code, principal activity, or registration to any reader, and a specific record is confirmed by the national statistical institute or business register holding it.