Skip to main content
Records Authority
Category: Essential Records and Continuity

Devolution

Also known as: Decentralisation of governmental power
Simply put

Devolution is the transfer of certain governmental powers from a central government to smaller regional or local government bodies, which remain part of the same sovereign state. A commonly cited example is the powers granted to bodies such as the Scottish Parliament and the Welsh Parliament within the United Kingdom. The powers involved are delegated rather than fully surrendered, so the central government typically retains overarching authority.

Formal definition

In a governance context, devolution refers to the statutory delegation of powers from the central government of a sovereign state to govern at a subnational level, such as a regional or local body, while that body remains under the ultimate authority of the central government. The scope and permanence of devolved powers depend on the enabling legislation and vary by jurisdiction; devolution should be distinguished from full independence or federal separation, as the subnational government continues to operate within the constitutional framework of the sovereign state. In its broader lexical sense, devolution can denote the transference of rights, powers, property, or responsibility to another party, but this entry addresses the governmental and constitutional meaning.

Why it matters

Devolution shapes where governmental authority sits, and by extension where recordkeeping accountability and information governance obligations fall. When powers are delegated from a central government to a subnational body such as the Scottish Parliament or the Welsh Parliament, that body typically becomes responsible for creating, capturing, and maintaining records of the activities it now governs. Understanding how powers have been distributed helps records and information professionals determine which authority holds the authoritative record of a given decision or function, and which body's policies and legal framework apply to its retention and disposition.

Because devolved powers are delegated rather than fully surrendered, authority can remain shared or overlapping between central and subnational bodies. This has practical consequences for information governance: responsibility for a particular function may straddle jurisdictions, and the applicable retention requirements, access regimes, and privacy obligations can differ between the central government and the devolved administration. Professionals should treat these arrangements as jurisdiction-specific, since the scope and permanence of devolved powers depend on the enabling legislation and vary considerably from one arrangement to another.

Who it's relevant to

Records managers in public sector bodies
Records managers working within central or devolved government need to establish which authority is responsible for records of a given function. Because powers are delegated rather than surrendered, responsibility for creating and maintaining authoritative records may sit with a devolved body, the central government, or be shared, and this affects which body's recordkeeping policies apply.
Information governance and compliance leads
Governance and compliance professionals must account for the possibility that policy, access, and privacy obligations differ between central and subnational administrations. Since the scope of devolved powers depends on the enabling legislation and varies by jurisdiction, applicable requirements should be confirmed against the specific arrangement rather than assumed to be uniform.
Archivists and public records custodians
Archivists concerned with the transfer, preservation, and disposition of public records may need to determine which body holds custodial responsibility for records generated by devolved functions. Where authority is shared between central and subnational bodies, custody and transfer arrangements can be affected accordingly.
Freedom of information and access practitioners
Practitioners handling access requests should be aware that the body responsible for a devolved function is often the one that holds the relevant records and, depending on jurisdiction, may operate under a distinct access regime. Identifying the correct responsible authority is a necessary first step in routing and responding to requests.

Inside Devolution

Transfer of recordkeeping responsibility
Devolution, in a recordkeeping context, typically refers to the passing of accountability for records and their management from a central authority to subordinate, regional, or successor bodies. The scope of what is devolved depends on the governing arrangement and may include operational control, custody, or policy responsibility, or some combination of these.
Custody and control distinction
Devolution often requires a clear separation between who holds physical or logical custody of records and who retains control over their disposition and access. These may move together or separately, and the arrangement should specify which body exercises which function.
Continuity of recordkeeping obligations
Where responsibilities are devolved, the underlying obligations attaching to records, such as retention, disposition authorization, and access provisions, generally continue to apply. Devolution changes who is accountable rather than removing the obligations themselves, though the applicable requirements depend on jurisdiction and sector.
Records affected by organizational change
Devolution frequently accompanies broader organizational or governmental change, meaning that records created before, during, and after the change may fall under different responsible bodies. Distinguishing these populations is often necessary to preserve the authenticity and integrity of the records as evidence.
Governing instruments and mandates
The terms of a devolution are typically set out in a legal, regulatory, or organizational instrument that defines the scope of what passes, the responsible parties, and any continuing central oversight. The precise form and authority of such instruments vary by jurisdiction.

Common questions

Answers to the questions practitioners most commonly ask about Devolution.

Is devolution the same as delegation of records management responsibilities?
Not quite. While the two concepts overlap, devolution typically refers to the transfer of records management authority and functions to a subordinate or constituent body, often on a more structural or enduring basis, whereas delegation more commonly describes assigning specific tasks or decision-making powers while retaining overall accountability. The precise distinction depends on organizational policy and, in the public sector, on the governing legal framework. It is prudent to document which authorities have been devolved versus delegated to avoid ambiguity over who is answerable for recordkeeping outcomes.
Does devolution mean the originating body no longer bears any responsibility for the records?
Not necessarily. Devolution of operational responsibility does not, in many arrangements, extinguish the originating or overseeing body's residual accountability for governance, compliance, or preservation. Depending on jurisdiction and sector, an overarching body may retain obligations for oversight, policy setting, or ultimate disposition decisions even after day-to-day functions have been devolved. The allocation of continuing responsibility should be defined explicitly rather than assumed.
How should devolved recordkeeping responsibilities be documented?
It is generally advisable to record the scope of devolved authority in a formal instrument such as a policy, terms of reference, or memorandum of understanding. This documentation typically identifies which functions have been transferred, which body holds continuing accountability, the applicable retention and disposition arrangements, and any reporting or oversight expectations. Clear documentation supports auditability and helps demonstrate that recordkeeping controls remain in place after responsibilities shift.
What governance controls help maintain consistency when records functions are devolved across multiple units?
Where functions are devolved to several units, organizations often maintain consistency through shared classification schemes, common retention rules, standardized metadata expectations, and periodic assurance activities. A central policy framework can set minimum requirements while permitting local implementation. Depending on organizational policy, oversight mechanisms such as reporting lines, audits, or compliance reviews help confirm that devolved units apply controls consistently.
How does devolution affect retention and disposition decisions?
Devolution can shift where retention and disposition are applied in practice, but the underlying authority to authorize disposition may remain centralized or subject to oversight, depending on the arrangement and applicable requirements. It is important to clarify whether a devolved body may make disposition decisions independently or must follow centrally approved retention rules and, in some public sector contexts, obtain authorization before destruction or transfer. These arrangements vary by jurisdiction and sector.
What risks should be considered before devolving records management functions?
Common considerations include the risk of inconsistent practice across units, gaps in accountability, loss of visibility over records held locally, and uneven application of retention and security controls. Organizations often assess whether the receiving body has adequate capacity, systems, and competence to sustain recordkeeping obligations. Establishing clear documentation, oversight, and assurance arrangements can help mitigate these risks, though the appropriate approach depends on organizational context and any governing requirements.

Common misconceptions

Devolution transfers ownership of records outright, ending the originating body's involvement.
Devolution commonly transfers responsibility, custody, or control rather than extinguishing all interest of the originating or central body. Depending on the arrangement, the central authority may retain oversight, residual rights, or continuing obligations. Ownership, custody, and control are distinct and should be assessed separately.
Once records are devolved, the original retention and disposition rules no longer apply.
The obligations attaching to records generally persist through devolution; what changes is the identity of the accountable body. In many jurisdictions the receiving body inherits the applicable retention and disposition requirements, and disposition still requires proper authorization. Requirements depend on jurisdiction and sector.
Devolution and destruction or transfer of records are the same event.
Devolution concerns the reassignment of recordkeeping responsibility and is distinct from disposition actions such as destruction, transfer to an archive, or permanent preservation. A devolution may be followed by such actions under the receiving body's authority, but the two should not be conflated.

Best practices

Document, before any devolution takes effect, precisely which records are affected and whether custody, control, or full responsibility is being transferred, since these functions may move independently.
Confirm the continuing retention and disposition obligations that apply to the affected records and ensure the receiving body understands and can meet them; treat obligations as persisting through the change unless a governing instrument clearly provides otherwise.
Maintain metadata and audit information that preserves the authenticity, integrity, and usability of records across the transfer, so that their evidential value is not compromised by the change in responsibility.
Identify and separate record populations created before, during, and after the devolution, and record which body is accountable for each, to avoid ambiguity about custody and control.
Ensure disposition following a devolution is carried out only under proper authorization by the body that holds control, and do not assume devolution itself authorizes destruction or transfer.
Verify the specific legal, regulatory, and organizational requirements applicable to the relevant jurisdiction and sector, as devolution arrangements and their attendant obligations vary and should not be assumed uniform.