Start with one piece of work. What information does the customer send you? What does your team create? Read the contract and customer instructions, follow where the information goes, and write down anything you need the customer to explain.
This guide helps you check whether your business keeps, uses, or sends Controlled Unclassified Information (CUI). It cannot decide whether a particular item is CUI or confirm that your company has none.
Sources reviewed October 21, 2026. You do not need an account. This page does not scan files, accept uploads, or send your answers to the site.
Keep your completed log in an approved restricted location. Do not put CUI or evidence contents into the template or send them to this site.
CUI is unclassified information the federal government creates or holds, or that someone creates or holds for the government. A law, regulation, or government-wide policy must provide the basis for protecting it or limiting who can receive it. A contractor may receive CUI or create it for the government. Check the rule behind the protection and the instructions for the item.
FCI is information supplied by or created for the government under a contract for products or services, when it is not intended for public release. The FAR definition excludes information the government makes public and simple transaction information such as payment-processing details. To decide whether FCI is also CUI, check whether it meets the CUI criteria.
Check whether the material was properly approved for unrestricted public release. Finding a file on the internet does not prove that someone was authorized to publish it. Find out where it came from and what approval allowed its release.
A Confidential label does not by itself make a file CUI. Neither does the presence of personal information or business secrets. Check its connection to the government, the relevant CUI category, and the rule behind that category. Even when an item is not CUI, privacy rules, contract terms, and other security duties can still require protection.
CUI is unclassified. If you handle classified information, use the separate process authorized for it; this guide does not cover that work. Ask two questions as you review CUI: which requirements apply to the contract, and which specific information is CUI? The answer to one does not settle the other.
2. Read the instructions and markings
Sit down with the people doing the work. Read the contract, subcontract, task instructions, and customer guidance together. Check what you must deliver, including reports and other information your team creates.
Look at the item and its accompanying instructions. Check for CUI or CONTROLLED banners, category markings, and details about who designated the information. Older FOUO labels, distribution statements, and export warnings need a closer look. None of those labels alone tells you to relabel an item as CUI.
Find the rule behind the category. Read the relevant entry in the official CUI Registry alongside the customer's instructions. A matching word, file type, or category name alone does not tell you whether this particular item is CUI.
Write down what you cannot resolve. Name the person who will ask for an answer. Direct the question to the person or agency that supplied the information, or to the government office responsible for the contract. If you are a subcontractor, use the appropriate route through your prime contractor or customer.
Unmarked information can still be CUI.
A contract that includes DFARS 252.204-7012 does not make every company document CUI. The clause's definition of covered defense information can include information your team creates or handles while doing the contract work, when that information meets the definition's other conditions. Check the item itself, the rule requiring protection, and the customer's instructions. Read the clause.
NARA says to take questions about marked or unmarked information back to its originator or the government contracting activity. While you wait for an answer, keep following the protection and reporting instructions that already apply. This guide does not give you permission to change markings, remove controls, or move the information to another service. Read NARA's guidance on asking for clarification.
Made-up examples with sample data. These do not decide the status of real information or report test results.
3. See what supports each answer
A technical package identified by the customer
In this made-up example, a customer sends a technical package marked CUI. Written contract instructions name the CUI category and explain how to handle the package.
CUI confirmed in this example
Record where to find the restricted instructions, then list every place the team uses the package. The example assumes the CUI status is established. If you dispute a marking on a real item, ask for clarification.
A report your team creates
In this made-up example, a contractor copies controlled measurements into a new report. Its written instructions say that the report content is CUI and explain which markings to use.
CUI confirmed in this example
Follow the report and its working copies through the systems that handle them. Include information the team creates when you review CUI, as well as files received from the customer.
An unmarked subcontract drawing
In this made-up example, a supplier receives an unmarked drawing for defense work. The subcontract does not give the team clear instructions about whether it is CUI or how to mark it.
Needs clarification
Write down the question. Ask the prime contractor or customer to get an answer from the appropriate government originator or office responsible for the contract. A missing marking does not prove that the drawing is not CUI.
An approved public brochure
In this made-up example, an agency has approved a brochure for unrestricted public release. The team uses that public edition without changing it or adding controlled information.
Reason this item is not CUI recorded in this example
Record where to find the approval for public release. That approval explains this item's status; you still need to check the other information the company receives and creates.
4. Follow where an item is stored, used and shared
Ask someone who does the work to walk you through one item. Use references you are authorized to review. Keeping a copy is storing it. Opening, viewing, editing, or creating information are examples of processing it. Sending or sharing it between people or systems is transmitting it. These examples help you follow the work; they do not decide an asset's formal assessment category.
Include files viewed in a customer portal. Even if no one clicks Download, the device may process the information or keep a cached copy. Ask IT to check what actually happens in that setup.
Made-up example with sample data: where a CUI technical package goes
Step 1
Receive
The package arrives through an approved customer portal. List the portal, the account used to receive it, and any copies downloaded or cached on a device.
Step 2
Use and create
An engineer uses an authorized workstation to open the package and create the report described in the sample instructions. List the application, workstation, and working files.
Step 3
Store and copy
The engineer saves the work in an approved restricted workspace. Check whether copies also go to synced folders, backups, exports, removable media, or a printer.
Step 4
Send and retain
The team returns the report through the approved route. List who receives it, the service used to send it, and the copies kept afterward. Record the instructions for keeping and disposing of those copies.
Ask whether the work uses email attachments, shared workspaces, chat, engineering tools, synced folders, backups, outside providers, or paper. In the log, record where authorized staff can find an item without copying its contents. Follow your approved instructions for how long to keep it and how to dispose of it.
Use this record when deciding which systems belong in an assessment. You may also need to include systems and services that provide security, even if they do not directly handle CUI. Use the Level 2 Scoping Guide to make that separate decision.
5. Record what you know and what needs an answer
Open the Excel log in your existing Office tools. Describe each information type in general terms and note where to find its instructions. Write down whether CUI has been confirmed or a question remains, who will follow up, and what they need to do. Use the Data flow tab to list the systems and services the item passes through. You enter each status yourself; the workbook does not decide it.
Do not put CUI, contracts, diagrams, credentials, or evidence contents into the template or send them to this site. Save your completed log in a restricted location your organization has approved. Its references and descriptions may also be sensitive. Before using a synced folder or online editor, check where it sends and stores the file.
Edit the template on your computer, then send it to your customer or prime contractor through your approved route. This page does not send an email.
Subject: Please clarify which information is CUI and how to handle it
Hello [contract or customer point of contact],
We are checking the information we receive and create for [approved contract or work reference]. We need help confirming whether [general description or restricted reference] is CUI, or which handling instructions apply.
Please answer the questions below or forward them to the appropriate government originator or office responsible for the contract.
1. Which information you supply and which deliverables we create are identified as CUI?
2. Which CUI categories apply, and which laws, regulations, or government-wide policies provide the basis for protecting the information? Please include the marking instructions and references to the contract or supporting documents.
3. Who should we ask about items with no markings, older markings, or markings that may be incorrect?
4. How should we protect and send the information while we wait for an answer?
Please reply in writing through our approved communication route. We can share restricted references through that route if you need them.
Thank you,
[authorized company contact]
Template instructions: Save and edit your copy on your computer. Replace the placeholders and send the request through your approved customer or prime-contractor route. Do not send the request, contract records, CUI, or supporting evidence to Purposeful Security. Keep meeting the protection and reporting duties that already apply while you seek an answer.
Once you have confirmed that an item is CUI, work out which systems need review and begin the readiness worksheet. If a question is still open, keep following up for an answer. If one item is not CUI, you still need to check the other information your company handles and meet your other contract duties.
Explains who to ask when markings or instructions are unclear. NARA reviewed the page on May 1, 2023. Check your current contract and agency instructions too.
Version 2.13. After identifying CUI, use this guide to decide which systems belong in the assessment and how to categorize their assets.
If a step is unclear or you spot an error, email a general description to cmmc@purposefulsecurity.com. Please do not send CUI, contracts, supporting evidence, or your completed log. These resources explain how to investigate. They cannot decide whether your information is CUI, approve which systems belong in an assessment, or confirm compliance.