Virginia's Chesapeake Bay Preservation Act: RPA, RMA, and the 100-Foot Buffer

For any project in Tidewater Virginia, the Chesapeake Bay Preservation Act (CBPA) is likely in play before the zoning ordinance, the USBC, or VSMP stormwater. Codified at Va. Code § 62.1-44.15:67 et seq. with implementing regulations at 9VAC25-830, CBPA requires 84 Tidewater localities — Richmond, Norfolk, Virginia Beach, Hampton, Newport News, the Middle Peninsula, the Northern Neck, Hampton Roads, and most of the eastern third of the Commonwealth — to designate Chesapeake Bay Preservation Areas and regulate land use within them. The 100-foot Resource Protection Area buffer is the most visible feature. The Resource Management Area, Intensely Developed Area overlays, and recent coastal-resilience amendments round out the framework. This essay walks what CBPA actually restricts, what triggers review, and how it stacks with VSMP.

Virginia tidal river with wooded shoreline buffer at golden hour, photorealistic, warm cinematic lighting, Chesapeake Bay watershed aesthetic

The statutory setup

Primary source: deq.virginia.gov/our-programs/water/chesapeake-bay/chesapeake-bay-preservation-act.

Resource Protection Area (RPA) — the 100-foot buffer

RPAs are lands adjacent to water bodies with perennial flow that have intrinsic water-quality value. The landward 100-foot buffer is the defining feature:

The RPA buffer is not optional guidance — it's a binding development restriction. Projects with site plans crossing into an RPA face substantial redesign or denial.

Resource Management Area (RMA)

The RMA is contiguous to and inland of the RPA, covering land that could significantly degrade water quality or diminish RPA functions if improperly developed:

Intensely Developed Area (IDA) — optional overlay

IDAs are local-option overlay designations for already-developed portions of CBPAs, intended for redevelopment contexts:

For urban Tidewater contexts — downtown Norfolk, downtown Richmond, built-out Virginia Beach — IDA designation is the mechanism that keeps redevelopment viable within the CBPA framework.

How CBPA interacts with VSMP

CBPA and VSMP (see our VA VSMP essay) are complementary:

The practical effect: in Tidewater VA, a site project engages CBPA (RPA/RMA compliance) + VSMP (stormwater + ESC) + local zoning + USBC + any locality-specific requirements. The stacking is real; budget for all of it.

Which VA localities are on the 84-locality list

DEQ maintains the list; the core areas covered include:

Non-Tidewater localities (Shenandoah Valley, Southwest VA, most of the Piedmont beyond the coastal plain line) are not on the CBPA list. Project-specific verification matters — the Fall Line roughly delimits CBPA applicability but each locality's designation is authoritative.

What developers should know

How CBPA relates to coastal/shoreline work

CBPA is distinct from — and coexists with — other VA coastal frameworks:

Waterfront and coastal projects in Tidewater VA typically engage CBPA + one or more of the others. The full stack is substantial.

What to do with this

If you're developing in Tidewater VA: confirm CBPA designation on parcel; map RPA/RMA/IDA; treat the 100-foot RPA buffer as a design constraint from day one.

If you're doing a redevelopment in an urban Tidewater locality: verify IDA designation status — it changes what's feasible.

If you're adjacent to tidal water or connected wetlands: expect layered permits (CBPA + Wetlands + VMRC + USACE + local).

For VSMP interaction, see our VA VSMP essay. For VA contractor licensing, see our VA Class A/B/C essay. For statewide code, see our VA USBC essay.

About The Hive

The Hive builds tools and publishes essays for working construction and MEP professionals in the Delaware Valley and Mid-Atlantic. Primary-source-grounded, practitioner-voiced, free to use.