Provo's Noise Ordinance: What 55 Decibels Actually Sounds Like

JoAnn Giordano Editor-in-Chief, Provo.com

There is a specific kind of Provo argument that happens over a fence, usually in September, usually between someone who has lived on the street for twenty years and someone who moved in three weeks ago. It runs like this: there's a city ordinance and you're breaking it. And then: no there isn't, I looked it up.

They are both, in a sense, right. There is an ordinance. And what the newcomer looked up was almost certainly wrong.

Provo repealed and re-enacted its entire public disturbances chapter in 2025, and a good share of the internet has not caught up. Search for Provo's noise limits and you will find pages confidently reporting an 85-decibel daytime cap for residential property, along with a rule requiring loud venues to take a mandatory ten-minute sound break. Neither of those is the law in Provo. The 85 dBA figure comes from the ordinance the city replaced. The sound-break provision does not appear in the current text at all.

Here is what Chapter 9.06 actually says, why the numbers are lower than people expect, and what happens when someone finally calls.

The table that settles most arguments

Provo's limits live in Section 9.06.040, and they are refreshingly short. Everything turns on two questions: what time is it, and what kind of property is receiving the noise.

Measured, per the section, at the property line or beyond.

Three things in that table do more work than they look like they do.

The limit follows the listener, not the noisemaker. The classification that matters is the property receiving the sound. A commercial building running a loading dock at 6:00 a.m. does not get to claim its own zoning. If the sound crosses into a residential property line, the residential number applies. Section 9.06.040(2) makes this explicit for the messy cases: when a noise source can be measured from properties in more than one land use category, the most restrictive classification governs.

Industrial property does not get quieter at night. Its 75 dBA cap is identical at 3:00 a.m. and 3:00 p.m. That is deliberate — an industrial receiving property has no one trying to sleep in it. But it cuts the other way too, and this is where Provo's geography starts to matter. Much of the city's older housing sits close to rail, to light industry along the west side, and to the arterials that feed them. The industrial cap applies to what industrial land receives. It does not license an industrial operator to push 75 dBA across the street into a bungalow.

Entertainment venues have their own ceiling. Section 9.06.040(3) makes it unlawful for any public entertainment venue — restaurants, bars, cafes, discotheques or dance halls, in the ordinance's own list — to maintain a sound level exceeding 105 dBA. This is a flat cap, not a property-line measurement, and it is the provision most often misquoted online, because the previous ordinance paired a similar number with a mandatory cooling-off period. The current chapter simply prohibits the level.

Fifty-five decibels is quieter than you think

Numbers in a table do not tell you whether your neighbor's swamp cooler is a problem, so it is worth grounding them.

A normal conversational voice a few feet away sits around 60 dBA. A refrigerator hums in the 40s. A window unit or a dishwasher running in the next room lands close to 55 to 60. Ordinary daytime traffic on a busy street will push past 70 without anyone thinking about it.

Which means the overnight residential limit of 55 dBA is set at roughly the level of people talking. That is not an accident. The number encodes a judgment about what a residential property is for after 10:00 p.m., and the judgment is that sustained sound at conversational volume, arriving at your property line from somewhere else, is more than you should have to absorb.

Two properties of decibels catch people out. The scale is logarithmic, so the gap between the daytime 65 and the overnight 55 is not a ten percent difference — it is a factor of roughly ten in sound energy. And the A-weighting in "dBA" deliberately discounts very low frequencies, tracking how human hearing works. That last point is genuinely double-edged for anyone bothered by bass. A subwoofer two houses down can be the only thing you can hear at midnight and still register modestly on an A-weighted meter, because A-weighting is doing precisely what it was designed to do: it is not listening the way an annoyed person at 12:30 a.m. is listening.

The rule that means a meter is not required

If you read only one sentence of Chapter 9.06, read Section 9.06.030.

It provides that sound level measurements, though generally preferred, are not required to demonstrate a violation if sufficient evidence or testimony proves the existence of a disturbance or public nuisance. It goes on to say that when city personnel do take measurements for enforcement, they should use equipment and procedures reasonably calculated to produce reliable measurements.

This is the practical hinge of the whole chapter, and it explains something about the 2025 rewrite. Reporting at the time of the council's work described a police department frustrated by an ordinance that was long, hard to interpret, and unclear about what evidence was needed to charge — with the added obstacle that enforcing it seemed to demand decibel-reader equipment officers did not reliably carry. The rewrite cut the number of enforcement options dramatically and left a short chapter with a plain evidentiary rule at the front.

So the folk theory that you are safe unless an officer arrives with a calibrated meter is wrong, and has been since the rewrite. Observation and testimony can carry a case. The corollary matters if you are the one complaining: a contemporaneous record helps. Dates, times, how long it ran, whether you could hear it indoors with the windows shut. That is testimony, and testimony is expressly sufficient.

The two patterns the ordinance measures

Section 9.06.040(1) does not treat noise as a single instantaneous reading. The limits apply to two shapes:

• continuous noise, assessed over two-minute intervals; or
• intermittent noise that exceeds the maximum five or more times within a ten-minute period.

The intermittent test is the one people trip over. A common defense — it stops, so it isn't continuous — collapses immediately against a five-in-ten standard. A car alarm cycling, a dog on a repeating bark, a bass track with gaps between songs, a compressor kicking on and off: all of these are the pattern the second clause was written for.

Equally, a single slammed car door at 11:00 p.m. is neither pattern. It is genuinely not a violation of Section 9.06.040, however irritating. The ordinance is aimed at sustained or repeating sound, not at the ordinary punctuation of people living near each other.

The eight exemptions, and the one that surprises homeowners

Section 9.06.050(2) exempts eight categories outright:

1. Emergency vehicles and sounds giving warning of emergencies.
2. Official inter-school athletic competitions, at a venue designed for such competitions and located on an educational institution's property.
3. Between 7:00 a.m. and 10:00 p.m., noise from a source on an educational institution's property — including a public address system — produced as part of a class or institution-sponsored event, including musical or athletic performances, practices and competitions, conducted consistently with the venue's purpose.
4. City-sponsored events, celebrations and public social gatherings.
5. Temporary activities permitted by law for which a city license or permit has been issued.
6. Fireworks discharged in compliance with Utah Code Title 53, Chapter 7.
7. Equipment removing snow and ice from roads and walkways.
8. Landscaping equipment operating between 8:00 a.m. and 8:00 p.m.

That last one deserves its own paragraph, because it is the exemption that generates the most fence-line disagreement in Provo, and because it does not track the general 7:00 a.m. boundary that governs everything else.

Landscaping equipment is exempt from 8:00 a.m., not 7:00. A leaf blower or a mower at 7:15 a.m. is outside the exemption window even though the general daytime period has begun. It closes at 8:00 p.m., not 10:00 — so the neighbor finishing the lawn at 9:00 p.m. in July, with plenty of light left, is also outside it. Between those hours, a mower is exempt regardless of what it reads on a meter.

The educational-institution exemptions are worth reading closely if you live near BYU. Item 2 is unbounded in time: an official inter-school athletic competition at a purpose-built venue on campus property is exempt, full stop. Item 3 is bounded — 7:00 a.m. to 10:00 p.m. — and covers the wider category of institutional classes and events, including public address systems and practices. The distinction is doing real work in a city where a stadium, a marching band's practice field and a residential neighborhood are within a few hundred yards of each other.

When you can be loud on purpose

Section 9.06.050(1) is the permit route, and it is more accessible than people assume.

The Mayor or the Mayor's designee may grant a written permit exempting an event from some or all of the chapter's restrictions. The permit has to specify three things: the nature of the event being exempted, the maximum allowable noise level in dBA, and the duration of the exemption. Each permit covers a single event unless it says otherwise. It may impose reasonable conditions to protect public peace and welfare — and if those conditions are violated, the exemption may be revoked on the spot.

The city's own guidance has historically pointed people to the Mayor's office to start this conversation, and has been candid that a permit comes with an expectation: if complaints are filed during the event, the applicant is expected to work with police to accommodate the reasonable needs of neighbors. A permit is not a shield. It is a negotiated allowance with a revocation clause attached.

For a wedding reception in a backyard, a block party, or a construction project that genuinely cannot be done inside the window, this is the correct move — and it is dramatically better than the alternative of hoping nobody calls.

What actually happens when someone calls

Two different systems handle noise in Provo, and picking the wrong one is why complaints sometimes seem to vanish.

A live event goes to police. A party, a car stereo, a dog, an argument at volume. This is a non-emergency call, not a 911 call, unless something beyond noise is happening. Chapter 9.06 includes a dedicated section on police response to a public disturbance, which tells you the drafters expected this to be the ordinary path.

A chronic property condition goes to code compliance. A commercial exhaust fan, a rooftop unit that has been failing since spring, a business operating outside the terms of its permit. These are structural problems, and an officer at 11:00 p.m. cannot fix a rooftop unit. Provo's code compliance line — (801) 852-6427 — and the city's online reporting form are the better route, and the city takes complaints about property conditions through that channel routinely.

There is also a middle path that resolves more of these than either system does, and the city's own materials on being a good neighbor lean on it: talk first. Not because the ordinance is toothless, but because most noise in a dense student-adjacent city is the byproduct of someone who has not thought about it rather than someone who has decided not to care. A conversation resolves the swamp cooler; an ordinance resolves the neighbor who already knows and does not care. Knowing which one you have is most of the problem.

Beyond Provo city limits

Every Utah Valley city writes its own version of this, and the numbers are not portable. Orem, Springville, Lehi, American Fork and Spanish Fork each maintain their own noise provisions, and the hours, the decibel figures and the exemption lists differ from Provo's in ways that matter. If you are in an unincorporated pocket, county provisions govern instead.

Two things generalize. First, the receiving-property principle is close to universal — the classification of the land taking the noise is what sets the limit. Second, the landscaping and construction carve-outs are where cities differ most, because that is where each council has drawn its own line between a working town and a sleeping one.

There is one more Provo-specific wrinkle worth naming. This is a city where a stadium, a university with a marching band, two hospitals with helicopters, a rail corridor, a regional airport and roughly thirty thousand students all sit inside the same municipal boundary as a great many people trying to sleep. The exemption list in Section 9.06.050 is not an accident of drafting — it is a map of the compromises a city like this has to make in order to function at all. Reading it that way makes the ordinance considerably easier to live with.

The rule of thumb: look up your own city's code, and check the enactment date on the section you are reading. Provo's current chapter carries a 2025 repeal-and-re-enact notation, and the city code site states plainly that the code is current through Ordinance 2026-17, passed June 9, 2026. A page without that kind of stamp is a page that might be quoting a repealed number at you — which is exactly how the 85-decibel myth outlived the ordinance it came from.

Related reading

• Calling Provo Police Without Calling 911 — the non-emergency line, online reports and records
• Dog Parks & Pet Life in Provo — including what to do about a barking dog next door
• Tree Removal in Utah Valley — the other ordinance that surprises Provo homeowners
• What Provo Can Actually Cite You For: Weeds, Junk Vehicles and the Nuisance Code
• Provo's Elevation: How High It Is and What That Actually Changes
• Where Provo's Water Actually Comes From
• Looking Up Property Records in Utah County: Four Offices, One Parcel Number
• The Fault Under Utah Valley: What the Forecast Actually Says, and What It Leaves Out
• How to Actually Follow Provo City Council (and Be Heard at One)
• Family Court in Utah County: The 30 Days, the Two 90s, and What the Forms Assume You Know

JoAnn Giordano

Editor-in-Chief

JoAnn Giordano is the editor-in-chief of Provo.com. Having lived in and around Utah Valley for years, she leads the site's editorial direction with a focus on the comprehensive, honest local coverage that helps residents, students, and newcomers feel at home. When she's not shaping Provo.com's restaurant and neighborhood coverage, she's exploring the valley's trails and tracking down the best new spots on Center Street.