States are not supposed to behave like mini-countries. They cannot make treaties, coin money, or run foreign policy. But the Constitution also recognizes something more practical: sometimes states have to cooperate.
They share rivers and ports. They run commuter rail systems that cross state lines. They handle criminal custody issues that do not stop at a border. So the Framers built a tool for interstate problem-solving and then put a lock on it.
That lock is the Compact Clause.
Join the Discussion
The Compact Clause in plain English
The Compact Clause appears in Article I, Section 10, Clause 3. The clause contains several limits, but the key language for interstate deals is this (excerpted):
No State shall, without the Consent of Congress, enter into any Agreement or Compact with another State, or with a foreign Power.
On its face, that sounds sweeping. No agreements between states unless Congress signs off.
But constitutional law rarely stays literal for long. The Supreme Court has interpreted the Compact Clause to require congressional consent only for agreements that would increase state power in a way that could threaten federal supremacy or shift the federal-state balance.
In other words, the Constitution does not force Congress to approve every handshake across a state line. It forces Congress to approve the kind of interstate deal that starts to look like a binding, power-enhancing arrangement between states.
Why consent matters
The Compact Clause is doing two jobs at once.
1) Preventing state alliances that could rival the Union
The Founders had fresh memories of the Articles of Confederation, where states often acted like independent nations loosely tied together. The Compact Clause helps prevent blocs of states from building alternative centers of power through binding agreements.
2) Letting states cooperate without running to Congress for everything
There is a federalism irony here: the Clause is also permission, not just prohibition. Interstate compacts are a constitutional way for states to solve regional problems without forcing Congress to legislate every time a river floods or a metro area spills over a border.
Consent is the checkpoint. It helps ensure compacts do not become a way to sidestep federal law, federal courts, or congressional authority.
When is consent required?
The key Supreme Court touchstone is Virginia v. Tennessee (1893). In broad terms, the Court explained that not every interstate agreement needs consent. Consent is required for agreements that:
- increase the political power of the states involved, and
- could encroach on or interfere with the supremacy of the United States.
Later cases have reinforced and applied this framework in modern settings, including U.S. Steel Corp. v. Multistate Tax Commission (1978) and Cuyler v. Adams (1981). The takeaway is stable even if the edge cases are not: the consent question turns on structural consequences, not on whether states used the word “compact.”
Deals that typically require consent
- Resource allocation compacts, especially water rights across multiple states (for example, the Colorado River Compact)
- Multi-state governing bodies that exercise delegated regulatory or operational authority (for example, the Port Authority of New York and New Jersey)
- Compacts creating commissions with binding authority, rulemaking, or enforcement mechanisms
- Agreements that materially affect federal interests like navigation, interstate commerce, or federal property
Deals that often do not require consent
- Routine coordination that does not pool sovereign power, such as shared services or informal cooperation
- Some boundary understandings that merely clarify a line (though many boundary compacts still seek consent for certainty)
- Parallel legislation where states pass similar laws without binding themselves to each other
A helpful way to keep the analysis straight is to separate two questions that are easy to blur:
- Is it a compact? That is, did the states make a binding commitment to each other, rather than simply coordinate?
- If it is a compact, does it require consent? Under Virginia v. Tennessee, only the power-enhancing, supremacy-affecting compacts need Congress to approve them.
This is why a deal can feel “compact-like” and still fall outside the consent requirement, and why a seemingly technical agreement can trigger major constitutional scrutiny if it reallocates power.
What counts as consent?
Congress can consent in different ways, and the form can matter.
Express consent
This is the straightforward version: Congress passes a statute approving the compact. Many large, durable compacts include language stating that they do not take effect until Congress consents.
Conditional consent
Congress can approve a compact but impose conditions, such as requiring certain governance rules or federal participation. If states accept the compact, they accept the conditions.
Implied consent
Implied consent is sometimes argued when Congress has enacted related legislation that appears to authorize or assume the compact. Courts tend to look for clear congressional authorization when consent is required, and implied-consent theories are contested and highly fact-specific.
Once Congress consents, an interstate compact is often treated as having the force of federal law in important respects. Depending on the compact and the approval statute, that can affect federal-court jurisdiction, supremacy or preemption questions, and how disputes are resolved.
How compacts work
Most interstate compacts follow a similar lifecycle.
Step 1: Negotiation
States negotiate terms through governors’ offices, attorneys general, legislators, and subject matter experts. Drafting is where the constitutional anxieties show up first: who enforces the compact, what counts as a breach, and how disputes are resolved.
Step 2: State enactment
Each participating state passes legislation adopting the compact. The text typically has to match across states, because the compact is a single bargain, not fifty versions of a bargain.
Step 3: Congressional consent (if required)
Congress may pass an approval statute. Sometimes it consents broadly. Sometimes it consents to a compact plus later amendments. Sometimes it refuses, and the compact never becomes binding in its intended form.
Step 4: Administration
Many compacts create a commission or authority, usually staffed by representatives from each member state. That body may:
- collect data
- issue regulations or standards (when the compact authorizes it)
- coordinate enforcement
- manage funds
- resolve routine disputes before they become lawsuits
Step 5: Disputes and enforcement
When states fight over compact obligations, the Supreme Court is often the forum. The Constitution gives the Court original jurisdiction over controversies between states, and many compact cases land there.
After consent: legal effect
Once consent is in place (when required), compacts tend to operate like a hybrid of statute and contract.
Supremacy and preemption
A congressionally approved compact can operate as federal law for supremacy purposes, meaning it can preempt conflicting state law in areas the compact covers. The exact effect depends on the compact’s text and Congress’s approval.
Interpretation
Courts often interpret compacts using contract-like tools, with close attention to the text, the structure of the bargain, and settled expectations among member states.
Limits on unilateral change
States generally cannot unilaterally rewrite a compact. Amendments usually require whatever the compact requires, commonly the agreement of member states and sometimes additional congressional consent.
Withdrawal is especially text-dependent. Some compacts include clear exit rules. Others do not, and unilateral withdrawal has become a live, contested issue in modern litigation. If a compact is silent, the legal answer can depend on the compact’s structure, reliance interests, and the surrounding case law.
Examples in real life
It is tempting to treat compacts as a niche tool that appears only during one political controversy. In reality, they are part of the country’s basic infrastructure.
Water allocation
Some of the most important compacts govern water, because rivers ignore state boundaries and drought does not respect state legislatures. A classic example is the Colorado River Compact, which coordinates allocation across a massive region. These compacts often require congressional consent because they allocate scarce resources and can affect navigation, federal lands, and interstate commerce.
Transportation and ports
Metro areas often span state lines. Compacts can create joint authorities to manage bridges, tunnels, ports, or rail systems. The Port Authority of New York and New Jersey is a well-known example of a compact-created entity with ongoing operational power.
Criminal justice and custody transfers
Some compacts streamline how states handle probationers, parolees, and incarcerated individuals who move across state lines. The Interstate Compact for Adult Offender Supervision is a prominent example. These agreements can be operational, but they still matter constitutionally when they create binding obligations and shared enforcement mechanisms.
Professional licensing
Licensing compacts allow professionals to practice across state lines under shared standards. The Nurse Licensure Compact is a common reference point. Not every licensing arrangement is a Compact Clause compact that requires congressional consent. Many are structured through coordinated state legislation plus a commission, and the consent question depends on whether the arrangement enhances state power in the constitutional sense under the Supreme Court’s framework.
The National Popular Vote compact
The National Popular Vote Interstate Compact is a useful teaching example because it highlights the core question: does the agreement alter the balance of power in a way that requires Congress’s consent?
Supporters argue it is an exercise of states’ constitutional authority over how they appoint electors. Critics argue it is a multi-state arrangement that effectively reshapes a federal election mechanism and therefore should require congressional approval under the Compact Clause.
Whether it needs consent is a legal question rooted in the general Compact Clause framework, not just a political question about presidential elections.
Common myths
Myth: All state cooperation needs consent
False. States coordinate constantly without compacts, and many agreements are too minor or too nonbinding to trigger the consent requirement.
Myth: Consent makes a compact immune
Also false. Consent can strengthen a compact’s legal footing and can give it federal-law effect for some purposes, but it does not turn an unconstitutional arrangement into a constitutional one.
Myth: A compact is just a contract, so states can exit anytime
Not necessarily. Some compacts contain withdrawal provisions. Others do not. Even when an exit clause exists, it may impose timing, notice, or financial conditions. Where a compact is silent, the withdrawal question can become a serious legal dispute rather than a simple policy choice.
The deeper idea
The Compact Clause is one of the Constitution’s most underappreciated balancing acts. It acknowledges that states are sovereign enough to bargain with each other, but not sovereign enough to form their own rival union.
That is why congressional consent matters. It is not mere paperwork. It is the constitutional signal that interstate cooperation has crossed from casual coordination into something with structural consequences.
If you want to understand a compact in the news, start here: what power is being pooled, what authority is being created, and whether the agreement could shift the federal-state equilibrium. The politics will be loud. The Compact Clause question is quieter, but it is the one that helps determine whether the deal is constitutionally built to last.
