Weber County staff, developer outline new Traditional Neighborhood Zone; river setback and open-space rules draw debate

Jeff Beck, a representative for the project (developer/Black Pine/Blanchard), told the Weber County Planning Commission at a work session that the proposal would rezone roughly 550 acres to a new Traditional Neighborhood Zone, or TNZ, and attach a development agreement that will govern land uses, design standards and infrastructure for the master-plan community.

The proposed TNZ would “promote a pedestrian-friendly master plan development that binds diverse residential, commercial, civic, and recreational uses,” Beck said. The draft term sheet and design code linked to the agreement set a framework for density, open space, street layout and a town-architect review process to enforce design standards.

Why it matters: planning staff said the development agreement and new zone are intended to deliver public benefits — trails, interconnected streets, parks, and a mix of housing — that the county’s standard zoning and subdivision rules would not secure on their own. Commissioners and agency representatives pressed the developer on how open space would be defined and delivered, how phasing and securities would protect public infrastructure, and whether the county could or should require specific river setbacks along the Weber River.

Key points from the work session

• Project scope and new zone. Beck described the TNZ as a form-based, master-plan zone that directs most of the detailed rules to an attached development agreement and a design code. The draft limits most buildings to four stories in the main-street corridor and anticipates a maximum of about six dwelling units per acre in the areas governed by the design code. The development agreement term in the term sheet is 30 years with a five-year renewal option.

• Open-space target and how to count it. The draft ties open-space requirements to a formula staff and the developer proposed: roughly 10 acres of open space for every 330 dwelling units (a simplification of “10 acres per 1,000 residents,” using an assumed three residents per dwelling). Planners and park-district representatives said publicly accessible open space should count toward that total, while private-only amenities (private parks accessible only to HOA members) should not. The parks representatives said large, contiguous parks are easier for them to maintain, and cautioned about accepting many tiny pocket parks that would create long-term maintenance burdens for the park district.

• Phasing and securities. Charlie (county planning staff) explained the county would expect logical phasing tied to infrastructure and would require securities so unfinished public improvements could be completed if development stops. He and other staff said they prefer flexible phasing but want to avoid dead-end streets and disjointed infrastructure if a developer stops building partway through the project.

• Town architect, design code and administrative approach. The draft creates a town-architect position to enforce the design code and speed routine design approvals. Staff said the design code would handle most day-to-day design compliance; the county commission and planning division would retain oversight of major land-use changes and the ultimate development agreement.

• Vesting and legislative risk. Staff warned that development agreements change how vesting and future laws interact: the developer would be vested in some rights described in the agreement, but the county is reserving the ability to apply future laws in certain circumstances. The draft therefore tries to balance predictability for lenders with the county’s need to address public-safety or statutory changes.

• River setback and mitigation debate. One of the most contested items was a river setback for the Weber River corridor. The developer’s consultant presented a hydrologist’s review of other Wasatch Front counties and recommended an approach that would generally use a 100-foot minimum setback from the river channel, with larger setbacks (up to several hundred feet) in places where hydrology, ecology or park design warrant it. The developer said a thinner continuous corridor with larger parks at nodes could produce a more usable, maintained public amenity than a uniform 300-foot buffer.

Park-district staff, county staff and several commissioners expressed concerns about river-bank stability and maintenance. As one parks representative put it, maintenance access and the capacity to remove fallen trees are real constraints and must be considered in any reduced setback. A county hydrology consultant and the developer’s hydrologist both emphasized that projects proposed inside the larger corridor would need site-specific bank stabilization, erosion control, floodproofing, and stormwater studies before the county could find development in the setback acceptable.

• Legal and fallback options. The group discussed alternatives if a 300-foot county-wide setback proved legally or politically infeasible. Staff suggested an approach that preserves safety and ecological function while permitting site-specific reductions after hydrologic and geotechnical mitigation are approved. They also discussed a form-based zone and a street-regulating plan that could be used as a default if a development stops or reverts.

Selected direct quotations (from meeting participants)

- “The purpose of the traditional neighborhood zone is to promote a pedestrian-friendly master plan development that binds diverse residential, commercial, civic, and recreational uses,” Jeff Beck, project representative, said while describing the TNZ concept.

- “We’re happy to share the development agreement. I think part of it is just the concern of... getting stuck on points that don’t pertain to the planning commission from the land,” Charlie (county planning staff) said, offering to circulate the full draft agreement for review.

- “Parks are an essential part of traditional neighborhoods… Parks that are closely integrated with the neighborhood not only provide a greater amenity for residents of that neighborhood, but they provide a better experience for everyone who uses the park,” Mike Watkins, town architect/designer (quoted by project staff), said while discussing park design and the “Emerald Necklace” approach of connected, scaled park pieces and trail corridors.

Outcomes and next steps

No formal actions, motions or votes were taken during the work session. Planning staff and the applicant agreed to circulate the development agreement term sheet, the hydrologist’s report, and the design-code exhibits to planning commissioners and other stakeholders before the next work session. Planning staff said they will bring the development agreement term sheet and design code back for a more detailed review at the next work session and will seek input from the parks district, county engineers and river-maintenance staff on the river-setback recommendations.

What remains unresolved

- The county and the parks district have not agreed to a single uniform river setback; the developer proposes a default 100-foot minimum plus wider park nodes, while some commissioners and parks staff prefer larger buffers in some locations for safety and maintenance reasons.

- The exact open-space counting rules remain to be finalized (what qualifies as publicly accessible open space; how to treat HOA-maintained plazas or pocket parks).

- The legal framing of vesting, reversion and default-response mechanisms in the draft development agreement requires additional staff and legal review.

Documents and evidence

Planning staff and the developer said they will circulate: - The draft development agreement (term sheet and exhibits) - The draft TNZ zone text and design code - The hydrologic report prepared by Bowen Collins (river setback analysis and recommended mitigation measures)

Ending note

Planning staff told commissioners they will schedule a follow-up work session to review the design code in more detail, circulate the hydrology and term-sheet documents to the planning commission and park-district representatives, and convene targeted technical meetings (county engineers, parks staff, developer civil engineers and hydrologists) to refine river-setback options and mitigation requirements before any formal public hearing or decision.