Permit and Height Rules by Jurisdiction, Metro Phoenix

One grid, eleven authorities, every cell dated

This grid covers ten incorporated metro Phoenix cities and unincorporated Maricopa County as of July 29, 2026. Each row names the authority document behind it and the date it was checked. That matters because a fence rule from the city beside yours can be useless at your lot line.

Treat this as a sourced summary to verify before you build, not certified advice. I have left a cell unconfirmed where the authority material in this record does not support a clean answer. An empty answer is safer than telling a homeowner that no permit is needed when it is not.

The city names below lead to the related city pages. For the practical steps behind a trigger, use the permit process, not a copied process walkthrough here.

Jurisdiction	Permit required for a standard wall	Issuing body and portal	Permit fee basis	Max height without engineering	Front setback rule	Side and rear rule	Corner sight triangle	Local pool addition	Code reference	Source and check date	Verification flag
Phoenix	3 ft trigger in the residential-fences summary	Phoenix Planning and Development Department	Valuation-based under City Code Appendix A.2; dollar amount not confirmed	Not confirmed	Not confirmed	Not confirmed	Not confirmed	State baseline only confirmed in this record	ZO 703.A; PBCC 105.2.2; City Code 31-13	PDD residential-fences summary, rev. September 16, 2013; checked July 29, 2026	Flagged for currency
Mesa	6 ft trigger	City of Mesa permitting authority	Per schedule; dollar amount not confirmed	Not confirmed	Not confirmed	Not confirmed	Not confirmed	State baseline only confirmed in this record	City Code Title 11, Ch. 14	Title 11 and zoning height provisions; checked July 29, 2026	Trigger confirmed; other cells not confirmed
Chandler	7 ft trigger	City of Chandler permit counter	Per schedule; dollar amount not confirmed	Over 7 ft needs the regional engineering review described below	Not confirmed	Not confirmed	Not confirmed	Exterior barrier above the state height	Homeowner Building Permit Manual; Pool Barrier Guidelines	Manual rev. April 9, 2026; checked July 29, 2026	Confirmed source
Scottsdale	3 ft trigger	City of Scottsdale permitting authority	Per hour plus per linear foot; dollar amount not confirmed	Over 7 ft needs the regional engineering review described below	Not confirmed	Not confirmed	Not confirmed	City maintains its own pool pages	Revised Code Sec. 7.104	Walls & Fences page updated May 21, 2026; checked July 29, 2026	Confirmed source
Gilbert	3 ft trigger	Town of Gilbert permitting authority	Per schedule; dollar amount not confirmed	Not confirmed	Not confirmed	Not confirmed	Not confirmed	State baseline only confirmed in this record	LDC Sec. 4.109; Municipal Code Sec. 42-110	Gilbert code sections; checked July 29, 2026	Trigger confirmed; fee and geometry cells not confirmed
Glendale	Not confirmed - contact the permitting department	City of Glendale permitting authority	Per schedule; dollar amount not confirmed	Not confirmed	Not confirmed	Not confirmed	Not confirmed	State baseline only confirmed in this record	Zoning Code Sec. 7.200	Laserfiche-hosted zoning code; checked July 29, 2026	Trigger unconfirmed
Tempe	Not confirmed - contact the permitting department	City of Tempe permitting authority	Per schedule; dollar amount not confirmed	Not confirmed	Not confirmed	Not confirmed	Not confirmed	State baseline only confirmed in this record	ZDC Sec. 4-702 and 4-706	ZDC and Clear Vision 4-702(G); checked July 29, 2026	Trigger unconfirmed
Queen Creek	Permit required for all fencing	Town of Queen Creek permitting authority	Per schedule; dollar amount not confirmed	Not confirmed	Not confirmed	Not confirmed	Not confirmed	Codified option set; confirm the applicable option with the town	Ordinance 479-10	Official fencing requirements page; checked July 29, 2026	Confirmed source; height caps not confirmed
Surprise	Not confirmed - contact the permitting department	City of Surprise permitting authority	Per schedule; dollar amount not confirmed	Not confirmed	Not confirmed	Not confirmed	Not confirmed	State baseline only confirmed in this record	Municipal Code Sec. 106-10	Municipal Code; checked July 29, 2026	Trigger unconfirmed
Peoria	7 ft trigger	City of Peoria permitting authority	Per schedule; dollar amount not confirmed	Over 7 ft needs the regional engineering review described below	Not confirmed	Not confirmed	10 ft by 20 ft sight triangle	State baseline only confirmed in this record	Zoning Ordinance Sec. 21-312 and 21-313	Peoria Zoning Ordinance, checked July 2026; verified July 29, 2026	Confirmed primary source
Maricopa County	Over 1 ft can trigger drainage clearance; confirm the project with the county	Maricopa County permitting authority	Per schedule; dollar amount not confirmed	Over 7 ft for CMU 6 in or thicker needs stamped plans	Not confirmed	Not confirmed	2 ft maximum height inside the triangle	State baseline only confirmed in this record	DD-5012-01; MCZO 1111.5 and 1504.5.2	Directive landing revision May 4, 2026; checked July 29, 2026	Engineering cell confirmed

Which authority governs your address

Start with the parcel, not the mailing address. A substantial share of Valley addresses are permitted by Maricopa County rather than the city printed in the address line. That is a different row with a different low-end issue: the county’s drainage-clearance trigger can start above 1 ft.

Use the assessor parcel lookup to identify the jurisdiction, then match that result to this grid. If a project sits near a municipal boundary, confirm the parcel result with the issuing body before ordering block or scheduling a crew. I have seen a wall planned under one rule set reach a counter governed by another. The setback mistake costs more than the lookup.

Do not treat a neighborhood name as an authority. It is not. The county row deliberately links to the permit process because that is the right next check when the parcel is unincorporated, rather than pretending it has a city page.

The engineering line, and the two dates behind it

For the county directive’s current revision, fences and walls over 7 ft require stamped plans by an Arizona Registered Professional when the CMU is 6 in or thicker. Retaining walls over 4 ft, measured from the bottom of footing to the top, also cross that line, as do retaining walls carrying a surcharge. Read the height and setback guide for measurement context before relying on a number from a sketch.

The useful part is not only the current threshold. The county’s superseded PDF revision dated November 20, 2024 used 6 ft and 9 ft figures. The landing revision dated May 4, 2026 is the current document identified in this record, and the older PDF remains visible here because people still find it. Do not smooth those two dates into one rule.

That distinction can change a bid. A 7 ft wall is not an over-7-ft wall, but an added cap course, grade change, or footing measurement can move the project across the line. I made a bad footing call during monsoon work once; the lesson was to measure the built condition, not the optimistic drawing.

The regional threshold is not permission to ignore a city rule. It tells you when the engineering issue appears in the current county directive. Your city may have a separate permit trigger, height cap, or zoning condition. Where this grid says not confirmed, contact that authority instead of borrowing the county answer.

Which cities add their own pool rule

Arizona’s floor appears in A.R.S. 36-1681: a pool 18 in deep and more than 8 ft wide needs a 5 ft barrier, a 4-inch sphere limit, and self-closing, self-latching outward gates, with the barrier 20 in from the water. A city can add to that floor. See fence code requirements for the statute rather than treating this table as a pool-design manual.

Chandler identifies an exterior-barrier requirement above the state height. Queen Creek publishes a codified option set. Scottsdale maintains its own pool pages. Those are headline flags, not a substitute for the controlling text or for an inspector’s answer at your address.

For the other rows, this record confirms the state baseline only. It does not prove that a local addition does not exist. Pool barriers deserve the same caution as a corner wall, especially when a gate or a grade change is involved.

Two approvals, then the locate call

Get HOA or ARC approval in writing first if your property has covenants. A city permit does not erase an association rule, and association approval does not issue the municipal permit. HOA approval in Arizona is the separate guide for that first approval.

Then file with the correct authority. Before anyone digs, call Arizona 811 at least two full working days ahead under A.R.S. 40-360.21 through 31. Do that before the post-hole crew arrives, not after the layout string is already tied off.

Before you build

• Confirm the permitting authority with the parcel lookup.
• Read the full row, including every unconfirmed flag.
• Check the local permit trigger and the over-7-ft engineering line.
• Get covenant approval in writing where it applies.
• File the municipal or county permit before construction.
• Call Arizona 811 at least two full working days before digging.
• Verify the relevant cell against the current code on the day you commit.

Where this grid is reliable, and where it is not

This is the table I wish I had when I was pulling permits in four cities in the same month. I would rely first on Peoria’s newly primary-sourced zoning ordinance, Scottsdale’s page updated May 21, 2026, Chandler’s manual revised April 9, 2026, Queen Creek’s official fencing page, and the county engineering cell. Those rows still require a project-specific check, but the documents named here support the published cells.

Phoenix needs extra caution because the operative summary is dated September 16, 2013. Mesa, Gilbert, Tempe, Glendale, and Surprise carry incomplete trigger or fee information in this record. Glendale, Tempe, and Surprise do not get a guessed permit answer. That is intentional.

No permit-fee dollar figure was confirmed for any of the eleven authorities. Phoenix publishes a valuation-based basis, Scottsdale uses an hourly and per-linear-foot basis, and the others point to schedules. Ask for the current amount when you file. Fee schedules and adopted code editions are the first things I would recheck.

Every row should be re-verified at least annually and immediately when a change is flagged. The only honest way to keep a grid useful is to show its weak cells alongside its strong ones. That is why the table does not borrow a number from the next city over.

Frequently asked questions

Which cities require a permit for a standard fence?

The confirmed triggers in this grid run from Queen Creek’s permit-for-all approach through 3 ft in Phoenix, Scottsdale, and Gilbert, 6 ft in Mesa, and 7 ft in Chandler and Peoria. Glendale, Tempe, and Surprise are not confirmed here, so read the row and contact the permitting department. Do not use a neighboring jurisdiction as a substitute.

How much is a fence permit?

No authority in this grid published a confirmed dollar figure to us. The fee column gives the published basis, and the city or county schedule supplies the current amount. Phoenix is valuation-based and Scottsdale uses an hourly plus per-linear-foot basis.

Above what height does my wall need an engineer?

Over 7 ft is the current regional engineering line for CMU 6 in or thicker in the county directive. Retaining walls over 4 ft or carrying a surcharge also require stamped plans under that directive. Confirm your authority’s separate rules before building.

Why do two of your sources disagree on that?

They disagree because the county revised its directive and an older PDF is still circulating. The superseded November 20, 2024 revision used 6 ft and 9 ft figures, while the current landing revision is dated May 4, 2026. Both dates are shown so you can identify the document in front of you.

Am I in a city or in unincorporated county?

Use the assessor parcel lookup to find out. Mailing addresses and neighborhood names can mislead near a boundary. The county’s over-1-ft drainage-clearance issue is one reason this check belongs before a design decision.

How often is this updated?

Every row is re-verified at least annually, with fee schedules and adopted code editions checked first. A flagged change calls for an earlier review. The row’s check date tells you when to make your own confirmation call.

Find your row, then confirm the cell with your city before you build.

Sources

• Phoenix - ZO 703.A, PDD residential-fences summary, PBCC 105.2.2, and City Code 31-13.
• Mesa - City Code Title 11, Chapter 14, and zoning height provisions.
• Chandler - Homeowner Building Permit Manual, revision April 9, 2026, and Pool Barrier Guidelines.
• Scottsdale - Walls & Fences page updated May 21, 2026, and Revised Code Sec. 7.104.
• Gilbert - LDC Sec. 4.109 and Municipal Code Sec. 42-110.
• Glendale - zoning code, Sec. 7.200.
• Tempe - ZDC Sec. 4-702, 4-706, and Clear Vision 4-702(G).
• Queen Creek - official fencing requirements page and Ordinance 479-10.
• Surprise - Municipal Code Sec. 106-10.
• Peoria - Zoning Ordinance Sec. 21-312 and 21-313.
• Maricopa County - DD-5012-01, MCZO 1111.5, and 1504.5.2.
• Arizona - A.R.S. 36-1681 and A.R.S. 40-360.21 through 31.

Last reviewed July 29, 2026.

This is a sourced summary to verify against the current code before building, not certified advice. Each published cell traces to the authority document named in the row; where that record does not support a clean answer, the cell says not confirmed. Permit fees, adopted codes, and local interpretations can change.

Reviewed by Alma Reyes, ICC-certified residential building inspector.