Maricopa — Variances and Exceptions

Last reviewed: July 6, 2026

Overview

This page explains how Maricopa’s zoning code handles relief from strict standards through variances, and where the code itself provides exceptions so a variance isn’t needed. Variances live in Title 17’s permits-and-approvals process and are decided either by the Planning Director (minor variances) or the City Council (major variances), with specific findings that must be met under § 17.2.60. For broader context on districts, uses, and review procedures, see the Maricopa zoning & planning overview, Maricopa Zoning, and Maricopa Development Standards.

Bottom line: In Maricopa, a “minor variance” can relax certain development standards by set percentages (e.g., up to 20% of a front setback), while anything beyond that is a “major variance” requiring City Council action and hardship findings under § 17.2.60.

What the ordinance says about Variances

• Authority and scope. A variance may be granted when strict application of a zoning regulation deprives a property of privileges enjoyed by others in the vicinity and same zoning due to special circumstances (including size, shape, topography, location, or surroundings). Variances may address development standards such as walls and screening, site area, width and depth, coverage, yards, height, open space, and on-/off-street parking and loading. Conditions of approval may be imposed (§ 17.2.60).
• Minor vs. major variance.
  • The Planning Director may approve a “minor variance” within defined limits (see table below).
  • Any other request is a “major variance,” acted on by the City Council (§ 17.2.60).
• Required findings. To approve any variance, the decision-maker must find:
  • strict or literal enforcement would cause practical difficulty or unnecessary hardship not shared by others nearby; and
  • exceptional or extraordinary conditions apply to the property or its intended use not common to other properties of the same zoning in the vicinity (§ 17.2.60).
• Public hearing and notice. Public hearing and notification procedures are set out in § 17.2.140 (cross-referenced throughout Chapter 2 of Title 17).
• Lapse and extensions. Entitlements issued under Title 17 lapse if not exercised within the prescribed time; extensions of time may be granted by the original approving authority (§ 17.2.170).

Table — What qualifies as a “Minor Variance” in Maricopa

Notes:

• Requests outside the limits above are “major variances” decided by the City Council (§ 17.2.60).
• Minor variances cannot change lot area or lot dimension requirements (§ 17.2.60).

“Exceptions” you can use without a Variance

Maricopa’s Title 17 includes some built-in exceptions and alternative paths where a variance is not required:

• Commercial parceling and site area in shopping centers. Within commercial districts, creating parcels inside a shopping center and certain commercial condominium lots are exempt from minimum site area/width/depth standards when a conceptual plan and reciprocal easements are in place. Also, when abutting a residential district, the residential setbacks apply to the commercial edge (Commercial District “Exceptions”) (§ Chapter 5, 3. Exceptions).
• Street tree planting exceptions. The Planning Director may grant exceptions to street-tree requirements on cul-de-sacs and tight lots based on spacing constraints (§ 17.10.360, Street Lighting and Tree Planting).
• Undergrounding utilities — general exceptions. Temporary overhead lines and certain equipment may be permitted above ground under Chapter 10’s general development standards (undergrounding) exceptions. These are operational exceptions, not variances (§ Chapter 10, General Exceptions).
• Parking adjustments and tandem parking. Chapter 13 allows adjustments to off-street parking requirements (§ 17.13.50 referenced), and limits tandem parking unless allowed by CUP or supported by variance findings (§ Chapter 13). For requirements and adjustments, see Maricopa Parking.

When a Variance is triggered by topic-specific chapters

• Wireless facilities. If a proposed wireless facility cannot meet all development standards of its underlying zone, a variance is required in addition to any required CUP; the variance must meet § 17.2.60 findings (Chapter 11).
• Nonconforming properties. Variances interact with the nonconforming chapter in that expansions of nonconformities are restricted; review both sets of rules before applying (§ 17.2.120 and § 17.2.60). See also Maricopa Nonconforming Uses.

District-by-District: How variances and exceptions tend to apply

Below is a practical, district-focused view of how Maricopa’s variance rules meet each district’s purpose and standards. For details on district uses and dimensional rules, see the underlying chapters and Maricopa Zoning.

Residential Districts — R-A, R-1, R-2, R-3

• Purpose and typical uses: Residential neighborhoods (from agricultural-residential through single- and multi-family). The code references these designations in siting and adjacency standards (e.g., for facilities near residential zones) (Chapter 11).
• Key dimensional standards: Not found in retrieved materials.
• Variance posture:
  • Minor variances can relax setbacks and certain area/coverage limits within the percentage caps in § 17.2.60; lot area/dimensions are excluded from minor variance.
  • Residential front-yard parking is specifically restricted citywide; relief, if sought, would require a variance or other authorization under Chapter 13 rules (§ Chapter 13).
• Where it applies: Citywide residentially zoned properties (verify actual mapped boundaries with the City).

Commercial Districts

• Purpose and typical uses: Retail, service, and mixed commercial patterns (Chapter 5). Not found in retrieved materials for specific sub-district designations.
• Key dimensional standards: Not found in retrieved materials.
• Built-in exceptions:
  • Commercial shopping centers and condo-lot creation have exceptions to minimum site area/width/depth if certain conditions are met; abutting residential triggers residential setbacks at the interface (Chapter 5, 3. Exceptions).
• Variance posture:
  • Minor variances can address parking and yard/setback issues up to the stated caps; larger deviations are major variances (§ 17.2.60).
  • Some specialized uses (e.g., wireless) needing extra height or yard deviations require a CUP plus a variance if base standards aren’t met (Chapter 11).

Employment Districts

• Purpose: Provide a diversified economic base with industrial and employment uses; ensure compatibility, open space buffering, and hazard mitigation (§ 17.6.10).
• Typical uses and standards: Not found in retrieved materials (index indicates § 17.6.30, § 17.6.40).
• Variance posture: Same citywide rules—use § 17.2.60 caps for minor relief (coverage, yards, parking), otherwise seek a major variance with hardship findings.

Agricultural (A)

• Purpose and where it applies: Preserves agricultural uses and separates them from incompatible development (§ 17.7.10, § 17.7.20).
• Typical permitted uses: Agricultural operations as described for the Agricultural district (Table 7.A referenced) (§ 17.7.30). Not found in retrieved materials for a full, legible list.
• Key dimensional standards: The A district sets minimum site area (e.g., 20 acres generally; 80 acres for Williamson Act parcels) and other site development minimums per Table 7.B (§ 17.7.40).
• Variance posture:
  • Minor variances cannot alter lot area/dimensions; any request to vary Agricultural minimum acreage would be a major variance subject to City Council findings (§ 17.2.60; § 17.7.40).

Special and Overlay Districts — PD, CF, H, DI, PE, RM

• Districts recognized: PD Planned Development, CF Community Facilities, H Airport Approach Height Overlay, DI Drilling Island, PE Petroleum Extraction (combining), RM Resource Management (§ 17.3.10 to § 17.3.60).
• Purpose and standards:
  • PD allows tailored development standards via a development plan with specific findings and Council approval (§ 17.3.10).
  • H (Airport Approach Height Overlay) governs height in approach zones; verify whether relief is available via variance given FAA and overlay constraints (§ 17.3.30). Not found in retrieved materials for the overlay’s detailed limits.
  • DI/PE/RM/CF establish specialized use contexts; details not found in retrieved materials beyond index and selected PD content.
• Variance posture:
  • Variances in overlays must be consistent with overlay purposes; for height-related relief in the H overlay area, FAA requirements apply to any proposal exceeding zone height limits (wireless section notes FAA review for height issues) (Chapter 11 cross-ref; § 17.3.30 noted). Verify feasibility with the City.

Related processes you may encounter with a variance

• Conditional Use Permits (CUPs). Some uses trigger a CUP, and if they also can’t meet base standards, a variance is required in parallel (§ 17.2.50 and Chapter 11 for wireless tiers).
• Design Review. Site and building changes may require design review; the Planning Director may approve or deny with conditions subject to appeal (§ 17.2.80 references).
• Nonconforming status. Alterations enlarging a nonconformity are restricted; coordinate any variance concept with Maricopa Nonconforming Uses (§ 17.2.120).
• Overlay checks. Confirm if an overlay district applies before pursuing variance relief (e.g., scenic corridors, airport approach). Portions of scenic resource siting standards also appear in Chapter 10.

Checklist

• Confirm whether a built-in exception or adjustment applies (commercial center parceling; street-tree spacing; parking adjustments) before seeking a variance (Ch. 5; § 17.10.360; Ch. 13).
• If a variance is needed, classify it: Does it fit a “minor variance” cap under § 17.2.60 (e.g., setbacks, parking, coverage, floor area), or is it a “major variance” to be heard by City Council?
• Prepare findings: show practical difficulty/unnecessary hardship and exceptional conditions unique to the property under § 17.2.60.
• Check district overlays and adjacency rules (e.g., residential interface setbacks in commercial districts; Airport Approach Height Overlay) and coordinate external agency input where applicable (FAA for height).
• Follow public hearing/notice procedures for entitlements (see § 17.2.140).
• Track expiration; request time extensions before lapse per § 17.2.170.

Risks & Ambiguities

Plain-English Summary

If you can meet a small, clearly defined relief threshold (like shaving a front setback by up to 20% or reducing parking by up to 30%/two spaces), ask the Planning Director for a minor variance. Anything bigger goes to the City Council as a major variance, and you’ll need to prove true hardship and unique site conditions under § 17.2.60. Before you file, check for built-in exceptions or adjustments in the code that could avoid a variance altogether, and remember to align with any overlays, parking rules, and design review where applicable.

Source References

• Variances: minor/major, findings, scope — § 17.2.60 (Title 17, Chapter 2: Permits and Approvals).
• Public hearing/notification procedures — § 17.2.140 (index reference).
• Lapse of approvals and extensions of time — § 17.2.170.
• Design Review authorization/appeal linkage — § 17.2.80 (referenced) and § 17.2.180 (appeals referenced).
• Commercial District “Exceptions” — Chapter 5, 3. Exceptions.
• Street tree planting exceptions — § 17.10.360.
• Undergrounding utilities — Chapter 10, General Exceptions.
• Parking adjustments and tandem rules — Chapter 13; § 17.13.50 referenced.
• Wireless facilities requiring variance if not meeting zone standards — Chapter 11 (Tier 2; CUP + variance; § 17.2.60 findings).
• Agricultural (A) district purpose and standards — § 17.7.10, § 17.7.20, § 17.7.40.
• Special/Overlay districts listing — § 17.3.10 through § 17.3.60 (index).

Retrieved passages

• Maricopa Zoning Code (CHAPTER 2) High relevance show source text
• CEC § 17.2.60 (Section 17.2.60) High relevance show source text
• Maricopa Zoning Code (Chapter 17.13) High relevance show source text
• Maricopa Zoning Code (CHAPTER 10) Medium relevance show source text
• Maricopa Zoning Code (CHAPTER 11) Medium relevance show source text
• Maricopa Zoning Code (CHAPTER 5) Medium relevance show source text
• Maricopa Zoning Code (CHAPTER 10) Medium relevance show source text
• Maricopa Zoning Code (CHAPTER 5) Medium relevance show source text
• CEC § 100 (CHAPTER 11) Medium relevance show source text
• Maricopa Zoning Code (CHAPTER 13) Medium relevance show source text
• Maricopa Zoning Code (CHAPTER 10) Medium relevance show source text
• Maricopa Zoning Code (§ 66314) Medium relevance show source text
• Maricopa Zoning Code (Title att) Medium relevance show source text
• Maricopa Zoning Code (Title by) Medium relevance show source text
• Maricopa Zoning Code (Section 17.13.60.7.b.) Medium relevance show source text

Cited sections

• Variances: minor/major, findings, scope — § 17.2.60 (Title 17, Chapter 2: Permits and Approvals). (§ 17.2.60)
• Public hearing/notification procedures — § 17.2.140 (index reference). (§ 17.2.140)
• Lapse of approvals and extensions of time — § 17.2.170. (§ 17.2.170.)
• Design Review authorization/appeal linkage — § 17.2.80 (referenced) and § 17.2.180 (appeals referenced). (§ 17.2.80)
• Commercial District “Exceptions” — Chapter 5, 3. Exceptions. (Chapter 5)
• Street tree planting exceptions — § 17.10.360. (§ 17.10.360.)
• Undergrounding utilities — Chapter 10, General Exceptions. (Chapter 10)
• Parking adjustments and tandem rules — Chapter 13; § 17.13.50 referenced. (Chapter 13)
• Wireless facilities requiring variance if not meeting zone standards — Chapter 11 (Tier 2; CUP + variance; § 17.2.60 findings). (Chapter 11)
• Agricultural (A) district purpose and standards — § 17.7.10, § 17.7.20, § 17.7.40. (§ 17.7.10)
• Special/Overlay districts listing — § 17.3.10 through § 17.3.60 (index). (§ 17.3.10)
• Maricopa_ZoningCode.md