The originator of a controlled unclassified information (CUI) document is responsible for applying the markings and dissemination controls, whether that originator is a Department of Defense (DoD) component, a civilian federal agency, or a contractor generating CUI under a government contract. That responsibility begins at the moment the information is created or received and continues until the information is decontrolled, destroyed, or transferred with proper markings intact. No downstream holder may strip a marking; only the designated original classification authority (OCA) or the agency's CUI office can change or remove the designation.
The question sounds bureaucratic but the answer has real operational teeth. A wrongly marked document can leak sensitive information. An over-marked one can break information-sharing that a mission depends on. This explainer follows the responsibility chain from creation to destruction, the regulatory basis behind it, the edge cases that trip up even experienced program staff, and the concrete steps that a compliance officer should take.
Mechanism: the originator owns the marking, and the chain never breaks
The governing rule is set out in 32 CFR Part 2002, the National Archives and Records Administration (NARA) regulation implementing Executive Order 13556 on CUI. NARA's CUI program states plainly that the authorized holder who creates or receives CUI is responsible for marking it. In DoD practice the same rule is stated in DoD Instruction 5200.48: the originator applies the CUI marking before the document leaves its control.
The reason it works this way is architectural. CUI categories are defined by a government-wide CUI Registry, but each category is legally owned by a specific agency that sets the marking and dissemination rules. If responsibility shifted to a downstream holder, that holder would need to know every agency's rules. Instead the originator, who already knows which authority applies, does the work once and every subsequent holder inherits an intact marking.
Doctrine draws a sharp line between designation and marking. Designation is a legal act: an authorized official decides that specific information falls into a CUI category and sets the dissemination controls. Marking is the administrative act of applying the required banner, category, and control indicators. On a single document, the same person usually performs both; in a large organization, a designated CUI office designates and trained staff mark. Either way, the authority flows only one direction, from the agency down through the creator to every holder.
The core principle is that marking is a legal assertion, not a clerical courtesy. A missing banner or a wrong dissemination control is a designation failure, not a formatting failure. That is why DoD treats CUI violations as a security incident and not as an editing error.
Quantified context: how big the responsibility surface really is
The CUI program is large. The CUI Registry lists roughly 70 categories and about 125 subcategories of controlled unclassified information, spread across more than 20 federal agencies that own one or more categories. Each category carries its own marking rules, which means an originator's exact obligations depend on which subcategory applies.
Marking obligations are the most frequently reported compliance gap across federal agencies and defense contractors. In DoD, the Defense Contract Management Agency (DCMA) reviews contractor CUI programs, and CUI marking deficiencies are among the most common findings in those reviews. The NARA CUI program reviews agency marking practices and has repeatedly flagged inconsistent marking as the weak point in implementation.
The reason the numbers matter is scale of exposure. Every document, drawing, training slide, spreadsheet, and email attachment that contains CUI is a marking event. A mid-sized defense contractor processing a few hundred CUI items per week faces tens of thousands of marking decisions per year. One unmarked page that reaches the wrong recipient is an incident, regardless of how many correctly marked pages exist.
The system reached its current form in 2010, when Executive Order 13556 established the CUI program. The implementing regulation, 32 CFR Part 2002, became effective on September 14, 2016. DoD adopted its own implementing instruction in 2020, with full implementation expected across the department by the end of 2022. NARA's CUI training requirement applies to all federal employees and contractors who handle CUI, with annual refresher training; DoD's parallel requirement is annual too.
That regulatory timeline matters because older documents, marked under the predecessor system, may not carry CUI markings. Legacy markings persist until the document is re-reviewed. An originator inheriting an old document under a legacy marking still owns the responsibility to re-mark it correctly when it is next used.
Edge cases: where the originator rule gets complicated
The clean rule has several exceptions that cause most of the confusion in practice.
First, derivative documents. When a holder incorporates CUI from a source document into a new document, the new creator becomes the originator of the derivative and must apply markings that reflect the source's controls. The derivative cannot be marked less restrictively than its most restrictive source. This is the rule that catches analysts who pull a paragraph from a CUI-No Foreign Dissemination document into a new brief and mark it only CUI.
Second, government-furnished information. When the government provides CUI to a contractor, the government is the originator of that information. But the contractor becomes responsible for preserving the marking on everything it generates from that information. A contractor that reformats a government-provided CUI document into a new template must carry the markings forward; the template's design does not excuse the omission.
Third, joint documents. When multiple agencies produce a joint document, the agencies coordinate the designation, and each agency typically applies an agency-specific marking to CUI it contributed. The lead agency sets the overall banner. Joint documents are a common site of over-marking and mixed controls.
Fourth, recipient obligations. Every authorized holder is responsible for adhering to the marking and dissemination controls on a document. A recipient cannot forward a CUI-No Foreign Dissemination document to a foreign national, even if the recipient believes the restriction is overbroad. The remedy is to ask the originator for a change, not to ignore the marking.
Fifth, decontrol and remarking. Only the originator (or the CUI office with authority over the category) can decontrol a document. A holder who believes a document no longer merits CUI must request decontrol, not decide unilaterally. Once decontrolled, the document should be re-marked or rendered unmarked, and the decontrol action documented.
Sixth, emails and conversations. A CUI email must itself carry a marking, and the marking should appear in the subject line and body. Verbal discussions of CUI are handled under agency policy rather than markup, but the responsibility to keep the conversation within authorized channels remains.
One counterintuitive point: a contractor employee is often the originator for marking purposes even though the government owns the information. The responsibility is about the act of creation, not the underlying ownership. Contractors on defense programs frequently hold the designation authority delegated by the contracting officer, and some assume the responsibility is always the government's. It is not.
Misconceptions: five common wrong answers
Several intuitive answers to the responsibility question are wrong, and each has consequences.
One misconception is that the receiving organization marks the document because it has the local security officer. In fact, the local security officer can advise, audit, and correct markings, but cannot originate them. A document arriving unmarked stays an incident even if it is corrected on receipt.
A second is that the classification authority is the only relevant authority. CUI designation sits with authorized officials who are not necessarily OCAs. A contractor's facility security officer is rarely an authorized CUI designator.
A third is that IT systems or automated tools apply markings. Tools can stamp banners and help enforce insertion, but the legal act is the originator's. A tool that auto-marks wrong is the originator's failure to configure and verify.
A fourth is that marking ends when the document is transmitted. Recipients must maintain markings, and any re-transmission or reproduction requires the marking to survive.
A fifth is that oral briefings are unregulated. Policies commonly require that verbal presentations containing CUI be delivered under controlled conditions and that slides carry markings.
Any document containing CUI must carry the required banner at the top and bottom of every page. The CUI category indicator and the specific dissemination control (such as No Foreign Dissemination) must be shown in the header or footer, not just in the body. Every email containing CUI must be marked in the subject line and body. Re-marked or derivative documents must be marked at least as restrictively as the most restrictive source. Markings must survive transmission, storage, and reproduction; a copy without markings is a violation. The originator or the agency CUI office must approve any decontrol or change of dissemination controls.
Comparison table: who does what in the responsibility chain
| Role | Responsible for applying markings? | Responsible for designation? | Can remove or change markings? |
|---|---|---|---|
| Original creator or originator | Yes, before release | Usually, if designated | Yes, through the CUI office |
| Downstream authorized holder | No, but must preserve them | No | Only by requesting decontrol |
| Contractor with delegated authority | Yes, for documents it generates | Usually, under contract terms | Only with government approval |
| Facility or local security officer | No | No | Can audit and flag, not originate changes |
| Agency CUI office | Yes, for agency-originated documents | Yes | Yes |
| IT system or email tool | Enforces and stamps, does not originate | No | No |
The table shows the practical division. Designation and mapping authority sit with the agency and its designated officials, flow to the originator, and bind every subsequent holder. The audit and correction role sits with security staff, but correction still runs back through the originator.
Timeline table: a document's responsibility path
| Stage | What happens | Who is responsible | Typical timeframe |
|---|---|---|---|
| Creation | Content is drafted and identified as containing CUI | The originator | At the moment of creation |
| Designation | Category and dissemination control are set | The authorized designator or CUI office | Before release to any holder |
| Marking | Banner, category indicator, and controls are applied | The originator | Before transmission |
| Transmission | The marked document moves to authorized holders | The originator (sender) and the system | Before receipt |
| Holding and use | The document is used, stored, and reproduced | Each authorized holder | Throughout the document's life |
| Re-use or derivative | New content incorporates the CUI | The new originator | At the moment of the new draft |
| Review | The originator reassesses the need for CUI | The originator or CUI office | At scheduled review |
| Decontrol or destruction | Marking is removed and the document is handled accordingly | The originator or CUI office | At the authorized end point |
Each stage has a responsible owner. The transitions are where failures cluster. The handoff from marking to transmission, and from use to re-use, are the two places where training most often says the responsibility "belonged to someone else."
Practical actions: a concrete compliance sequence
For an organization that handles CUI, the following steps turn the responsibility rule into a workable routine.
Step one is to identify every role that creates or receives CUI and confirm who holds designation authority. Map the CUI categories your organization actually handles, then confirm which office in the originating agency owns each category. The mapping takes a few hours and prevents most marking errors.
Step two is to write the rule into the workflow: no CUI document leaves the originator's control unmarked. A two-person check at release, or a system-enforced banner requirement, catches the gap. Organizations that have implemented a release checklist report catching the majority of marking gaps before transmission.
Step three is to train the people who mark, not just the people who administer. The NARA and DoD annual training requirements cover all CUI handlers; supplement that with a one-hour practical session on your own document types. The practical session matters more, because generic training does not cover your agency's specific category indicators.
Step four is to run a quarterly self-audit of a sample of created and received documents, checking for required banners, category indicators, dissemination controls, and surviving markings on derivatives. A sample of 30 documents per quarter is enough to reveal systematic gaps; larger samples add detail, not new issue types.
Step five is to build a decontrol request path that routes to the originator or agency CUI office, not to a local decision-maker. Every request should be logged with the document, the requester, the decision, and the date.
Step six is to treat any unmarked CUI finding as an incident, with the same reporting path as a security violation. Reporting discipline is what keeps the originator rule from becoming a paper rule.
A useful threshold: if a single reviewer cannot trace a document's marking to its originating authority within a few minutes, the organization's designation map is out of date and should be rebuilt.
Limitations: what this framework does not resolve
The originator rule is unambiguous in principle, but several real limits remain.
First, the CUI Registry is not uniform. Each agency interprets its own categories, and the marking indicators differ in wording and format. A document transferring between agencies may undergo re-marking, and the responsibility during that transition can be genuinely unclear in practice.
Second, legacy markings and older documents predate the current program. The responsibility to re-mark when the document is next used is clear, but nothing forces a re-review until then. Organizations holding archived material can carry inconsistent markings indefinitely unless they schedule a review.
Third, delegation in contracts can be ambiguous. Contractors sometimes assume designation authority the government never actually delegated. Reviewing the contract's terms and the contracting officer's delegation letter is the only reliable test, and those reviews are irregular in practice.
Fourth, the regulatory language is stable, but agency implementation guidance changes on its own cycle. Marking examples and category wording can shift between guidance versions. Organizations should confirm against the current CUI Registry and their agency's current implementing guidance rather than relying on a training example.
Fifth, this explainer describes the framework and not any specific obligation under a particular contract or agency rule. Individual programs can impose stricter requirements than the baseline.
This article is general educational information about the CUI marking framework, not a legal opinion or a compliance determination for any specific document, contract, or agency. It does not replace the governing regulation, the current CUI Registry, or agency-specific implementing guidance. Readers with a specific marking or dissemination question should consult their designated CUI office, a qualified attorney, or their agency's security office.