Change Codes Documentation
Alongside information on included organisations, the database tracks structural changes using the “Change Code” classification.
(101) Pure Founding
This code is used when a unit is created without evolving from another entity, when no prior organizational history is known. However, many units assigned to this code may have a history suggesting that other change codes should have been used. In cases where available sources do not indicate such a history during the coding process, this code is applied.
(102) Founded by Secession
Code "102 new via secession" is used when a unit gains independent status by being separated from an already existing entity. In this spin-off process, the existing entity also changes its organisational status. See also code "202 maintenance by secession".
(104) Founded by Splitting
When a unit ceases to exist by being divided into two or more new entities, code "104 new via splitting" is used. In this splitting process, code "304 terminanted by splitting" is applied to the organisational unit that ceases.
(106) Founded by Merger
This code is used when a unit is established by merging two or more entities into a new one. In this merger process, code "306 terminated by merger" is applied to the units that cease.
(111) Founded by Complex Reorganisation
In some cases, it is challenging to use specific change codes when a change occurs in a unit or a group of units. Based on two points in time, a group of units may have received new names and reporting lines in such a way that it is not possible to use more detailed change codes. In such cases, new units in this change process are coded with "111 founded by complex reorganisation". In this reorganisation process, codes "211 maintained by complex reorganisation" and "311 terminated by complex reorganisation" are also used.
(112) Inscripted
This code is used in cases where the establishment date is unknown. The date of the change is set based on judgment. The database includes units that have existed since January 1, 1947. Many units that existed as of January 1, 1947, are inscripted using this change code if the correct establishment date is not known.
(202) Maintained by Secession
Code "202 maintained by secession" is used when a unit continues to exist after a part of it is spun off as a new entity. In this secession process, the new entity is coded with "102 founded by secession".
(203) Maintained by Absorption
Code "203 Maintained by Absorption" is used when an existing unit continues after absorbing another already existing entity. In this absorption process, the organisational unit that is absorbed into the existing unit is coded with "303 terminanted by absorption".
(207) Change of Name
When a unit changes its name without any other changes, this code is used. For some organisational units assigned to this code, there may be functional changes beyond just a name change.
(209) Change of Location
When a unit changes its physical location to another municipality, this is registered as a change of location, for example, relocations of state institutions from Oslo.
(211) Maintained by Complex Reorganisation
In some cases, it is challenging to use specific change codes when a change occurs in a unit or a group of units. Based on two points in time, a group of units may have received new names and reporting lines in such a way that it is not possible to use more detailed change codes. In such cases, units that "survive" such a change process are coded with "211 maintained by complex reorganisation". In this reorganisation process, codes "111 founded by complex reorganisation" and "311 terminated by complex reorganisation" are also used. Note that this code is also used to register internal reorganisations and significant changes in entities where the internal structure is not registered (i.e., units outside the ministries).
(213) New line of Reporting
Code 213, new line of reporting, is used in cases where a new unit is established between two units in the hierarchy. In such cases, the unit at the lowest level in the hierarchy will have a new superior. This change code is used to indicate that the lowest unit in the hierarchy has a new reporting line. For example, establishing a section between an already existing department and office within a ministry would result in an entry indicating that the office has changed its superior.
(221) New Superior Organization (Horizontal Transfer)
A horizontal move occurs when an entity reports to a new superior without changing its affiliation form and/or administrative level. For administrative units within ministries, this move can take place both within and between ministries. However, for main entities (such as directorates), horizontal moves generally happen between ministries.
(222) Vertical Relocation (Transformation)
This code is used when an organisation changes its form of affiliation and/or administrative level. The terms "transformation" and "change in affiliation" are also used for this type of relocation. Vertical relocation typically applies to main entities (such as directorates, agencies etc). For example, if a government administrative enterprise is restructured into a company but remains under the same ministry, this code is used. It also applies when administrative levels change for units within ministries, for example if a section is transformed into a department.
(223) Horizontal and Vertical Relocation
When an organisation reports to a new superior while also changing its form of affiliation and/or administrative level, it is classified as a horizontal and vertical relocation. This type of change is a combination of 221 New Superior Organization (Horizontal Transfer) and 222 Vertical Relocation. It also includes cases where a unit moves in or out of the public sector. For example, if an organisation is transferred to the private sector, it is recorded under this code because both the affiliation type and superior authority change.
(291) Redistributed transfer
When a unit gets a new superior (at the same level) without the affiliation and/or administrative level of the unit itself being changed at the same time as the previous superior is closed down, this is registered as a redistributed transfer. For example, if a ministry is divided into two new ministries, the original ministry is dissolved, and its subordinate units are redistributed to the new ministries. Since the reason for the transfer is external to the unit itself, this type of change may not be included in aggregated relocation statistics. Although there is no change in affiliation or administrative level, the unit gets a new superior, making it similar to a horizontal transfer. This change code is of a more technical nature in order to be able to place the unit correctly in the hierarchies.
(292) Units moving into, or out of, integrated services
This code is used when an organisation moves under an agency or a grouped entity that is itself under an agency or ministry. However, these grouped entities are considered "empty", meaning they don't have independent organisational resources, and no units report directly to them. As a result, there is no actual change in the unit's superior authority, affiliation type, or administrative level.
Note: If a national single body moves under an agency (e.g., a directorate structured as an integrated service), it may also result in a change of superior authority.
(303) Terminated by Absorption
This code is used when an organisation is dissolved after being incorporated into an existing unit. In this process, the unit that continues to exist is coded as 203 maintained by absorption
(304) Terminated by Splitting
When an organisation is dissolved by splitting into two or more new entities, this code is applied. The newly created entities receive the code 104 Founded by Splitting.
(306) Terminated by Merger
If two or more organisations merge to form a new entity, the original organisations are coded as 306 Terminated by merger. The newly created entity is coded as 106 Founded by Merger.
(310) Pure termination
This code is used when an organisation is permanently closed. However, in the Norwegian State Administration database, this code has likely been overused due to a lack of information about whether the organisation's functions have been transferred elsewhere.
(311) Terminated by Complex Reorganization
In some cases. It is difficult to apply specific change codes when an organisation or group of organisations undergoes structural changes. Over time, units may receive new names and reporting structures in a way that prevents the use of more detailed change code. In such cases, organisations that are dissolved due to a reorganisation process are assigned to this code. During this process, the codes 111 Founded by Complex Reorganisation and 211 Maintenance by Complex Reorganisation may also be used.
(312) Dissolved with Deregistration
This code is used when an organisational change results in the unit no longer being affiliated with a ministry. For example, if the unit is privatised or transferred to private sector, it is removed from the database because it is no longer a valid entity in the database. The previous recorded event will indicate the reason for deregistration. This code states that no further changes to the unit will be recorded.