CUI documents must be reviewed according to the procedures in 32 CFR Part 2002, the National Archives rule implementing the CUI Program, layered on each agency's CUI implementing directives and its approved CUI policy. In practice that means a lifecycle review: designation, safeguarding, decontrol, and self-inspection, each tied to specific triggers, timelines, and accountable officials rather than a single annual check.
That answer works as a standalone snippet, but it compresses a genuinely layered system into one sentence. The regulation sets a floor. Agency directives set the ceiling. Contract clauses and system security plans fill gaps in between. Understanding which procedure applies, and when, is the difference between a compliant review and a review that merely looks like one.
This explainer walks through the mechanism, the timelines, the edge cases practitioners actually hit, and the audits that find failures. Plain version: CUI review is a system of scheduled and event-triggered checks, not a checkbox.
The Review Mechanism: Triggers, Roles, and the Two-Track System
The CUI Program replaced the old patchwork of Confidential, For Official Use Only, Sensitive But Unclassified, and dozens of legacy markings. Executive Order 13556 established the program in 2010, and 32 CFR Part 2002 made it enforceable across executive branch agencies (National Archives, 32 CFR Part 2002). The review obligation sits inside that regulation, but it is distributed across several distinct procedures rather than concentrated in one clause.
Review happens on two tracks. The first is scheduled review: periodic decontrol review of designated information and recurring self-inspection of the agency's CUI program. The second is event-triggered review: review at designation, review at decontrol request, review at unauthorized-disclosure response, and review at any change in law, policy, or mission that could affect designation status.
The roles are specific. The agency head designates a CUI Senior Official, who owns program-level compliance. The Senior Official approves the agency's CUI policy and its self-inspection plan. Designating officials create and mark CUI. Decontrolling officials remove CUI status when the basis for designation no longer exists. Each of these roles carries review duties, which is why "who reviews" depends on which procedure is running.
The mechanism matters because CUI is not a classification category. It is an administrative designation based on law, regulation, or government-wide policy. That legal basis is the review anchor: when the underlying authority changes, the designation must be re-examined. A document marked CUI for privacy reasons under the Privacy Act must be reviewed when the applicable system of records changes. A document marked for export-control reasons must be reviewed when the control list is revised.
Here is the counterintuitive part most thin explainers miss: decontrol review is not primarily about age. It is about whether the legal basis for designation still exists. A 40-year-old document with a live statutory basis stays CUI. A two-year-old document whose authorizing statute sunset drops out. Retention schedules inform review but do not drive it.
Quantified Context: Timelines, Durations, and Review Loads
The regulation sets explicit clocks, and agencies build on them. These are the numbers that matter in practice.
| Procedure | Trigger | Governing timeline | Accountable role |
|---|---|---|---|
| Initial designation review | Document creation or receipt | Before marking is applied | Designating official |
| Decontrol review (scheduled) | Retention schedule milestone | Per agency CUI directive; commonly 5, 10, or 25-year intervals | Decontrolling official |
| Decontrol request review | Public or internal request | Agency-defined; often 30-90 days | Decontrolling official |
| Unauthorized disclosure review | Suspected spill or exposure | Immediate containment, then formal review | Senior Official and security office |
| Self-inspection cycle | Program schedule | At least annually per agency policy | CUI Senior Official |
| Policy review after authority change | New statute, rule, or policy | Per agency implementation directive | Senior Official |
The CUI Registry maintained by the National Archives lists the authorized categories and their governing authorities. The registry is the reference point for the "legal basis" test, and it is updated as authorities change. Each agency's CUI implementing directive is the operative document that converts registry categories into local procedures, timelines, and forms.
Training is a quantified control that supports review. The CUI Program requires role-based training, with annual refresher training for personnel who handle CUI. Training completion is one of the artifacts self-inspection looks for, because an untrained workforce produces inconsistent designations and missed decontrol reviews.
Review load scales with program size. A small agency component might process dozens of decontrol reviews per year. A large department with heavy contract volume can run thousands of designation reviews annually across its CUI holdings. The self-inspection is where these loads get sampled rather than exhaustively checked, which is a limitation worth naming plainly.
Edge Cases: Where the Standard Procedure Breaks Down
Edge case one: legacy markings. Documents marked FOUO, SBU, or Law Enforcement Sensitive predate the CUI Program. Transition procedures required agencies to convert or retire legacy markings, but holdings that were never converted still surface. The review procedure is to apply the CUI designation standard to the content, not to honor the old marking. A legacy marking is evidence of past practice, not proof of a current lawful basis.
Edge case two: contractor-held CUI. When CUI sits on a contractor system, the review obligation splits. The contract clause dictates handling requirements, and the contractor's system security plan documents the controls. The government's review right flows through the contract, not through direct regulatory reach. This is the most common structural failure point: agencies assume the contractor is running decontrol review, contractors assume the agency owns it, and nobody reviews until an audit or a spill.
Edge case three: CUI commingled with classified information. If a document contains both classified and CUI portions, the classified procedures govern the whole document's handling. CUI review procedures do not override classification review. The correct sequence is classification review first, then CUI review of the residual unclassified portions.
Edge case four: information that loses its basis mid-life. A statute sunsets, a control list is revised, a Privacy Act system of records is amended. The designation does not automatically lapse on the date of the change. It requires an affirmative decontrol review and remarking. Documents can sit over-designated for months if no one owns the trigger.
Edge case five: aggregate or compilation CUI. Individual unmarked items can become CUI when aggregated. The review question shifts from "is this item designated" to "does the compilation meet a CUI category." This is where designation review at creation matters most, because aggregation happens silently in working files.
Red flags that a review procedure is failing:
Documents carry CUI markings with no recorded category or authority citation. Decontrol reviews are triggered only by retention-schedule dates and never by authority changes. Contractor-held CUI has no documented government review touchpoint in the contract. Self-inspection findings repeat across cycles with no corrective action record. Spill response closes without a root-cause review of the designation. Legacy markings persist in active holdings years after the transition deadline.
Misconceptions: What CUI Review Is Not
Misconception one: "CUI review is a classification review." It is not. CUI review tests whether an administrative designation still has a lawful basis. Classification review tests whether information meets the standards for classified status. They use different authorities, different officials, and different procedures. Conflating them produces over-designation, because reviewers apply classification caution to administrative designations.
Misconception two: "Review means re-reading every document." It does not, and the regulation does not require it. Scheduled decontrol review works from retention schedules, designation records, and sampling. Self-inspection samples the program, not the entire holdings. The practical implication: review quality depends on the quality of designation records, not on reading volume.
Misconception three: "Once marked CUI, always CUI until the retention date." Wrong in both directions. Designation can end early when the basis disappears, and it must be affirmatively removed. Retention dates inform review timing but do not control the legal-basis test.
Misconception four: "The CUI Registry tells you exactly what to mark." The registry lists categories and their authorities. It does not resolve every document-level judgment. Agency implementing directives and designating-official training do that work. A registry citation is necessary but not sufficient for a defensible designation.
Misconception five: "Self-inspection is optional if no one complains." Self-inspection is a program requirement, not a complaint-response mechanism. Its purpose is to find designation drift, missed decontrol reviews, and training gaps before an external audit or a spill does.
Plain version: review is a legal-basis test applied on a schedule and at trigger events, supported by records that let you prove it happened.
Practical Actions: Running a Defensible Review Procedure
These steps convert the regulation into operational thresholds. They are general process guidance, not agency-specific instructions.
Step one: map every CUI category your organization uses to its registry authority and your agency implementing directive. Any category without a written authority citation is a review finding on day one. Target: 100 percent of active categories mapped, with the citation recorded in the designation record.
Step two: build the trigger register. List every event that forces review: statute or rule change, control-list revision, system of records amendment, retention milestone, decontrol request, and spill. Assign an owner to each trigger. The register is what converts an event into a completed review.
Step three: set decontrol review intervals by category, not by uniform schedule. Privacy-based designations may warrant shorter intervals than law-enforcement-based ones. Document the interval rationale per category so the self-inspection can test it.
Step four: put contractor-held CUI review in the contract and the system security plan. Specify who performs decontrol review, at what interval, and what evidence the contractor delivers. A review right without a delivery requirement is not a procedure.
Step five: run self-inspection on a fixed annual cycle with a written sampling plan. Sample designation records, decontrol decisions, spill responses, and training completion. Track repeat findings as a threshold: any finding appearing in two consecutive cycles escalates to the Senior Official.
Step six: close spill reviews with a designation root-cause finding within the agency's defined response window. Containment first, then the formal review that asks whether the designation, the marking, or the handling control failed.
Reconciling the timelines: the regulation's floor is annual self-inspection and event-driven decontrol review. Agency directives commonly layer category-specific intervals on top. When the two differ, the stricter applicable requirement governs the review timing, and the record should cite which requirement was applied. One unit system throughout: all intervals in days or months, all dollar figures in USD.
Limitations: What the Procedure Cannot Guarantee, and Where Experts Disagree
The review architecture has structural limits. Self-inspection is sampling-based, so it measures program health statistically, not exhaustively. It can miss isolated over-designation in low-volume categories. Decontrol review depends on designation records that are often thin at creation, which means reviewers reconstruct legal basis after the fact. Contractor review depends on contract drafting quality and enforcement follow-through.
There is also a live professional debate about review cadence. Some practitioners argue for tighter periodic review of all CUI holdings to counter designation drift. Others argue that event-triggered review tied to authority changes is more efficient and more legally precise, because age alone does not predict whether a basis persists. The regulation supports the event-triggered model as the core, with periodic review as a backstop. Neither position eliminates the need for accurate designation records, which remain the binding constraint on review quality in every model.
A second limit is jurisdictional. CUI review procedures apply across the executive branch, but state, local, tribal, and private-sector holders operate under different authorities unless a contract or grant imports the requirements. Review expectations do not automatically travel with the information.
This article is general educational information about the CUI review framework. It is not legal advice, an agency implementation directive, or a compliance certification for any specific document or system. Review obligations vary by agency, contract, and information category, so consult your agency's CUI Senior Official, legal counsel, or a qualified compliance professional before applying these procedures to specific holdings. For immediate security incidents involving CUI, contact your local security office and follow agency incident response procedures.