What makes categories mutually exclusive?

Categories in ISIC Rev. 5, UN Statistics Division, are designed to be mutually exclusive, so each activity belongs in one category at each level rather than in two at once. Explanatory notes, includes lists and excludes lists police those borders by telling the reader what belongs inside and what belongs elsewhere. The design is not perfect in every borderline case, but exclusivity is the goal that makes counts add up without double counting.

Why must each activity have exactly one home at each level?

Mutual exclusivity is a design promise: at any given level, each activity belongs in one category rather than in two at once. The promise is what lets counts add up. If an activity could sit in two categories, adding the categories together would count it twice, and a total built from those categories would overstate the economy it claims to measure. If an activity could sit in none, the total would understate it. Exclusivity is therefore not a tidiness preference. It is the condition that makes an industry total arithmetically meaningful, and it is the reason category borders are policed as carefully as they are.

The policing is done in writing, not by intuition. Explanatory notes say what a category covers. Includes lists name what belongs inside. Excludes lists name what belongs elsewhere, often pointing to the neighbouring category that should take it. Residual categories catch what fits nowhere else, so that nothing falls through the cracks while pretending to fit somewhere specific. Together those devices draw borders a coder can follow and a reader can check, which is the point: a border that only the original coder understood is not a border at all.

What strains exclusivity in real life?

The design is not perfect in every borderline case, and honesty about that imperfection is part of using the system well. Real activities rarely fit textbook examples. An organisation may combine several activities, so that more than one category seems to claim the same unit until the unit and its activity are examined separately. An activity may change character over time, so that a grouping that was exclusive last year becomes contestable now. A new method of production may blur an old boundary, so that work once clearly on one side now sits astride the line. In each case ISIC Rev. 5, UN Statistics Division, offers the notes, includes lists, excludes lists and residual categories as tools, but the tools only help if they are actually read. A reader facing a borderline case should slow down, read the notes for both candidate categories, and note the uncertainty, rather than forcing a quick answer that later proves hard to defend.

What four checks protect a comparison built on exclusive categories?

A comparison is only as exclusive as the figures behind it, so four checks come before quotation. Check the version label, and name ISIC Rev. 5, UN Statistics Division, where Rev. 5 is meant, because a different label silently substituted would mean the categories being compared were never the same categories. Check the level, because a division total and a class figure answer different questions even when they share a word in their titles. Check the reference period, because revisions and national adoption dates can fall inside a series and move a border mid-trend. Check the source of the classification, because a border can only be verified against a named structure.

How does an analyst demonstrate exclusivity in practice?

Picture an analyst preparing a table for readers who never collected the data. The analyst writes the activity in plain words first, then 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 can point 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 exclusivity made auditable. The activity has one home at that level, the reason is written down, and a stranger can retrace it.

Hold the comparison to the same standard: same version, same level, same definitions, across the tables being compared. Where any one of those changes, the comparison needs a note explaining the change, because without that note the reader will assume exclusivity held and addition was safe, and that assumption is exactly what a broken comparison exploits.

For statistics only, and for no individual determination: this guide does not assign a code, a principal activity or a registration to any reader, and a specific record belongs with the national statistical institute or business register that holds it for confirmation.