If you handle federal contracts, understanding what is FCI vs CUI as a federal contractor is not optional. These two categories of government information carry different rules, different risks, and different compliance requirements. Get the distinction wrong and you may over-invest in controls you do not need, or leave sensitive data exposed with the wrong level of protection.
After reading this, you will know what separates Federal Contract Information from Controlled Unclassified Information, why that line determines whether you face CMMC Level 1 or Level 2, and how to look at your own environment and identify which type you actually handle.
Why the FCI vs CUI Line Matters for Subcontractors
The classification of your data as FCI or CUI is not a paperwork exercise. It is the single decision that sets your compliance path before you can win a contract. CMMC requirements apply to each contractor information system that will process, store, or transmit FCI or CUI during contract performance.
The required CMMC level must be achieved prior to award for every system that handles either type of information (OSD). For subcontractors, the stakes are higher than they appear. Prime contractors pass compliance requirements down the supply chain.
Here is a scenario that catches small businesses off guard. You start a task order and your system is scoped for FCI only. Mid-performance, the government adds a deliverable and the prime sends you technical drawings that carry export-control distribution markings. Your environment is now a CUI system. The controls you had in place for FCI are no longer enough, and your system security plan no longer matches the data it holds. You may not discover this until a prime asks for your CMMC evidence at award time.
Another blind spot: a prime shares files that look routine and carry no marking. If those files came from a CUI-designated system on the prime's side, they carry CUI status regardless of how they arrived. The practical question is not what your contract says. It is what data actually flows into your systems. Get that answer before you bid, and check it again every time scope changes.
What Is FCI in Plain Language
Federal Contract Information, or FCI, is data the government gives you under a contract to do the work. It is not public. The government did not intend it for general release.
Think about what that looks like day to day. A contracting officer emails you a statement of work. You receive a purchase order with line items tied to a government program. A prime contractor shares specs so you can bid a subcontract. All of that is likely FCI.
FCI does not have to be stamped or labeled to count. If the government provided it and it is not publicly available, treat it as FCI until you confirm otherwise. Where FCI typically lives in a small business: email inboxes, shared drives, proposal files, and invoicing systems. Those are the first places to audit.
A common mistake is assuming that because a file arrived from a prime rather than directly from a government office, it falls outside the FCI definition. The source of the data does not change its category. If you handle FCI, you have security obligations, and knowing where that data sits is the first step to meeting them.
What Is CUI and Where It Comes From
Controlled Unclassified Information, or CUI, is government data that is sensitive but not classified. It sits above FCI on the sensitivity scale. While FCI covers information you receive to do contract work, CUI carries specific legal protection requirements tied to its category.
CUI authority flows from the National Archives and Records Administration (NARA) registry, which lists approved categories and subcategories. When a contract clause designates information as CUI, that designation tells you what category applies and which handling rules govern it.
Small businesses often miss CUI in places that look routine. Technical drawings, engineering specs, and test data can qualify. According to NIST SP 800-171, the protection of Controlled Unclassified Information resident in nonfederal systems is of paramount importance to federal agencies and can directly impact the ability of the federal government to successfully conduct its essential missions and functions.
Defense contracts use specific distribution statement criteria to flag controlled technical information. If a document carries one of those statements, it likely meets the threshold for CUI treatment (Acquisition). The practical takeaway: read your contract clauses carefully and ask the program office which CUI categories apply before work begins. Do not wait until a deliverable arrives.
How Your Data Type Determines What CMMC Level You Need
The type of federal data you handle maps directly to the CMMC level your contract will require. If you handle only FCI, you are looking at CMMC Level 1. If you handle CUI, you are looking at Level 2 or higher.
You will not have to guess which level applies. The contracting officer is required to state the CMMC level in the solicitation and the resulting contract clause (Acquisition). Look for that language before you bid. If you do not see it, ask the contracting officer directly before you invest in compliance work.
For most contractors, the requirement lands at Level 1 or Level 2. DoD intends to include Level 1 or Level 2 requirements across all applicable solicitations and contracts as a condition of award (ECFR). That requirement can also apply when the government exercises an option period on a contract awarded before the rule took effect (ECFR).
Level 1 is a self-assessment. To reach that status, you must meet all the security requirements spelled out under the applicable rule (ECFR). That means documented, verified controls, not just good intentions. Level 2 brings a third-party assessment option in certain cases. Read every solicitation clause before you submit a proposal.
Common Misclassification Mistakes and Their Consequences
Misclassification usually runs in one direction: contractors label CUI as plain FCI and apply the lighter controls. The reasoning is understandable. The marking on the document is unclear, the program office did not flag it, and Level 2 looks expensive. So the data slides into a lower bucket.
That choice carries real risk. If a cyber incident occurs and the government investigates, the contracting officer must consult with the DoD component cybersecurity office before assessing your compliance (Acquisition). At that point, your classification decisions will be reviewed against the actual data, not your assumption about it.
Common mistakes to watch for:
- Treating unmarked data as uncontrolled when the contract clause covers it.
- Storing CUI in personal email or consumer cloud tools not authorized under your system security plan.
- Failing to tell subcontractors which data type they are receiving.
- Assuming a task order inherits the same level as the base contract without checking the new scope for CUI triggers.
The fix is straightforward. Build a short data inventory before work starts. List every deliverable, every file share, every inbox that touches contract data. Assign a type to each one. Review it when scope changes, when new personnel are added, and when a task order modifies the work.
Checklist to Classify Your Data Before CMMC Evidence Is Due
Pull your active contracts first. Read each statement of work and look for language about sensitive data, export controls, privacy, or law enforcement. That language signals CUI, not plain FCI.
Next, map every system that touches contract data. Include shared drives, email inboxes, project management tools, and any cloud storage. Write down what type of data sits in each one.
Then apply the labels:
- FCI: data the government gave you solely to perform the contract, with no additional handling markings.
- CUI: data that carries a category designation such as export-controlled technical data, personally identifiable information, or law enforcement sensitive.
After labeling, check each system's controls against the label. FCI requires basic cyber hygiene. CUI requires the full set of controls tied to its category. A mismatch is a gap you must close before evidence collection starts. Our cybersecurity services and managed IT services pages describe how we help small businesses work through this process.
Finally, document who reviewed each label and when. A prime contractor or assessor will ask for that record. A one-page log with contract number, system name, assigned label, reviewer, and date is enough. Update it every time scope or personnel changes. Keep the log somewhere you can retrieve it in under ten minutes. For a related guide on what a prime will specifically ask you to produce, see CMMC for Subcontractors: What Your Prime Will Ask For.
Start this week by pulling your active contracts and listing every system that touches contract work. Then assign each one a label of FCI or CUI based on the criteria above. That log is the foundation every other compliance step builds on.
Book a free 30-minute call with Joshua to talk through your specific contracts and get a clear picture of which compliance path applies to your business.




