Which Is the Primary Source for Derivative Classification?
Ever stared at a stack of classified documents and wondered, “Where does the original classification even come from?” You’re not alone. In the world of intelligence and defense, derivative classification is the rule‑of‑thumb that keeps the chain of secrecy unbroken. But the real question is: **what’s the primary source that tells you what to copy, what to change, and what to leave out?
The answer isn’t a single form or a vague policy memo. It’s a specific, legally‑mandated document that sits at the top of the classification hierarchy. Let’s dig into that source, why it matters, and how you can use it without tripping the compliance alarms Easy to understand, harder to ignore..
Not the most exciting part, but easily the most useful.
What Is Derivative Classification?
Derivative classification is the process of taking existing classified material and incorporating it into a new product—whether that’s a report, a briefing, an email, or a slide deck—while preserving the original classification level and any handling caveats. In plain English, you’re not allowed to “re‑classify” something on a whim; you must inherit the classification from the source that gave it to you Practical, not theoretical..
The Chain of Authority
The authority to classify originates from three places:
- Executive Orders (e.g., EO 13526) – set the legal framework.
- Agency Classification Guides – interpret the executive order for a specific mission set.
- Original Classification Decisions (OCDs) – the actual markings on the source document.
The moment you create a derivative, you’re basically saying, “I’m borrowing the classification from this original source.” The primary source for that decision is the Original Classification Decision attached to the source material Simple, but easy to overlook..
Original Classification Decision (OCD) Explained
An OCD is the official determination, usually made by a senior classified official, that a piece of information must be protected for national security reasons. Practically speaking, g. O. The OCD also notes the reason (e.Think about it: , “E. Still, 13526 § 1. , “Military Plans”) and the authority (e.g.It’s recorded in the document’s classification markings—those little “// TS //” or “// CONFIDENTIAL //” stamps you see in the header and footer. 4(b)”).
That’s the primary source. Every derivative classification you do must trace back to an OCD, not just a vague “the guide says it’s secret.”
Why It Matters / Why People Care
If you get the source wrong, you’re either over‑classifying (wasting time, slowing down decision‑making) or, worse, under‑classifying (exposing a vulnerability). Both scenarios have real costs That's the part that actually makes a difference..
- Operational impact – Over‑classification clogs the information flow. A commander waiting on a briefing that’s “Secret” when it could be “Confidential” may miss a critical window.
- Legal liability – Under‑classification can lead to criminal penalties under the Espionage Act. You’ve probably heard the headlines about former contractors getting fined; those cases start with a missed OCD.
- Audit headaches – The Inspector General will chew you up if a derivative product can’t be traced back to a valid OCD. You’ll spend hours pulling audit trails instead of doing your job.
In practice, the primary source is the safety net that keeps you from falling into either pit.
How It Works: Tracing the Primary Source
Below is the step‑by‑step workflow most agencies follow. It’s not rocket science, but the details matter.
1. Identify the Source Document
Open the file you’re about to reuse. Look for the classification markings on the first page, the cover sheet, or the metadata. If it’s an electronic file, check the security label in the header/footer or the file properties.
2. Verify the Original Classification Decision
The OCD should be explicit:
- Classification Level (TS, S, C, U)
- Reason(s) (e.g., “Nuclear Weapon Design”)
- Authority (the specific clause of EO 13526 or agency directive)
If any of those elements are missing, you have a problem. The rule is simple: no OCD, no derivative.
3. Determine If the Information Is Still Classified
Classifications can be de‑controlled. So look for a de‑classification date or a “// NOFORN //” that might have been lifted. If the source is older than ten years, check the agency’s de‑classification schedule The details matter here..
4. Apply the Same Markings to Your Derivative
Copy the exact level, handling caveats, and reason codes. Day to day, if you add new material, you must evaluate whether that new content requires a higher classification. If it does, you’ll need a new OCD for the added portion.
5. Document the Source in Your New Product
Most agencies require a “Source” line, e.g.Which means , “Derived from DOC‑12345, Original Classification Decision dated 12 Mar 2022. ” This creates an audit trail that an inspector can follow.
6. Review and Approve
A classification authority (CA) or a designated senior official must sign off on the derivative. In many organizations, that’s a quick “Approved” in the document’s header.
Common Mistakes / What Most People Get Wrong
Mistake #1: Assuming a Guide Equals an OCD
A classification guide tells you what might be classified, but it’s not the primary source. You can’t cite “Agency Guide 3‑2” as the authority for a derivative; you need the actual OCD on the source document.
Mistake #2: Ignoring De‑classification
People love to reuse old reports because “they’re probably public by now.” Wrong. Unless you have a documented de‑classification, the original OCD still applies.
Mistake #3: Over‑relying on “Classified as” Statements in Emails
An email that says “Classified as Secret” is not an OCD unless it was authored by a properly delegated classification authority. Treat it as informal and verify the original source Worth keeping that in mind..
Mistake #4: Dropping Reason Codes
The reason code isn’t decorative; it tells downstream users why the info is protected. Stripping it can cause mishandling later on.
Mistake #5: Mixing Multiple Sources Without Proper Attribution
If you mash together three classified documents, you must list each source and keep each segment’s markings intact. A single blanket “Secret” label won’t cut it.
Practical Tips: What Actually Works
-
Create a “Source Log” – A simple spreadsheet with columns for Document ID, OCD Date, Classification Level, Reason, and De‑classification Date. Update it every time you start a new derivative Easy to understand, harder to ignore..
-
Use Automated Classification Tools Wisely – Many DOD systems can auto‑populate the source line. Verify the auto‑fill against the physical document; don’t trust the software blindly Practical, not theoretical..
-
Ask the Original Classifier – If you’re unsure whether a document’s OCD is still valid, reach out to the person who made the original decision. A quick email can save you a compliance nightmare Small thing, real impact..
-
Keep a “Classification Cheat Sheet” on Your Desk – List the most common authority clauses (e.g., “E.O. 13526 § 1.4(b)”) so you can spot them fast in the markings Still holds up..
-
Never Derive From “Unmarked” Material – If a document lacks markings, treat it as unclassified until you get a proper OCD. It’s better to ask for clarification than to assume it’s public Worth knowing..
-
Regularly Review Your Derivatives – Schedule a quarterly audit of all derivative products you’ve authored. Look for missing source lines, outdated OCDs, or mismatched handling caveats.
FAQ
Q: Can I use a classification guide as the primary source for a derivative?
A: No. The guide is a reference, not an authority. You must trace back to the original document’s OCD.
Q: What if the source document is a handwritten note with no markings?
A: Treat it as unclassified until a senior classified official issues an OCD for that content.
Q: Do I need a new OCD if I only rearrange the order of paragraphs?
A: No new OCD is required, but you must still cite the original source and keep the original markings.
Q: How do I handle “NOFORN” or “REL TO USA, AUS, CAN” markings in a derivative?
A: Replicate the exact dissemination controls. If you add new content that is not covered by those controls, you may need a separate marking for that portion Worth knowing..
Q: My manager says “just mark it Secret, we’re short on time.” Is that okay?
A: Only if the original source’s OCD is Secret. Otherwise you’re either over‑classifying or under‑classifying, both of which are compliance violations.
Understanding that the Original Classification Decision is the primary source for derivative classification isn’t just a bureaucratic footnote—it’s the linchpin that keeps the whole security apparatus from unraveling. Keep your source logs tidy, double‑check those OCDs, and you’ll avoid the most common pitfalls that trip up even seasoned analysts.
So next time you sit down to assemble a briefing, pause and ask yourself: “What OCD am I borrowing from?” If you can answer that confidently, you’re already doing the hard part right. Happy (and compliant) classifying!
