Backyard Chickens in Provo: Six Hens, No Roosters, and a Lot Size That Decides Everything

Abigail Giordano Senior Writer, Provo.com

The single most common way a Provo chicken project fails is not a predator, or a rooster, or a neighbor. It is a tape measure.

Someone reads that Provo allows backyard hens — true — buys six chicks in March, builds a handsome coop against the back fence in April, and discovers in June that the coop is nine feet from a property line where the ordinance requires fifteen, on a lot that is 6,400 square feet and therefore entitled to two birds rather than six.

Everything about that sequence is recoverable except the part where the chickens are already living in the yard.

Provo's rules are unusually specific, unusually readable, and unusually badly reported by the sites that aggregate this kind of thing. Here is what Section 8.02.190 of the Provo City Code actually requires, in the order you will need it.

Start with the square footage, because it decides everything else

Provo does not set a flat flock limit. It sets a sliding one, and the slider is your lot.

Two structural facts sit inside that table.

Six is the ceiling, permanently. There is no rung above 10,000 square feet. A half-acre lot in the Foothills and a 10,000-square-foot lot in Grandview are treated identically: six hens. The ordinance is not scaling to land area in any real sense — it is scaling to a rough proxy for how close your neighbors are, and it stops caring once you are far enough away.

Six thousand square feet is the floor. The schedule simply does not extend below it. This is the provision that quietly excludes a large share of Provo's oldest and densest housing — the central neighborhoods where lots were platted small and later subdivided smaller. If you are in Joaquin, Dixon, or the older Maeser blocks, checking your parcel size is genuinely the first thing to do, before you price a single bag of feed. Utah County's parcel records will tell you, and so will most listing sites, though the authoritative number is the county's.

There is a second gate in Section 8.02.190(1)(b): the principal use on the lot must be a one-family dwelling. Duplexes, triplexes and the various multi-unit configurations scattered through Provo's central zones are out regardless of how much land they sit on. And the whole section is limited at the front end to lots in a residential (R) zone.

No roosters, at any age, and the reason that clause matters

Section 8.02.190(1) permits hen chickens "and no roosters," and adds three words that do a surprising amount of work: regardless of age.

That phrasing exists because of how people actually buy chickens. Feed stores sell chicks in spring, and unless you pay for sexed pullets, a straight-run batch is a coin flip per bird. Nobody can tell reliably at a week old. By four or five months, one of them is standing differently, and shortly after that the question answers itself at 5:30 in the morning.

The ordinance gives you no grace period for that discovery. There is no provision for rehoming within thirty days, no allowance for a young bird whose sex was not yet apparent. A rooster in a Provo backyard is unlawful from the day it is a rooster.

The practical response is to buy sexed pullets from the outset and accept the higher per-bird price, or to have a rehoming plan arranged before the chicks arrive rather than during the week you need it. Utah County has a reasonably active informal network for exactly this, because the problem is universal and predictable.

The coop is a specification, not a suggestion

Section 8.02.190(2) requires chickens to be confined within a secure outdoor enclosed area, and then describes what that has to include.

The coop itself must be covered, ventilated and predator-resistant. Those three adjectives are the whole standard — the ordinance does not prescribe materials, height or construction method, which leaves genuine latitude in how you build.

Floor area is where it stops being vague. The coop needs a minimum of two square feet per chicken if the birds can roam within an enclosed area outside the coop, and six square feet per chicken if they cannot. That three-to-one ratio is the ordinance stating a welfare position without using the word: a coop is somewhere birds sleep and lay, and if it is also the only place they ever are, it has to be three times larger.

For a four-hen flock, that is the difference between an eight-square-foot coop with a run and a twenty-four-square-foot coop without one. On a constrained lot, building the run is almost always the cheaper path.

Placement is set in Section 8.02.190(2)(b), and this is the requirement that most often ends a project already underway. The coop must be:

• located in a rear yard;
• at least fifteen feet from any property line; and
• at least six feet from any dwelling.

Run those against a typical Provo lot and the fifteen-foot setback binds hard. A 60-foot-wide lot with a house on it leaves a corridor down the middle of the back yard, not the tidy back-fence position most coop plans assume. Measure before you buy lumber, and measure from the actual property line rather than from the fence — the two are not always the same thing, which is a lesson Provo homeowners also learn the expensive way about street trees.

Maintenance is written as a performance standard rather than a schedule. Section 8.02.190(2)(b)(i) requires the coop and enclosed area to be kept in a neat and sanitary condition and cleaned as necessary to prevent any odor detectable at a property line. That is a smart piece of drafting: it does not tell you to clean weekly, it tells you the outcome the city will measure, which is what a neighbor would notice anyway.

Roaming is addressed directly in subsection (2)(b)(ii): no chicken shall be permitted to roam outside the coop or enclosed area. A fenced back yard is not automatically the "secure outdoor enclosed area" the section contemplates, and hens wandering a lawn are outside the permission the ordinance grants.

Feed gets its own clause. Section 8.02.190(2)(c) requires chicken feed to be stored and dispensed in rodent- and predator-proof containers. This is not decorative. Open feed is the single most reliable way to convert a chicken project into a rodent problem, and a rodent problem into a code complaint under an entirely different chapter.

Registration, not a permit

Section 8.02.190(3) requires that chickens not be kept on a residential lot unless the keeper first registers with the City.

Registration is a light-touch mechanism by design. The registrant acknowledges the rules set out in the section and, as a condition of filing, agrees to comply with them. The registration lasts one year and may be renewed annually. The cost is not stated in the ordinance — it points to the Consolidated Fee Schedule adopted by the Municipal Council, which is where Provo keeps its fees so they can move without amending the code.

Two implications. First, the registration is the moment the city hands you the rules, which is precisely why "I didn't know about the setback" lands poorly afterward. Second, because the fee lives in a separate schedule that the council updates, any dollar figure you find quoted in a blog post is a figure that may already have moved. Ask the city.

One more clause worth noticing: Section 8.02.190(4) specifies that chickens kept under this section are not household pets as defined elsewhere in the code. That sounds like housekeeping, and mostly it is — but it means the various provisions written for dogs and cats do not automatically extend to hens in either direction.

What the aggregator sites get wrong

If you search for this, you will encounter a widely-syndicated table reporting that Provo allows up to twelve hens in residential zones under Section 14.34.240, with a permit, a thirty-foot setback from neighboring dwellings and a five-foot setback from property lines.

Every element of that is wrong for Provo.

The section is 8.02.190, in Title 8 (Animal Control), not Title 14 (Zoning). The cap is six, not twelve. The property-line setback is fifteen feet, not five. The dwelling separation is six feet, not thirty. And the mechanism is a registration, not a permit.

It is not hard to see how the error propagated: these tables are assembled at scale across hundreds of cities, and a mis-keyed row is invisible unless someone checks it against the source. But it is a genuinely costly error to inherit, because five feet versus fifteen is the difference between a coop that stays and a coop that moves.

The lesson generalizes past chickens. Go to the city code, not to a site that summarizes city codes. Provo's is published online, and the site states what it is current through — at the time of writing, Ordinance 2026-17, passed June 9, 2026. A summary without that kind of stamp cannot tell you whether it is describing law or history.

The rest of Utah Valley does it differently

Provo's ordinance is not the county's ordinance. Each city has its own, and the variation is real — different caps, different setbacks, different treatment of lot size, and in some cases a permit rather than a registration. Orem, Lehi, American Fork, Springville, Spanish Fork and Pleasant Grove all have their own provisions, and a rule you learned from a friend one city over is not a rule you can rely on.

Unincorporated Utah County is a different regime again, governed by county land use provisions rather than by any city's animal control title, and generally more permissive on flock size and on roosters — which is why the birds you hear on a drive through the county's agricultural pockets are not evidence of anything about what your street allows.

A related note for anyone whose interest in a backyard flock is really an interest in backyard food generally: Provo maintains a separate chapter on beekeeping (Chapter 8.03), with its own requirements, and a separate section prohibiting the feeding of wild deer, elk, moose or turkey (Section 8.02.200). Title 8 is worth twenty minutes of reading if you are planning anything involving animals and a Provo yard.

"Predator-resistant" is a local specification

The ordinance's requirement that a coop be predator-resistant is doing more work in Utah Valley than the phrase suggests, because of where the valley sits.

Provo's residential neighborhoods run right up against canyon mouths and undeveloped bench land, and the animals that use those corridors do not stop at the city limit. Raccoons are the most persistent problem and the most capable — they have hands, they work latches, and they are entirely comfortable in dense residential blocks. Foxes and skunks work the bench neighborhoods. Birds of prey are a genuine daytime risk in the open lots on the west side, and a covered run is the only reliable answer to them.

What "predator-resistant" means in practice, in this valley:

• Hardware cloth, not chicken wire. Chicken wire keeps chickens in. It does not keep a raccoon out — the mesh is large enough to reach through and weak enough to tear.
• A buried or aproned perimeter. Digging predators go under, not through. An apron of mesh laid flat and pinned outward at the base defeats this more cheaply than trenching.
• Real latches. Two-step closures that a raccoon cannot work. A simple hook and eye is a raccoon convenience feature.
• A covered run, which the ordinance's roaming restriction effectively requires anyway.

Winter, which is the part people underestimate

The other local reality is a genuine winter. Utah Valley runs cold enough, long enough, that a coop designed for spring will disappoint in January.

Chickens tolerate cold considerably better than most new keepers expect — a dry, draft-free, well-ventilated coop with unfrozen water is the entire requirement, and heat lamps are a fire risk that experienced keepers largely avoid. Ventilation without draft is the trick, and it is the one that separates a coop that works from one that grows frost on the inside walls.

Water is the actual daily problem. Frozen water is the thing that will define your December, and it is worth solving before December rather than during it.

Egg production also drops sharply with the short days, which is worth knowing before you build a budget around six birds. Laying is driven by daylight hours, and Utah Valley's are short from November through January.

Is it worth it?

Fairly: the economics are not the reason to do this. Between the coop build, the feed, the registration and the winter months when production drops off, backyard eggs in Utah Valley do not beat the grocery store on cost across a normal year. They can close the gap during a price spike, and they are unquestionably fresher, but a flock that pays for itself is a flock you are not accounting for honestly.

What it does deliver is a genuinely different relationship with a small piece of your yard, a use for kitchen scraps, an unreasonable quantity of garden fertilizer, and — on the evidence of every Provo keeper who has stuck with it past the first winter — considerably more entertainment than the ordinance's businesslike phrase "for the sole purpose of producing eggs" would suggest.

Just measure the setback first.

Related reading

• Tree Removal in Utah Valley — the other Provo ordinance that surprises homeowners
• Wildlife Removal in Utah Valley — what to do when something else moves into the yard
• Pest Control in Utah Valley — including the rodent problem an open feed bin creates
• Provo's Last Frost Is May 1. It's Also May 21. Both Numbers Are Right.
• HOAs in Utah Valley: What You're Actually Signing Up For
• Burning Anything in Utah Valley: Two Windows a Year, and a Number Called the Clearing Index
• Building Permits in Provo: When You Need One and When You Don't
• Does Provo Have Hard Water? Yes — Here's What It Costs You & What Helps
• Towed in Provo: The Sign at the Entrance Decides Whether They Were Allowed To

Abigail Giordano

Senior Writer

Abigail Giordano is a senior writer at Provo.com covering student life, family resources, and community events across Utah Valley. Her writing focuses on making Provo more accessible and navigable for newcomers, students, and families — the practical guides that help people feel at home faster.