Can a contract be considered a classified contract even if the contract document itself is not classified?

• A. Yes
• B. No
• C. Only if the contractor has a clearance
• D. Only if the project requires

Answer: (A)

Classification depends on the nature of the work and how information will be handled, not on how the contract document is marked. A contract is considered classified if the performance will involve access to, or safeguarding of, classified information, or if it must be conducted under security controls for handling sensitive data—even if the contract document itself is not labeled classified.

For example, if a contractor is to develop or integrate a system that uses classified data, the work requires security protections, and there will be controlled distribution of information. In that case, the contract is treated as classified, and security provisions (such as safeguarding, marking, need-to-know restrictions, and possibly a classified annex) are put in place, regardless of the main document’s unclassified appearance. If no classified information is involved and no special handling is required, the contract remains unclassified.

So it can be a classified contract even when the contract document isn’t classified, because classification follows the handling requirements of the work, not the label on the contract.