Provo runs on a code enforcement paradox. The city is dense, young, transient in large patches, and full of houses built for one kind of household and occupied by another. That produces friction. And the mechanism for resolving that friction is a phone number most residents could not name if asked.
It is (801) 852-6427, and the division on the other end describes its own remit in eleven words: poorly maintained properties, junk vehicles, or overgrown weeds in your neighborhood.
That short list conceals a genuinely sprawling body of code — four separate titles of the Provo City Code touch it, and one of them is an entire administrative enforcement program. What follows is the map: which section governs what, what the city can actually do about it, and what happens in the weeks between a complaint and anything visible on the ground.
The four places the rules live
Most residents assume there is a single "code enforcement ordinance." There is not. Provo distributes this across four titles, and knowing which one you are in changes what happens next.
Title 7 — Health and Sanitation. This is where nuisance is defined. The city's own summary of Section 7.01 lists what typically qualifies: visual blights, noxious weeds, trash, discarded or unused furniture, dead trees or other dead or diseased vegetation, graffiti, dilapidated buildings, signs and fences. It is a deliberately wide net.
Title 14 — Zoning. Section 14.34.080 carries the awkward but precise title Trash Storage, Abandoned, Wrecked, or Junked Vehicles; Miscellaneous Materials. This is the workhorse. Junk, trash, weeds and inoperable vehicles all route through here.
Title 15 — Land Use and Development. Sections 15.20.060 and 15.20.070 govern landscaping — what you may plant and how you must maintain it.
Title 17 — Provo City Administrative Enforcement Program. An entire title devoted to the machinery of enforcement, which tells you something about how the city prefers to handle these matters: administratively, not criminally, wherever it can.
Weeds: a consequence test, not a height test
Plenty of cities set a number. Twelve inches, eighteen inches, some measurable threshold you can argue about with a tape measure.
Provo mostly does not, and the drafting is more interesting for it.
Section 14.34.080(5) makes it a class B misdemeanor to maintain or store on any property within Provo City "injurious or noxious weeds, garbage, refuse, or unsightly or deleterious objects or structures" — but only when such may constitute one of six things:
- a health hazard;
- a present danger to the citizens of the city;
- a potential source of contagious disease;
- a harborage for rats or other rodents, or other carriers of disease;
- a fire hazard; or
- an attractive nuisance likely to cause injury to small children.
The clause structure matters enormously. Tall weeds alone are not the offense. Tall weeds that have become a fire hazard are — and in a valley where August routinely bakes the untended margins of vacant lots into tinder, that condition is met more often than people think. The same goes for the rodent-harborage limb, which is why a pile of scrap lumber against a fence is treated differently from a pile of the same lumber stacked and off the ground.
A separate and much plainer standard applies to landscaped areas. Section 15.20.070 requires landscaping to be maintained by the property owner in a live and thriving condition — fertilized, mowed, trimmed, edged, and free from weeds. That is a maintenance obligation with no consequence test attached. It applies to what you have chosen to plant.
Which raises the question everyone in a drought state eventually asks.
Yes, you can xeriscape
The single most persistent misconception in Provo code enforcement is that "live and thriving" means lawn, and that letting grass go means a citation.
It does not. The city states directly that xeric landscaping is allowed, and points to Section 15.20.060 for its design standards.
The distinction is between what and how well. Section 15.20.060 governs what a compliant xeric design looks like. Section 15.20.070 governs the upkeep of whatever you have installed. A well-executed xeriscape — appropriate plant palette, proper ground cover, weeds controlled — satisfies both. A lawn left to die in July satisfies neither.
This matters in a valley on secondary water with real conservation pressure, and it is worth knowing before a neighbor tells you confidently that the city will make you re-sod. The relevant homework is Section 15.20.060's standards, not a decision about whether to convert.
Vehicles: the word doing the work is "open"
Inoperable vehicles are the most-reported category after weeds, and the most misunderstood.
The city's guidance is that when inoperable vehicles — expressly including unlicensed and unregistered ones — are stored on private property in open areas, there may be a zoning violation. Section 14.34.080's opening subsection reaches the parking, storing or leaving of licensed or unlicensed motor vehicles, which is the point people miss: current registration is not by itself a defense if the vehicle is otherwise within what the section prohibits.
"Open areas" is the operative limitation, and it is a real one. The section is aimed at outdoor storage. A project car inside a closed garage is in a different position from the same car on blocks beside the driveway, and this is the single most useful thing to know if you have a vehicle you are genuinely working on rather than abandoning.
The section also covers used materials, junk, household furniture, appliances, scrap material, equipment or parts thereof in the same breath as vehicles. A couch on a porch and a transmission on a tarp are the same category of problem to this ordinance.
Trash containers, and the exemption for your city can
Section 14.34.080 sets requirements for trash storage containers — setback and screening designed to minimize odor nuisance and to obscure the view from any abutting lot or public street, plus a practical requirement that users can actually get to them.
Then it draws a line. Those provisions apply to containers of two cubic yards and larger, and expressly do not apply to the ninety-gallon containers Provo City provides.
So: the dumpster behind a fourplex is regulated. Your city can is not. This is a small thing that saves a genuinely surprising number of arguments, because the screening language reads as though it covers everything until you reach the capacity clause.
Occupancy: the rule that generates the complaints
Any honest account of Provo code enforcement has to address the provision that produces more friction than weeds and vehicles combined.
The city's own guidance states that most properties in Provo City only allow One Family or Three Singles. Three unrelated adults. In a city with two large student populations and a housing stock of generous older homes, that ceiling is lower than what the buildings can physically hold, and the gap between the two is the origin of a large share of neighborhood disputes.
The city does not ask residents to guess. It directs people to apply for a Zone Verification or contact the Zoning Division at the same (801) 852-6427 number. A Zone Verification letter carries a fee set in the city's schedule and takes a stated minimum number of business days, so it is a document to request before closing on a property or signing a lease rather than after.
The city's advice on this is unusually direct, and worth repeating verbatim in substance: Provo encourages all buyers of property, and anyone who intends to occupy a rental unit, to obtain correct zoning information before occupying or taking ownership. That sentence exists because people routinely do the opposite.
Related, and frequently missed by first-time landlords: under Section 6.26.020 it is unlawful to keep, conduct, operate or maintain a rental dwelling without a business license for that dwelling, with "rental dwelling" defined in Section 6.02.010 to reach residences available or designed to be rented for a period of one month or longer. Renting out a basement apartment is a licensed activity in Provo.
What actually happens after you call
The sequence is less dramatic than either complainants or recipients expect.
A complaint is not a citation. It is a report that triggers an inspection. Code compliance officers verify the condition themselves; a neighbor's characterization is a starting point, not a finding.
Most matters resolve by correction. The purpose of the program, in the city's own framing, is compliance — properties and activities meeting the code — rather than punishment. The ordinary first move is notice and an opportunity to fix the condition.
Title 17 exists so that not everything has to be a crime. The class B misdemeanor language in Section 14.34.080(5) is real, but Provo maintains a full administrative enforcement program as a parallel track. Which track a matter takes depends on the conduct and the history, which is why any confident online claim about "the fine for weeds in Provo" should be treated with suspicion. Ask the division.
There is an ombudsman. Provo maintains one, and the city lists general nuisance complaints — weeds, junk, abandoned vehicles, potholes, animals at large, street lighting, damaged sidewalks, odor problems — among what the ombudsman commonly receives. The ombudsman handles concerns about any city department and is the right escalation if a complaint has gone nowhere. The stated boundary is worth knowing: the ombudsman handles concerns about Provo City government, and civil or private contracts and agreements fall outside that jurisdiction. A landlord-tenant dispute is not an ombudsman matter.
If a notice arrives with your address on it
The other side of this is less written about, and it is where people make expensive mistakes out of alarm.
Read what it actually says. A notice of violation identifies a condition, cites a section, and sets a period to correct it. It is not a fine, and it is not a court summons. The overwhelming majority of Provo code matters end at this stage, with the condition fixed and the file closed.
Call the number on it. This is the step people skip, and it is the one that resolves things. Code compliance officers deal with property conditions all day and are generally willing to discuss what compliance looks like — whether a partial fix counts, what specifically is objectionable about a condition, whether a stated period can be extended for a supply delay or a genuine hardship. An officer who hears nothing has no basis for extending anything.
Fix the identified condition, not what you assume was reported. A notice about an inoperable vehicle is about that vehicle. Clearing an unrelated pile does not close it. If the notice is ambiguous about which condition triggered it, ask before you spend a weekend on the wrong thing.
Document the correction. Photograph the property after the fix, with a date. Re-inspection is not instantaneous, and the gap between when you corrected a condition and when someone verified it is exactly where disputes about timelines start.
If you disagree, say so early and in writing. Sections like 14.34.080(5) turn on a consequence test — whether a condition constitutes a fire hazard, a rodent harborage, an attractive nuisance. Those are judgments, and judgments can be wrong. A vehicle that is registered, insured and driven weekly is not an abandoned vehicle, and saying so at the notice stage is far cheaper than saying so later. Title 17's administrative program exists in part to give these matters a process rather than a confrontation.
The condition is what matters, not the reporter. Provo does not require complainants to identify themselves publicly, and pursuing who called is both unproductive and a reliable way to turn a maintenance issue into a neighborhood feud. The officer verified the condition independently. That verification is the case.
One genuinely useful frame: most code notices are about deferred maintenance, and deferred maintenance is a symptom of something — a hard year, an illness, a job loss, an older resident who can no longer manage the yard. If that is what a notice is telling you about a neighbor rather than about yourself, the productive response is frequently a mower and an afternoon rather than a second complaint. Utah Valley has a reasonably strong culture of exactly this, through wards, neighborhood associations and service groups, and it resolves more of these conditions than the enforcement program ever will.
Before you report a neighbor
A practical note, offered without moralizing.
Code enforcement is a genuinely valuable municipal function, and there are conditions — a fire hazard against a shared fence, a rodent harborage, an attractive nuisance in a yard full of children — where reporting is straightforwardly the right thing to do and waiting is not.
There are also conditions where a complaint is a slower, more adversarial and less effective version of knocking on a door. An officer's notice arrives days later, addressed formally, from the city. A conversation arrives immediately and lets the person explain that the vehicle is being repaired, or that the yard got away from them during a hard month.
The categories that reward a conversation first are the ones where the property owner plausibly has not noticed or has been overwhelmed: weeds, a single derelict appliance, a yard in mid-project. The categories that do not are the ones involving a decision someone has already made and defended.
Provo is a city where a lot of people are living close together in housing that was not designed for how they are living in it. The code exists because that produces real problems. It works best when it is the second thing tried.
Related reading
- Recycling & Garbage in Provo — collection, cans and what actually goes in them
- Provo's Noise Ordinance — the other complaint channel, and which one to use
- Tree Removal in Utah Valley — dead trees are on the nuisance list, and the park strip is not yours
- The Fault Under Utah Valley: What the Forecast Actually Says, and What It Leaves Out
- Provo's Elevation: How High It Is and What That Actually Changes
- Where Provo's Water Actually Comes From
- 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