S. 2240 (119th)Bill Overview

Expanding Defense Community Partnerships Act

Armed Forces and National Security|Armed Forces and National Security
Cosponsors
Support
Bipartisan
Introduced
Jul 10, 2025
Discussions
Bill Text
Current stageCommittee

Read twice and referred to the Committee on Armed Services.

Introduced
Committee
Floor
President
Law
Congressional Activities
01 · The brief
Plain-English summaryWhat this bill actually does

This bill amends 10 U.S.C. 2679 to broaden authorities for intergovernmental support agreements (IGSAs) between the Department of Defense and state, local, or tribal governments. It (1) explicitly allows such partners to collaborate with other federal agencies in providing, receiving, or sharing installation-support services; (2) expands the types of DoD funds that may be used to pay for installation-support services to include operation and maintenance, research, development, test, and evaluation (RDT&E), procurement of ammunition, military construction, and non-appropriated funds; (3) appears to extend a statutory date from September 30, 2025, to September 30, 2030; and (4) creates a pilot program authorizing the Secretary of Defense to enter into up to one IGSA per service (Army, Navy, Air Force) for a term of up to 20 years notwithstanding an existing shorter-term limit.

Why people may split

Scope and permissible uses of funding: liberals worry about diversion of RDT&E/MilCon/procurement funds to non-defense community uses, while conservatives emphasize operational flexibility and centrist view seeks fiscal guardrails.

Watch point

Relative to its intended legislative type, this bill is a direct substantive amendment to 10 U.S.C. 2679 that concretely expands intergovernmental support agreement authorities (partnering with other federal agencies, permitting specified fund sources, extending statutory dates, and authorizing a limited pilot for up to 20‑year agreements).

This bill amends 10 U.S.C. 2679 to broaden authorities for intergovernmental support agreements (IGSAs) between the Department of Defense and state, local, or tribal governments.

It (1) explicitly allows such partners to collaborate with other federal agencies in providing, receiving, or sharing installation-support services; (2) expands the types of DoD funds that may be used to pay for installation-support services to include operation and maintenance, research, development, test, and evaluation (RDT&E), procurement of ammunition, military construction, and non-appropriated funds; (3) appears to extend a statutory date from September 30, 2025, to September 30, 2030; and (4) creates a pilot program authorizing the Secretary of Defense to enter into up to one IGSA per service (Army, Navy, Air Force) for a term of up to 20 years notwithstanding an existing shorter-term limit.

The bill as written focuses on expanding DoD flexibility in structuring and funding installation-support partnerships.

Passage65/100

On content alone, the bill is a narrow, technical statutory tweak that aligns with routine defense administration and contains conservative guardrails (limited pilot, time-limited extension). Such measures commonly advance as provisions in larger defense authorization packages. The primary risks are fiscal/appropriations questions and any stakeholder-specific objections, but those are solvable and do not on their face make the measure politically transformative or widely contested.

CredibilityPartially aligned

Relative to its intended legislative type, this bill is a direct substantive amendment to 10 U.S.C. 2679 that concretely expands intergovernmental support agreement authorities (partnering with other federal agencies, permitting specified fund sources, extending statutory dates, and authorizing a limited pilot for up to 20‑year agreements). It is specific in statutory drafting but sparse on problem framing, fiscal acknowledgment, safeguards, and accountability provisions.

Contention50/100

Scope and permissible uses of funding: liberals worry about diversion of RDT&E/MilCon/procurement funds to non-defense community uses, while conservatives emphasize operational flexibility and centrist view seeks fiscal guardrails.

02 · What it does

Who stands to gain, and who may push back.

Likely benefits vs burdens50% / 50%
Federal agencies · Local governmentsLocal governments

These are examples from the analysis, not a ranked list of the most-affected groups.

Likely helped
  • Federal agenciesIncreased flexibility to combine DoD funding streams and to partner with other federal agencies could enable more coord…
  • Local governmentsLonger-term IGSAs (via the pilot) and expanded authority for facility repair/construction could encourage multi-year pl…
  • Permitting processPermitting use of multiple funding categories and non‑appropriated funds may allow DoD to leverage available resources…
Likely burdened
  • Potential burdenLonger IGSA terms and broader allowable funding sources may reduce congressional control over future budgetary choices…
  • Potential burdenAuthorizing use of RDT&E, ammunition procurement, military construction, and non‑appropriated funds for installation-su…
  • Local governmentsExpanded cross‑agency and intergovernmental partnerships and increased construction/operation activities could raise lo…
03 · Why people split

Why the argument around this bill splits.

Scope and permissible uses of funding: liberals worry about diversion of RDT&E/MilCon/procurement funds to non-defense community uses, while conservatives emphasize operational flexibility and centrist view seeks fiscal…
Progressive60%

A mainstream liberal would likely view this bill as having pragmatic potential to strengthen community ties to military installations and bring federal resources to local projects, but would be cautious about the expanded funding authorities and long-term agreements.

They would welcome collaboration with other federal agencies if it advances community services, environmental remediation, or public-benefit projects, but worry that permitting RDT&E, procurement, MilCon, and non-appropriated funds to be used could reduce Congressional oversight and divert funds from other priorities.

The 20-year pilot agreements and extended statutory authority raise concerns about transparency, accountability, labor standards, environmental review, and impacts on tribal sovereignty or local control.

Split reaction
Centrist75%

A moderate would likely see this bill as a practical, administrative flexibility measure that enables DoD to coordinate more effectively with state, local, tribal governments and other federal agencies to support installations.

They would appreciate the potential efficiency gains and local benefits, but want clarity on fiscal controls and accountability so that expanded funding authorities are not misused.

The 20-year pilot allowance is useful for program stability but should be limited to pilots with clear metrics and reporting.

Leans supportive
Conservative85%

A mainstream conservative would likely view the bill positively as it increases DoD flexibility to partner with local governments and other federal agencies and to finance installation-support services from a wider set of funds.

They would favor measures that reduce bureaucratic friction and enable longer-term contracting that can produce efficiencies and improve readiness-support infrastructure.

Some conservatives might still raise questions about ensuring funds remain focused on defense priorities and avoiding mission creep, but overall would see this as a pro-defense, pro-efficiency change.

Leans supportive
04 · Can it pass?

The path through Congress.

Introduced

Reached or meaningfully advanced

Committee

Reached or meaningfully advanced

Floor

Still ahead

President

Still ahead

Law

Still ahead

Passage likelihood65/100

On content alone, the bill is a narrow, technical statutory tweak that aligns with routine defense administration and contains conservative guardrails (limited pilot, time-limited extension). Such measures commonly advance as provisions in larger defense authorization packages. The primary risks are fiscal/appropriations questions and any stakeholder-specific objections, but those are solvable and do not on their face make the measure politically transformative or widely contested.

Scope and complexity
24%
Scopenarrow
24%
Complexitylow
Why this could stall
  • No cost estimate or Congressional Budget Office score is included in the text; fiscal impact and how often the newly authorized funding sources would be used are therefore unclear.
  • The bill contains some truncated or compacted language (e.g., small textual insertions) that may require drafting clarification in committee to resolve ambiguity about scope and limits.
05 · Recent votes

Recent votes on the bill.

No vote history yet

The bill has not accumulated any surfaced votes yet.

06 · Go deeper

Go deeper than the headline read.

Included on this page

Scope and permissible uses of funding: liberals worry about diversion of RDT&E/MilCon/procurement funds to non-defense community uses, whil…

On content alone, the bill is a narrow, technical statutory tweak that aligns with routine defense administration and contains conservative…

Unlocked analysis

Relative to its intended legislative type, this bill is a direct substantive amendment to 10 U.S.C. 2679 that concretely expands intergovernmental support agreement authorities (partnering with other federal agencies, p…

Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.

Perspective breakdownsPassage barriersLegislative design reviewStakeholder impact map
Open full analysis