Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Land Use Development topic
No spam. Unsubscribe anytime.
Developer frames ‘Vesper’ as gravel‑pit reuse; neighbors demand traffic, noise and conservation guarantees
Summary
At an informational North District meeting, the Vesper project team presented a concept to convert a long‑disturbed gravel pit at Provo Canyon’s mouth into an amphitheater and mixed venue. City staff and the developer said detailed studies and a development agreement are required; residents voiced strong concerns about traffic, noise, light and loss of open space.
Provo — Developers and city staff presented the Vesper amphitheater concept Thursday evening to a packed North District neighborhood meeting, and residents spent the bulk of public comment urging caution over traffic, noise, lighting and the scale of proposed development.
“Most of us understand what it feels like to look at an older home or property and see potential,” said Brian Bis, a representative of the Vesper project team. Bis described the proposal as “restoration and reuse” of a long‑disturbed gravel‑pit site and said the concept aims to replace industrial extraction with trails, conservation easements and public access while providing a venue for music and recreation. He emphasized the project is at a high‑level due‑diligence stage and that “the studies, engineering, agency review, public process, and development agreement commitments all have to support the path forward.”
City staff reiterated that the meeting was informational only and that formal approvals follow a multi‑step review. Development Services Director Bill Pepperon said three applications are active — a general‑plan amendment, a zone change (to SC3) and a concept plan — and that the planning commission will provide a recommendation to council. He said technical work such as traffic studies, geotechnical analysis and UDOT access review are required during the project‑plan stage and must demonstrate the project can meet applicable standards before approval. Pepperon also warned that, under state law, gravel pits carry unusual protections that limit what the city can unilaterally require of an existing mining operation.
Neighbors pressed for specifics. Residents and conservation groups repeatedly asked whether large‑event scenarios — which the developer described as varying from about 5,000–8,000 attendees for typical events to a maximum scenario that could reach roughly 20,000 when an indoor/ outdoor configuration is combined — would be feasible without unacceptable impacts. “Just because something can be done doesn’t mean it should,” said Kay Nelson of Conserve Utah Valley, who urged slower, more thorough study and stronger protections for the canyon.
Speakers raised a string of recurring concerns: how traffic and egress would be handled on the single canyon road, whether UDOT would allow required access changes, how emergency evacuation would work in wildfire scenarios, sound levels and decibel limits in a narrow echoing canyon, light pollution, water use and effects on wildlife and trails. Several speakers questioned the project’s footprint — Bis said the current concept covers roughly 100 acres, with about 40.3 acres inside the proposed development footprint and approximately 60 acres intended for conservation easement, but he added those numbers are preliminary and subject to change.
Some residents urged alternatives: smaller‑scale facilities, public‑land conservation, or leaving the site’s status unchanged. Others argued buying and reusing the gravel‑pit property could be preferable to leaving industrial operations in place; a few attendees said they favored redevelopment over housing or other uses that might occupy canyon land more permanently.
On process, staff clarified that a development agreement would be negotiated with the city and that zoning changes would not be finalized on city maps until that agreement is complete and signed by the mayor and developer. Pepperon said the application review began in March; meeting materials and staff comments are part of the public record. The meeting hosts and staff noted the planning commission is scheduled to consider the application on June 10 and the city council later in July (announced during the meeting as July 14), and attendees were urged to submit written comments and use a QR survey provided by the project team.
No formal action or vote was taken at the neighborhood meeting; it served to gather public feedback and to inform the city and developer as they continue technical studies and negotiate permit and agreement details. City staff and project representatives stayed afterward to answer individual questions from residents.
What’s next: the planning commission will review and make a recommendation at its scheduled hearing; if the zone change is approved by council the developer must still satisfy project‑plan requirements and sign a development agreement before zoning is recorded.
