The first action is to secure and preserve the full classification record before doing anything else — the source document, the derivative's own marking rationale, the classification guide entry relied on, and the date the marking was applied. A derivative classifier who picks up the phone or fires off an email before locking down that record loses the evidentiary basis for the challenge. The challenge lives or dies on paperwork, and paperwork that hasn't been preserved can be altered, superseded, or quietly withdrawn upstream. Preservation comes before notification, before escalation, and before any informal conversation with the original classifier.

This matters because derivative classification is a chain-of-custody function. Under Executive Order 13526 and its implementing directive (32 CFR Part 2001), a derivative classifier must apply markings that already exist on an authorized source document and must be able to point to that source. When a derivative classifier believes a marking is improper — wrong level, wrong category, wrong duration, wrong decontrol instruction — the dispute is about the source, and the source has to be captured intact first. The sections below walk through preservation, the regulatory backstop, the notification sequence, the common failure modes, and the records that decide the outcome.

Why Preserving the Classification Record Comes Before Any Notification

Preservation is not a bureaucratic nicety. It's the difference between a challenge that a classification authority can adjudicate and a complaint that has no anchor. When a derivative classifier challenges a marking, the first question any reviewer asks is: what exactly said what, and when? If the answer depends on memory, the challenge stalls.

The record set to preserve has a defined shape. It includes the source document with its markings and any classification guide entry cited, the derivative document's marking block and the rationale that produced it, the date and location of derivative classification, and the identity of the original classifier or classifying authority. A derivative classifier who can produce these four items in a single package has already done more than most challengers, who typically arrive with a verbal objection and a vague citation.

Why does sequence matter so much? Because the marking itself can change while a challenge is in motion. A source document can be re-marked, a classification guide can be revised, a prior classification decision can be superseded. If the derivative classifier preserved the pre-challenge state, the reviewer can see what was actually being challenged. If not, the reviewer sees only the current state, which may already have corrected the problem — and the challenge gets closed as moot without ever being examined.

There's a practical angle too. A preserved record is what lets a derivative classifier distinguish between three very different problems: the source itself is misclassified, the derivative misapplied an otherwise valid source, or the derivative is correct and the objection is mistaken. Only the first two are challengeable. Getting that distinction right depends on the preserved file, not on recollection. The first action, therefore, is the boring one: capture the file.

The Regulatory Backstop: What 32 CFR Part 2001 Actually Requires

The controlling framework is unambiguous about who carries the burden. Under Executive Order 13526, Section 1.1, classification is the exclusive province of the President and the agency heads and officials designated in advance. A derivative classifier does not have independent classification authority — they carry forward an existing determination. That's why a challenge is framed as a question about the source, not a competing classification judgment.

The implementing directive, 32 CFR Part 2001, sets out the mechanics. Section 2001.22 addresses derivative classification and the requirement to carry forward source markings. Section 2001.60 establishes the mandatory declassification review process, which is the formal channel for challenging classification that the challenger believes is improper. The directive also assigns responsibility for correcting misclassification, and it requires agencies to have a process for challenging classification determinations. The key point for a derivative classifier is that the directive presumes the derivative is not the final arbiter — the classifying authority is.

That hierarchy creates the procedural rule. A derivative classifier who believes a marking is improper should not simply strip it. They should preserve the record, document the objection, and route it through the agency's classification challenge channel. The specific channel varies by agency — some use a formal classification challenge program, some use the mandatory declassification review process, some use an internal classification review board — but all of them require documentation first. The Information Security Oversight Office (ISOO) publishes guidance on these processes, and the agency's own classification guide or security manual names the local channel.

There is one hard boundary worth stating clearly. This is not legal advice, and the specific process depends on the agency, the classification guide in force, and whether the document involves special access programs or other compartments. A derivative classifier facing an actual dispute should check their agency's security manual and consult their command's security officer or legal counsel. The regulatory framework tells you the shape of the process; the agency tells you the door.

A Numbered Walkthrough of the First 48 Hours

Here is the sequence a derivative classifier should run when a marking looks wrong. The steps assume the derivative has authorization to handle the document and is not creating a new copy to investigate — that would be a separate problem.

1: Segregate the document and stop derivative work on it. Pull the derivative document and its source from the active production queue so no further copies are made while the objection is live. Log the segregation with date, time, and the identity of the person doing it.

2: Capture the source package intact. Photograph or scan the source document's marking block, any classification guide entry, the derivative's marking block, and the covering authorization. Store the capture in a controlled location with a hash or signature if local policy allows.

3: Write a one-page objection memo before speaking to anyone. State the marking as it appears, the specific defect alleged (wrong level, wrong category, wrong duration, missing decontrol instruction), the source relied on, and the remedy sought. Date it and sign it. This memo is not the challenge — it is the record that a challenge exists.

4: Verify the classification guide in force on the derivative date. Confirm which guide version applied when the marking was made. A guide revised after the fact does not justify the original marking, and a derivative classifier who challenges against the wrong guide version undermines the objection before it starts.

5: Notify the original classifier in writing and request acknowledgment. The first contact should not be a hallway conversation. Written notice with a response deadline creates a trace, and it gives the original classifier a chance to correct the record before formal escalation.

6: Escalate to the agency's classification challenge channel if no correction is confirmed within the response window. Route the objection memo and the preserved package to the security officer or classification review office named in the agency manual.

The most common failure at this stage is step 5 executed in reverse — the derivative classifier calls the original classifier first, gets a verbal "I'll look at it," and then discovers weeks later that no one remembers the conversation. The second most common is step 2 done after the source has already been re-marked. If either happens, the challenge isn't dead, but it has to be rebuilt from a weaker record.

Source Misclassification vs. Derivative Error: A Comparison That Decides the Channel

Not every improper marking is the same kind of problem, and the comparison matters because the two categories go to different reviewers. A derivative classifier who misdiagnoses the category wastes the challenge on the wrong desk.

Dimension Source misclassification Derivative application error
What's wrong The source document itself carries an incorrect level, category, or duration The source is correct, but the derivative misapplied the marking
Who reviews The original classifying authority or its successor The derivative classifier's own chain and security office
Typical trigger Level inconsistent with the guide, or duration exceeds the guide limit Wrong portion marking, missed decontrol instruction, wrong category
Remedy Source re-marked or re-reviewed; derivative re-derived from corrected source Derivative re-marked to match source; corrective training entry
Preserved record needed Source marking block, guide entry, original classifier identity Derivative marking block, guide entry, original source
Time to resolution Longer — may trigger mandatory declassification review Shorter — internal correction typically within one review cycle
Risk if mishandled Challenge gets closed as a derivative dispute, not a source dispute Challenge gets escalated unnecessarily and delays production

The table's verdict is simple. If the defect traces to the source, the challenge belongs with the classifying authority and should not be framed as a derivative judgment. If the defect is in the derivative's own work, the classifier should correct it internally and document the correction rather than escalate. Deciding which column applies is the second most important judgment after preservation, and it's the one most often skipped.

When the Challenge Is Improper on Its Face: Four Failure Modes

Some challenges should never be filed, and the derivative classifier who recognizes this early saves the agency a review cycle. The first failure mode is a challenge built on personal disagreement with the classification level rather than a defect against the guide. A derivative classifier who thinks a document "feels over-classified" but cannot point to a guide provision has no challenge — they have an opinion, and opinions go through the declassification review channel, not the classification challenge channel.

The second failure mode is a challenge filed after the derivative has already altered or destroyed the marking. Once the derivative has re-marked the document without authorization, the original state is gone, and the challenge becomes a dispute about the derivative's own unauthorized action. That converts a legitimate objection into a security incident.

The third failure mode is a challenge to a marking that carries a properly invoked decontrol instruction the derivative misread. This is common with documents marked for automatic declassification under Section 3.3 of the Order, where the derivative reads the date but misses the exemption code attached to it. The marking is correct; the derivative's application is wrong. The fix is a corrected derivative, not a challenge to the source.

The fourth failure mode is a challenge that leaks the document's existence. A derivative classifier who raises the objection in an unclassified email chain, or who discusses the marking with someone outside the need-to-know circle, has created a spillage problem while trying to solve a marking problem. The objection memo goes through the security channel, and the channel is classified at the level of the document. None of these four failure modes is rare. Security officers report them routinely, and each one costs the agency more time than the original marking dispute would have taken to resolve cleanly.

The Preservation Log a Reviewer Expects to See

A preserved record is more useful when it's a single package with a defined structure. The table below is the minimal set a classification reviewer can act on within a single session.

Record item Format What the reviewer uses it for
Source document marking block Scan or photograph, dated Confirm what was originally marked and by whom
Classification guide entry in force on derivative date Cited by guide number, version, and section Establish the standard the marking is measured against
Derivative marking block and rationale Copy of derivative plus the classifier's reasoning Show what the derivative actually produced
Objection memo Signed, dated, one page Confirm the challenge exists and is scoped
Written notice to original classifier and acknowledgment Email or memo with timestamps Establish the notification trace
Escalation routing record Security officer receipt or case number Confirm the challenge entered the formal channel

A reviewer who receives this package can resolve the dispute without contacting the derivative classifier for missing pieces. That matters because the reviewer's time is the scarcest resource in the process. A challenge that arrives as a phone call and a vague reference gets deprioritized; a challenge that arrives as a complete tabbed package gets worked.

One further item belongs in the log even though it's not a document: the derivative classifier's own authorization to handle the document at that level. A challenge from someone who lacks the clearance or the need-to-know for the material is not a challenge the reviewer can act on. The first action after preservation is confirming that the person filing the objection is entitled to see the source.

How Agency Practice Varies on Challenge Routing

The regulatory framework is national, but the routing is not. Agencies implement the challenge process differently, and a derivative classifier who assumes a single universal channel will misfile the objection.

The Department of Defense, through its security manual and component instructions, typically routes classification challenges through the component's classification management office or security office, with a defined review board for disputed determinations. Civilian agencies vary more widely — some use the agency's mandatory declassification review channel for all classification challenges, while others maintain a separate classification appeal process. Intelligence community elements often have compartment-specific review procedures that sit outside the agency's general channel. The ISOO publishes guidance that describes the common elements, but the agency's own manual is the authority for the specific door.

The practical consequence is that the derivative classifier should check the agency's manual before step 5 in the walkthrough. The notice to the original classifier still goes out — that part is universal — but the escalation route in step 6 depends on which office the manual names. A challenge sent to the wrong office gets forwarded, and forwarding adds weeks. A challenge sent to the right office with the package intact gets a case number within days.

There's a version-specific wrinkle worth flagging. Classification guides are revised on cycles, and a guide revision can change both the marking standard and the challenge route. The derivative classifier should confirm the guide version in force on the date the marking was applied, not the current version. A challenge measured against a superseded guide will be rejected even if the marking was genuinely wrong under the older guide. The guide number and version belong in the preservation log for exactly this reason.

Correcting the Record Without Waiting for the Review to Finish

A challenge doesn't pause the derivative's other obligations. If the derivative document has already been distributed with the disputed marking, the derivative classifier still has to handle it correctly while the challenge is pending — and the handling rule is to keep the marking in place until the challenge is resolved. A classifier who strips a disputed marking before adjudication has created an unauthorized declassification.

The correct interim posture is to apply the marking as it appears on the source, log the dispute, and route all copies through the channel that knows about the pending challenge. Distribution continues at the source-marked level, not at the derivative's preferred level. When the challenge resolves in the derivative's favor, the corrected marking propagates forward from that point; earlier copies are handled under the correction process the security office directs.

This interim rule has a cost, and it's worth stating plainly. Keeping a disputed marking in place means production continues at the higher level even if the derivative is right. That's slower and more expensive. The alternative — stripping the marking to the derivative's judgment — is faster and illegal. The challenge process exists precisely because the derivative is not the final arbiter, and the interim posture reflects that.

If the challenge resolves in the source classification authority's favor, the derivative classifier needs to close the loop: withdraw the objection memo, record the resolution date and authority, and note the correction to the derivative's own reasoning if any. A challenge that isn't formally closed hangs on the classifier's record as an open conflict with the source — a condition that complicates every subsequent derivative from the same source.

FAQ

Does the derivative classifier need to notify the original classifier before preserving the record?

No — preservation comes first. The record must be captured while it still reflects the pre-challenge state, and notifying the original classifier creates a window in which the source can be re-marked or the guide revised. Capture the source package, the derivative marking block, the guide entry, and the date, then notify. The notification can go out the same day; the preservation should already be done.

Is a verbal objection to a marking ever sufficient?

It is not sufficient for a formal challenge, though it can be a useful first contact after the record is preserved. A verbal objection leaves no trace, cannot be adjudicated, and typically evaporates within one personnel rotation. The written objection memo — one page, signed, dated, naming the defect and the remedy — is the minimum artifact that survives long enough to be reviewed.

What if the marking looks wrong but the derivative classifier isn't sure the source is the problem?

That's the most common situation, and it's why the comparison between source misclassification and derivative application error comes second in the sequence. Capture the record, then test the marking against the guide entry in force on the derivative date. If the guide supports the source marking, the issue is in the derivative's own work and should be corrected internally. If the guide contradicts the source marking, the issue belongs with the classifying authority.

How long does a formal classification challenge typically take to resolve?

Resolution time depends on the channel and the complexity of the source document, and agencies do not publish a single standard timeline. Internal derivative corrections are typically handled within one review cycle, while challenges that reach a classification review board or the mandatory declassification review process take longer because they may require the original classifying authority's participation. The security office that assigns the case number can give the applicable timeline for that agency.

Can a derivative classifier challenge a marking on a document they are not cleared to see?

No. A challenge requires authorization to handle the document at the level it's marked. A derivative classifier who lacks the clearance or need-to-know cannot review the source, cannot write a valid objection memo, and cannot receive the reviewer's response. The correct action in that situation is to route the concern to someone with the required access rather than to file the challenge personally.

What happens if the derivative classifier strips the marking before the challenge resolves?

Stripping a disputed marking before adjudication is an unauthorized declassification, regardless of whether the derivative turns out to be right. The marking stays in place until the challenge resolves in the derivative's favor, at which point the correction propagates forward through the process the security office directs. Earlier distributed copies are handled under the correction procedure, not by the derivative classifier's own re-marking.

Does the challenge process differ for special access program material?

Yes. Special access programs and other compartments typically have their own review procedures that sit outside the agency's general classification challenge channel. The preservation principle is the same, but the routing in the escalation step depends on the program's own security instructions rather than the agency-wide manual. The program security officer is the correct first point of contact for the routing question.

This article is general educational information about classification challenge procedures and is not legal advice or a substitute for agency-specific security policy. Classification authority, challenge routing, and documentation requirements vary by agency, guide version, and program, and a derivative classifier facing an actual dispute should consult their agency's security manual, command security officer, or legal counsel. For immediate security incidents, including suspected spillage, contact the agency's security office or watch desk rather than proceeding through the challenge process.