If you’ve got a project anywhere near the Wasatch Front, you’ve probably already heard about Utah HB 400 secondhand — from a city planner, a civil engineer on your team, or a client who read a headline and wants to know what it means for their timeline. Here’s the short version: Utah HB 400 requires municipalities and counties within the Great Salt Lake basin to adopt, maintain, and enforce water-efficient landscaping standards for new development, with a compliance deadline of November 1, 2027. It was signed during the 2026 General Session, sponsored by Rep. Doug Owens and Sen. Lincoln Fillmore, and took effect May 6, 2026. You can read the full bill text directly from the Utah State Legislature.
We’ve been practicing as landscape architects in Utah and several other states since 2005, and we’ve sat through enough Wasatch Front entitlement cycles to know that bills like this rarely stay contained to the section of code they amend. HB 400 touches planting design, irrigation zoning, grading, and — depending on how a given municipality writes its ordinance — could reshape your review timeline too. This post walks through what the bill actually says, where it applies, and what it means for land planners, land developers, landscape architects, and landscape irrigation design consultants working across the basin.
What Is Utah HB 400 and Who Does It Apply To?
HB 400 amends two existing sections of Utah Code — 10-20-619 for municipalities and 17-79-615 for counties — both dealing with local landscaping regulation. The obligation to adopt an ordinance falls on the jurisdiction, not on individual property owners or design teams directly. But since it’s the jurisdiction that reviews your site plan, the practical burden lands on whoever’s designing the project.
“New development” is defined broadly: construction or expansion of a building or use that creates additional demand for public facilities, plus qualifying changes in use of a building, structure, or land. That’s a wide net. Most commercial, multifamily, and residential subdivision work that already triggers site plan review will fall under it.
One nuance worth flagging for out-of-state clients: this is a basin-scoped law, not a statewide one, which is a little unusual as far as Utah landscape architecture regulation goes. A project in St. George isn’t automatically subject to HB 400’s November 2027 deadline the way a project in Salt Lake, Davis, Weber, or Utah County would be.
The Great Salt Lake Basin: Where HB 400 Applies
The eight-foot turf rule. No municipality or county can require turf in a strip narrower than eight feet. That kills the traditional narrow parkway lawn as a mandatory element, full stop. If your streetscape plans still show 4- or 5-foot turf strips along curb frontage, those need to move toward groundcover, mulch, or hardscape treatments before they get to review.
Overhead spray irrigation. The statute doesn’t ban spray irrigation, but the definition of “water efficient” leans hard toward plant material that doesn’t need it. Expect ordinances to push ornamental beds toward drip and reserve overhead spray for turf areas that actually serve a recreational or functional purpose.
Milestone
Date
What It Means
HB 400 effective date
May 6, 2026
Statewide provisions — the 8-foot turf rule, the anti-prohibition clause — apply now, basin-wide
Local ordinance adoption deadline
November 1, 2027
Every basin municipality and county must have an enforceable water-efficient landscaping ordinance in place
Division of Water Resources reporting
Ongoing
Jurisdictions report ordinance status; the state publishes a public list of noncompliant jurisdictions annually
Regional standards adoption
Optional, ongoing
Jurisdictions can adopt regional water use efficiency standards, which ties into the state's turf-conversion incentive program
Here’s the part that trips people up: the November 2027 deadline is when the ordinance has to exist, not when it’s safe to ignore the bill until then. The 8-foot rule and the anti-prohibition clause are already law. And several Wasatch Front cities already had water-efficient landscaping codes before HB 400 passed — those now need to be reconciled with the new statutory floor, which means some ordinances you’re designing against today could change mid-review.
How HB 400 Affects Land Planners, Land Developers, Landscape Architects, and Landscape Irrigation Design Consultants
HB 400 doesn’t land the same way on every discipline at the table. It’s worth breaking out separately, because the questions a land planner needs answered at the entitlement stage aren’t the same ones a landscape irrigation design consultant needs answered when finalizing a controller schedule.
This is where the earliest decisions get made, and where a missed detail is cheapest to fix and most expensive to ignore. Basin status, right-of-way width, and open space allocation all need a second look under HB 400:
Confirm basin jurisdiction during initial due diligence, before a concept plan gets drawn — not after.
Revisit standard right-of-way and parkway strip widths. Any planting strip drawn under eight feet needs a different treatment than the turf default most master plans still default to.
Build water-efficient landscaping language into the entitlement narrative and any development agreement, particularly for phased master-planned communities where later phases might land under a different (and possibly stricter) version of a city's ordinance than phase one did.
Coordinate open space and common-area programming with the landscape architecture team early, since common-area turf reduction affects both maintenance budgets and how much of a project's open space requirement gets satisfied by functional versus ornamental space.
The planners we work with tend to treat this as a zoning question first and a design question second. That's backwards under HB 400 — the design standard is what drives whether the entitlement package clears review at all.
For Land Developers
For land developers, HB 400 is mostly a budgeting and scheduling issue, with a secondary marketing angle worth paying attention to:
Common-area landscape and irrigation costs may shift. Water-efficient palettes and drip zoning aren't necessarily more expensive than a traditional turf-and-spray plan, but the cost profile is different — less irrigation infrastructure, potentially higher plant material costs depending on palette.
The state's turf-conversion incentive under Section 73-10-37 can offset some of that cost in jurisdictions that adopt regional standards. That's worth a line item in your pro forma rather than an afterthought.
Schedule risk is real where a jurisdiction hasn't adopted its ordinance yet. A project that clears preliminary review today under an interim standard could face a different, stricter standard by the time it reaches final landscape plan approval.
For residential product, HB 400 allows (but doesn't require) a municipality to require sellers to disclose a water-efficient landscaping ordinance to the first buyer of a newly constructed home — worth checking with your sales and legal team on whether your jurisdiction has adopted that disclosure requirement.
Water-efficient common areas increasingly read as an amenity rather than a compromise to buyers and tenants, particularly in water-conscious submarkets. That's a marketing conversation worth having with your team rather than treating compliance purely as a cost center.
This is where HB 400 shows up most directly, day to day. A few things we've changed in how we run projects in the basin:
Hydrozone mapping now starts at schematic design, not construction documents, so planting plans and irrigation design develop together instead of irrigation chasing a finished planting plan.
Plant palettes need to be checked against each jurisdiction's specific vegetative coverage and prohibited-species standards rather than a single firm-wide standard palette applied across the portfolio.
Grading and drainage coordination with civil engineers matters more than it used to, since reduced turf area changes infiltration and runoff assumptions that were likely modeled around a turf-heavy landscape plan.
Construction documents and specifications should call out irrigation zoning explicitly by hydrozone, not just by planting bed, to make jurisdictional review straightforward and to avoid a resubmittal over ambiguous drip-versus-spray delineation.
Maintenance specifications carry more weight in review than they used to, since several ordinances condition approval on demonstrating that water-efficient plant material will be kept in a healthy condition long-term, not just installed to spec.
For Landscape Irrigation Design Consultants
Irrigation consultants are the discipline most directly on the hook for translating "water efficient" from a legal definition into a working system, and HB 400 raises the technical bar in a few specific ways:
Hydrozoning becomes a compliance document, not just good practice. Expect jurisdictions to want zones grouped by plant water need, not just by area, with drip and spray physically separated on controller schedules.
Controller programming and smart irrigation technology (ET-based or soil-moisture-sensor controllers) are increasingly the difference between a design that reads as "water efficient" on paper and one that actually performs that way in a compliance audit or a water-conservancy-district incentive inspection.
Design documentation needs to explicitly demonstrate reduced supplemental irrigation demand — precipitation rates, application efficiency, and zone-by-zone water budgets are worth including in submittals, not just holding in reserve for an RFI.
Coordinate directly with the landscape architect on which turf areas are functional (and can retain overhead spray) versus ornamental (and should move to drip or subsurface), since that distinction now has real design and budget consequences, not just an aesthetic one.
Where a project is pursuing the state's turf-conversion incentive, irrigation design needs to meet the specific drip-conversion requirements tied to that funding, which can be stricter than a jurisdiction's baseline ordinance.
What This Means for Site Plans, Phasing, and Irrigation Coordination
Irrigation design can’t sit downstream of planting design anymore — not that it ever really should have. Because the statute ties “water efficient” directly to irrigation method, hydrozone mapping needs to start early, so irrigation design and planting plans develop together instead of one chasing the other.
Grading and hydrology assumptions shift when turf area shrinks. If your civil team modeled infiltration or detention around a turf-heavy landscape plan, swapping in drought-tolerant beds changes runoff coefficients and maintenance access. That conversation needs to happen between landscape and civil early, not get discovered in a resubmittal.
CC&Rs deserve a second look, too. HB 400 prohibits ordinances that effectively bar water-efficient landscaping — which means a developer’s own design guidelines mandating turf coverage could end up in tension with both the ordinance and the statute’s protections for property owners. Worth a conversation with legal counsel on new master-planned communities before those documents get recorded.
And if a jurisdiction adopts the state’s regional water use efficiency standards, that opens the door to the turf-conversion incentive program under Section 73-10-37 — historically worth a couple dollars per square foot in some conservancy districts. For HOA-maintained common areas in particular, that’s worth flagging to the client early; it can meaningfully offset the cost of a lower-turf design.
For a broader sense of how water-efficient design principles are being applied outside Utah, the American Society of Landscape Architects maintains resources on water conservation in landscape design, and the EPA’s WaterSense program is a useful reference point for irrigation efficiency benchmarks that several Utah ordinances have drawn from.
For asset managers and CFOs evaluating the timing of an AB 1572 retrofit program, the financial calculus favors early action over deadline-driven compression — for several reasons.
No. The mandatory adoption requirement only reaches jurisdictions within the statutory basin boundary — the Bear River, Weber River, Jordan River, Utah Lake, and Tooele Valley drainages, plus the Great Salt Lake itself. A project in Washington County or Iron County isn’t subject to the November 2027 deadline, though nothing stops a city outside the basin from adopting similar standards on its own.
The Division of Water Resources publishes a public list of noncompliant jurisdictions each year. There’s no direct penalty spelled out in the bill beyond that. In practice, that means some cities will adopt late, or adopt an interim ordinance and revise it — so don’t assume the ordinance you’re designing against today is final. Ask.
Yes, and this trips people up. HB 400 doesn’t take away a municipality’s ability to review site plans, require plant maintenance standards, or set vegetative coverage minimums and maximums. It also doesn’t stop a city from restricting or banning specific plant materials. What it takes away is a city’s ability to ban water-efficient landscaping outright, or to mandate turf strips under eight feet wide.
No — that’s a common misread of the bill. Functional turf for active recreation, open space, or athletic fields is still a completely legitimate design element. What’s going away is the requirement to install turf in narrow, purely decorative strips, and the expectation that ornamental turf gets the same irrigation treatment as functional turf.
Section 73-10-37 of Utah Code funds incentive payments — historically a few dollars per square foot depending on the water conservancy district — for property owners converting turf to water-efficient landscaping. HB 400 links eligibility to whether the local jurisdiction has adopted the state’s regional water use efficiency standards, which gives cities an added reason to align their new ordinance with that framework rather than write something entirely custom.
Now, honestly. The statewide provisions — the eight-foot rule and the anti-prohibition clause — are already in effect. Waiting for your specific jurisdiction to formally adopt before you touch hydrozone planning or plant palette selection is how projects end up redesigning landscape plans mid-review. We’d rather have that conversation at schematic design than at plan check.
Let's Talk About Your Project's Jurisdiction
Utah’s HB 400 is a good reminder that a narrow-sounding bill can still reach into every phase of a project — palette, irrigation, grading, review timing — and every discipline on the team, from the land planner setting the concept plan to the irrigation consultant finalizing a controller schedule. Evergreen Design Group has been doing land planning, landscape architecture, and irrigation design for developers, civil engineers, architects, and design-build teams since 2005, licensed across multiple states, and we’re tracking how individual Wasatch Front jurisdictions are translating HB 400 into local code as those ordinances get adopted.
If you’ve got a project in the Great Salt Lake basin and want to talk through how HB 400 fits into your entitlement schedule, reach out to our team — we’re happy to look at your specific jurisdiction and figure out where the design decisions need to happen first.
Evergreen Design Group, a landscape architectural firm, was formed in 2005 by Rodney McNabb. After serving seven years in the U.S. Marine Corps, Rodney entered the landscape contracting business in 1992. Beginning his career as a landscape chemical applicator, Rodney’s employer quickly realized that Rodney was in the wrong position when he kept unintentionally killing all the grass he was spraying for weeds. While this was a commercial landscape maintenance business, Rodney was quickly re-routed to fill the company’s first sales and estimator position for landscape construction projects. This is where Rodney began to excel. After a few short years, he was promoted to oversee the operations of the different branch offices of this company. He even went to work for another firm where he was a regional manager overseeing multiple offices in multiple states that focused on the exterior and interior landscape maintenance of shopping malls. Rodney eventually formed his full-service landscape company – focusing on design, installation, and maintenance. While enjoying the contractor world, he enjoyed the design side more and created Evergreen Design Group to focus strictly on landscape design and consulting. Evergreen Design Group grew quickly and efficiently. The firm now employs approximately 15 landscape architects, landscape designers, and irrigation designers – and focuses on projects all over the U.S. View all posts by Rodney McNabb
If you’ve got a project anywhere near the Wasatch Front, you’ve probably already heard about Utah HB 400 secondhand — from a city planner, a civil engineer on your team, or a client who read a headline and wants to know what it means for their timeline. Here’s the short version: Utah HB 400 requires municipalities and counties within the Great Salt Lake basin to adopt, maintain, and enforce water-efficient landscaping standards for new development, with a compliance deadline of November 1, 2027. It was signed during the 2026 General Session, sponsored by Rep. Doug Owens and Sen. Lincoln Fillmore, and took effect May 6, 2026. You can read the full bill text directly from the Utah State Legislature.
We’ve been practicing as landscape architects in Utah and several other states since 2005, and we’ve sat through enough Wasatch Front entitlement cycles to know that bills like this rarely stay contained to the section of code they amend. HB 400 touches planting design, irrigation zoning, grading, and — depending on how a given municipality writes its ordinance — could reshape your review timeline too. This post walks through what the bill actually says, where it applies, and what it means for land planners, land developers, landscape architects, and landscape irrigation design consultants working across the basin.
What Is Utah HB 400 and Who Does It Apply To?
HB 400 amends two existing sections of Utah Code — 10-20-619 for municipalities and 17-79-615 for counties — both dealing with local landscaping regulation. The obligation to adopt an ordinance falls on the jurisdiction, not on individual property owners or design teams directly. But since it’s the jurisdiction that reviews your site plan, the practical burden lands on whoever’s designing the project.
“New development” is defined broadly: construction or expansion of a building or use that creates additional demand for public facilities, plus qualifying changes in use of a building, structure, or land. That’s a wide net. Most commercial, multifamily, and residential subdivision work that already triggers site plan review will fall under it.
One nuance worth flagging for out-of-state clients: this is a basin-scoped law, not a statewide one, which is a little unusual as far as Utah landscape architecture regulation goes. A project in St. George isn’t automatically subject to HB 400’s November 2027 deadline the way a project in Salt Lake, Davis, Weber, or Utah County would be.
The Great Salt Lake Basin: Where HB 400 Applies
The eight-foot turf rule. No municipality or county can require turf in a strip narrower than eight feet. That kills the traditional narrow parkway lawn as a mandatory element, full stop. If your streetscape plans still show 4- or 5-foot turf strips along curb frontage, those need to move toward groundcover, mulch, or hardscape treatments before they get to review.
Overhead spray irrigation. The statute doesn’t ban spray irrigation, but the definition of “water efficient” leans hard toward plant material that doesn’t need it. Expect ordinances to push ornamental beds toward drip and reserve overhead spray for turf areas that actually serve a recreational or functional purpose.
Here’s the part that trips people up: the November 2027 deadline is when the ordinance has to exist, not when it’s safe to ignore the bill until then. The 8-foot rule and the anti-prohibition clause are already law. And several Wasatch Front cities already had water-efficient landscaping codes before HB 400 passed — those now need to be reconciled with the new statutory floor, which means some ordinances you’re designing against today could change mid-review.
How HB 400 Affects Land Planners, Land Developers, Landscape Architects, and Landscape Irrigation Design Consultants
HB 400 doesn’t land the same way on every discipline at the table. It’s worth breaking out separately, because the questions a land planner needs answered at the entitlement stage aren’t the same ones a landscape irrigation design consultant needs answered when finalizing a controller schedule.
For Land Planners
Land Planners
This is where the earliest decisions get made, and where a missed detail is cheapest to fix and most expensive to ignore. Basin status, right-of-way width, and open space allocation all need a second look under HB 400:
The planners we work with tend to treat this as a zoning question first and a design question second. That's backwards under HB 400 — the design standard is what drives whether the entitlement package clears review at all.
For Land Developers
For land developers, HB 400 is mostly a budgeting and scheduling issue, with a secondary marketing angle worth paying attention to:
For Landscape Architects
Landscape Architects
This is where HB 400 shows up most directly, day to day. A few things we've changed in how we run projects in the basin:
For Landscape Irrigation Design Consultants
Irrigation consultants are the discipline most directly on the hook for translating "water efficient" from a legal definition into a working system, and HB 400 raises the technical bar in a few specific ways:
What This Means for Site Plans, Phasing, and Irrigation Coordination
Irrigation design can’t sit downstream of planting design anymore — not that it ever really should have. Because the statute ties “water efficient” directly to irrigation method, hydrozone mapping needs to start early, so irrigation design and planting plans develop together instead of one chasing the other.
Grading and hydrology assumptions shift when turf area shrinks. If your civil team modeled infiltration or detention around a turf-heavy landscape plan, swapping in drought-tolerant beds changes runoff coefficients and maintenance access. That conversation needs to happen between landscape and civil early, not get discovered in a resubmittal.
CC&Rs deserve a second look, too. HB 400 prohibits ordinances that effectively bar water-efficient landscaping — which means a developer’s own design guidelines mandating turf coverage could end up in tension with both the ordinance and the statute’s protections for property owners. Worth a conversation with legal counsel on new master-planned communities before those documents get recorded.
And if a jurisdiction adopts the state’s regional water use efficiency standards, that opens the door to the turf-conversion incentive program under Section 73-10-37 — historically worth a couple dollars per square foot in some conservancy districts. For HOA-maintained common areas in particular, that’s worth flagging to the client early; it can meaningfully offset the cost of a lower-turf design.
For a broader sense of how water-efficient design principles are being applied outside Utah, the American Society of Landscape Architects maintains resources on water conservation in landscape design, and the EPA’s WaterSense program is a useful reference point for irrigation efficiency benchmarks that several Utah ordinances have drawn from.
For asset managers and CFOs evaluating the timing of an AB 1572 retrofit program, the financial calculus favors early action over deadline-driven compression — for several reasons.
FAQ: Utah HB 400 and Landscape Design
Does Utah HB 400 apply to my project if it's outside the Great Salt Lake basin?
No. The mandatory adoption requirement only reaches jurisdictions within the statutory basin boundary — the Bear River, Weber River, Jordan River, Utah Lake, and Tooele Valley drainages, plus the Great Salt Lake itself. A project in Washington County or Iron County isn’t subject to the November 2027 deadline, though nothing stops a city outside the basin from adopting similar standards on its own.
What happens if a municipality doesn't adopt an ordinance by November 1, 2027?
The Division of Water Resources publishes a public list of noncompliant jurisdictions each year. There’s no direct penalty spelled out in the bill beyond that. In practice, that means some cities will adopt late, or adopt an interim ordinance and revise it — so don’t assume the ordinance you’re designing against today is final. Ask.
Can a city still reject our planting plan or require specific plants?
Yes, and this trips people up. HB 400 doesn’t take away a municipality’s ability to review site plans, require plant maintenance standards, or set vegetative coverage minimums and maximums. It also doesn’t stop a city from restricting or banning specific plant materials. What it takes away is a city’s ability to ban water-efficient landscaping outright, or to mandate turf strips under eight feet wide.
Does this mean turf is basically banned in new development?
No — that’s a common misread of the bill. Functional turf for active recreation, open space, or athletic fields is still a completely legitimate design element. What’s going away is the requirement to install turf in narrow, purely decorative strips, and the expectation that ornamental turf gets the same irrigation treatment as functional turf.
How does the state incentive program factor in?
Section 73-10-37 of Utah Code funds incentive payments — historically a few dollars per square foot depending on the water conservancy district — for property owners converting turf to water-efficient landscaping. HB 400 links eligibility to whether the local jurisdiction has adopted the state’s regional water use efficiency standards, which gives cities an added reason to align their new ordinance with that framework rather than write something entirely custom.
When should we start designing around Utah HB 400, even if our city hasn't adopted its ordinance yet?
Now, honestly. The statewide provisions — the eight-foot rule and the anti-prohibition clause — are already in effect. Waiting for your specific jurisdiction to formally adopt before you touch hydrozone planning or plant palette selection is how projects end up redesigning landscape plans mid-review. We’d rather have that conversation at schematic design than at plan check.
Let's Talk About Your Project's Jurisdiction
Utah’s HB 400 is a good reminder that a narrow-sounding bill can still reach into every phase of a project — palette, irrigation, grading, review timing — and every discipline on the team, from the land planner setting the concept plan to the irrigation consultant finalizing a controller schedule. Evergreen Design Group has been doing land planning, landscape architecture, and irrigation design for developers, civil engineers, architects, and design-build teams since 2005, licensed across multiple states, and we’re tracking how individual Wasatch Front jurisdictions are translating HB 400 into local code as those ordinances get adopted.
If you’ve got a project in the Great Salt Lake basin and want to talk through how HB 400 fits into your entitlement schedule, reach out to our team — we’re happy to look at your specific jurisdiction and figure out where the design decisions need to happen first.
Get in Touch with Us
Ensure your compliance with CA AB 1572 now, before the deadline approaches.
Related Posts
Author: Rodney McNabb
Evergreen Design Group, a landscape architectural firm, was formed in 2005 by Rodney McNabb. After serving seven years in the U.S. Marine Corps, Rodney entered the landscape contracting business in 1992. Beginning his career as a landscape chemical applicator, Rodney’s employer quickly realized that Rodney was in the wrong position when he kept unintentionally killing all the grass he was spraying for weeds. While this was a commercial landscape maintenance business, Rodney was quickly re-routed to fill the company’s first sales and estimator position for landscape construction projects. This is where Rodney began to excel. After a few short years, he was promoted to oversee the operations of the different branch offices of this company. He even went to work for another firm where he was a regional manager overseeing multiple offices in multiple states that focused on the exterior and interior landscape maintenance of shopping malls. Rodney eventually formed his full-service landscape company – focusing on design, installation, and maintenance. While enjoying the contractor world, he enjoyed the design side more and created Evergreen Design Group to focus strictly on landscape design and consulting. Evergreen Design Group grew quickly and efficiently. The firm now employs approximately 15 landscape architects, landscape designers, and irrigation designers – and focuses on projects all over the U.S. View all posts by Rodney McNabb
California AB 1572 Retrofit Compliance for Existing Commercial Properties: A Portfolio Owner's Guide to the Nonfunctional Turf Irrigation Ban
Low-Water-Use Landscape Ordinances in Phoenix, Scottsdale, Tucson, and Mesa: A Developer's Comparison