Answers to the questions practitioners most commonly ask about Preservation Obligation.
Is a preservation obligation the same as a retention period?
Not quite, although the two are closely related and often confused. A retention period typically specifies how long a record is to be kept before it becomes eligible for disposition, usually as a matter of routine policy or scheduled recordkeeping. A preservation obligation, by contrast, is a duty to keep and protect specific records that may arise independently of, and sometimes in tension with, the ordinary retention schedule, for example when litigation, investigation, audit, or a legal hold is anticipated or underway. Where such an obligation applies, it commonly suspends or overrides the normal disposition that a retention period would otherwise permit. In practice both may operate on the same records, and organizations generally need to reconcile scheduled retention with any active preservation obligation before authorizing destruction or transfer.
Does meeting a preservation obligation just mean not deleting the records?
Refraining from destruction is a necessary part, but it is generally not sufficient. Beyond preventing disposition, a preservation obligation typically extends to safeguarding the qualities that make the material function as a record, such as its authenticity, reliability, integrity, and usability over the required period. Depending on organizational policy and jurisdiction, this can mean protecting associated metadata and context, preventing alteration, and ensuring the records remain accessible and interpretable for as long as the obligation lasts. Simply leaving files in place while allowing systems, formats, or contextual information to degrade may fall short of what the obligation requires. The precise expectations vary by jurisdiction, sector, and the source of the obligation.
How can an organization identify which records fall under a preservation obligation?
Identification typically begins with understanding the source of the obligation, since it may arise from statute, regulation, contractual terms, a legal hold, or organizational policy, each of which may define scope differently. Many organizations map the obligation against their classification scheme and retention schedule to locate potentially relevant record classes, then apply criteria such as subject matter, date range, custodian, business activity, or system of origin to scope the specific records involved. Because obligations and their triggers depend on jurisdiction and sector, it is common to involve legal, compliance, and records functions in defining scope. Documenting how the scope was determined is often advisable so the basis for inclusion or exclusion can be demonstrated later.
How does a preservation obligation interact with an existing retention and disposition schedule?
In many organizations a preservation obligation acts as an override on routine disposition. When an obligation attaches to records that are also governed by a retention schedule, the scheduled destruction or transfer is typically suspended for the affected records until the obligation is lifted, even if their retention period has otherwise elapsed. Records not covered by the obligation generally continue to follow the normal schedule. Managing this interaction often relies on being able to flag or hold specific records within recordkeeping systems so that automated or manual disposition does not inadvertently affect them. Practices for applying, tracking, and releasing such holds vary by organizational policy and by the capabilities of the systems in use.
What should happen when a preservation obligation ends?
When an obligation is lifted, the affected records generally return to the control of the ordinary retention and disposition regime, subject to any other obligations that may still apply to them. In practice this often involves formally releasing the hold, confirming that no other preservation obligation covers the same records, and then determining whether they are eligible for disposition under the retention schedule, which may include destruction, transfer, or continued retention depending on their scheduled treatment. Because premature release could expose an organization to risk, release decisions are commonly documented and authorized, and any subsequent disposition is typically recorded so the sequence of decisions can be evidenced. The specifics depend on organizational policy and the nature of the original obligation.
What records should an organization keep about its handling of a preservation obligation?
Organizations often maintain evidence of how an obligation was recognized, scoped, applied, monitored, and eventually released, so that their conduct can be demonstrated if questioned. This can include documentation of the trigger or source of the obligation, the criteria used to define its scope, the records or custodians affected, the measures taken to protect authenticity, integrity, and usability, and the authorization and timing of any eventual release and subsequent disposition. Keeping this trail supports accountability and defensibility, particularly where the obligation arose in a legal or regulatory context. What is expected varies by jurisdiction, sector, and organizational policy, and such recordkeeping is itself typically governed by its own retention requirements.