Your team probably deletes working files without a second thought. They're just drafts, right? Not official business. But when an auditor asks why your disposition log shows no record of them, or a legal hold sweeps up files you thought were temporary, you'll wish someone had read 36 CFR 1222.12(c) more carefully.
These myths persist because digital environments blur the line between "working" and "official." When a draft email becomes a circulated memo, or a copy gets posted to an intranet, the file's status changes even if its content doesn't. Most organizations rely on gut instinct instead of the two-part test that actually determines record status. Let's fix that.
Myth 1: Working Files Are Never Records
Reality: Working files become records the moment they meet two conditions under 36 CFR 1222.12(c). First, they must have been circulated or made available to employees beyond the creator for official purposes like approval, comment, action, recommendation, follow-up, or communicating about agency business. Second, they must contain unique information such as substantive annotations or comments that add to a proper understanding of your organization's policies, decisions, actions, or responsibilities.
Notice the "AND" in that test. Both conditions must be true. A draft you email to your colleague for feedback crosses the circulation threshold. If that colleague adds margin notes explaining why the proposed policy won't work in the field office, you've now got unique information. That working file is a record requiring a NARA-approved disposition authority.
The practical implication: your collaboration tools are creating records faster than your retention schedule can classify them. Every commented Google Doc, every annotated PDF in SharePoint, every Slack thread where someone makes a decision, potentially qualifies.
Myth 2: Copies Don't Count as Records
Reality: Copies are records when they're used to conduct business, serve a different function than other versions, or are posted on a website (internal or external). The format doesn't matter. The location doesn't matter. The function does.
Consider a contract. The signed original in your legal department is obviously a record. But the copy your procurement team keeps to verify vendor performance? That's also a record because it serves a different function (contract administration versus contract execution). The copy posted to your supplier portal for reference? Record. The copy you forwarded to your manager with a note saying "FYI, we're locked in for three years"? Probably a record if that context isn't captured elsewhere.
This myth costs organizations during litigation. You can't claim you searched all relevant files if you exempted "copies" from your legal hold. Courts don't care whether you called it a copy. They care whether it was used to conduct business.
Myth 3: If It's Not in the File Plan, It's Not a Record
Reality: Record status is determined by how a document functions, not where it lives in your classification scheme. Your file plan describes records you know about and have scheduled. It doesn't define what is or isn't a record.
A working file that meets the 36 CFR 1222.12(c) criteria is a record whether your Records Control Schedule anticipated it or not. This creates an uncomfortable truth: you can be out of compliance even if you're following your file plan perfectly. If your plan doesn't account for annotated drafts circulated for approval, and your teams create hundreds of them monthly, you've got unscheduled records.
The fix isn't to declare them non-records. It's to update your disposition authority to cover them. This is why NARA requires approval for disposition schedules. You can't unilaterally decide that inconvenient documents aren't records.
Myth 4: The Creator Decides Record Status
Reality: The two-part test decides record status. The creator's intent is irrelevant. Your project manager might think they're just keeping "working notes," but if those notes were shared with the team to coordinate action and contain unique details about why a deadline shifted, they're records.
This myth is particularly dangerous in email. People assume their sent folder is personal workspace. But every message circulated for official purposes that contains unique information (a decision rationale, a policy interpretation, an instruction) is a record. The sender doesn't get to opt out.
The compliance gap here is enormous. Most organizations have email retention policies, but few have trained staff to recognize when a "quick note" crosses into record territory. Your team thinks they're being efficient by keeping informal channels moving. Your auditor sees unmanaged records.
Myth 5: Digital Files Are Easier to Classify Than Paper
Reality: Digital environments make the working-file problem worse, not better. Paper workflows had natural breakpoints. A draft stayed on your desk until it was final. Once you routed it for signature, everyone knew it was official.
Digital collaboration collapses that distinction. A Google Doc starts as a personal draft, gets shared for comment (now it's circulated), accumulates tracked changes and margin discussions (now it contains unique information), and becomes a record without anyone declaring it as such. Version control makes it worse. Is the record the final version, or the version-with-comments that shows how you reached the decision?
You can't solve this with technology alone. Auto-classification tools can't read intent or assess whether annotations are substantive. You need clear procedures: when does a draft get declared as a record? Who's responsible for capturing the version with decision context? What happens to earlier versions?
What to Do Instead
Start with the two-part test from 36 CFR 1222.12(c). Train your teams to ask: (1) Was this circulated for official purposes? (2) Does it contain unique information? If both answers are yes, it's a record.
Next, audit your collaboration platforms. Where are working files being circulated? What unique information are they capturing? Map those workflows to your Records Control Schedule. If you don't have disposition authorities covering annotated drafts, commented documents, or decision threads, you need them. Contact your NARA appraiser if you're in the federal space, or your records authority if you're in a regulated industry.
Finally, build declaration into your workflows. Don't rely on end-of-project cleanup. If a draft becomes a record when it's circulated with substantive comments, capture it then. Your document management system should prompt: "This file has been shared with annotations. Declare as record?" Make the right choice the easy choice.
The line between working files and records isn't blurry. The regulation is clear. What's blurry is your team's understanding of when they've crossed it. Fix that, and you'll stop failing audits over files you didn't know mattered.
