If you e-mail controlled unclassified information (CUI), three markings are required: the CUI banner marking at the top of the body, the category abbreviation inside that banner, and a portion marking on every section, paragraph, or graphic that carries CUI. The destination e-mail address and file name get the same banner. Miss the portion marking and the document is noncompliant even if the banner is perfect.
The controlling source is the National Archives and Records Administration's implementing directive for 32 CFR Part 2002, issued September 14, 2016, plus the CUI Registry that NARA maintains. Your agency's or contract's marking guide can add requirements on top. It cannot subtract these three.
This article covers where each marking lands in an e-mail, what the banner looks like, why the old FOUO habit now fails, how the rules compress for CUI that has been decontrolled or for legacy documents, and where agencies most often slip.
The CUI Banner Goes at the Top of the E-mail — and It Must Match the Body Exactly
The banner is the line that begins with "CUI" and carries the category or categories in parentheses. For a single category, it reads CUI followed by the abbreviation in parentheses — for example, CUI followed by the privacy abbreviation in parentheses. For multiple categories, they appear alphabetically inside one set of parentheses, separated by commas.
In an e-mail, that banner sits at the top of the message body, on its own line, above any salutation. If the e-mail carries a complete CUI document as an attachment, the body banner still appears when the body itself contains CUI. When the body is entirely free of CUI and the attachment is marked, you mark the attachment and the e-mail subject line.
The banner's job is to tell a reader, at a glance, that the message contains controlled information and which categories apply. That's why the category list inside the parentheses must match the body exactly. A banner that says one category while the text carries two is a marking error under NARA's directive, and it's one of the errors auditors look for first because it's easy to check.
Add a limited dissemination control when e-mail goes outside your organization. Contractors handling Department of Defense work add the distribution statement A through F, per DoD Instruction 5200.48. If your organization adds a control such as NOFORN or a contractor-specific legend, it goes in the banner after the category list.
The banner appears on every page of a printed CUI document and on the first page of an e-mail body. A short reply e-mail that quotes CUI text inherits the banner. A one-line acknowledgment that names no controlled content does not.
The Category Abbreviation Is the Marking Most People Get Wrong
The abbreviation inside the banner comes from the CUI Registry. It is not free text. Privacy appears as the privacy abbreviation, proprietary business information as the proprietary abbreviation, and so on. Guessing at an abbreviation isn't optional formatting — a wrong abbreviation is a marking violation under the 32 CFR Part 2002 implementing directive.
Each abbreviation represents a category approved by NARA and, typically, a controlling agency. That matters because the same information can travel under two categories with different abbreviations. Export-controlled technical data and a contractor's proprietary design for the same part may carry different registry categories and different abbreviations, and both appear in the banner if both apply.
Watch the common slip: people write CUI and leave the parentheses empty. NARA's marking guidance treats a bare banner as incomplete because it tells the recipient nothing about which category applies or who controls it. An empty parenthesis pair is worse than useless — it signals that someone marked the document without knowing why.
Contract documents sometimes bury a category list in the body. If the contract, security classification guide, or DD Form 254 lists applicable categories, those define the abbreviation you use. When in doubt, the controlling agency's CUI Registry entry wins over local habit.
The banner shows the abbreviation; the body shows the portion marking, and those two have to agree. An e-mail with a privacy banner and paragraphs marked for proprietary information is mislabeled and should be corrected before it leaves your outbox.
Every Paragraph, Bullet, and Graphic Carries a Portion Marking
Under the implementing directive, CUI must be marked at the portion level — each section, paragraph, bullet, table cell, and graphic carries a parenthetical marking noting the category. The standard form is the abbreviation in parentheses at the start of the portion. A paragraph marked with the privacy abbreviation begins "(Privacy)" and, where space allows, the full term.
Graphics, charts, and images carry the marking too. NARA's guidance allows marking a graphic with a caption or a callout line when the image itself can't carry text, but the marking has to exist somewhere a reader can see it. Pasted into an e-mail, that means either a caption line under the image or a marking line in the body that identifies the graphic.
The portion marking is where most real-world e-mail failures happen. People mark the banner and stop. An e-mail with a CUI banner and unmarked paragraphs fails a self-inspection, and a reviewer who finds one unmarked paragraph can't tell whether it's truly uncontrolled or the author got lazy. Either way, the whole thread becomes suspect.
Multiple categories in one paragraph get marked together — both abbreviations in the same parenthetical. Classification markings follow a different syntax with "(U)" and "(C)", so don't port that habit into CUI work. Portion markings answer the question "why is this controlled?" for each piece of text, and they do it without the reader needing the banner.
If portion marking everything is impractical, the fallback is a cover marking that applies the banner to the entire document, which NARA permits for some formats. An e-mail thread is not one of those formats in most agencies' guidance. Mark the paragraphs.
The E-mail Subject Line and File Name Carry the Same Banner
The header of a CUI e-mail — or the subject line — gets the banner marking according to your agency's marking guide. NARA's guidance points organizations to their own implementation for e-mail headers, and most federal agencies require the banner in the subject. Put it first: the subject starts with the CUI banner, then a colon or a dash, then the topic.
Attachments carry their own markings. An attached CUI file needs a banner on the first page or top of the document, portion markings throughout, and the banner in the file name or in the cover note. DoD components vary in whether they require the banner in the file name, so confirm the local marking guide before you rename anything.
What if the attachment is a form with no room for a banner? Add a cover page or a marking line at the top of the form. Short text files and scripts still get a banner line. Calling a file "unmarkable" isn't a category the directive recognizes.
Beware of the attachment that inherits nothing. A CUI slide deck pasted into a new e-mail loses nothing — the slides carry their own markings — but a CUI paragraph copied into a new plain-text e-mail inherits everything, including the obligation to add a banner and a portion marking. Copying text out of a marked document strips the markings. That's not a loophole; it's the classic error.
CUI Is Not FOUO, and That Tripwire Is Where Old Habits Fail
Before November 2016, For Official Use Only was a catch-all for unclassified-but-sensitive information. When 32 CFR Part 2002 took effect, FOUO was retired as a government-wide marking. The 2016-11-14 effective date of the final rule marked the divestment, and NARA's CUI Registry replaced FOUO with specific categories and specific markings.
That transition turned lots of old templates into land mines. If your team still marks emails with FOUO, the marking says the content predates the CUI program and possibly was never correctly categorized under a registry category. Either way, the e-mail doesn't match the current marking scheme.
Some government agencies still use legacy markings for specific categories. In DoD work, for instance, the old distribution statement scheme coexists with CUI markings in ways that local guides explain. That nuance is exactly why the safest move is to read the appendix or marking guide from the controlled agency or your security office.
Common pre-2016 habits that no longer fit: writing FOUO in the banner, using "Sensitive But Unclassified" or SBU as a banner category, and marking only the cover page. The current standard replaces all of those with registry categories, an abbreviation inside the banner, and portion markings throughout.
If the document came in under a legacy marking, don't silently rebadge it. Check whether it's actually in the CUI Registry, get the correct category from the controlling agency, and re-mark only under guidance. Marking without authority is its own problem.
The Official Registry Is the Only Legitimate Source for Category Names
NARA's CUI Registry is the authoritative catalog of categories, abbreviations, and controlling agencies. Each entry names the category, the abbreviation that appears inside the banner, the agency that controls it, and links to the implementing guidance for that category. You use it to build a banner — not memory, not habit.
Try a concrete case. A personnel privacy record goes in the banner under the privacy abbreviation, and each paragraph bearing personal data gets a privacy portion marking. A proprietary engineering report from a contractor gets the proprietary category abbreviation, with the business-information portion markings on the paragraphs containing that data. Both categories appearing in the same e-mail requires both abbreviations in the banner, comma-separated, in alphabetical order, and no portion marked with only one.
Registry entries also carry the marking fields the controlling agency cares about. For ITAR-controlled technical data, the international traffic in arms regulations' framing applies through the registry entry, and the marking line often needs the addressee-specific control. For DoD CUI, the local marking guide cross-references instructions and DD Form 254 requirements.
When a category can't be found in the registry, stop. The fallback is the controlling agency's designated CUI office, not a best guess at an abbreviation. NARA's own e-mail is the designated channel for registry questions, phrased as a marking question and traced to the agency that controls the category.
Your security officer can also route the question. The Registry exists precisely so the answer is written down somewhere traceable, and using it is a work step, not a preference.
Before You Hit Send: A Nine-Point Checklist for the E-mail Marking
Run this before sending. It's built directly from the directive's marking obligations and takes about a minute on a normal e-mail.
1: Confirm the information has an active CUI category and you have dotted the taxonomy to a Registry entry. 2: Type the banner first — CUI in capitals, categories in parentheses, alphabetical, comma-separated. 3: Match the banner to the body: one category or all categories, never fewer. 4: Add portion markings on every paragraph, bullet, and table row that carries CUI; parenthetical abbreviation at the start. 5: Mark graphics with a caption line or a marking paragraph pointing to the image. 6: Banner the subject line of the message following your agency's marking guide. 7: Check any attachment — first-page banner, portion markings, acknowledgement in the cover note. 8: Check the recipient list against need-to-know and the dissemination controls; add NOFORN or distribution statements only per the controlling guide. 9: Send — the sent item keeps the marking, and replies inherit it.
Failure handling: if you catch a missing portion marking after sending, re-send the corrected version and ask the recipient to delete the original. If you catch the missing marking before the recipient opens it, most enterprise clients support a brief recall. Neither move is a substitute for doing the check — recalling an unmarked CUI e-mail doesn't unseat the recipient.
The highest-risk e-mail is the smallest one. A three-line reply pasted from a CUI document with no markings is the file most likely to sit in a personal mailbox for a year.
Marking Patterns That Work for Decontrolled and Legacy Material
Decontrol has its own marking. When a category no longer applies — an expiration passed, a controlling authority released the document, or the information never should have been marked — the marking becomes CUI with the notation "Decontrolled" attached to the applicable portion and to the legend. NARA's guidance allows the marking "CUI//Decontrolled" on released portions, and the associated notice or legend should name the release basis.
That notation matters because it's the only way a recipient knows the content was once controlled and the release was authorized. Without it, decontrolled content reads like mislabeled CUI. With it, the record shows what happened.
A worked example: a contract deliverable had a proprietary portion that expired under the contract's data-rights terms. The paragraph is re-marked with the decontrol notation attached and a release legend, and the rest of the document keeps its proprietary marking. The decontrolling authority is the controlling agency — here the contracting officer's designated POC — not the person who wants the shelf cleared.
For legacy documents that predate the CUI program, don't rebadge without the agency's guidance. A pre-2016 document marked FOUO is not automatically CUI, and the reverse is also true: a document under legacy markings is inspected against its own regulation, not the current one. The safe move is the CUI office or security officer, asked about the specific document.
One more grey zone: the e-mail that discusses a CUI document without quoting it. That's not automatically CUI. Decide by category, not by topic, and if you can't decide, route the content through the channel that can.
Which Actions Never Require a CUI Marking
The e-mail that names only a document ID and a control number and asks for a status update isn't CUI. Neither is a one-line reply that says "received, working on it." Apply the registry test: does the text reveal information in a registry category? A number in a subject line without context typically doesn't, but a project nickname or case number tied to a specific person might.
The subject line is the classic under-the-radar case. If the topic itself reveals the controlled information — say, a personnel matter naming a person or an investigation identifier — the subject needs the banner too. If the subject is "Q3 report timing," it doesn't. When the subject line matters, it's because it leaks, and leaking is not an administrative formality.
Attachments that support the message — a schedule, a timeline — get marked if they contain CUI. A PDF that reproduces a CUI table is a CUI document. The message text wrapping it can be unmarked if it clears the registry test.
The practical rule from NARA's guidance: mark what carries the content, not what mentions the content. When your agency's guide goes further, follow the agency. The registry is a floor for the federal executive branch, and local tables exist precisely because additional markings come from specific authorities.
FAQ
Is it a violation to e-mail CUI without a banner in the subject line?
It depends on your agency's implement of 32 CFR Part 2002 — NARA's directive sets the banner requirement, but e-mail header practice lives in agency marking guides, and most require the subject banner. A missing subject banner more often flags a local noncompliance than a federal one. Ask your security or information office which line applies to your e-mail system.
Can I mark a whole e-mail with one banner and skip portion markings?
No — the portion marking is required by the implementing directive, and a banner alone gives the reader no way to identify which lines are controlled. Portion markings start each affected paragraph with the category abbreviation in parentheses. Graphics get captioned or explained by a marking line.
What number of categories can go in a single CUI banner?
There's no numeric cap in the directive; the banner carries every applicable category, alphabetically, comma-separated inside the parentheses. A three-category e-mail has three abbreviations in one banner. The matching burden is to keep every portion marked correctly so no category is silently dropped.
I received a CUI e-mail in a personal mailbox by mistake — what now?
Don't forward it, don't reply from the personal account, and notify the sender or your security officer. NARA's guidance on marking is what keeps a record recoverable, and a misdirected e-mail can be re-sent with corrected recipients. Your agency's incident procedures govern deletion and documentation — don't improvise them.
How is CUI marked differently from "For Official Use Only"?
FOUO was retired as a government-wide marking when the CUI program took effect with the September 2016 final rule, and its replacement is the CUI banner with a registry category abbreviation. FOUO content was not reclassified or renumbered; it was re-tagged under specific categories. Legacy FOUO documents are handled under their own regulations, not by relabeling.
Does an outgoing CUI e-mail with multiple recipients need a dissemination control?
Sometimes. DoD Instruction 5200.48 adds distribution statements A through F for DoD CUI, and NOFORN appears when the controlling guide requires it. Most civilian agency e-mails instead handle dissemination through need-to-know and the banner. Check your agency's guide before adding a control that isn't required — an unauthorized legend is also a marking error.
How should decontrolled portions be marked so recipients know they're no longer controlled?
Attach the notation "Decontrolled" to the applicable portion and the legend, and confirm the release basis with the controlling authority. NARA's marking guidance permits a CUI//Decontrolled legend on released portions. Decontrol is a documented act by the controlling agency — writing decontrolled on a paragraph without that authority doesn't decontrol anything.
This article is general educational information about federal CUI marking practice and is not legal advice, an agency policy determination, or a substitute for your organization's controlled unclassified information guide. Marking authority varies by agency, contract, and registry entry — verify with your security officer, designated CUI office, or legal counsel before relying on any marking scheme. Unmarked or misdirected CUI should be reported through your organization's incident channels.