Read twice and referred to the Committee on Foreign Relations.
This resolution directs the President to remove U.S. Armed Forces from hostilities in or affecting Syria within 30 days after Congress adopts the resolution, unless Congress authorizes a later date. It relies on existing laws and the War Powers Resolution to treat current U.S. activities in Syria as "hostilities" that require congressional authorization and invokes a statutory process for removal-directed measures. The resolution does not authorize the use of military force. It would become binding only if both chambers pass it and the President signs it (or Congress overrides a veto).
As a joint resolution, it must be passed by both the House and Senate and be presented to the President for signature or veto. It also invokes a pre-existing statute that requires expedited consideration under special procedures for measures that would direct removal of U.S. forces.
This joint resolution directs the President to remove United States Armed Forces from hostilities in or affecting Syria within 30 days of the resolution’s adoption, unless the President requests and Congress authorizes a later date.
It cites the War Powers Resolution and declares that the 2001 and 2002 AUMFs do not specifically authorize force in Syria.
The resolution does not itself authorize new military force and conditions continued presence on a subsequent declaration of war or specific statutory authorization.
Narrow subject but high political sensitivity, no fiscal incentives, strong executive-branch countervailing force, and significant Senate procedural barriers.
Relative to its intended legislative type, this bill is a clear, narrowly focused substantive directive that effectively leverages existing War Powers and related statutes to compel removal of U.S. forces from unauthorized hostilities in Syria and sets a short statutory deadline. It integrates well with existing law but provides only minimal operational and oversight detail.
Agreement that Congress should decide use of force, disagreement on security costs
These are examples from the analysis, not a ranked list of the most-affected groups.
Agreement that Congress should decide use of force, disagreement on security costs
Likely to view the measure favorably as restoring Congressional war‑making authority and ending an open‑ended military presence.
Sees it as a corrective to executive overreach and unnecessary U.S. entanglement.
Will still worry about humanitarian consequences if removal is hasty.
Balances support for constitutional oversight with concern for regional stability and orderly implementation.
Views the resolution positively for forcing congressional debate, but worries a 30‑day pullout could undermine counterterrorism and partner security.
Prefers a staged, transparently resourced withdrawal plan.
Many mainstream conservatives will likely oppose or be skeptical, prioritizing regional deterrence and partner protection.
They see risks to national security, counterterrorism, and influence versus Iran and Russia.
Some small‑government conservatives, however, might welcome withdrawing forces without congressional authorization.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
Narrow subject but high political sensitivity, no fiscal incentives, strong executive-branch countervailing force, and significant Senate procedural barriers.
The bill has not accumulated any surfaced votes yet.
Agreement that Congress should decide use of force, disagreement on security costs
Narrow subject but high political sensitivity, no fiscal incentives, strong executive-branch countervailing force, and significant Senate p…
Relative to its intended legislative type, this bill is a clear, narrowly focused substantive directive that effectively leverages existing War Powers and related statutes to compel removal of U.S. forces from unauthori…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.