Skip to main content
Your trusted guide to Provo, Orem & Utah Valley

Vesper Amphitheater: The Council Vote Slipped to August — and the Land Deal Came Into View

Provo's City Council was set to decide the Vesper Amphitheater rezone on July 14. That vote has been pushed to August. Here's what moved in the meantime — a 74.5-acre land sale, a draft development agreement, and a process where the council's real leverage isn't the yes.

The date everyone had circled came and went. Provo's City Council was scheduled to decide the Vesper Amphitheater rezone on July 14 — the vote that would settle whether a 20,000-seat venue can be built at the mouth of Provo Canyon. That vote didn't happen. It was pushed to August — and Provo City has since listed the item for the City Council meeting on Tuesday, August 11, 2026, at 5:30 p.m., in the City Council chambers.

That's the headline, and it's a smaller one than the city expected to be reading this month. But the weeks since the Planning Commission's denial haven't been empty. Reporting in mid-July surfaced two things that had been hazy before: the size and shape of the land deal Provo itself would have to sign, and the specific terms in the draft development agreement. Both matter more than the calendar slip.

Here's where the project actually stands.


What changed, and what didn't

Nothing about the proposal itself has been approved or rejected. The June 24 Planning Commission vote — 5-2 to recommend denial of the general plan and zone map amendments, plus denial of the concept plan — still stands as a recommendation. The City Council still holds the decision on the land-use changes. The only change is timing: what was a July agenda item is now an August one.

Advertisement

For a project of this scale, a few weeks of slippage is unremarkable. It's worth resisting the urge to read strategy into it. Council calendars move for ordinary reasons — document readiness, negotiation timelines, member availability — and neither supporters nor opponents should treat the delay as a signal about the outcome.

What the delay does mean, practically, is that anyone who wants to speak on the record has more runway than they thought. The city has listed the hearing for August 11, 2026, at 5:30 p.m. at the City Council chambers. Meeting agendas and public-comment procedures are posted at provo.gov — and because this item has already slipped once, confirm the date there before making plans around it.


Provo isn't just the referee — it's a seller

The detail that reframes the whole thing: Provo City owns most of the land.

The development footprint is roughly 100.7 acres. About 26.2 of those acres come from the Provo Canyon Mining Company, the private operator of the existing quarry. The remaining 74.5 acres or so would have to be purchased from Provo City itself.

That puts the city in two roles at once. It's the land-use authority deciding whether the zoning changes are appropriate, and it's the property owner negotiating a sale price. Those are different jobs with different incentives, and residents have noticed.

Mayor Marsha Judkins has been direct about where her influence sits, and it isn't the vote:

"I don't have a vote on approving this development or not. So where I have a say is kind of now, in this development agreement and the real estate contract."

Advertisement

On price, the picture is partial. Judkins has said she saw one appraisal and believed it came in around $1.3 million. That's her recollection of a single appraisal, not a confirmed sale price — and the underlying documents aren't public. Provo denied a public records request from KUER seeking documents and communications related to the parcel sale. Until the transaction terms are disclosed or the deal closes, the actual number should be treated as unconfirmed.

The mayor has also pushed back on the idea that the city land is pristine canyon. Most of it, she says, has already been disturbed: it's used for parking, sits beside a shooting range, and carries debris from that use. Satellite imagery is consistent with that description — the city parcel adjoins the mining company's pit rather than untouched hillside. That doesn't resolve the disagreement about whether the canyon mouth is the right place for a venue, but it does sharpen it. The argument isn't really about saving a meadow. It's about what a disturbed industrial site at a canyon entrance should become next.


The development agreement, in plain terms

The council won't vote on the rezone in isolation. It considers the development agreement alongside it, and that document is where the enforceable promises live.

As drafted and reported in July 2026, the agreement would require Vesper to:

Two honest caveats. First, these are draft terms; they can be renegotiated, strengthened, or weakened before adoption, and the version the council votes on is the one that counts. Second, the qualifier on the lighting standard — "to the extent reasonably possible" — is the kind of language that does real work in a contract. Whether it functions as a genuine constraint depends on who interprets "reasonably" later.

Wilf Sommerkorn, a retired urban planner now with the nonprofit Utah Land Use Institute, told KUER that an agreement like this isn't unusual, and that cities increasingly rely on them for a specific reason:

"You do see projects that get the rezones that they're looking for, and then the projects don't happen."

A development agreement is a contract. If a project stops honoring it — even years on — the city has grounds to act.


Why the council's real power is the "no," not the "yes"

This is the part of the process most people get backwards, and it's worth walking through slowly.

If the council grants the rezone, the project does not become approved. The sequence continues:

  1. Council approves the general plan amendment, the rezone, and the development agreement.
  2. Vesper completes the technical work — traffic, geotechnical, and environmental studies — and secures UDOT sign-off on highway access and infrastructure.
  3. The final project plan goes back to the Planning Commission.
  4. If that plan meets code and follows the development agreement, the commission must approve it.

Step four is the one that surprises people. Once the zoning and the agreement are in place, the commission's later role is largely ministerial — it checks compliance, not desirability. The discretionary judgment happens now.

But the agreement also runs the other direction. Provo is writing in a provision letting the council vote to rescind the rezone if Vesper doesn't meet the requirements, effectively shutting the project down.

Sommerkorn's framing captures it: the council doesn't get final approval, but it does get final disapproval.

For residents deciding where to spend their energy, that has a practical implication. The August vote is the last broad discretionary decision — the moment when "should this exist here at all" is squarely on the table. After that, the questions narrow to compliance.


The studies-first objection

One recurring public demand: do the traffic and environmental studies before the rezone vote, not after.

It's an intuitive ask. A canyon served by a single main road, absorbing crowds from a 20,000-seat venue, is exactly the scenario where you'd want numbers before commitments. The Orem City Council has already written to Provo warning about strain on US-189, and traffic was the concern the Planning Commission returned to most often.

Judkins has said developers typically won't fund expensive studies without some assurance the project is moving forward. Sommerkorn largely agreed that this is the normal order of operations, and noted the alternative some developers choose: buying land and betting on a rezone that may never come, sometimes losing significant money when it doesn't.

Both things can be true. The sequence is standard practice, and standard practice still leaves the council voting on a canyon-mouth entertainment district without a completed traffic study in hand. Residents who find that uncomfortable aren't misunderstanding the process — they're objecting to it, which is a different and entirely legitimate position.


Where the public pressure stands

The petition opposing the project has passed 5,000 signatures, with concerns clustering around canyon traffic, loss of open space, and precedent. Supporters continue to make the reclamation argument: the site is two idle gravel pits, and a venue would be an improvement over what's there now.

The Osmond family backing remains the project's most visible feature, and Vesper did not respond to KUER's request for comment before its publication deadline.

Whether any of that moves seven council members is the open question August answers.


What to watch

We'll cover the council's decision when it happens, whichever way it goes.


Related: The Vesper Amphitheater Fight, Explained · Provo Canyon and the Alpine Loop · Mount Timpanogos: The Complete Summit Guide · More from The Wire

Advertisement

Frequently Asked Questions

Did the Provo City Council vote on Vesper Amphitheater on July 14?
No. The council had been scheduled to take up the general plan map amendment and rezone on July 14, 2026, but the vote was pushed to August. Provo City has since listed the item for the City Council meeting on **August 11, 2026, at 5:30 p.m.** in the City Council chambers. As of late July 2026, no final council decision has been made on the land-use changes the project needs, and this item has already moved once — confirm the date on the Provo City Council agenda at provo.gov before planning around it.
Does Provo City own part of the Vesper Amphitheater site?
Yes, and that is a central piece of the deal. The development covers roughly 100.7 acres, of which about 26.2 acres come from a private mining company and about 74.5 acres would have to be purchased from Provo City. Mayor Marsha Judkins has said she saw one appraisal on the city parcel and believed it came in around $1.3 million. Provo denied a public records request from KUER for documents related to the sale, so the final terms are not public.
What is in the draft development agreement?
The draft agreement, as reported in July 2026, would require putting undeveloped property into a conservation easement, allowing public use and trail improvements within that easement, obtaining Utah Department of Transportation approval on a traffic management plan, designing dark-sky-compliant lighting to the extent reasonably possible, using noise-mitigating technology to limit off-site sound, and incorporating natural materials into the design. The mayor has said at least half the land would go into the easement and that any hotel would be capped at 75 rooms. Draft terms can change before adoption.
If the council approves the rezone, is the project approved?
No. A rezone is a first step, not a green light to build. After a rezone, the final project plan returns to the Planning Commission, which must approve it if it meets code and follows the development agreement. The project would still need traffic, geotechnical, and environmental studies plus UDOT sign-off. The draft agreement also lets the council vote to rescind the rezone if Vesper fails to meet the requirements — which is why the arrangement has been described as the council holding final disapproval rather than final approval.
Why does Provo want the project at all?
Mayor Judkins has framed it primarily as a revenue question. The city would collect money from selling the land, sales tax from venue activity, and a hospitality tax from a hotel on the site. She has said Provo struggles with point-of-sale tax revenue and that the city looks for options that avoid raising taxes on residents. Opponents argue the traffic, noise, and precedent costs in a one-road canyon outweigh that revenue.
P
Provo.com News Desk
Newsroom
The Provo.com News Desk covers community news, business openings, civic announcements, and cultural events across Provo, Orem, and Utah Valley. Stories are curated from local outlets, city sources, and primary reporting, then written in our own words to give residents, students, and visitors a faster way to track what's actually happening in the area.