Retention is a decision, not a folder name

Abstract

Federal records schedules assign retention periods and disposition rules to categories of records, and their structure offers a useful model for private offices. They are not binding on a private company, and they do not resolve jurisdiction-specific obligations. This review explains how the schedules work, what they can and cannot tell a board office, and how to build a local retention rule for minutes, resolutions, packs, and working papers [1][2][3].

Methodology

The review uses public records management guidance and general records schedules as a design reference, not as legal advice. It distinguishes the official record from convenience copies and working papers, and it defines retention by a record type plus a trigger event. The method includes a hold check, an approval path, and a retrieval test. Local legal and tax obligations must be confirmed separately [1][2][4].

The question and why board records matter

Board records carry decisions, authority, and accountability, yet many private offices keep them in a folder named after the year. The question is not whether to keep board minutes, but for how long and in what form. Public records schedules offer a structured way to think about the answer. They are not binding on a private company, but they show how retention can be reasoned rather than guessed [1][2]. The answer matters because board records are requested by auditors, directors, investors, and sometimes courts. A missing minute can be harder to explain than an old one. A retention rule that is applied consistently is easier to defend than a folder that grew by habit [3][4].

Write the retention decision at the level of the record type, not the individual document. That keeps the rule stable when the format or the storage system changes. A minute remains a minute whether it is in a binder or a collaboration platform. The rule should follow the record, not the tool.

How federal records schedules define retention

Federal records schedules assign a retention period and a disposition instruction to a category of records. Some records are temporary and can be destroyed after a set period, while others are permanent and transfer to the National Archives. The schedule also defines what counts as the official record, which may differ from working papers [1][2]. The structure is useful because it separates the record type from the format. A minute is a minute whether it is paper or digital. The schedule also distinguishes the official record from convenience copies, which can usually be destroyed sooner. That distinction is directly transferable to a private office [1][3].

A schedule also says who may authorize disposal and what evidence must be kept. Those procedural details are as important as the period itself. Without an approval path, a purge becomes an individual judgement. With one, the office can show that disposal was controlled.

What general schedules can and cannot tell a private office

General records schedules cover common administrative records, such as meeting files, routine correspondence, and administrative housekeeping. They can suggest a reasonable period for similar material in a private office. They cannot establish a legal obligation for that office, and they may not reflect industry-specific rules [1][2]. A private company may also have contractual, tax, or regulatory obligations that are longer than a general schedule. The schedule is a starting point for a local policy, not the policy itself. Legal review should confirm the periods that apply to the company's jurisdiction and sector [3][4].

When a general schedule is used as a reference, record the specific schedule and the reasoning in the local policy. That note helps a later reviewer see why a period was chosen. It also makes the policy easier to revise when the reference changes. Borrow the structure, not the authority.

The role of the board secretary

The board secretary or the person performing that function usually owns the official minute and the resolution register. The support desk may maintain the files, but the secretary should confirm what is official. That separation prevents the desk from deciding which version of a minute is authoritative [1][2]. The secretary should also define the packet record. Is the final board pack retained, or only the minutes? Are committee papers included? The answers affect both retention and access. Write them down so a new assistant does not have to infer the practice from old folders [3][4].

The secretary should also confirm who can access the official record and how a correction is made. A minute that can be edited without a trace is not a reliable record. Define the correction process and keep the prior version. Access and integrity belong together.

Building a local retention schedule

List the board record types: minutes, resolutions, agendas, board packs, committee reports, and working papers. For each, define the official version, the retention period, the trigger, and the owner. Add the storage location and the access rule. Keep the schedule short enough to use [2][3]. Choose triggers that are easy to observe, such as the end of the financial year or the date of the meeting. Avoid vague instructions to keep records permanently without saying who can authorize disposal. The schedule should also cover electronic copies and collaboration tools [1][4].

Include the location of the official record and the backup in the schedule. A retention period is not useful if nobody can find the document after the period begins. Test the location with a real retrieval request. The schedule should describe a working system, not a theoretical one.

Applying holds and exceptions

A legal hold overrides the normal retention schedule. The office needs a way to flag affected records and pause disposal. The hold list should be maintained by the person with legal authority, not by the desk alone. The desk should check the list before any purge [1][2]. Other exceptions include investigations, audits, and director requests. Record the exception and its expected end date. When the exception ends, return the records to the normal schedule rather than leaving them in a permanent hold. A hold that is never released becomes a silent archive [3][4].

Document who placed the hold, when it began, and what it covers. A hold that is described only in an email is easy to miss during a purge. Review the list before each cycle and record the review. Release the hold in writing when the matter closes.

Testing the schedule before an audit

Pick a recent board cycle and reconstruct the record from the schedule. Can you find the official minute, the resolutions, and the final pack? Does the retention rule tell you what to keep and what to discard? If the test takes more than a few minutes, the schedule or the filing needs work [2][4]. Test a disposal decision as well. Choose a record past its retention period and confirm that the hold check and the approval path work. Document the test result and fix the gaps before an auditor asks. A schedule that has never been exercised is only a document [1][3].

Keep the test record with the schedule so the next reviewer can see what was checked. Note the date, the sample, and any gaps found. A test that is repeated annually becomes a control rather than a one-off exercise. The result should lead to one or two specific fixes.

Limits and responsible use

This review cannot determine the legal retention period for a specific company or jurisdiction. It cannot guarantee that a schedule will satisfy a regulator or a court. It also cannot resolve privilege questions, which require counsel. The method is a way to organize the question [1][3]. Apply the schedule consistently and review it annually. Keep the source of each period visible so a later reader can see why it was chosen. Where the law is unclear, seek qualified advice rather than inventing a rule. Responsible retention protects the organization and the people whose information it holds [2][4].

Finally, distinguish a retention policy from a storage policy. Retention says how long a record must be kept, while storage says where it lives and who can access it. Both matter, but they answer different questions. Keeping them separate makes each easier to review.

Key findings

  • Federal records schedules assign retention by record type and disposition, not by folder location [1][2].
  • General schedules are a design reference for private offices, not a binding legal rule [1][3].
  • The board secretary should define the official minute, resolution register, and packet record [1][2].
  • A local schedule needs a record type, official version, trigger, period, owner, and access rule [2][4].
  • Test retrieval and disposal, and document hold checks before relying on the schedule [1][3].

Sources

  1. General Records Schedules, U.S. National Archives and Records Administration
  2. Records Management, U.S. National Archives and Records Administration
  3. Standards for Internal Control in the Federal Government, U.S. Government Accountability Office
  4. The NIST Cybersecurity Framework, National Institute of Standards and Technology

Return to the Research Content library