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

Delegations of Authority

Also known as: DOA, Delegation of Authority, DOA policy
Simply put

A delegation of authority is a formal statement that gives specific positions in an organization the power to make certain decisions or carry out particular actions. It sets out who is permitted to do what, so that responsibilities are clearly assigned rather than left ambiguous. In many organizations these delegations flow from a governing body, such as a board, down to particular roles or levels of management.

Formal definition

A delegation of authority is a formal, documented instrument that confers on a defined position, rather than a named individual, the authority to execute specified actions and activities within stated limits. It typically forms part of an organization's decision-making framework, establishing a structured chain by which powers held by a governing body or senior officer are assigned to subordinate positions, often with conditions, thresholds, or scope constraints attached. In an information governance context, delegation instruments are themselves records that evidence who was authorized to act, and they may support accountability by documenting the basis on which decisions, including recordkeeping decisions such as approving disposition or applying holds, were validly taken. The precise form, scope, and legal effect of delegations depend on organizational policy and, where relevant, applicable statutory or regulatory requirements, which vary by jurisdiction and sector.

Why it matters

Delegations of authority underpin accountability in recordkeeping and information governance because they establish who was permitted to make a given decision at a given time. When a record shows that a disposition was approved, a legal hold applied, or a set of records transferred, the validity of that action often depends on whether the person acting held the authority to do so. Without clear delegations, decisions may be taken by individuals lacking the mandate, creating ambiguity that can undermine the defensibility of recordkeeping practices and complicate later review or audit.

Because delegation instruments are typically documented and assigned to positions rather than named individuals, they help preserve continuity as people move in and out of roles. This matters for information governance, where accountability must persist over long retention periods and across staff turnover. A delegation framework that flows from a governing body down to management levels provides a traceable basis for demonstrating that authority was properly conferred and exercised, which can be important when an organization must explain or justify its decisions to auditors, regulators, or other oversight bodies.

The delegation instruments themselves are records, and they evidence the authority under which other decisions were made. Where organizations cannot show a valid delegation supporting a significant recordkeeping decision, they may struggle to demonstrate that the decision was authorized. The precise legal effect of a delegation and the requirements for its form depend on organizational policy and, where relevant, on statutory or regulatory frameworks that vary by jurisdiction and sector.

Who it's relevant to

Records managers
Records managers rely on delegations of authority to confirm that significant recordkeeping actions, such as approving disposition, authorizing transfers, or applying holds, are taken by positions with the mandate to do so. Where delegations are clear and documented, records managers can more readily demonstrate that such decisions were validly authorized.
Information governance officers
For those responsible for the broader accountability framework, delegations of authority are a foundational governance instrument. They help establish who is accountable for particular decisions across policy, risk, and recordkeeping domains, and they provide traceable evidence of how authority flows from a governing body through to operational roles.
Compliance and audit leads
Compliance and internal audit functions often examine delegation instruments to assess whether decisions were taken within authorized limits. Because delegations are themselves records, they support review of whether actions fell within stated thresholds or scope constraints, subject to applicable organizational policy and any relevant statutory or regulatory requirements that vary by jurisdiction.
Boards and senior management
Governing bodies and senior officers are typically the source from which delegations flow. They set the decision-making framework and assign specific powers to subordinate positions, retaining responsibility for the structure of the delegation chain even where day-to-day decisions are exercised at lower levels.
Archivists
Archivists have an interest in delegation instruments both as records to be retained and as evidence supporting the authority under which appraisal, transfer, or permanent preservation decisions were made. Retaining delegations over time helps preserve the accountability context for recordkeeping decisions made in the past.

Inside DOA

Delegated authority
The formal grant of power from a position holder to another person or role, enabling that delegate to make decisions or take actions that would otherwise sit with the original authority. In recordkeeping contexts, this often includes the authority to approve retention and disposition actions, sign off on classification decisions, or authorize destruction.
Delegator and delegate
The party conferring the authority and the party receiving it. The delegator typically retains ultimate accountability even where operational responsibility is passed to the delegate, depending on organizational policy and applicable governance frameworks.
Scope and limits
The defined boundaries of what the delegate may and may not do, which may include monetary thresholds, categories of decision, classes of records, or time-bound constraints. Explicit scoping helps distinguish authorized action from action that exceeds the delegation.
Conditions and constraints
Any prerequisites, approvals, or circumstances that must be met before the delegated authority can be exercised, such as requiring a legal hold check before authorizing destruction, or escalation above a set threshold.
Evidentiary record of the delegation
Documentation that captures who was delegated what authority, by whom, when, and under what conditions. Such documentation is itself often a record that should be authentic, reliable, and retained in accordance with organizational policy, since it evidences the legitimacy of subsequent decisions.
Revocation and expiry
The mechanisms by which a delegation ceases to have effect, whether through explicit withdrawal, a set expiry date, or a change in the delegator's or delegate's position. Managing revocation helps prevent authority being exercised after it should have lapsed.

Common questions

Answers to the questions practitioners most commonly ask about DOA.

Is a delegation of authority the same as a records disposition schedule?
No. A delegation of authority identifies who is authorized to make and approve particular decisions or actions within an organization, whereas a records disposition schedule specifies retention periods and disposition outcomes for classes of records. The two are related in that a disposition action such as approving destruction or transfer typically requires an appropriately delegated authority, but the delegation instrument itself governs decision-making power rather than defining what happens to records over their lifecycle. Conflating the two can lead to gaps where a schedule exists but no one is properly authorized to act on it.
Does holding a delegation of authority mean a person can personally destroy records at their discretion?
Not in the sense of unfettered discretion. A delegation typically confers the authority to approve or authorize an action, such as a disposition decision, within defined limits and subject to organizational policy, applicable schedules, and any legal holds that may suspend routine action. The scope, conditions, and reporting expectations attached to the delegation constrain how that authority may be exercised. Depending on organizational policy and jurisdiction, exercising a delegation often requires documentation and may be subject to review or audit, so it should not be understood as personal or informal discretion to destroy records.
How should delegations of authority be documented so they are defensible?
In many organizations, delegations are captured in a written instrument that identifies the delegating officer, the person or role receiving the authority, the specific powers delegated, any limits or conditions, and the effective period. Documenting the delegation as a record in its own right, with attention to authenticity, integrity, and traceability, supports accountability and helps demonstrate that actions were properly authorized. The precise form and formality required typically depend on organizational policy and, in some sectors, on regulatory or legislative expectations.
Should delegations be assigned to named individuals or to roles or positions?
Both approaches are used, and the choice often depends on organizational policy and the stability of the function. Delegating to a role or position can provide continuity when individuals change, while delegating to a named individual can offer clearer personal accountability. Where delegations attach to positions, organizations typically need a reliable way to confirm who currently occupies that position. Whichever approach is chosen, keeping the delegation register current is important so that authority can be traced to an identifiable person at the time an action was taken.
How do delegations of authority interact with legal holds?
A legal hold, where applicable, may suspend routine disposition actions that would otherwise be authorized under a delegation. In such cases the existence of a valid delegation does not permit disposition of records subject to the hold. Organizations often address this by ensuring that those exercising delegated authority are aware of, and check for, any holds before acting, and by building hold status into disposition approval processes. The specific requirements around legal holds depend on jurisdiction and sector.
How often should delegations of authority be reviewed?
Delegations are typically reviewed periodically and also on the occurrence of triggering events, such as organizational restructuring, changes in reporting lines, or the departure of a delegate or delegating officer. Regular review helps ensure that delegations remain current, that lapsed or superseded authorities are removed, and that the register accurately reflects who holds which powers. The appropriate review frequency generally depends on organizational policy, the rate of change within the organization, and any applicable regulatory expectations.

Common misconceptions

Delegating authority transfers accountability away from the delegator.
In many governance frameworks, the delegator retains overall accountability even when the delegate carries out the action. Delegation typically distributes operational responsibility rather than fully discharging the delegator's answerability, though the precise position depends on organizational policy and jurisdiction.
An informal instruction or verbal say-so is sufficient to establish a delegation of authority.
For recordkeeping purposes, a delegation is usually most defensible when documented in an authentic and reliable record capturing its scope, conditions, and timing. Undocumented arrangements can make it difficult to demonstrate that an action, such as authorized destruction, was properly sanctioned.
A delegation of authority is open-ended once granted.
Delegations are typically bounded by defined scope, conditions, and duration, and can be revoked or expire. Treating a delegation as permanent or unlimited risks authority being exercised outside its intended boundaries.

Best practices

Document each delegation in a record that captures the delegator, the delegate, the specific authority conferred, its scope, any conditions, and the effective and expiry dates, so the basis for later decisions can be evidenced.
Define scope and limits explicitly, including any thresholds and the categories of records or decisions covered, to make it clear where authorized action ends and escalation is required.
Attach conditions to sensitive delegations, such as requiring a legal hold or retention check before authorizing destruction, recognizing that specific requirements depend on jurisdiction and sector.
Establish clear revocation and expiry mechanisms and review delegations when roles change, so that authority does not persist after the delegate's position or circumstances alter.
Retain the delegation records themselves in line with organizational retention policy and treat them as evidence of the legitimacy of decisions taken under them.
Periodically review active delegations to confirm they remain current, appropriately scoped, and aligned with the organization's governance framework.