The statement that is not true is almost always the absolutist one: a sentence claiming records must be kept forever, destroyed at a fixed age regardless of content, or purged once they're scanned. Effective programs run on retention schedules tied to legal, fiscal, and operational need, and any statement that removes that condition is the false one. The rest of this article names the specific traps exam writers and policy reviewers bury in multiple-choice sets, and why each fails.
Why the Fill-In-the-Blank on Records Management Trips Up Experienced Staff
Certification exams and internal audits love this phrasing because the wrong answers sound like best practice. A statement like "all records should be retained permanently to avoid legal risk" reads as cautious. It's false, and it's expensive. The U.S. National Archives and Records Administration's records management regulations, 36 CFR Part 1220, require agencies to maintain records only for the time needed for business use, then dispose of them under approved schedules.
The core distinction sits between "records" and "non-records," and between "retention" and "permanent preservation." A records management program covers the full lifecycle: creation, distribution, use, maintenance, and disposition. Any statement that skips disposition isn't describing the program at all.
You'll also see false statements built on partial truths. "Electronic records don't need to be scheduled because backups exist" is false on two counts. Backups protect against loss, not against retention obligations, and the Federal Records Act treats electronic records as records regardless of storage medium. NARA's 36 CFR Part 1236 sets specific requirements for electronic records management that mirror paper.
Recognize the pattern and the exam gets easier. True statements carry conditions: "unless legal hold applies," "per the approved schedule," "based on business need." False statements are unqualified. They use "all," "always," "never," or "immediately," and they usually promise a benefit the program can't deliver.
That rule of thumb resolves most disputed items. When two options both sound reasonable, pick the one that names a condition or a controlling authority, and flag the one that asserts a blanket rule. The blanket rule is your answer. If you're writing policy rather than taking a test, the same filter catches language that will cause trouble with auditors later.
The Myth That Everything Should Be Kept Forever Costs Real Money
Permanent retention of everything is the single most common false statement in training materials, and the cost is measurable. A 2023 survey by the information management firm Iron Mountain put the average cost of storing a physical file at roughly $0.35 per file per month across surveyed North American organizations. Run the math on 500,000 files and you're looking at about $175,000 a month, or $2.1 million a year, for records a schedule might have cleared in year three.
Defenders of keep-everything argue storage is cheap now. Cloud tiers are cheap per gigabyte, but the number that matters is cost per record under management. That figure includes indexing, legal review during discovery, privacy compliance, and staff time to answer requests against a bloated repository. Iron Mountain's own guidance separates storage cost from management cost, and the second dwarfs the first as volume grows.
Storage also carries legal exposure. Courts in the United States have sanctioned organizations under Federal Rule of Civil Procedure 37(e) when retained records were poorly managed and relevant material became unrecoverable. Keeping data without governing it doesn't protect you, because you still have to produce it and you still have to find it.
Three Statements About Legal Holds That Are Always False
Legal holds suspend disposition, so any statement that treats a hold as optional or automatic is false. Under the Federal Rules of Civil Procedure, once litigation is reasonably anticipated, the duty to preserve attaches. A program that destroys on schedule without checking for holds isn't compliant, it's spoliation waiting to happen.
Watch for statements that limit holds to paper. "A legal hold only applies to documents in the central file room" is false. Holds reach email, chat logs, mobile device data, and backup media when those hold relevant information. The Sedona Conference Commentary on Legal Holds covers this reach directly and is the reference most U.S. practitioners cite.
Another false variant claims a hold ends when the case closes. Holds are released by an authorized person after the matter concludes and any appeal window passes. An automatic release on a court date has no legal basis, and systems that auto-expire holds without human review create exactly the record-loss scenario holds exist to prevent.
The fourth trap is subtler: "A hold means records must be preserved forever." False in the other direction. Holds are temporary by design. Once released, the retention schedule resumes, including any backlog the hold accumulated. Programs that treat held records as permanently exempt from disposition have quietly turned a legal tool into the retention problem they were trying to avoid.
Retention Schedules Follow Legal, Fiscal, and Operational Need — Not a Single Clock
No universal retention period exists, and any statement asserting one is false. The General Records Schedules published by NARA show this at scale. GRS 2.2 covers employee compensation and benefits records with retention running from three years to 56 years depending on the record series. GRS 1.1 covers financial transaction records at six years after final payment. One number cannot govern both.
The table below contrasts how the three drivers usually resolve, using published federal schedules as the reference point.
| Record type | Primary driver | Retention under NARA GRS | What triggers the clock |
|---|---|---|---|
| Employee compensation records | Fiscal and legal | 3 to 56 years by series | Separation, final payment, or benefit maturity |
| Financial transaction records | Fiscal | 6 years after final payment | Final payment date |
| Routine correspondence | Operational | 2 years or less | File closure |
| Grant case files | Legal and fiscal | 3 years after final action | Closeout and final report |
| Executive-level policy records | Legal and historical | Permanent | Never destroyed |
Private-sector schedules follow the same logic under different authorities. The Internal Revenue Service's general retention guidance for businesses points to employment tax records keeping for at least four years after the tax is due or paid, whichever is later. State statutes add layers; California's records retention requirements for employers, for instance, run three years for payroll records under Labor Code Section 1174.
The failure case sits in organizations that copy a peer's schedule without checking jurisdiction. A retention period lawful in one state can violate another state's statute, and the error usually surfaces only during litigation or audit. Legal counsel signs off on schedules for a reason, and that sign-off should be dated and revisited when regulations change.
Disposition Is Not Destruction, and the Difference Changes the Correct Answer
Statements that equate disposition with destruction are false. Disposition is the final stage of the lifecycle, and it has three outcomes: destruction, transfer to an archive, and permanent preservation in place. A program statement saying "disposition means shredding" misses two-thirds of the definition and would, applied literally, destroy permanent records.
NARA's records management training materials describe disposition as the authorized action at the end of a retention period. Authorization comes from the schedule. Without a schedule, there is no disposition, only unauthorized destruction. The distinction matters because inadvertent destruction of unscheduled records is a reportable event for federal agencies and a spoliation risk for anyone in litigation.
Transfer is the outcome people forget. Records with historical value go to an archival repository rather than the shredder. The practical test is whether the schedule says "permanent" or gives a transfer instruction. If it says either, destruction is off the table and any statement implying otherwise is false.
Watch for statements coupling disposition to media type. "Paper records get disposed, electronic records get archived" is false as a general rule. Media type affects method, not eligibility. The schedule governs the record, and the record's format determines whether destruction means shredding, degaussing, or cryptographic erasure. Physical shredding vendors in the U.S. often certify under standards like NAID AAA, but certification proves method, not legal authority to destroy.
Scanned Files, Email, and Collaboration Platforms: The Medium Gets Three Statements Wrong
Scanning and then destroying originals isn't automatically fine, so any statement making it automatic is false. The U.S. Internal Revenue Service accepts electronic records as originals under Revenue Procedure 97-22 only when the imaging system meets specific requirements for accuracy, indexing, and retrievability. Organizations outside the U.S. should check their own tax authority's imaging rules before shredding paper.
Email is a record when it documents a business transaction, and statements treating it as exempt are false. NARA's guidance on managing email under the Capstone approach, codified in 36 CFR Part 1236, treats email accounts of senior officials as permanent. Statements like "email is corralled by IT, so records staff can ignore it" leave an entire record series ungoverned.
Collaboration platforms create the newest version of the false statement. "Chat messages aren't records" is false when chat carries decisions, approvals, or commitments. The retention question for Teams, Slack, or similar tools is the same as for email: does the content document organizational activity? If yes, it needs a schedule, and archiving tools that capture chat without classifying it produce a repository nobody can dispose of.
The edge case worth knowing is the auto-delete policy. Platforms default to short retention windows, and a program statement claiming those defaults satisfy records obligations is false unless the defaults were mapped to a schedule and approved by counsel. Default settings are technical configuration, and configuration isn't a retention schedule.
A Seven-Item Checklist Auditors Use to Spot a False Records Statement
Evaluators and exam writers run the same short test on each candidate statement. Telling them about it helps every reader distinguish a compliant claim from a false one. The check below takes under two minutes per statement.
1: Find the qualifier. True statements carry conditions such as "per schedule" or "unless on hold." No qualifier means the statement fails this check. 2: Look for an authority. A retention claim without a named schedule, regulation, or statute is an assertion, not a fact. 3: Test the lifecycle. A statement covering only storage, or only creation, is incomplete and effectively false. 4: Check the medium neutrality. Compliant statements apply to paper and electronic records equally unless law says otherwise. 5: Verify the disposition language. The statement should distinguish destruction, transfer, and permanent retention. 6: Scan for cost claims. Statements promising savings from keeping everything more than two years fail the arithmetic test in most settings. 7: Match the jurisdiction. U.S. federal schedules don't govern state agencies or private employers, and statements implying they do are false.
Use the checklist on your own policy language. It catches the sentences that were true when written and aren't anymore, which is the failure mode auditors report most often.
What an Effective Program Actually Requires, and the Statements That Misdescribe It
Statements that describe records management as an IT function are false. IT provides systems, but the program requires an accountable records officer, written policy, training, and audit. NARA's Federal Records Management program requires each agency to designate a records officer, and the private-sector equivalent is a named owner with authority over disposition decisions.
Statements that treat training as a one-time event are also false. Requirements change, platforms change, and the Iron Mountain survey noted that fewer than half of surveyed organizations trained staff annually. Training frequency should match change frequency, and annual is the floor rather than the ceiling in sectors with heavy regulation.
The most consequential false statement is the one promising the program is "set and forget." Records management requires review cycles. Schedules get reapproved when regulations shift, holds get audited, and repositories get sampled for compliance. ISO 15489, the international standard for records management, describes the program as continuous, with monitoring and review built into the design.
And statements that make the program someone else's job fail in practice. Effective programs distribute obligation across creators, managers, and legal owners while keeping a central authority for schedules. A statement assigning all responsibility to the records team removes accountability from the people who make records every day, and auditors mark that as a governance gap.
FAQ
Is "records should be kept forever to be safe" a true or false statement?
False. NARA's 36 CFR Part 1220 requires disposal after the business need ends, so indefinite retention violates federal records rules. The 2023 Iron Mountain survey's storage figure of roughly $0.35 per file per month makes the cost concrete. Safety comes from governed disposal, not from unlimited retention.
Does a legal hold expire automatically when a case closes?
No. Holds release only when an authorized person documents the release, and automatic expiry has no legal foundation. The Sedona Conference guidelines treat hold release as a deliberate decision with a record of it. Systems that auto-expire holds create exactly the data-loss exposure holds were meant to prevent.
Can we shred paper once it's scanned?
Only if the imaging system meets your tax authority's rules, such as Revenue Procedure 97-22 in the U.S. The scan must be accurate, indexed, and retrievable for the full retention period. Check with counsel before destroying originals, because several jurisdictions require the paper for specific record types.
Is email covered by a records retention schedule?
Yes, when it documents business activity. NARA's Capstone approach in 36 CFR Part 1236 treats senior officials' email as permanent, and that coverage extends to any email documenting decisions. Programs that exclude email leave a record series ungoverned, and auditors flag the gap.
Why is "delete everything after one year" false?
Because retention follows record type, not a single clock. GRS 2.2 in the U.S. runs from 3 to 56 years across employee benefit series. A one-year blanket rule destroys records still legally required, which courts can sanction under Rule 37(e) when relevant material is lost.
What is the cheapest way to fix a keep-everything policy?
Get legal approval of a schedule, then dispose in batches under it. The arithmetic favors this: at Iron Mountain's survey figure of about $0.35 per file per month, clearing 400,000 scheduled records saves roughly $140,000 monthly. Batch disposal carries lower risk than one-time purges.
Does ISO 15489 require a software purchase?
No. ISO 15489 defines principles for records management systems and does not mandate a product. Organizations can meet it with existing repositories if policy, authority, and audit are in place. The standard's review requirements, not the tooling, are where most programs fall short.
This article is general educational information about records management concepts and is not legal advice. Retention requirements vary by jurisdiction, industry, and record type, so consult a qualified records professional or attorney in your location before changing schedules or destroying records. Immediate legal exposure in active litigation requires counsel, not general guidance.