Codify — Article

Allows Chesapeake Bay Program Office to join Maryland Whole Watershed State team

Grants the federal Chesapeake Bay Program Office advisory membership on Maryland's watershed management team and authority to coordinate, offer technical help, and provide funds for Chesapeake Bay watershed projects.

The Brief

The bill authorizes the Chesapeake Bay Program Office to serve as an advisory member of the State Management Team for the Maryland Whole Watershed Program and for ‘‘substantially similar’’ state programs. It explicitly permits the Office to coordinate with state and local governments and other federal agencies and to provide technical assistance and financial resources for projects in the Chesapeake Bay watershed.

This change formalizes a federal advisory and resourcing role within a state-managed watershed program. For implementers and state officials, the bill could streamline access to federal expertise and money; for federal managers, it creates a standing channel for project-level coordination.

The text does not appropriate funds or change enforcement authorities, leaving open questions about funding sources, oversight, and how the advisory role will be operationalized.

At a Glance

What It Does

Makes the Chesapeake Bay Program Office an advisory member of Maryland’s Whole Watershed Program State Management Team and of any substantially similar state program. It authorizes the Office to coordinate among governments and agencies and to provide technical and financial support for projects in the Chesapeake Bay watershed.

Who It Affects

Maryland’s State Management Team and project implementers in the Chesapeake Bay watershed (local governments, conservation districts, NGOs, and contractors) and the Chesapeake Bay Program Office itself. Other federal agencies that work on watershed projects may be asked to coordinate with the Office.

Why It Matters

Adds a formal seat and explicit resourcing role for a federal program inside state watershed governance, which may speed project delivery and align federal/state priorities. It also raises implementation questions about funding authority, accountability, and the boundaries between advisory input and operational control.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

The bill is short and narrowly focused. It gives the Chesapeake Bay Program Office a formal advisory role on Maryland’s Whole Watershed Program State Management Team and extends that ability to similar programs in other states.

That advisory seat is expressly limited to the role of a member of the State Management Team, not to any regulatory authority over state decision-making.

Alongside advisory membership, the Office may coordinate with state and local governments and federal agencies—an explicit authorization to act as a cross-jurisdictional coordinator. The bill also authorizes the Office to provide technical assistance and financial resources for projects in the Chesapeake Bay watershed.

The text does not specify funding sources, application processes, or reporting requirements for those financial resources; it simply permits the Office to provide them.The statute ties the authorization to the existing legal entity known as the Chesapeake Bay Program Office by citing section 117(b) of the Federal Water Pollution Control Act. Practically, implementation will depend on governance instruments—memoranda of understanding, operating procedures, and possibly grant or contract mechanisms—that define how the Office participates in State Management Team meetings, how it channels technical assistance, and how any funds are awarded and tracked.Because the bill treats participation as advisory, states retain formal program control, but the Office’s ability to provide money and technical tools gives it practical influence.

The lack of statutory detail on funding sources and oversight, plus the open-ended phrase ‘‘substantially similar program in a State,’’ means agencies and states will have to fill in implementation mechanics through negotiation and administrative guidance.

The Five Things You Need to Know

1

Section 2(a) makes the Chesapeake Bay Program Office an advisory member of Maryland’s Whole Watershed State Management Team and of any substantially similar state program.

2

Section 2(b)(1) authorizes the Office to coordinate with State and local governments and other Federal agencies on watershed matters.

3

Section 2(b)(2) authorizes the Office to provide technical assistance and financial resources for projects carried out in the Chesapeake Bay watershed.

4

The statute applies to programs beyond Maryland where a program is ‘‘substantially similar,’’ creating a flexible but ambiguous scope for federal participation.

5

Section 2(c) defines the Chesapeake Bay Program Office by reference to section 117(b) of the Federal Water Pollution Control Act (33 U.S.C. 1267(b)).

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 1

Short title

Declares the Act’s short title, the Maryland Whole Watershed Program Federal Partnership Act. This is purely nominal but signals the bill’s targeted focus on Maryland’s watershed initiative and federal–state partnership.

Section 2(a)

Advisory membership on State Management Team

Authorizes the Chesapeake Bay Program Office to serve as an advisory member of Maryland’s State Management Team for the Whole Watershed Program and for any substantially similar program in other states. The provision grants a formal seat for federal advisory participation but does not create regulatory power for the Office or change the statutory authorities of the State or the EPA; it establishes only membership and advisory status.

Section 2(b)

Authorized activities: coordination, technical help, and funding

Enumerates two categories of activity the Office may undertake: coordinating with state, local, and federal entities; and providing technical assistance and financial resources for Chesapeake Bay watershed projects. The mechanics—whether financial resources are grants, contracts, or in-kind support—are not specified, which leaves agencies to determine procurement, grant conditions, and any matching or reporting requirements needed to distribute funds or services.

1 more section
Section 2(c)

Definition of Chesapeake Bay Program Office

Clarifies that references to the Chesapeake Bay Program Office mean the entity established under section 117(b) of the Federal Water Pollution Control Act. That tie anchors the new authority to an existing statutory office and its current administrative structure, which will influence how the authorization is exercised within the EPA and partner agencies.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Environment across all five countries.

Explore Environment in Codify Search →

Who Benefits and Who Bears the Cost

Every bill creates winners and losers. Here's who stands to gain and who bears the cost.

Who Benefits

  • Maryland’s State Management Team: Gains a formal federal advisory partner with technical and funding capacity, which can accelerate project planning and access to federal expertise.
  • Local governments and project implementers in the Chesapeake Bay watershed (counties, municipalities, conservation districts): Stand to receive more coordinated technical assistance and potentially new funding pathways for on-the-ground restoration and stormwater projects.
  • Watershed NGOs and conservation practitioners: Benefit from streamlined federal-state coordination and access to federal technical resources, which can improve project design, monitoring, and grant competitiveness.
  • Chesapeake Bay Program Office: Receives an explicit statutory role that consolidates its position as a convenor and potential funder within state watershed governance, increasing its influence over project prioritization and implementation.

Who Bears the Cost

  • Chesapeake Bay Program Office and parent federal agencies: Must allocate staff time and potentially reprogram existing funds or seek appropriations to provide the technical assistance and financial resources authorized by the bill.
  • State agencies and local partners: May need to absorb coordination costs and adjust State Management Team processes to integrate federal participation, including drafting MOUs and aligning reporting requirements.
  • Project implementers receiving federal financial resources: Could face additional federal oversight, procurement standards, or reporting obligations tied to those funds, increasing administrative compliance costs.

Key Issues

The Core Tension

The central dilemma is between the practical benefits of deeper federal engagement—coordinated expertise and potential funding—and the risk that such engagement blurs lines of state control, accountability, and funding responsibility; the bill solves coordination gaps but leaves open who pays, who oversees, and how to prevent federal involvement from crowding out established state priorities.

The bill authorizes providing ‘‘financial resources’’ but contains no appropriation language or detail about the type of financial support, eligibility rules, or oversight mechanisms. That gap means the Office would either use existing appropriations under other statutes or require separate appropriations; both paths carry different legal and administrative constraints.

Agencies will have to decide whether to use grants, cooperative agreements, interagency transfers, or in-kind support—and each option triggers distinct procurement and audit rules.

The advisory membership is explicit but the bill does not define the practical limits of participation: it does not prescribe meeting frequency, voting rights (if any), conflict-resolution mechanisms, or reporting and transparency rules. The undefined phrase ‘‘substantially similar program in a State’’ creates scope uncertainty that could prompt disputes about which state programs qualify.

Implementation will therefore depend on negotiated governance documents (MOUs, charters) and internal agency guidance, which could vary across states and create inconsistent application.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.