You can designate unclassified information as Controlled Unclassified Information only when three tests pass at once: the information falls inside a category listed in the National Archives CUI Registry, a law, regulation, or government-wide policy requires or permits handling controls for it, and the information is not already classified. If any test fails, it stays uncontrolled unclassified information and DoD Instruction 5200.48 gives you no authority to mark it CUI β€” a rule that invalidates the most common habit in the field, marking something CUI because a contract clause appeared in the same inbox.

DoDI 5200.48, "Controlled Unclassified Information," issued March 6, 2020 and incorporating Change 1 on December 2, 2020, implements the government-wide CUI program run by the National Archives and Records Administration. The instruction does not create categories of sensitive information. It tells DoD components how to apply categories that already exist in law and policy.

The first gate is the CUI Registry. The registry is the government's official list of lawful CUI categories and subcategories, organized under about twenty top-level groups including Privacy, Proprietary Business Information, Critical Infrastructure, Export Control, and Law Enforcement. Designation authority runs through the registry. Nothing in the registry, nothing to control.

The second gate is a legal or policy driver. A statute, regulation, or government-wide policy must require or permit safeguarding or dissemination controls for that information. The instruction's own text ties designation to that requirement, which makes designation a legal act rather than a professional judgment call.

The third gate is classification status. Information that is classified under Executive Order 13526 falls outside the CUI program entirely. So does information the CUI program itself excludes, such as information in the public domain and information that meets a registry index entry with nothing else attached.

Run all three as pass-fail. A typical failure looks like this: a program office drafts an internal integration schedule, writes "CUI" in the header because the program is acquisition-sensitive, and files it. No registry category covers a schedule built from unclassified planning assumptions, and no statute requires controls for it. Three tests, one failure, invalid marking.

Walk the Registry Index Line by Line, Not by Feel

The registry indexes each category and subcategory with its legal authority and the required or permitted controls. That index is the designation instrument. You must find the information inside an entry, and you must be able to name the entry and its authority if asked.

Start with the closest top-level category and read down. An inspector general's interview notes about a named employee sit under Privacy, not Law Enforcement, if no investigative authority applies. A vendor's pricing worksheet attached to a proposal sits under Proprietary Business Information, subcategory Contract Performance Information, when the contract action supports it.

Read the authority column, not just the category name. Registration under the International Traffic in Arms Regulations is the driver that makes export-controlled technical data CUI. Without a registration or licensing basis, the label "export controlled" is a conclusion nobody can audit.

If you cannot name the exact subcategory, the answer is no. "Close enough" does not survive a program review, and it does not survive a spill investigation either, because the reviewing office will ask which registry entry you relied on.

Test the Lawful Category Against Failure Cases Before You Apply a Marking

DoDI 5200.48 states that information may not be designated CUI to conceal violations of law, inefficiency, or administrative error; to prevent embarrassment to a person, organization, or agency; to restrain competition; or to prevent or delay the release of information that does not require protection in the interest of national security. Those four prohibited purposes are the fastest diagnostic in the program.

Work them as a checklist. Would release embarrass the command? That is a prohibited basis. Would release complicate a competition? Also prohibited unless a registry subcategory such as Source Selection Information independently applies. Would release expose a mistake in a test report? Prohibited, and the correct disposition is release after ordinary review.

The controlling federal case is Cuff v. Department of Justice, 2022, in which the U.S. Court of Appeals for the Third Circuit held that unclassified documents marked "Law Enforcement Sensitive" β€” a legacy marking that predates the CUI program β€” did not qualify as withheld under the relevant exemption because that legacy label was not a lawful withholding statute. The lesson transfers directly: a legacy label inherited from a predecessor system is not a registry category with authority behind it.

A second failure pattern shows up in audits and spills: the serial marking renews itself. Someone stamps a document CUI, the next reviewer sees the stamp and leaves it, and no one can name the registry entry three years later. When the reviewing office asks for the category, the file has no answer, and the designation falls apart retroactively.

Apply DoDI 5200.48 Designation Rules the Way the Instruction Actually Writes Them

The instruction does not assign designation authority evenly. It gives DoD components β€” not individual analysts left to improvise β€” the job of designating CUI within categories, with the DoD CUI Program Office at the Washington Headquarters Services providing program management and the Senior Agency Official for CUI overseeing implementation. In practice, you designate by category assignment approved at the component level.

The practical consequence is a two-step question. First, does the doctrine, manual, or system security plan assign this information type to a registry category? Second, does the local process require the designation? If a component's CUI implementation guidance maps a data type to a registry subcategory, use that mapping. If no mapping exists, escalate rather than improvise.

The instruction also extends CUI requirements into contracts. DoD contracts include CUI requirements through the DFARS 252.204-7012 clause and the associated National Institute of Standards and Technology requirements in NIST SP 800-171, which defines how contractors protect CUI on nonfederal systems. Designation flows from the government side; the clause tells the contractor how to safeguard what has been designated. A contractor cannot designate CUI, and a clause in a contract does not convert unclassified deliverables into CUI by itself.

Separate CUI From Classified, For Official Use Only, and Sensitive But Unclassified

Three confusions drive most misdesignation. The first is classification. Classified national security information lives under Executive Order 13526 and its marking, handling, and declassification rules. CUI never sits above or below classified material; it is a parallel track for unclassified information, and information that is classified is simply not eligible for the CUI program.

The second is the legacy label "For Official Use Only" and its cousins, which the CUI program retired. DoD components were required to complete transition from FOUO and other legacy markings to CUI, and once transition is complete, a document bearing FOUO is a paperwork defect, not a protected designation. If you encounter FOUO in a current file, check whether the underlying information meets a registry entry, then mark accordingly or remove the label.

The third is "Sensitive But Unclassified," which was a broad umbrella term rather than a designation authority. It is not a registry category, and no statute creates controls for "SBU" as such. The distinction that matters in practice is whether a named legal driver exists for the exact information in front of you.

That difference shows up in adjacent programs. A system processing CUI runs the NIST SP 800-171 assessment path under DFARS for defense contractors, while a system processing only Federal Contract Information follows the narrower requirements of FAR 52.204-21. Misdesignating FCI as CUI forces a contractor into an assessment regime it never needed, and the cost lands on both sides.

Steps to Reach a Defensible Designation Decision

Use this sequence when information crosses your desk and the designation is unclear. Each step produces a record you can defend in a review, an audit, or a spill investigation.

1: Read the information and write a one-sentence description of what it actually says, not what program it belongs to. 2: Search the CUI Registry for a category and subcategory that covers that description; record the exact entry name. 3: Confirm the registry entry's legal authority column cites a statute, regulation, or government-wide policy that requires or permits controls. 4: Check the four prohibited purposes in DoDI 5200.48; if any applies, stop and do not designate. 5: Confirm the information is not classified and is not already public. 6: Check the component's own CUI implementation guidance for a mapping to the entry and for marking instructions. 7: If every check passes, apply the CUI marking and record the category, the authority, and the designator in the document's control record.

When a step fails, the handling is the same: leave the information unmarked, document why, and route the question to the component's CUI point of contact. If someone insists on the marking anyway, write down what authority they cite. A designation without a registry entry is the exact defect that Cuff-style challenges exploit.

Label Precedence and Legacy Markings Trap Experienced Staff

Precedence between classification and CUI is settled: classified information carries classification markings and is outside the CUI program, so there is no scenario where a record is both. The trap is legacy material migrating forward. Old FOUO documents, old "Sensitive But Unclassified" files, and old Law Enforcement Sensitive folders in shared drives often contain information that now maps cleanly to a registry subcategory β€” or that maps to nothing at all.

Build the migration decision into your review. For each legacy-marked file, ask whether the information meets a current registry entry. If yes, remark to CUI and note the entry. If no, remove the legacy label and handle the information as ordinary unclassified material. The migration is a designation decision, not a clerical one, and treating it as clerical is how unverifiable markings survive for years.

Two adjacent facts confuse people at this stage. First, the DoD Freedom of Information Act program under DoD 5400.07 handles release decisions, and CUI is not an exemption from FOIA; it is a control regime that feeds into exemption analysis, which is exactly the issue the Third Circuit examined in Cuff. Second, the Privacy Act of 1974 governs systems of records, and personal information can be CUI under the Privacy category even when no Privacy Act system of records notice applies yet.

Work Through CUI Designation Examples Real Programs Face

The table runs five worked cases through the three gates. The verdict column is the designation answer, and the reason column names the registry entry or the failing gate.

Information in hand Registry entry found Legal driver cited Verdict
Employee medical accommodation request in a supervisory file Privacy, subcategory Health Information Privacy Act and component privacy policy Designate CUI
Vendor's cost breakdown submitted with a proposal Proprietary Business Information, Contract Performance Information Procurement law and regulation Designate CUI
Draft press release about a base construction milestone None matched after search None Not CUI; ordinary unclassified
Internal test schedule with no controlled technical content None matched after search None Not CUI; the marking is invalid
Technical data on a defense article with an active ITAR registration Export Control International Traffic in Arms Regulations Designate CUI

Read the third and fourth rows together. Both feel sensitive to the people who wrote them, and both fail the first gate. The fifth row looks like ordinary engineering data until the registration is confirmed, which is why the authority column matters as much as the category name.

The common thread across the passing rows is that someone can name the entry. If the best available answer is "it's obviously sensitive," the information stays unmarked. That standard is stricter than most people expect, and it is the standard the instruction actually sets.

The Designation Authority Sits With Components, and the Registry Controls the List

Authority and list-keeping are separate jobs, and the separation matters. NARA's Information Security Oversight Office administers the government-wide CUI program and maintains the registry, which means the category list changes at the government-wide level, not at the local level. DoD components designate within those categories and cannot add their own. The DoD CUI Program Office handles DoD-level policy implementation and registry alignment.

That division produces a useful rule for analysts. Check the registry first, then check the component guidance, then designate. When the two conflict, the registry controls the category list and the component's own guidance controls the local process. Neither one gives an analyst authority to invent a category.

The instruction also directs components to establish a self-inspection program for their CUI. That is not busywork. Self-inspection is the mechanism that catches misdesignation before an external review does, and the questions asked are the three gates. If your office has never run one, the designation errors in the filing cabinet are probably not rare.

Why Most Wrong CUI Designations Come From Good Intentions

Wrong designations cluster into recognizable patterns, and almost all of them start with care rather than carelessness. The first is "sensitivity-driven marking": the analyst marks what feels sensitive. The second is "inherited marking": the prior reviewer marked it, so the current reviewer leaves it. The third is "routine-driven marking": the workflow includes a CUI stamp, so every output gets one. The fourth is "convenience marking": CUI slows a release, and slowing the release was the goal.

Each pattern fails the same gate. The third-gate check on classification is usually fine, but the registry-entry check has no answer. When a reviewer asks "which subcategory," the file is silent.

A related failure involves the marking system itself. A hand-typed "CUI" header with the wrong category, the wrong limited dissemination control, or no designation record is not a proper marking even when the underlying information genuinely qualifies. The review standard asks for the designation record, which includes who designated and under which authority.

The most consequential cases are the ones that leave the organization. A contractor who receives a misdesignated package runs NIST SP 800-171 controls over information that never required them, and a mismarked public record can lock out requesters who should have gotten it. Either direction creates cost someone has to absorb.

Handle Spills and Misdesignation When You Find One

A spill happens when CUI is disclosed to someone without the need to know. A misdesignation is the mirror problem: information was marked when it should not have been. Both get handled, and both get documented. Google the answer yourself and you will find general "report it" guidance. DoD guidance is more specific about classification spills, and the CUI program uses analogous logic.

For a spill, contain it, notify the component's CUI point of contact and security office, and preserve records of the incident. The reviewing office determines which registry categories were actually present, which tells everyone what was exposed. That determination relies on the designation records you wrote at marking time, which is one more reason to write them.

For a misdesignation, correct the marking and record the correction. If the misdesignation affected a contractor's system, coordinate through the contracting officer, because the DFARS clause and the NIST SP 800-171 assessment obligations attach to information the government designated. A correction that never reaches the contractor leaves the protection requirement running on a phantom category.

For low-risk internal cases, the fix is documentation and training. For cases involving the privacy or export categories, the notification chain widens. The instruction contemplates annual training for the workforce, which is the mechanism that keeps spills and misdesignations from repeating.

The Costs of Getting Designation Wrong, in Real Numbers

Designation errors are not free, and the invoice has three line items. The first is review labor. Every spill investigation, misdesignation correction, and audit finding consumes staff time that the self-inspection calendar would otherwise claim; an office that spends a week untangling a phantom CUI designation has lost that week from the inspection schedule.

The second is contractor expense. A misdesignated package sends the contractor into NIST SP 800-171 controls, including the assessment obligations triggered for certain defense contractors under DFARS 252.204-7019 and 252.204-7020, and then into corridor and remediation work priced against the inventory of CUI it holds. If the categorization was wrong, the contractor paid for requirements it never had.

The third is the release delay. Information misdesignated as CUI does not get to the requester on time, which produces FOIA backlog and the exact scenario the Third Circuit addressed in Cuff. The cost of the delay lands on the requester, and the credibility cost lands on the program.

The internal-audit arithmetic is worth knowing too. CUI self-inspection programs under DoDI 5200.48 draw on the same reviewing staff who handle classification reviews. Every hour spent clarifying a vague designation is an hour not spent on an inspection that would have caught the designation earlier. Error rates fall when designation records are spot-checked, which is the cheapest intervention in the program.

FAQ

What are the three tests for designating information as CUI under DoDI 5200.48?

The information must fall inside a category listed in the National Archives CUI Registry, a law, regulation, or government-wide policy must require or permit controls for it, and it must not be classified under Executive Order 13526. All three pass or the information stays uncontrolled. A designation that cannot name a registry subcategory fails the first test and is invalid regardless of how sensitive the content feels.

Can a contractor designate information as CUI?

No. Designation authority sits with DoD components and their designated officials, not with contractors. Contractors receive CUI, safeguard it under the applicable FAR and DFARS clauses, and can flow designations down through subcontracts when the government designated the information. A contractor's own internal label, however well intentioned, creates no CUI legal status.

What are the consequences of marking unclassified information as CUI without a registry category?

The marking is a misdesignation, and the information remains ordinary unclassified material. Contractors may have absorbed NIST SP 800-171 assessment and safeguarding costs for information that never required them, FOIA releases may have been delayed illegally, and the marking record cannot be defended in a review. Correct the marking, document the correction, and route through the CUI point of contact.

Does CUI require a specific marking format under DoDI 5200.48?

Yes. A proper marking identifies the information as CUI, includes the category, carries any applicable limited dissemination controls, and links to a designation record. A hand-typed "CUI" header with no category and no designation record does not meet the standard, even when the information under it genuinely qualifies for protection.

How does CUI differ from FOUO and Sensitive But Unclassified?

FOUO and SBU were legacy umbrella labels that the CUI program retired, and neither one authorizes safeguards by itself. CUI is different because each designation traces to a specific registry subcategory with a cited legal authority. Encountering an FOUO or SBU file means deciding whether the information now maps to a current registry entry, not treating the old label as a valid designation.

What should I do if I find information marked CUI but I cannot identify the registry entry?

Treat it as a potential misdesignation and escalate to your component's CUI point of contact before changing the marking. The reviewer will confirm whether a registry entry and legal driver exist. Designation records written at marking time are what make this determination quick; if none exists, preserve the document as found and document the absence.

This article is general educational information about the Controlled Unclassified Information program and DoD Instruction 5200.48. It is not a legal opinion and does not create an official designation determination for any specific document. Designation decisions for actual DoD information should go through your component's CUI point of contact or a locally qualified professional, and current policy should be confirmed against the National Archives CUI Registry and DoD CUI Program Office guidance.