Category: Retention and Scheduling

Time-Based Retention

Also known as: Time-Based Retention Period, Time-Driven Retention

Simply put

Time-based retention is an approach to keeping records for a fixed period measured in time, such as 5, 10, or 20 years, after which they become eligible for disposition. The record is held and typically protected from deletion or alteration until the specified period elapses. It contrasts with retention that is triggered by the occurrence of an event rather than the passage of a set span of time.

Formal definition

Time-based retention is a retention model in which the retention period for a record or class of records is defined as a fixed duration counted from a determinable start point, commonly the date of creation, capture, or another calculable reference date. During this period, the record is typically held in a manner that prevents deletion and, in many systems, in-place modification, thereby supporting the integrity and usability required of an authoritative record. On expiry of the defined duration, the record becomes eligible for a disposition action, which depending on organizational policy and the applicable retention schedule may include destruction, transfer, or continued preservation rather than automatic deletion. Time-based retention is distinguished from event-based (or events-based) retention, where eligibility for disposition depends on the occurrence of a triggering event whose timing is not fixed in advance. The specific durations and the lawfulness of any subsequent disposition depend on jurisdiction, sector, and organizational requirements, which fall outside the scope of this definition.

Why it matters

Time-based retention provides one of the most predictable and administrable models for controlling records across their lifecycle. Because eligibility for disposition is tied to a fixed duration counted from a determinable start point, organizations can calculate in advance when a record or class of records will become eligible for a disposition action. This predictability supports defensible recordkeeping: it allows retention schedules to be applied consistently, reduces reliance on manual judgment, and creates a clear audit trail for why a record was held and when it became eligible for further action.

The model also has clear limits that professionals should keep in view. A fixed time period works well where the appropriate holding duration is knowable at the point of creation or capture, but it is less suited to records whose retention should depend on an event whose timing cannot be fixed in advance, such as the closure of a matter or the end of a relationship. As industry commentary has noted, retention becomes more complex when disposition eligibility cannot be reduced to a simple elapsed span of time, which is where event-based retention is often applied instead. Choosing time-based retention for records that are really event-driven can lead to records being disposed of too early or held longer than necessary.

It is important not to conflate expiry of a time-based retention period with automatic deletion. On expiry, a record becomes eligible for a disposition action, which depending on organizational policy and the applicable retention schedule may include destruction, transfer, or continued preservation. Treating expiry as an automatic trigger for deletion can undermine both compliance and preservation obligations, and the lawfulness of any subsequent disposition depends on jurisdiction, sector, and organizational requirements.

Who it's relevant to

Records Managers

Records managers apply time-based retention when designing and maintaining retention schedules, particularly for record classes where the appropriate holding duration is knowable at creation or capture. They are responsible for selecting the correct start point, distinguishing time-based classes from event-based ones, and ensuring that expiry triggers a review or disposition action consistent with the schedule rather than defaulting to deletion.

Information Governance Officers

Those with broader accountability for information governance rely on time-based retention as one instrument within a wider framework spanning policy, risk, privacy, and value. They should ensure that fixed-duration retention aligns with organizational policy and that expiry and subsequent disposition decisions remain defensible, recognizing that the lawfulness of any disposition depends on jurisdiction and sector.

Compliance and Legal Teams

Compliance and legal staff are concerned with whether time-based periods are consistent with applicable obligations, which vary by jurisdiction and sector, and with the interaction between scheduled retention and legal holds. They need assurance that records held under a time-based period are protected from deletion and in-place modification during that period, and that expiry does not override any hold or preservation requirement.

Systems and Content Management Administrators

Administrators configuring records or content management systems implement time-based retention as holds that prevent deletion and, in many systems, in-place updates to content until the specified time elapses. They translate schedule durations and start points into system configuration and ensure that expiry surfaces records for the correct disposition action rather than performing unintended automatic deletion.

Inside Time-Based Retention

Retention Trigger

The defined event or point in time from which a retention period is calculated. For time-based retention this is typically a fixed or predictable temporal marker, such as the date a record is created, captured, or finalized, rather than an open-ended business or lifecycle event.

Retention Period

The specified length of time a record is required or expected to be kept, measured from the trigger. The period is generally derived from statutory, regulatory, contractual, operational, or historical requirements, which vary by jurisdiction, sector, and record type.

Calculation Basis

The rule set that converts the trigger and period into a due date, for example counting a set number of years from the end of the calendar or financial year in which the record was created. The basis should be documented so that the resulting date is consistent and defensible.

Disposition Action

The action to be applied once the retention period elapses. Disposition is not synonymous with destruction; depending on organizational policy and any applicable requirements it may involve secure destruction, transfer to an archive, or permanent preservation.

Retention Schedule Entry

The documented instrument, typically part of a retention schedule, that binds a record class to its trigger, period, calculation basis, and disposition action, providing the authority for consistent and auditable treatment of records over time.

Suspension Mechanism

A control, such as a legal hold, that can override or pause the normal expiry of a time-based period when circumstances (for example litigation, investigation, or regulatory inquiry) require records to be retained beyond their scheduled date. Requirements for such holds depend on jurisdiction.

Common questions

Answers to the questions practitioners most commonly ask about Time-Based Retention.

Does time-based retention mean records must be destroyed the moment the retention period elapses?

No. The expiry of a time-based retention period typically signals that a record has become eligible for disposition, not that destruction is automatic or mandatory. Disposition may involve transfer, permanent preservation, or destruction, depending on the applicable retention schedule and organizational policy. In many cases a review or approval step precedes any destructive action, and overriding factors such as legal holds can suspend disposition entirely. The elapsed period establishes eligibility rather than compelling immediate deletion.

Is time-based retention the same as archiving a record?

Not necessarily. Time-based retention is a method of determining how long a record is kept, usually measured from a defined trigger such as creation, closure, or last action. Archiving refers to preserving records, often those with continuing value, and is one possible disposition outcome. A record may reach the end of its time-based retention period and then be destroyed, transferred, or archived, so retention and archiving describe different stages and decisions in the lifecycle rather than equivalent concepts.

What events can serve as the trigger for a time-based retention period?

Time-based retention periods are typically calculated from a defined starting point, which may be the date of creation, the date a file or matter is closed, the date of last action, or another event specified in the retention schedule. The choice of trigger affects when disposition eligibility is reached, so it should be documented clearly and applied consistently. The appropriate trigger often depends on the record type, business context, and any applicable jurisdictional or sector requirements.

How should time-based retention periods be documented and applied across a records system?

Time-based retention periods are commonly recorded in a retention schedule that associates record classes with their applicable periods and triggers. Consistent application often relies on accurate classification at capture, reliable metadata to record the relevant trigger date, and a mechanism to calculate eligibility. Depending on organizational policy and system capabilities, the calculation and flagging of eligible records may be automated, though decisions about the resulting disposition frequently remain subject to review.

How do legal holds interact with time-based retention?

A legal hold typically suspends the normal application of a retention period, preventing disposition of affected records even if their time-based period has elapsed. Records under hold are generally retained until the hold is lifted, after which normal retention and disposition processes may resume. Because the scope and triggers for legal holds vary by jurisdiction and matter, organizations often need a defined process to identify, apply, and release holds so that time-based retention does not inadvertently override preservation obligations.

What are the risks of relying on time-based retention without periodic review?

Without periodic review, time-based retention rules may become outdated as business needs, systems, or applicable requirements change, and inaccurate trigger dates or classification errors can cause records to be retained too long or become eligible for disposition prematurely. Regular review of the retention schedule, verification of trigger metadata, and controls around disposition approval can help mitigate these risks. The appropriate frequency and rigor of review generally depend on organizational policy and the sensitivity of the records involved.

Common misconceptions

Time-based retention means a record is automatically destroyed as soon as its period expires.

Expiry of a time-based period typically makes a record eligible for disposition, not automatically destroyed. The scheduled disposition action may be destruction, transfer, or permanent preservation, and any active legal hold or other suspension generally takes precedence over the calculated date.

Time-based retention is interchangeable with event-based retention.

Time-based retention calculates the disposition date from a fixed or predictable temporal marker such as creation date, whereas event-based retention depends on the occurrence of a business event whose timing may be uncertain. Many schedules combine both, and the distinction matters for how and when records become eligible for disposition.

Once a retention period is set, it is fixed and universal.

Retention periods are typically derived from statutory, regulatory, contractual, and operational requirements that differ across jurisdictions and sectors and can change over time. Periods should be reviewed periodically and are subject to override by holds, so treating any single period as permanent or universal is generally unsafe.

Best practices

Document the trigger, period, calculation basis, and disposition action for each record class in the retention schedule so that resulting due dates are consistent, transparent, and defensible.

Define the calculation basis explicitly, including whether periods run from the record date or from the end of the relevant calendar or financial year, to avoid ambiguity in how dates are computed.

Ensure that scheduled disposition dates can be suspended by legal holds or equivalent mechanisms, and confirm that such holds take precedence over automated expiry, recognizing that hold requirements depend on jurisdiction.

Treat expiry as a point of eligibility for a defined disposition action rather than an automatic trigger for destruction, and apply the correct action, whether destruction, transfer, or permanent preservation.

Review retention periods periodically against current statutory, regulatory, and operational requirements, since these can change and vary by jurisdiction and sector.

Maintain auditable records of retention decisions, calculated dates, holds, and completed disposition actions to support accountability and demonstrate defensible practice.