FAR 52.204-18—Commercial and Government Entity Code Maintenance.
Plain-English Summary
FAR 52.204-18, Commercial and Government Entity Code Maintenance, tells contractors how to keep CAGE and NCAGE codes current during contract performance. It covers the definition of a CAGE code, the requirement to maintain the code for each place of performance and subcontract performance, how SAM registration affects CAGE data updates, what to do during novation or change-of-name actions, how U.S.-based contractors not registered in SAM must request changes from DLA, how non-U.S. contractors not registered in SAM must work through the appropriate NATO National Codification Bureau or NSPA, where to find additional guidance, and the special subcontractor-maintenance requirement when FAR 52.204-2 Security Requirements is included. In practice, the clause exists so the Government can reliably identify the legal entity and location associated with contract performance, keep procurement and security records accurate, and avoid mismatches between the contract, SAM, and the CAGE master file. It matters because CAGE data affects award administration, payment and reporting systems, security coordination, and contract modifications. Contractors must actively monitor changes in name, location, registration status, and organizational structure, while contracting officers must ensure the contract record is updated when the code changes.
Key Rules
CAGE and NCAGE Defined
The clause defines CAGE codes for entities in the United States and outlying areas, and NCAGE codes for entities outside those areas. The distinction matters because the update process depends on where the contractor is located and whether SAM registration applies.
Maintain Code Throughout Performance
Contractors must keep the CAGE code current for each location of contract performance, including subcontract performance. This is an ongoing obligation for the life of the contract, not just at award.
SAM Drives U.S. Updates
For contractors registered in SAM, DLA will only change CAGE master file data when the contractor updates its SAM registration first. In other words, SAM is the source of truth for registered U.S. entities.
Report Changes Within 30 Days
If a contractor’s CAGE code changes, the contractor must notify the contracting officer within 30 days so the contract can be modified. This ensures the contract file matches the current entity and location information.
Novation and Name Changes
Contractors involved in novation or change-of-name agreements must notify the contracting officer under FAR subpart 42.12. These organizational changes often require coordinated updates to the contract and related records.
U.S. Non-SAM Entities Use DLA
Contractors located in the United States or outlying areas that are not registered in SAM must submit written change requests directly to the DLA CAGE Branch through the specified website. Only the entity identified by the code may request changes.
Non-U.S. Non-SAM Entities Use NATO Channels
Contractors outside the United States and outlying areas that are not registered in SAM must request changes through the appropriate National Codification Bureau or NSPA. This reflects the international CAGE/NCAGE administration structure.
Subcontractor Codes Must Also Stay Current
If FAR 52.204-2 Security Requirements is in the contract, the prime contractor must ensure subcontractors maintain their CAGE codes throughout performance. This extends the maintenance obligation down the supply chain where security-sensitive work is involved.
Responsibilities
Contractor
Maintain the correct CAGE or NCAGE code for each contract performance location for the life of the contract. Update SAM when registered, submit change requests through the proper channel when not registered in SAM, notify the contracting officer of any code change within 30 days, and comply with novation or change-of-name notification requirements.
Contracting Officer
Receive notice of CAGE code changes, ensure the contract file and contract terms are updated by modification when needed, and coordinate with the contractor during novation or name-change actions under FAR subpart 42.12.
DLA Commercial and Government Entity (CAGE) Branch
Maintain the CAGE master file and process changes for U.S. entities not registered in SAM, and for SAM-registered entities only after the contractor updates SAM. DLA records and maintains the master file data tied to the code.
National Codification Bureau / NSPA
Process CAGE/NCAGE change requests for entities located outside the United States and outlying areas that are not registered in SAM, using the NATO administrative process.
Subcontractors
When the prime contract includes FAR 52.204-2 Security Requirements, maintain their CAGE codes throughout the life of the subcontracted performance as required by the prime contractor’s flowdown obligations.
Agency / Contract Administration Personnel
Support accurate contract records, monitor organizational changes affecting contractor identity or location, and help ensure the contract data aligns with SAM and the CAGE master file.
Practical Implications
Contractors should treat CAGE maintenance as a continuing compliance task, not a one-time registration step. Changes in address, legal name, ownership, or performance location can trigger a need to update records and notify the CO.
If a contractor is in SAM, updating the CAGE record usually starts with updating SAM first. Skipping SAM and going straight to DLA can delay the change because DLA relies on SAM-fed data for registered entities.
The 30-day notice to the contracting officer is important. Missing it can leave the contract file out of sync with the actual entity, which can complicate invoicing, modifications, security processing, and closeout.
Novation and change-of-name events require special attention because they affect who is legally performing the contract. Contractors should coordinate early with the CO and follow FAR subpart 42.12 rather than waiting until after the transaction closes.
Prime contractors on security-requirement contracts need to watch subcontractor compliance too. A subcontractor with stale CAGE data can create downstream administrative or security issues even if the prime’s own record is current.
Official Regulatory Text
As prescribed in 4.1804 (c) , use the following clause: Commercial and Government Entity Code Maintenance (Aug 2020) (a) Definition. As used in this clause– Commercial and Government Entity (CAGE) code means– (1) An identifier assigned to entities located in the United States or its outlying areas by the Defense Logistics Agency (DLA) Commercial and Government Entity (CAGE) Branch to identify a commercial or government entity by unique location; or (2) An identifier assigned by a member of the North Atlantic Treaty Organization (NATO) or by the NATO Support and Procurement Agency (NSPA) to entities located outside the United States and its outlying areas that the DLA Commercial and Government Entity (CAGE) Branch records and maintains in the CAGE master file. This type of code is known as a NATO CAGE (NCAGE) code. (b) Contractors shall ensure that the CAGE code is maintained throughout the life of the contract for each location of contract, including subcontract, performance. For contractors registered in the System for Award Management (SAM), the DLA Commercial and Government Entity (CAGE) Branch shall only modify data received from SAM in the CAGE master file if the contractor initiates those changes via update of its SAM registration. Contractors undergoing a novation or change-of-name agreement shall notify the contracting officer in accordance with subpart 42.12 . The contractor shall communicate any change to the CAGE code to the contracting officer within 30 days after the change, so that a modification can be issued to update the CAGE code on the contract. (c) Contractors located in the United States or its outlying areas that are not registered in SAM shall submit written change requests to the DLA Commercial and Government Entity (CAGE) Branch. Requests for changes shall be provided at https://cage.dla.mil . Change requests to the CAGE master file are accepted from the entity identified by the code. (d) Contractors located outside the United States and its outlying areas that are not registered in SAM shall contact the appropriate National Codification Bureau (points of contact available at http://www.nato.int/structur/AC/135/main/links/contacts.htm ) or NSPA at https://eportal.nspa.nato.int/AC135Public/scage/CageList.aspx to request CAGE changes. (e) Additional guidance for maintaining CAGE codes is available at https://cage.dla.mil . (f) If the contract includes Federal Acquisition Regulation clause 52.204-2 , Security Requirements, the contractor shall ensure that subcontractors maintain their CAGE code(s) throughout the life of the contract. (End of clause)