A derivative classifier who is unsure how to mark information because of conflicting guidance must not guess. The responsibility is to stop the classification action, preserve the information in its unmarked or current state, document the specific conflict, and escalate it to the designated derivative classification authority or security officer for a written determination. That holding rule applies at every level of the chain — original classifier, derivative classifier, and reviewing official.

The logic behind it is simple. A derivative classifier applies classification guidance that someone else created; they don't create it. When two source documents, a marking guide, and a security classification guide disagree, the derivative classifier has no authority to resolve the disagreement by picking a winner. Guessing in either direction creates a document that is either over-classified (costing money and slowing mission work) or under-classified (risking disclosure of protected information). Both are reportable errors in most classification programs.

This article walks through what "conflicting guidance" actually looks like in practice, the exact steps to take when you hit it, how long you can hold information before escalation becomes a compliance problem, and what happens at each rung of the escalation ladder.

Conflicting Guidance Is Defined by Source Conflict, Not by Your Gut Feeling

Conflicting guidance means two authoritative sources give incompatible marking instructions for the same information. It does not mean the classifier feels uncertain, lacks training, or finds the guidance hard to read.

The distinction matters because "I'm not sure" covers a wide range of situations with different correct responses. A classifier who hasn't read the relevant security classification guide has a training gap, not a guidance conflict — the fix is to read the guide. A classifier facing a 2019 guide that says SECRET and a 2023 guide that says CONFIDENTIAL has a genuine conflict.

Common conflict patterns include:

Version conflict. An older security classification guide and its replacement disagree on the same category, and the classifier isn't certain which is current. Source-document conflict. Two classified source documents carry different markings for the same information, and neither is obviously derivative of the other. Guide versus source conflict. A current guide and a source document marked under a different guide disagree. Cross-program conflict. Information from two programs with separate guides is combined, and each guide's rules produce a different marking. Marking-guide ambiguity. A marking guide specifies a category but not the level, or specifies a level but not the duration.

The presence of any of these patterns is the trigger. The classifier's personal confidence level isn't the test.

The Derivative Classifier's Legal and Policy Responsibility Is to Not Create a Marking

Under Executive Order 13526 and its successor framework, derivative classifiers are authorized to apply classification only as directed by an original classification authority's guidance. They are not authorized to make classification decisions. That's the whole point of the derivative role.

Practically, this means the responsibility when guidance conflicts is:

1: Do not assign a classification level you cannot trace to a single, current, authoritative source. 2: Do not remove a marking that a source document already carries, absent written authority. 3: Do not delay indefinitely — escalation has a deadline. 4: Do not resolve the conflict silently and move on, even if you're confident you're right.

The Information Security Oversight Office's marking handbooks and each agency's implementing directive spell out the derivative classifier's duty to follow guidance "exactly." Where guidance is contradictory, the duty to follow exactly becomes impossible to discharge, and the duty to escalate takes over. The classifier's obligation is procedural: raise the conflict to the authority that can resolve it.

Step-by-Step: What to Do the Moment You Hit a Conflict

Here's the sequence most agency classification programs expect, in the order you should perform it.

1: Stop marking that item. Do not apply the contested classification level to the document, slide, email, or dataset. Leave it unmarked or leave its existing marking in place. 2: Isolate the conflict. Write down the exact information in question, the two (or more) sources giving conflicting guidance, and the specific instruction each source gives. Cite document numbers and dates. 3: Check for currency first. Confirm whether one of the conflicting sources has been superseded. The Defense Information System for Security, each agency's classification guide repository, and the originating program office are the normal places to confirm. A superseded guide isn't a conflict at all. 4: Apply the conservative hold. If currency can't be confirmed quickly, mark the item at the higher of the conflicting levels, or leave the source document's existing marking untouched, and flag it as provisional. 5: Document the hold. Record the conflict, the provisional marking, the date, and the name of the person who will resolve it. This documentation is what protects you if the document is later reviewed. 6: Escalate to the derivative classification authority. This is normally the original classification authority for the information, the agency's classification management officer, or the security classification guide's point of contact. State the conflict and ask for a written determination. 7: Record the determination. When the answer comes back, apply it, note the resolving authority and date, and keep the record with the document's classification history.

Failure handling: if no determination arrives by the program's deadline (commonly 5 to 10 business days depending on agency), escalate one level up and continue the conservative hold. If the document is needed for a deadline before the answer arrives, it can usually proceed marked at the higher level with a caveat, but only with documented approval from the reviewing official.

Conservative Hold Is the Default: Over-Marking Until Resolved

When in doubt, classify up. That's been standard practice in U.S. classification programs for decades, and it's still the working rule for unresolved conflicts today.

The reasoning: over-classification is a cost problem. Under-classification is a security problem. Cost problems can be corrected later; disclosures cannot be undone. A document marked SECRET that turns out to be CONFIDENTIAL can be declassified. A document marked CONFIDENTIAL that turns out to be SECRET has already leaked.

The Information Security Oversight Office's annual reports to the President have repeatedly flagged over-classification as a systemic cost — the 2017 report noted that over 50 percent of classified documents reviewed in some agency sampling were over-classified or not properly classified. That's the price of the conservative default working as designed. Programs accept the cost because the alternative is worse.

Two limits on the conservative hold matter. First, it's temporary — a hold that never gets resolved becomes over-classification by neglect. Second, it doesn't apply to information you have positive reason to believe is unclassified; if a source is clearly wrong, the correct action is still escalation, not a permanent higher marking.

Escalation Goes to the Classification Authority, Not Your Supervisor

The person who resolves a guidance conflict is the one with authority to classify the information — usually the original classification authority for that category, not the classifier's direct supervisor.

That distinction trips people up. A first-line supervisor can tell you how the office usually handles something; they can't tell you what the correct classification is. Only the original classification authority, or a designated classification management officer acting on their behalf, can issue a determination that binds the derivative classifier.

Typical escalation targets:

The originating program office that issued the security classification guide. The agency's classification management officer or senior agency official for classification. The original classification authority named in the guide. For joint or coalition information, the appropriate foreign disclosure officer or the lead agency in the arrangement.

Route the request in writing. Verbal determinations are the source of most later disputes; a written record showing who resolved what, and when, is what makes the classification defensible on audit.

Documenting the Conflict Protects You on Audit and on Review

A derivative classifier who escalates and documents is protected. One who guesses is exposed, even if the guess turns out correct.

The documentation should include the information at issue, the conflicting sources and their instructions, the provisional marking applied, the escalation date and recipient, and the final determination. Keep it with the document's classification record or in the program's classification log.

Why this matters on audit: when an inspector general or an ISOO review finds a mis-marked document, the first question is whether the classifier followed guidance. If the guidance itself was contradictory and the classifier escalated, the finding usually attaches to the guidance, not the classifier. If the classifier guessed without documenting, the finding attaches to the classifier.

The same logic applies in litigation and in mandatory declassification review. A documented escalation trail shows the marking was made in good faith under the guidance available at the time.

Time Limits: How Long Can a Conflict Stay Unresolved?

Most agency classification programs expect resolution within 5 to 10 business days. Longer holds require documented justification and higher-level approval.

Those timeframes are program-specific, not uniform across the federal government. The Department of Defense's marking guide and each military department's supplement set their own timelines; civilian agencies set theirs in their implementing directives. Confirm the specific deadline with your agency's classification management office before relying on a number.

The practical rule: treat the deadline as a commitment to the reviewing official, not a suggestion. A conflict that sits unresolved for a month has effectively become a silent decision to keep the higher marking, which is a classification error in its own right.

For information with an operational deadline — a briefing, a deployment package, a congressional response — the escalation and the conservative hold run in parallel. The document goes out at the higher marking with a documented caveat, and the determination follows.

What Happens if You Guess Wrong — Worked Failure Case

Consider a realistic case. A derivative classifier preparing a program briefing pulls from two source documents. Source A, marked under the 2018 program guide, marks a specific technical parameter SECRET. Source B, marked under the 2022 guide, marks the same parameter CONFIDENTIAL. The classifier has read both guides and can't tell which is current for this program.

If the classifier guesses CONFIDENTIAL and applies it, and the 2018 guide turns out still to govern that parameter, the briefing is under-classified. That's a security incident — reportable, investigable, and potentially a spill requiring notification to the original classification authority and remediation across every copy distributed.

If the classifier guesses SECRET and applies it, and the 2022 guide governs, the briefing is over-classified. That's a classification error — less severe, but still reportable and still a finding on audit.

If the classifier stops, documents the conflict, marks the parameter at SECRET provisionally, and escalates, neither outcome attaches to the classifier. The determination resolves the question, the provisional marking is corrected or confirmed, and the record shows the classifier did exactly what the program requires.

The cost of the third path is time — usually a few days. The cost of the first path, when it goes wrong, is a spill investigation.

Frequently Asked Questions

Is it ever acceptable for a derivative classifier to make the classification call themselves?

No. A derivative classifier applies guidance; they don't create it. The only exception is where the derivative classifier is also a trained original classification authority for the same category — and even then, the correct action when guidance conflicts is to resolve it as the authority, not to guess as the derivative classifier.

What if the conflicting guidance comes from a foreign government or coalition partner?

Foreign disclosure rules sit on top of classification rules and are usually stricter. When a foreign-origin document and a U.S. guide conflict, the holding action is to consult the foreign disclosure officer before marking anything. Coalition documents are typically handled under the specific coalition guide, which overrides the national guide for that information.

How is this different from the "classification by compilation" problem?

Compilation is a separate issue: individual items may be unclassified, but their aggregation reveals classified information. Guidance conflicts and compilation problems can overlap — a guide may be silent on the compilation effect while a source document marks it. When both issues are present, escalate both at once and treat the compilation question as part of the same determination.

What happens if the information must go out before the conflict is resolved?

The document can usually proceed at the higher of the conflicting markings with written approval from the reviewing official, and the determination is applied retroactively when it arrives. Skipping the approval and marking at the lower level is the option that creates a reportable incident.

Does the derivative classifier need to notify the original classification authority personally?

Not necessarily. Most programs route through the classification management officer or the guide's point of contact. What matters is that the determination comes from someone with authority to make it, and that the classifier records who that was.

Can a derivative classifier be disciplined for escalating too often?

Not in a well-run program. Escalation is the designed response to conflict. Repeated escalation of the same category usually signals a guidance problem that program management needs to fix — it's a signal, not a performance issue for the classifier.

Where can a classifier confirm the current version of a security classification guide?

Through the agency's classification guide repository, the originating program office, or the agency classification management officer. For DoD, the Defense Information System for Security and each service's classification guide portal are the standard paths; confirm current editions there before treating an older copy as authoritative.

This article is general educational information about classification procedures, not legal advice or an official determination. Derivative classification responsibilities are set by executive order, agency directives, and program-specific guides that vary by organization and change over time; confirm the controlling rules with your agency's classification management office or a qualified professional in your jurisdiction before acting on any specific marking decision.