How do service splits differ from renaming, merging and restructuring?

A split, a renaming, a merger and a restructuring are four different kinds of change in NACE Rev. 2.1, and the manual records each kind in different terms. A split divides one category into two or more. A renaming changes a title without changing the scope. A merger joins two or more categories into one. A restructuring rearranges the grouping of categories. The distinctions matter for reading correspondence tables, and no change type determines a code for a specific reader.

What is a split, in the manual terms?

A split is recorded in section 4 with the word split, or with the phrase has been split, and it names the new categories that result. Group 49.1 split into classes 49.11 and 49.12, in paragraph 161. Group 64.2 split into classes 64.21 and 64.22, in paragraph 175. Group 74.1 split into four classes, in paragraph 182. In each case, one source category becomes two or more target categories, and the correspondence pattern is one to many, where the split is clean, or many to many, where the content has been rearranged. The table records the scopes, and the notes for the new classes state the contents. A split increases the detail of the classification at the level where it occurs, without changing the higher levels.

The split pattern must be distinguished from the creation of a new class that has no single source. A new intermediation class, for example, is created in a division, but its content is drawn from work previously held in several classes, and it is not a split of one class. The manual lists the intermediation creations separately, in paragraph 135, and it does not call them splits. A reader who calls every new class a split will misread the correspondence table, because the table records a new class differently from a split class, and the notes for the new class state a scope that no single old class held.

What are renaming, merging and restructuring, with service examples?

A renaming changes a title, or a section letter, without changing the scope of the category in the terms the manual states. The section letter shift, in which the old Section K became Section L and the sections after it shifted one letter, is a renaming at section level, recorded in paragraphs 174 to 202. The scope of the financial and insurance section did not change because its letter changed. A reader who treats a renamed category as a new category will invent a change that the manual does not record, and will miss the continuity that the renaming preserves.

A merger joins two or more categories into one, and it is recorded with the word merged or merger. In services, classes 82.11 and 82.19 merged into class 82.10, office administrative and support activities, in paragraph 188. Groups 80.1, 80.2 and 80.3 were integrated into group 80.0, investigation and security activities, restructured to classes 80.01 and 80.09, in paragraph 187. The merger pattern in a correspondence table is many to one, the reverse of a split. A restructuring rearranges the grouping, as in divisions 90, 91 and 96, where groups were created, split or promoted, and the manual uses the words restructuring and restructured for those changes, in paragraphs 195, 196 and 200.

How are the four change types compared?

| Change type | Manual wording | Correspondence pattern | Service example in section 4 |

|---|---|---|---|

| Split | Split, has been split | One to many, or many to many | Group 49.1 into classes 49.11 and 49.12 |

| Renaming | Renamed, has been renamed | One to one, scope unchanged as stated | Old Section K renamed to Section L |

| Merger | Merged, merger | Many to one | Classes 82.11 and 82.19 into class 82.10 |

| Restructuring | Restructuring, restructured | Many to many, in most cases | Division 90 into groups 90.1, 90.2 and 90.3 |

The table follows section 4 and paragraph 207. The correspondence pattern column states the usual pattern for each change type, not a guarantee for a particular category, because the manual records the patterns class by class in the correspondence table, and a restructuring can contain splits, mergers and renamings inside it. The table is a reading aid for section 4, and the correspondence table itself is the authority for the pattern that applies to a given category.

What does a split not decide?

This cluster presents no correspondence mapping as a one to one guarantee where a split or rearrangement is recorded in the table. A clean split is recorded as one to many, and content rearranged across several categories is recorded as many to many. In both cases, joint scopes are recorded in the table, and each new class note must be read. This page guardrail states the limit directly, and the guide body repeats the limit in its own wording.

Where is a split class confirmed?

A service split is confirmed by reading the explanatory note for each new class, the correspondence table entry for the old group or class, and the entry held for the unit concerned, confirmed with the national statistical institute or the business register holding the record.

Name the change type before reading the table, expect the pattern that belongs to that type, and confirm the entry with the institute or register that holds it.