Ivins council asks developer for clarifications, continues Red Mountain Resort development agreement

Ivins — The Ivins City Council on Thursday continued consideration of a development agreement for Red Mountain Resort after council members requested written clarifications on density limits, infrastructure capacity and construction impacts.

Council members said the draft agreement seeks to vest three principal elements for the developer: an overall cap of 500 units, the ability to cluster density within the project, and a locked-in table of uses for the RC (resort commercial) zone. Staff and the developer told the council those entitlements would still require further approvals on conditional uses and design at later planning and permitting stages.

Why it matters: The agreement would establish long-term vesting and use expectations across the Red Mountain/Black Desert property. Council members said the agreement as written contains too few specifics for final approval and that some items — such as whether the full 500 units could be developed given water and sewer ERU limits — must be tied to infrastructure analyses.

What council and staff said

City staff told the council that infrastructure work done for the parcel had sized utilities for about 233 equivalent residential units (ERUs) and that the 500-unit cap in the agreement does not automatically override ERU-based infrastructure limits. A staff member said, "They may not be able to even hit the 500 units... it was based on the fact that we'd already been sizing our infrastructure on that number." (staff comment on ERU limits.)

Developer representatives said the agreement was intended as an initial “first shot” to lock in broad parameters while reserving detailed design and conditional-use review for future submittals. One developer representative said the team had tried "to keep this development agreement very simple and very straightforward as the first shot." (developer representative)

Council concerns and requested follow-up

Councilmembers asked for written responses and edits on a range of technical and policy items (council member Gillespie circulated a list with 36 points). Specific concerns raised publicly included:

- Whether the 500-unit cap is attainable given utility ERU limits and what infrastructure studies would be required to exceed ERU assumptions. - How blasting would be scheduled and communicated to nearby residents and how the city would enforce or require advance notice of blasting. - Construction traffic routing, particularly large truck movements through existing roundabouts and the impact on adjacent neighborhoods.

Outcome and next steps

The council voted to continue the item to a future meeting and asked staff to compile council questions and transmit them to the developer. City staff indicated many of the design- and use-specific issues will be resolved during the conditional-use and site-plan review processes, but council members insisted that the development agreement itself be tightened on points that vest long-term rights.

Ending

The council’s decision leaves the draft agreement open for revision. The developer and staff will return with revised language and technical studies, including water/ERU and traffic analyses, before the council considers final approval.