Report to Congress on the Department of Defense

TL;DR

Executive Order 14347 (dated September 5, 2025) authorizes the Department of Defense to use "Department of War" and the Office of the Secretary of Defense to use "Office of the Secretary of War" as secondary designations. This change appears to be primarily a nomenclature update rather than a structural reorganization, but it can affect official documentation, contract language, and agency references in solicitations and awards. Government contractors supporting defense and related market segments should expect to see dual designations appear in correspondence, solicitations, and award documents and must ensure internal systems and templates recognize both names. Immediate implications include search/match failures, contract administration confusion, and potential procurement documentation inconsistencies if systems or personnel only recognize the primary designations. Contractors should inventory where agency names are used (templates, CRM, eProcurement filters, compliance mappings) and implement updates to accept both designations while monitoring for follow-on policy or process guidance.

Key Points

• What happened: Executive Order 14347 (September 5, 2025) authorized the Department of Defense to adopt "Department of War" as a secondary designation and authorized the Office of the Secretary of Defense to adopt "Office of the Secretary of War" as a secondary designation.
• Who is affected: Segments named in the event include NAICS codes and market segments listed in the segmentation, and the agencies named in the segmentation (see Who Is Affected below).
• Timeline: The Executive Order is dated September 5, 2025.
• What contractors should do NOW: Search and update contract templates, CRM records, solicitation-watch rules, and compliance mappings to accept both designations; notify capture/proposal/contracts/compliance teams; run rescans of opportunity pipelines for affected agencies and contract vehicles; preserve audit trails of any amended documents.

Who Is Affected

Contractors across the defense and professional services ecosystem are affected, particularly those that rely on automated searches, CRM records, and template-driven documentation. Specific NAICS codes, agencies, and contract vehicles pending source review.

However, segmentation explicitly provided with the event includes:

• NAICS: 541330, 541512, 541519, 541611, 541618, 541690, 541715, 336411, 336412, 336413, 336414, 336415, 336419, 334511, 334290, 541714, 561110, 561210, 561990
• Agencies: DOD; Department of the Army; Department of the Navy; Department of the Air Force; Defense Logistics Agency; Defense Contract Management Agency; Defense Information Systems Agency; Missile Defense Agency; Defense Advanced Research Projects Agency; National Security Agency
• Contract vehicles: OASIS+, SEWP, GSA (General Services Administration) MAS, STARS III, ITES-SW2, 8(a) STARS III, Alliant 2, CIO-SP3, T4NG, VETS 2
• Market segments: Defense; Professional Services; IT Services; Cybersecurity; Aerospace and Defense Manufacturing; Research and Development; Systems Engineering; Logistics and Supply Chain; Administrative Services; Consulting Services
• Compliance surfaces referenced in segmentation: DFARS (Defense Federal Acquisition Regulation Supplement); FAR (Federal Acquisition Regulation); CMMC (Cybersecurity Maturity Model Certification); NIST 800-171 (NIST Special Publication 800-171); ITAR (International Traffic in Arms Regulations); EAR; NIST 800-53; CUI (Controlled Unclassified Information)

Frequently Asked Questions

Q: Does this Executive Order change the Department of Defense's organizational structure?

A: The Summary states this appears to be primarily a nomenclature change rather than a structural reorganization. For definitive organizational changes, pending source review is required.

Q: Will existing contracts be reissued or require amendments to reflect the secondary designations?

A: The Summary does not specify contract amendment requirements. Contractors should assume documentation may reference dual designations and be prepared to address amendments or clarifications on a case-by-case basis. Final determinations pending source review.

Q: What immediate document and system changes are recommended?

A: Update search indexes, CRM and opportunity-monitoring rules, procurement templates, and contract-administration trackers to accept both the primary and secondary designations; notify capture/proposal/contract/compliance teams to watch for dual-designation language in solicitations and awards.

Definitions

• Executive Order 14347: The Executive Order, dated September 5, 2025, that authorized the secondary designations described in the Summary.
• Department of Defense (secondary designation: "Department of War"): The federal department authorized by the Executive Order to use "Department of War" as a secondary designation.
• Office of the Secretary of Defense (secondary designation: "Office of the Secretary of War"): The Office authorized by the Executive Order to use "Office of the Secretary of War" as a secondary designation.

Intelligence Response

• Cabrillo Signals War Room — Already detected this event and delivered this briefing. Cabrillo Signals War Room continuously monitors regulatory changes, contract vehicles, and policy shifts to surface naming or designation changes that can affect pipeline visibility.
• Cabrillo Signals Match Engine — Will automatically rescore opportunity pipelines and alerts where title/agency name changes impact opportunity matching, ensuring no eligible solicitations are missed due to nomenclature variance.
• Cabrillo Signals Intelligence Hub — Tracks affected agencies, NAICS codes, and contract vehicles and runs saved searches to alert when follow‑on solicitations or awards containing either designation appear on SAM.gov (System for Award Management). Use the Intelligence Hub to publish updated watchlists and to seed searches for both primary and secondary agency names.
• Proposal Studio (Proposal OS) — Use to update proposal templates, compliance matrices, and win-theme libraries to reflect both agency designations and to maintain audit-ready documentation.
• Proposal Studio Workflow Tracker — Use the 9-gate capture workflow to route required contract and compliance reviews automatically when solicitations or awards reference the secondary designations.

Who to notify internally: capture managers, proposal leads, contracts teams, compliance officers (including CUI/NIST/CMMC leads), IT/sysadmin teams responsible for search and eProcurement filters, and security officers tracking policy changes.

First 48-hour playbook

• Hour 0–4: Acknowledge detection. Cabrillo Signals War Room confirms event; notify capture/proposal/contracts/compliance teams and stand up a single point of contact. Run an immediate keyword search for both designations via Cabrillo Signals Intelligence Hub.
• Hour 4–12: Rescore opportunity pipelines with Cabrillo Signals Match Engine to surface opportunities that may have been missed due to naming variance. Export a prioritized list of impacted active opportunities and awards.
• Hour 12–24: Update CRM and procurement monitoring rules to accept both designations. Use Proposal Studio to flag affected templates and compliance matrices for revision; begin routing changes through Proposal Studio Workflow Tracker.
• Hour 24–48: Communicate guidance to business development and contracts teams; implement template updates and publish internal guidance. Maintain a watchlist in the Intelligence Hub for follow-on policy or solicitation language that clarifies whether the change is purely nominal or requires contractual action.

Relevant guidance and compliance references: review internal procedures in the Secure Operations Guide (/insights/secure-operations-guide). For compliance and CUI handling considerations, use the CMMC Compliance Guide (/insights/cmmc-compliance-guide) and the CUI-Safe CRM Guide (/insights/cui-safe-crm-guide).