"Information may be CUI in accordance with" is the sentence often printed in a Department of Defense contract or solicitation to flag that controlled unclassified information (CUI) may appear, with the governing authority to be named elsewhere. Treat the phrase as a pointer, not a designation. It tells you the contract might contain CUI and sends you to the specific CUI category or marking guide—most often DFARS 252.204-7012 or a DoD CUI registry entry—rather than declaring anything CUI on its own.
The phrase is a pointer, not a CUI designation
The words describe a conditional. Something may be CUI. The authority is in accordance with a named rule or contract clause. Neither half classifies the material in front of you.
Real CUI designation happens through an approved category listed in the National Archives CUI Registry, applied by a government-designated CUI authority under 32 CFR Part 2002, the federal CUI rule that took effect in 2017. A banner reading "CUI" plus the category marking—"CUI//SP-PRVCY" for privacy, for example—is the actual designation. The "may be" sentence carries none of that weight.
Practically, that means you can't read the phrase and start marking legacy documents with a CUI banner. You need the category. DoD's own CUI training materials make the point bluntly: markings must reflect an authorized category, and "may contain" language in a contract does not authorize any specific marking.
The phrase shows up most in pre-award and legacy contract language, where a contracting officer has to acknowledge the possibility of CUI without knowing yet which category applies to deliverables. That is why the sentence trails off into "in accordance with" rather than finishing the thought. If you are the contractor, your first move is to find where that sentence is completed—usually in a separate CUI marking exhibit, a DD Form 1423 for data items, or a clause incorporated by reference.
Where DoD contracting officers most often place the sentence
You will see it in Section C performance work statements, Section H special contract requirements, and attachment cover sheets. The DoD CUI Program Office's marking guide—managed by the Washington Headquarters Services—expects CUI to be identified by category, not by a generic warning phrase.
A 2023 DoD Inspector General audit of CUI implementation across six DoD components found inconsistent CUI identification in contracts, with some components relying on generic "may contain" language rather than category-specific marking. That finding matters here: generic phrasing is exactly the gap auditors flagged, because it gives contractors no actionable category to protect.
| Document location | Typical wording | What it actually tells you |
|---|---|---|
| Section H, special requirements | "Information may be CUI in accordance with DFARS 252.204-7012" | Safe-handling expectations exist; category comes from the marking exhibit |
| Statement of Work attachment | "May contain CUI in accordance with the DoD CUI Registry" | You must look up the category yourself |
| DD Form 1423 data item | "CUI may apply in accordance with [category]" | The category is named; this is closer to a real designation |
| Email from contracting officer | "Treat as CUI in accordance with…" | Not a valid category marking; ask for the authorized category in writing |
The table row that matters most is the DD Form 1423—when the category is named on the form, you have something to work with. When it isn't, you don't.
Reading the authority clause without guessing at the category
The "in accordance with" half of the sentence points to one of four authorities. Identify which one before you do anything else.
1: DFARS 252.204-7012. Applies to DoD contracts; requires safeguarding of covered defense information and 72-hour incident reporting under the clause. Note: the clause covers covered defense information, a term the DoD is transitioning toward CUI alignment—the DoD's own CUI transition guidance sets a target of full CUI alignment across the department, tracked through the DoD CUI Program Office. 2: 32 CFR Part 2002. The government-wide rule; applies when the contract is non-DoD or when the agency's CUI policy cites it. 3: An agency-specific CUI policy. The Department of Energy, for example, has its own CUI directives that layer on top of the federal rule. 4: A specific CUI registry category. Category codes like CTI (critical infrastructure), EXPT (export controlled), or PRVCY (privacy) each have their own safeguarding requirements in the registry.
Read the clause number first. If DFARS 252.204-7012 is cited, you're in DoD territory, and the clause's definition of covered defense information controls until the DoD's CUI transition completes. If 32 CFR 2002 is cited, the agency's CUI policy controls, and your safeguarding obligations follow the registry category, not the clause.
The legacy transition gap: covered defense information versus CUI
This is where contractors most often get the designation wrong. DFARS 252.204-7012, issued in 2015, uses "covered defense information." CUI, as a formal category system, arrived with 32 CFR Part 2002 in 2017. The DoD has been transitioning from one to the other since, and the phrase "may be CUI in accordance with" is a symptom of that overlap.
The DoD's CUI transition plan—announced through the DoD CUI Program Office—intends to replace CDI references with CUI category markings, but the transition is not complete across all contract vehicles. Until it is, a contract can legitimately cite both frameworks, and your obligations may be determined by whichever one is more restrictive for the data at issue. That's a judgment call, and it's one worth getting in writing from the contracting officer.
The failure case is concrete. A contractor receives a work statement saying "information may be CUI in accordance with DFARS 252.204-7012," treats the phrase as a full CUI designation, applies a CUI banner with no category, and stores the data on a system that doesn't meet the clause's safeguarding requirements. An assessment finds unmarked CUI and inadequate protection. The contractor's defense—"the contract said it may be CUI"—doesn't hold, because the clause required safeguarding of covered defense information regardless of whether a banner was applied. The lesson: the clause imposes obligations whether or not the "may be" sentence was ever resolved into a category.
What "may be" obligations look like on a real deliverable
Take a typical deliverable: a technical report under a DoD research contract. The statement of work says "information may be CUI in accordance with DFARS 252.204-7012." The DD Form 1423 for that report lists no category marking. What do you do?
First, treat the report as potentially CUI during drafting—don't put draft content on unapproved systems—until you confirm the category. Second, check whether the underlying data is export controlled (EXPT) or critical infrastructure related (CTI) by asking the technical point of contact. Third, if the category is confirmed, mark the document with the banner and category marking per the DoD marking guide, and record the designation in your CUI register.
Record-keeping matters. The CUI registry's requirements under 32 CFR 2002 include documenting the designation basis for CUI in your possession. If you can't name the category and the authorizing official, you can't show the designation was lawful—and that's the exposure auditors care about most.
Distinguishing the phrase from a banner, a category, and a register entry
These four things get conflated constantly. The table separates them.
| Element | Example | Who creates it | Legal effect |
|---|---|---|---|
| "May be CUI" phrase | "Information may be CUI in accordance with…" | Contracting officer in solicitation | None by itself; signals possibility |
| CUI banner | "CUI" at top and bottom of page | Designated CUI authority | Marks the document as CUI |
| Category marking | "CUI//SP-PRVCY" | Designated CUI authority | Tells you which registry category and safeguarding rule applies |
| Registry entry | Privacy data logged in agency CUI register | Agency CUI program office | Documents the lawful basis for designation |
Only the banner-plus-category combination and the register entry carry actual designation weight. The "may be" phrase is upstream of all of them.
A common misuse: someone sees the phrase on a legacy contract, applies a CUI banner to everything in the file room, and creates a de facto classification system that the agency never authorized. That's over-marking, and the CUI rule explicitly disfavors it—over-marking degrades the system as surely as under-marking. If you find yourself marking broadly because of a "may be" sentence, stop and get the category in writing.
Failure modes when the phrase is misread
Three failures recur.
Over-marking. Covered above, but the cost is real: over-marked documents slow information sharing and can make the CUI system appear unreliable. If your team banners everything because the contract had a "may be" sentence, the banners lose meaning.
Under-marking. The reverse: treating the phrase as boilerplate, ignoring it, and never resolving the category. If CUI is later found in unmarked documents stored on unapproved systems, the "may be" sentence becomes evidence that you were on notice. Notice is exactly what the phrase is designed to create.
Wrong-category marking. Marking privacy data as export controlled, or vice versa, routes the data to the wrong safeguarding rules—and if the error reaches a foreign disclosure, it can implicate export control law. The registry categories are distinct, and the marking guide's category codes are the authority.
Each failure has the same antidote: resolve the category with the contracting officer or the technical point of contact before marking, and document the resolution.
Asking the contracting officer the right question
You want a written answer that names the category and the authority. A request that works looks like this:
"Section H of [contract number] states 'information may be CUI in accordance with DFARS 252.204-7012.' Please confirm the CUI category or categories applicable to deliverables under CLIN [X], and the authorized marking for each. If the covered defense information definition governs, please confirm that as well, given the DoD CUI transition."
That last sentence acknowledges the transition and puts the CDI-versus-CUI question on record. Contracting officers who are up to date on the transition will answer it; those who aren't may refer to the CUI program office. Either answer is better than a guess.
Ask early—during proposal or at contract award—not after a deliverable is in draft. The phrase usually sits in documents you have at award, and the category confirmation is fast when requested up front.
Safeguarding duties attach to the category, not the phrase
The safeguarding requirement you must meet is set by the category and the clause, not by the sentence. DFARS 252.204-7012 requires implementation of the security requirements in NIST SP 800-171 for covered defense information—110 controls, across 14 families, as published by NIST. That's the operational reality behind the "in accordance with" phrase: if the category resolves to CUI covered by that clause, you owe the 800-171 controls, incident reporting within 72 hours, and flow-down of the clause to subcontractors handling the data.
If the authority is 32 CFR Part 2002 for a non-DoD agency, the agency's CUI policy sets the safeguarding rules, and they vary by agency. Don't assume NIST 800-171 applies; check the agency policy.
The phrase "may be CUI" in the clause context is a notice of potential obligation. The obligation itself is concrete: controls, reporting timelines, flow-down. A contractor who reads the phrase as a formality and skips the controls is the failure case described earlier.
FAQ
Does "may be CUI" mean the information is already CUI?
No. The phrase signals possibility, not designation. Actual CUI requires an approved category from the National Archives CUI Registry and a marking applied by a designated authority. Until the category is named and the marking applied, the material is potentially CUI—not CUI.
If my contract cites DFARS 252.204-7012, am I obligated even without a CUI banner?
Yes. The clause imposes safeguarding and incident-reporting obligations for covered defense information regardless of whether a banner was applied. The "may be CUI in accordance with" sentence creates notice; the clause creates the duty. That's why ignoring the phrase because no banner appeared is the classic under-marking failure.
How does the DoD CUI transition change what the phrase requires me to do?
The DoD is moving from "covered defense information" to CUI category markings, and the transition isn't complete across all contract vehicles. Until it is, a contract may legitimately cite both frameworks, and the more restrictive one can control for a given data set. Ask the contracting officer which authority applies to your deliverables.
Can I mark a document with a CUI banner if the contract just says "may be CUI"?
Don't. Marking requires an authorized category and a designated authority. Applying a banner based on a "may be" sentence creates an unauthorized marking, which is over-marking—disfavored under the CUI rule and functionally harmful to the system. Get the category in writing first.
What's the difference between "may be CUI" and "CUI//SP-PRVCY"?
The first is a conditional sentence in contract language with no legal marking effect. The second is a real designation: banner plus category marking for privacy data, governed by the registry category's safeguarding rules. Only the second tells you what category and what controls apply.
How quickly must I report an incident involving information covered by the phrase?
If DFARS 252.204-7012 applies, report within 72 hours of discovering the incident, per the clause. The phrase "may be CUI in accordance with [that clause]" puts you on notice of the clause, and the clause's reporting timeline controls regardless of whether the specific data was marked.
Is "may be CUI in accordance with" boilerplate I can ignore?
No. Even when it appears in legacy contract language, it creates notice of possible CUI, and ignoring it is the under-marking failure auditors cite. Resolve the category with the contracting officer, record the answer, and mark only per the confirmed category.
This article is general educational information about CUI marking language and is not a legal opinion or compliance determination. CUI obligations vary by contract, agency, and category—consult your contracting officer and a locally qualified attorney or compliance professional for your specific situation. If you're facing an active incident involving controlled information, follow your contract's reporting channel and agency incident procedures immediately.