The Vesper Amphitheater proposal has not been voted down in Provo. It has not been approved either. The application that spent four months moving toward a city council decision no longer exists, because the developers pulled it days before the council's first real opportunity to vote — and in the weeks since, the neighboring city that has to absorb most of the traffic has put its objection in writing and passed it.
That is a more complicated outcome than either side wanted, and it is worth being precise about, because "withdrawn" has been read in public as everything from "dead" to "nothing happened."
What actually happened
The proposal — a 20,000-seat outdoor music venue near the mouth of Provo Canyon, made public in May 2026 and led by David Osmond with his uncle, the entertainer Donny Osmond — was set to reach the Provo City Council in early September. That meeting mattered because it would have been the first genuine chance for Provo's elected officials to vote on the plan rather than discuss it.
The vote did not happen. The Provo City Council announced that the developers had withdrawn their application and intended to restart the process, and the item came off the agenda.
Reporting on the withdrawal has tied it to council concerns about traffic safety and noise. The council's own public statement was careful about what it did and did not know: it said it could not speak to precisely what a new application would propose until one is actually submitted, and that the understanding is the revised plan will address the Critical Hillside Overlay Zone and parking requirements.
A representative for the developers framed the move as a pause — reassess, then come back with something that reflects what the community has said. On the substance of a revised plan, the details circulating are exactly that, circulating: reports have described reduced parking and restaurants, retail and concessions capped at 40,000 square feet, with the seating capacity and a 75-room hotel unchanged. We are attributing that rather than adopting it. Until an application is filed with Provo, nobody outside the development team knows what is in it, and the council said as much itself.
This is the fourth date that did not produce a decision
Anyone following this since spring will recognize the pattern, and it is the most useful thing to understand about the timeline.
August 11 was widely described as the vote. It was not — Provo City's own project page said the item was going to the council for initial consideration, with the earliest possible vote later. August 25 was then named as the earliest. That passed. September 8 became the next published date. Then the application was withdrawn and the September meeting lost the item altogether.
Four moments, four non-decisions, and the fourth one failed for a completely different reason than the first three. The first three were continuances in a live process. This one is the process itself being restarted.
Orem's resolution, and what it can and cannot do
Orem's council has now passed a formal resolution opposing the development. It followed an open letter from the Orem mayor and council published on the city's own site, and the letter is unusually direct about why a city is commenting on a decision outside its borders at all: they do not typically weigh in on matters outside Orem, but consider the impacts on the health, safety and welfare of Orem residents too significant to ignore.
Three specific objections are named:
- Sound and light pollution.
- Impacts on Orem's Mt. Timpanogos Park and the people who use it.
- Traffic on SR-189 and SR-52 — the Provo Canyon highway and 800 North. The council's position is that a development at this scale cannot proceed without significant and costly transportation improvements, many of which would fall on Orem.
Timing matters here. The letter was written after the withdrawal, and says so — the council noted that although the original application had been withdrawn, a revised proposal is understood to be coming and their concerns remain either way. This was not a reaction to a live vote. It was a position taken deliberately for the record ahead of the next one.
What the resolution cannot do is stop anything. The site is inside Provo's boundaries and Provo's council holds the land-use authority, which Orem's letter explicitly acknowledges while asking Provo to weigh the impacts anyway. A neighboring city's resolution is a formal statement, not a veto.
What it can do is harder to dismiss. It puts a documented objection from an affected municipality into the record of a process that has to start again, and it names the specific impacts a revised application now has to answer in public. Orem also asked for something broader than opposition: a joint long-term vision for Provo Canyon involving Provo, Orem, the state, Utah County and the regional planning bodies.
What a revised application has to clear
The route back is the route it came, from the beginning.
A new submission goes to the Provo Planning Commission first. That body recommended denial of the concept plan in June 2026, and the commission stage is not a formality — it is where the hillside overlay and parking questions the council flagged get examined in detail. Only after that does a revised proposal reach the City Council, which is the body that would actually vote.
So the earliest realistic decision point is some distance out, and we are not going to publish a date for it. Four published dates have now come and gone without a vote, and the reason this page exists at all is that treating a scheduled meeting as a decision has been the single most common error in coverage of this project — including, at one point, in ours.
What we will and will not tell you next
We will report the revised application when it is actually filed with Provo, and we will link the filing rather than the coverage of it. We will report the Planning Commission hearing when it is noticed, and we will describe it as a hearing rather than a verdict.
We will not publish a fifth "the vote is on this date" headline until a date is on a Provo City agenda with the item actually on it. That is the standard this story has earned.
Related Guides
- The Vesper Amphitheater fight, explained — what is proposed, and the case on both sides
- Vesper: August 11 is not the vote — the first of the four dates that did not produce a decision
- Vesper: no vote on August 25 either — the pre-withdrawal record, kept as written
- Provo Canyon — the canyon itself, and why the traffic argument is what it is
- Public meetings in Utah Valley — how to find agendas and speak at a hearing