Skip to main content
Category: Disposition and Destruction

Superseded Records

Also known as: Superseded Record
Simply put

A superseded record is one that has been replaced by a newer version or by a more current record covering the same subject. The older record is no longer the operative one, though it may still be kept for a defined period before disposition, depending on organizational policy and applicable requirements. Being superseded describes a record's status; it does not by itself mean the record should be destroyed immediately.

Formal definition

In recordkeeping practice, a superseded record is a record that has been supplanted by a later version, revision, or replacement instance, such that the newer item becomes the authoritative or current record for a given function or subject. Supersession is a status trigger rather than a disposition action in itself: retention schedules frequently express retention periods relative to the point of supersession (for example, retaining a policy for a defined period once it is superseded or obsolete), after which the applicable disposition, which may include destruction, transfer, or continued preservation, is carried out. The specific handling of superseded records depends on jurisdiction, sector, and organizational policy; in some regimes retention schedules may automatically supersede prior coverage unless an exception is notified, and in some data systems supersession has a narrower technical meaning, such as a demographic record whose original identifier has been replaced with a new one (often where the original was a duplicate). Practitioners should distinguish a superseded record (a former authoritative version retained under a defined rule) from a draft, a working copy, and transitory information, and should not treat 'superseded' as equivalent to 'immediately destroyed.'

Why it matters

The status of being superseded is one of the most common triggers used in retention schedules, yet it is frequently misunderstood as an instruction to destroy. Treating supersession as automatic destruction can lead to the premature loss of records that an organization is still obliged to keep, while treating it as no change at all can leave obsolete versions circulating as if they were current. Both errors carry risk: the first may undermine accountability, legal defensibility, or the ability to reconstruct past decisions, and the second may cause staff to rely on outdated policies or superseded information as though it were authoritative.

Retention schedules often express periods relative to the point of supersession rather than a fixed calendar date, for example, retaining a corporate policy for a defined number of years once it is superseded or obsolete. This means the retention clock does not start until a newer version takes effect, and the older version continues to be governed by a defined rule in the interim. Where schedules themselves are revised, prior coverage may in some regimes be automatically superseded unless an exception is notified, as with revisions to general records schedules issued by national archives authorities. Understanding when supersession occurs, and what disposition it eventually leads to, is therefore central to applying retention rules correctly.

Because supersession describes a change in status rather than a disposition action, the eventual outcome depends on jurisdiction, sector, and organizational policy. In some contexts the applicable disposition after supersession is destruction; in others it may be transfer or continued preservation, and guidance may direct staff to consult an archivist before disposing of superseded material. Getting this distinction right helps organizations retain the current authoritative record while managing former versions in a consistent, defensible way.

Who it's relevant to

Records Managers
Records managers design and apply retention schedules that frequently use supersession or obsolescence as the trigger for the retention period. They need to distinguish a superseded record from a draft, working copy, or transitory information, and to ensure that supersession is not mistaken for immediate destruction.
Information Governance Officers
Those responsible for governance frameworks must ensure that policies for handling superseded records are consistent, defensible, and aligned with applicable requirements. This includes tracking revisions to the schedules themselves, since in some regimes a revised schedule may automatically supersede prior coverage unless an exception is notified.
Archivists
Archivists are relevant where the disposition following supersession may include transfer or permanent preservation rather than destruction. Some retention guidance directs staff to consult a regional or responsible archivist before disposing of superseded material, so archivists play a role in identifying records of continuing value.
Compliance and Policy Owners
Owners of corporate policies and other periodically updated documents rely on supersession rules to determine how long former versions must be kept. For example, a schedule may require retaining a policy for a defined number of years once it is superseded or obsolete, meaning the previous version remains subject to a defined rule after replacement.
Health and System Data Administrators
In certain data systems, supersession has a narrower technical meaning, such as a demographic record whose original identifier has been replaced with a new one, often where the original was a duplicate. Administrators of such systems should understand this specific usage and not conflate it with the broader recordkeeping sense of a former authoritative version.

Inside Superseded Records

Superseded Version
A record or document instance that has been replaced by a newer, current version following an update, revision, or amendment. The superseded version reflects a prior state of the information and is no longer the operative or authoritative version for ongoing use, though it may retain evidential value.
Current (Operative) Version
The version that has replaced the superseded record and now serves as the authoritative reference for business activity. Distinguishing the current version from superseded ones is central to maintaining the reliability and usability of records.
Version Relationship and Lineage
The documented linkage between a superseded record and its successor, typically captured through version control, metadata, or audit information. This lineage helps establish the sequence of changes and supports the integrity of the record over time.
Retained Evidential Value
The continuing significance a superseded record may hold as evidence of a past decision, state, or activity, even after it ceases to be the operative version. Whether such value warrants ongoing retention typically depends on organizational policy, legal or regulatory requirements, and the applicable retention schedule.
Disposition Status
The lifecycle position of a superseded record, which is not automatically destruction. Depending on the retention schedule and any applicable legal holds, a superseded record may be retained for a defined period, transferred, preserved, or destroyed once no longer required.

Common questions

Answers to the questions practitioners most commonly ask about Superseded Records.

Does a record becoming superseded mean it should be destroyed?
No. Superseding a record changes its status relative to a newer version; it does not by itself authorize destruction. A superseded record remains subject to the applicable retention schedule and may need to be kept as evidence of prior activity, a decision made under the earlier version, or the state of affairs at a given time. Destruction should occur only when the retention period has lapsed and disposition has been properly authorized, and never while a legal hold or comparable obligation applies. Depending on organizational policy and jurisdiction, some superseded records are retained for extended periods or preserved permanently.
Is a superseded record the same as an obsolete or transitory document?
Not necessarily. A superseded record is an authoritative record that has been replaced by a newer version but which typically retains value as evidence of what was in force previously. Transitory information, by contrast, has only short-term or no ongoing recordkeeping value and often falls outside formal retention requirements. Treating superseded records as merely obsolete risks premature loss of material that may still be required to demonstrate authenticity, reliability, and the integrity of a decision trail. The distinction depends on the record's evidential role and the applicable retention policy.
How should the point at which a record becomes superseded be documented?
In many recordkeeping environments, the transition is captured through version control and metadata that record when a new version took effect, which prior version it replaced, and, where relevant, who authorized the change. Maintaining a clear link between the current and superseded versions supports auditability and helps demonstrate the integrity of the record over time. The specific mechanisms depend on the systems and policies in place, and organizations often define these rules in their records management procedures.
Should superseded records be retained in the live system or moved elsewhere?
Practice varies by organization and system capability. Some systems retain superseded versions in place with clear status labelling, while others transfer them to a controlled repository so that the current authoritative version is readily distinguishable from earlier ones. The key considerations are typically that the current version can be reliably identified, that superseded versions remain accessible for as long as retention requires, and that their authenticity and usability are preserved. The appropriate approach depends on organizational policy and the risks involved.
What retention period applies to a superseded record?
The retention period is generally determined by the applicable retention schedule for the record class rather than by the fact of being superseded. In some cases retention is calculated from the point of supersession, so that the clock begins when a newer version takes effect. Statutory and regulatory requirements differ across jurisdictions and sectors, so organizations typically map superseded records to their retention rules and confirm whether any specific obligation governs earlier versions.
How should legal holds be handled for superseded records?
When a legal hold or comparable obligation applies, superseded records within its scope should be preserved regardless of their status and should not be destroyed even if their retention period would otherwise have lapsed. Because a superseded version may capture the state of affairs relevant to a dispute or investigation, organizations often ensure that hold processes explicitly cover prior versions. The precise obligations depend on jurisdiction, sector, and the terms of the hold.

Common misconceptions

A superseded record can be deleted immediately once a newer version exists.
Being superseded governs which version is operative, not whether the earlier version may be destroyed. Superseded records often need to be retained to satisfy retention schedules, legal holds, or evidential requirements, which vary by jurisdiction, sector, and organizational policy. Disposition should follow the applicable retention rules rather than the act of supersession alone.
A superseded record is the same as a draft or transitory information.
A superseded record was typically an authoritative or operative version at some point, whereas a draft is a working state that never became operative and transitory information has no ongoing value. A superseded record may still carry authenticity, reliability, and evidential weight for the period it was in effect, so it should not be treated as disposable working material by default.
Superseding a record erases or overwrites the earlier version.
Sound recordkeeping generally maintains the superseded version alongside the current one, preserving the record's integrity and the ability to demonstrate what the information stated at a given time. Overwriting can compromise authenticity and auditability; version control is intended to add a successor, not obliterate the predecessor.

Best practices

Apply version control that clearly identifies the current operative version and preserves the relationship between it and its superseded predecessors.
Capture metadata recording when and why a record was superseded, and by which successor version, to support authenticity, integrity, and traceable lineage.
Manage the disposition of superseded records through the applicable retention schedule rather than destroying them automatically when a newer version is created.
Check for and honor any legal holds before disposing of superseded records, recognizing that retention obligations depend on jurisdiction, sector, and organizational policy.
Distinguish superseded records from drafts and transitory information so that each is handled according to its actual status and evidential value.
Retain superseded versions where they hold continuing evidential value, ensuring they remain usable and their integrity is protected for as long as they are required.