What a defensible retention schedule must separate

Abstract

Executive offices create records that range from routine travel confirmations to board decisions and sensitive personnel notes. This article reviews federal records management guidance and the legal hold concept, then proposes a bounded schedule that an office can maintain. It distinguishes retention from destruction and explains why a hold overrides the normal timetable. The method is an operating aid, not legal advice, and high-risk records require qualified review [1][2][3].

Methodology

The review draws on National Archives records management guidance, the federal records regulations in 36 CFR Part 1226, and the Federal Rules of Civil Procedure on preserving electronically stored information. It treats retention as a documented business decision and a legal hold as a separate obligation that suspends disposal. The article does not create a jurisdiction-specific schedule and cannot certify compliance. Applicable laws, contracts, and litigation requirements need qualified counsel [1][2][3].

Why retention needs a schedule

Without a schedule, an office keeps everything or deletes by convenience. Both approaches create risk. Keeping everything increases storage cost, slows searches, and preserves information that may later be misread out of context. Deleting without a rule can remove a record that an audit or a dispute requires. A schedule replaces habit with a documented decision [1][2].

The schedule should cover records regardless of format. A signed contract, an email approval, a calendar entry, and a paper note can all be records if they document a decision or a transaction. The office should describe the record series rather than the file type. That approach survives changes in software and devices [1][3].

Retention is not the same as backup. A backup may restore a system after a failure, but it is not a records archive and should not be searched as one. The schedule should identify the authoritative copy and the system that holds it. Confusing backups with records leads to both gaps and unnecessary preservation [2][3].

Identify the record series the office owns

Start with the work the executive office actually performs. Include board and committee materials, executive correspondence, contracts and approvals, travel and expense records, personnel notes, and facilities or vendor records. Add the systems where each series lives, such as email, a document library, or a finance platform. The inventory does not need to be exhaustive to be useful [1][2].

Assign an owner to each series and ask the owner to describe the business purpose. A record without a purpose is a candidate for earlier disposal. A record with a legal or regulatory driver needs a retention period that reflects that driver. The owner should confirm the period rather than leaving it to the support desk [2][3].

Separate official records from convenience copies. A printed agenda, a forwarded email, or a downloaded report may be a duplicate of an authoritative record. The schedule can treat duplicates differently if the office confirms which copy is official. That distinction prevents the same information from being retained in several places with different rules [1][3].

Include records held by the executive's direct reports where the office is responsible for the file. A chief of staff may keep planning documents, and an assistant may keep scheduling records that document decisions. The schedule should identify those custodians rather than assuming that all records sit in one system. Responsibility follows the record, not the job title.

Set retention periods and disposal methods

Use the organisation's approved retention periods where they exist. Where they do not, work with legal or records management to set a period based on business need, statutory requirements, and risk. Record the basis for the period in plain language. A period without a reason is difficult to defend and easy to change without thought [1][2].

Define how each series will be disposed of at the end of its period. Digital records may be deleted from the authoritative system, while paper may require secure destruction. Confirm that backups and shared copies are handled consistently. A disposal method that leaves copies behind does not achieve the schedule's purpose [2][3].

Build a pause before irreversible deletion. A short review step can confirm that no hold, audit, or open matter applies. The pause should be documented rather than relying on someone remembering. It is the control that prevents an automatic deletion from becoming a serious error [1][3].

A legal hold is an instruction to preserve potentially relevant information when litigation, an investigation, or another legal matter is reasonably anticipated. It suspends the normal disposal schedule for the covered records. The hold may apply to a person, a topic, a date range, or a system. The office should follow the instruction from legal counsel rather than deciding the scope itself [3].

A hold is not limited to the records a person thinks are important. It can cover drafts, emails, calendar entries, messages, and notes that relate to the matter. The office should preserve the original format and avoid editing or deleting metadata. If a record is in a personal device or account, legal counsel should decide how to collect it [2][3].

When a hold is issued, confirm that automated deletion is suspended for the covered systems. Tell the people who manage records what they must stop doing. Keep a record of the hold notice and the steps taken. A hold that exists only in a legal file may not reach the system that deletes the record [3].

Test the disposal process with a sample before applying it broadly. Choose a low-risk record series and walk through the review, approval, and deletion steps. Confirm that the authoritative copy is removed and that no unintended copy remains. A small test exposes gaps that a written procedure can hide.

Document the schedule and train the office

Write the schedule in a table that lists the series, the owner, the authoritative system, the retention period, the disposal method, and the review date. Keep it short enough to use and specific enough to act on. Store it where the people who manage records can find it. A schedule that lives only with counsel will not guide daily work [1][2].

Train the executive office on the schedule at onboarding and whenever a major system changes. Explain the difference between a record, a duplicate, and a convenience copy. Give people a way to ask about a record they are unsure about. The cost of a question is much lower than the cost of an accidental deletion [2][3].

Assign one owner to review the schedule annually and after a reorganisation or system migration. Check that the series still exist, the owners are current, and the periods still reflect the business and legal context. Update the schedule rather than adding exceptions in side conversations. A maintained schedule is a control, not a shelf document [1][3].

Ask counsel how the organisation wants to handle a hold that overlaps with a scheduled disposal. The office needs a clear instruction about who can pause a deletion and how quickly. A hold that arrives after the record is gone cannot be repaired. The process should prioritize preservation over tidiness.

Build a simple process for receiving a hold notice, confirming the scope, and communicating it to the people who manage the records. Include a contact for questions and a deadline for confirmation. The process should work outside normal hours if the matter is urgent. A hold that waits for the next business day may be too late [3].

During an audit or investigation, preserve the request and the records provided. Do not reconstruct a record from memory or create a new document that appears to be contemporaneous. If a record is missing, say so and explain what was searched. Honest documentation is more defensible than a fabricated completeness [1][3].

At the end of a hold, legal counsel should confirm in writing that the hold is released. The office can then return the record to the normal schedule. Do not resume deletion automatically without that confirmation. The release is part of the record and should be retained with the hold file [3].

Keep the schedule and the hold log in a location that survives staff turnover. A new assistant should be able to find the current version and the name of the records owner. Review the access list when someone leaves. Continuity is part of a defensible records program.

This article describes a general operating method and does not create a legal retention schedule. Retention periods vary by jurisdiction, industry, entity type, and the nature of the record. A schedule that is appropriate for one office may be wrong for another. Qualified counsel or a records professional should review the high-risk series [1][2].

A legal hold can arise from many kinds of matters, including employment disputes, contract claims, regulatory inquiries, and investigations. The office should not decide whether a matter is serious enough to warrant a hold. That judgment belongs to counsel. The office's role is to preserve, report, and follow instructions [2][3].

The schedule should also account for privacy and access. Some records contain personal information that should be restricted even while retained. Retention does not imply open access. Use role-based permissions and review them when people change roles. A defensible schedule protects confidentiality as well as completeness [1][3].

Key findings

  • A retention schedule documents what to keep, for how long, and how to dispose of it [1][2].
  • Records should be described as series with an owner and an authoritative system [1].
  • A legal hold suspends normal disposal for potentially relevant information [3].
  • Automated deletion must be paused when a hold applies and confirmed with counsel [3].
  • Retention periods and high-risk records require qualified legal or records review [1][2].

Sources

  1. Records Management, U.S. National Archives and Records Administration
  2. 36 CFR Part 1226: Implementing Disposition of Federal Records, U.S. National Archives and Records Administration
  3. Federal Rules of Civil Procedure, Administrative Office of the U.S. Courts
  4. Guide to Protecting the Confidentiality of Personally Identifiable Information (SP 800-122), National Institute of Standards and Technology

Return to the Research Content library