Local zoning · Palmdale

Palmdale — Variances and Exceptions

Variances and Exceptions under the Palmdale local zoning and planning code, with the controlling citations.

Ask a question free See coverage

Last reviewed: July 2, 2026

Overview

Palmdale’s local zoning Title 17 treats variances and minor exceptions as two distinct paths for adjusting development standards where strict code application would unfairly burden a parcel. The procedures, decision standards, time limits, and the scope of what can be adjusted (setbacks, fences, heights, lot coverage, parking, etc.) are set out in PMC Chapter 17.23; required findings and appeal/expiration rules are in PMC § 17.23.020 through § 17.23.070.

Important cross-links for applicants (first mention of topic is linked): the rules commonly interact with the city’s Palmdale Development Standards, Palmdale Parking rules, Palmdale Design Review, Palmdale Overlay Districts, and Palmdale ADUs. Always confirm building technical compliance separately with the California Building Standards Code.

Core rules (what Title 17 actually says)

  • Purpose: A variance/minor exception exists so “no property…because of special circumstances…shall be deprived of privileges commonly enjoyed by other properties in the same vicinity and zone.” See § 17.23.010.

  • Scope / What may be adjusted:

    • The Review Authority may grant variances or minor exceptions from any property development standard in Title 17 (setbacks, heights, lot coverage, parking, landscaping, etc.), but never to allow a use not permitted in the zone. See § 17.23.020(A)–(B), (E).
    • Specific items that may be processed as a minor exception with stated caps include:
      • Fence height: up to +2 ft where grade/topography warrants, without breaking sight‑distance safety (see PMC § 17.82.070).
      • Setbacks: up to 10% reduction generally; up to 5 ft side setback reduction on single‑family lots in some legacy tentative‑map situations.
      • Lot coverage: up to +10%.
      • Off‑site parking: up to 10% of required parking on a contiguous parcel within 300 ft walking distance.
        All of the above are laid out in § 17.23.020(C).

  • What requires a full variance: any deviation not specifically in the minor‑exception list (e.g., larger setback reductions, height increases beyond minor caps, nonstandard lot dimensions, or parking waivers beyond 10%) must be processed as a variance (see § 17.23.020(E)).

  • Who decides:

    • Minor exceptions — decided by the Director (or approved with the project if the Director is also acting on a larger application) with notice to adjacent owners and a minimum 10‑day comment period prior to decision. See § 17.23.040(A).
    • Variances — heard and decided by the Planning Commission at a public hearing under general review procedures (see § 17.23.040(B) and PMC § 17.20.010).

  • Required findings (both variance and minor exception): the decision‑maker must find that:

    1. Special circumstances apply to the property so strict application would deny privileges enjoyed by nearby properties;
    2. The request is necessary to preserve a substantial property right;
    3. The relief will not be materially detrimental to public health, safety, welfare, or injurious to nearby properties; and
    4. The approval does not constitute a special privilege inconsistent with limitations on nearby properties.
      These findings are specified in § 17.23.060(C).

  • Conditions, expiration, and revocation:

    • The Review Authority may attach conditions (special setbacks, landscaping, maintenance, street dedications, schedules, periodic review, etc.) — see § 17.23.050.
    • A variance/minor exception generally becomes null and void if construction authorized has not been started within 36 months of the effective date; extensions up to 24 months may be granted by the Review Authority for delays beyond the applicant’s control — see § 17.23.070(C)(1), (3).
    • Any decision may be appealed per PMC § 17.20.110; re‑application after denial for the same or substantially similar request is barred for one year. See § 17.23.070(A)–(B).

District-by-district (how variances/minor exceptions are used in Palmdale’s actual zones)

Below are the frequently encountered zones where applicants request adjustments. Each district subsection contains the zone purpose, typical uses, key dimensional standards relevant to variance requests, and where it commonly applies in the city. All standards cited are the development standards tables and text in Title 17.

ER / SFR 1 / SFR 2 / SFR 3 (single‑family residential)

  • Purpose & typical uses: Low‑density single‑family homes, estate and suburban lots. See the single‑family development table (Table 17.36.010‑1).
  • Commonly requested adjustments: front/side/rear setback reductions, accessory‑structure placement, and fence height where lot grade varies. Minor exception caps (e.g., 10% setback reduction or +2 ft fence) are often applied to infill properties; larger deviations require a variance per § 17.23.020.
  • Key dimensional examples from Table 17.36.010‑1: typical front setbacks range from 5–35 ft depending on ER/LDR/SFR class; max height commonly 35 ft / 2 stories for SFR zones — measure heights per § 17.17.030. See PMC § 17.36.010 for the full table.

RN 1 / RN 2 / RN 3 (multifamily residential)

  • Purpose & typical uses: Townhomes, duplexes, and multifamily buildings with higher density. See Table 17.36.010‑2 and related RN tables.
  • Typical variance topics: lot coverage increases, reduced open space, and setback averaging/adjustments to achieve feasible building layouts; minor exceptions allow limited lot coverage increases (+10%) under § 17.23.020(C)(3).

MU 1 / MU 2 / MU 3 (mixed‑use)

  • Purpose & typical uses: Vertical mixed commercial/residential, commercial with residential components. Standards are in Table 17.55.010‑1; special design standards and performance rules apply (PMC Chapter 17.56 and design guidelines).
  • Variances commonly requested: parking reductions (sometimes granted as a minor exception with a parking analysis under PMC § 17.87.220), setbacks for plazas, or stepbacks for taller mixed‑use buildings. See PMC § 17.87.220 for when a parking standard may be handled through a minor exception and needed analysis.

Commercial/Office zones — NC, RC, VC (Neighborhood, Regional, Village Commercial)

  • Purpose & typical uses: Retail, office, hotels, services — each zone’s development standards are in Table 17.48.010‑1 (NC/RC/VC/MEDFX/EDFX/OFX).
  • Key standards: maximum heights vary (e.g., NC 35 ft/2 stories, RC up to 55–85 ft / multiple stories depending on use and allowances); setbacks commonly 5–10 ft front, 10–25 ft sides when adjacent to residential.
  • Variance examples: height stepbacks, frontage setbacks for plazas, unusual parking layouts — some sign and parking departures are explicitly referenced to Title 17 variance paths (e.g., signs — PMC § 17.88.170 refers to Chapter 17.23).

Public Facilities / Open Space — PF‑C / PF‑P / OS

  • Purpose & typical uses: Government facilities, schools, parks. Development standards summarized in Table 17.76.010‑1; heights typically 25 ft, front setbacks 10–25 ft depending on PF‑C or OS.
  • Variances here typically involve setbacks, open‑space calculations, or building height for specialized public structures; such deviations follow the usual Chapter 17.23 processes.

Industrial — LI / HI / AI / MRE

  • Purpose & typical uses: Light, heavy, and airport‑related industrial uses; allowed uses table and supplemental standards are in Chapter 17.65 and Table 17.65.020‑1.
  • Typical adjustments sought: loading dock location, setbacks adjacent to residential, parking and circulation, and landscaping buffering; the code explicitly contemplates variances/minor exceptions to loading location and parking when site features make strict compliance impractical. See PMC § 17.87.200–220 and Chapter 17.23.

Note: For all districts, the Director and Planning Commission must ensure approvals are consistent with the General Plan and other applicable codes (see § 17.23.060(A)–(B)).

Quick Reference Table — routine adjustments (decision‑relevant)

Adjustment Minor exception cap (when allowed) When a full variance is required Code Reference
Fence / wall height Up to +2 ft (if topography/grade justifies and no sight‑distance conflict) If increase would violate safety visibility or exceed +2 ft § 17.23.020(C)(1)
Setbacks (front/side/rear) Up to 10% reduction (single‑family side setback reduced up to 5 ft in limited pre‑ordinance map cases) Any reduction > caps or reductions that allow a use otherwise prohibited § 17.23.020(C)(2)
Lot coverage Up to +10% of parcel area Any greater increase § 17.23.020(C)(3)
Off‑site parking Up to 10% of required parking on a contiguous parcel, within 300 ft walking distance Shared parking beyond 10% or non‑contiguous parking § 17.23.020(C)(4)
Parking reductions for TDM Minor exception with TDM plan and monitoring Major reductions require variance and detailed analysis § 17.87.220
Any other development standard (heights, lot dimensions, etc.) — Variance required § 17.23.020(E)

Checklist (what an applicant must satisfy to be complete)

  • File a signed application with the Department; pay the fee set by City Council (owner or authorized agent must sign) — § 17.23.030(A).
  • Submit complete plans and materials showing existing conditions, surrounding context, and proposed adjustment (must depict existing/proposed buildings, uses, and distances) — § 17.23.030(B).
  • For minor exceptions: provide justification against the specific minor‑exception standards in § 17.23.020(C) (e.g., topographic photos for fence height; parking analysis if requesting shared parking).
  • For variances: document the four required findings in § 17.23.060(C) with facts/evidence (unique parcel circumstances, property rights impact, no material detriment, no special privilege).
  • Provide any specialist reports (parking analysis, traffic, arborist, geotech) if the adjustment affects those systems (per Chapters 17.87, 17.86, or other Title 17 sections).
  • If contesting parking counts or proposing a TDM program, include monitoring/enforcement mechanisms (PMC § 17.87.220).
  • Be prepared for notice, comment, and the appeal period: minor exceptions require written notice to contiguous owners with a minimum 10‑day comment window; variances require public hearing notice procedures — see § 17.23.040(A) and § 17.20.010.

Risks & Ambiguities

Issue Why it matters What to verify
Trying to change a use (not allowed via variance) Title 17 forbids granting a variance/minor exception to allow a use not permitted in the zone — variance only adjusts development standards, not allowable uses. Confirm allowed/conditional uses in the zone and use the Director’s “similar use” determination or a zone change if use is not listed. See § 17.23.020(A) and § 17.24.040.
Overreliance on minor exception caps If the needed adjustment exceeds the stated caps (e.g., >10% setback reduction), the Director cannot process it as a minor exception; the project needs a variance and public hearing. Measure the requested deviation versus the caps in § 17.23.020(C); if over the caps, prepare full variance findings § 17.23.060(C).
Parking proposals relying on shared off‑site spaces Off‑site parking as a minor exception is limited to 10% and 300 ft; larger or noncontiguous arrangements require variance and legal agreements. Confirm walking distance measurement, contiguous parcel status, and provide a legal parking agreement if approved (see § 17.23.020(C)(4) and PMC § 17.87.220).
Time limits and concurrent approvals Variances/minor exceptions expire in 36 months unless construction is initiated; when combined with other approvals, the shortest expiration governs. If project has other entitlements, coordinate timing and request time extensions (up to 24 months per § 17.23.070(C)(3)) if needed.
Parcel‑specific zoning/overlay conflicts Overlay district standards, Specific Plans, or recorded private covenants may be stricter than Title 17; Title 17 does not override those. Verify overlay rules (see Palmdale Overlay Districts) and recorded covenants; Director’s interpretation may be needed (PMC § 17.12.040–050).

Plain‑English Summary

If your Palmdale property needs a small tweak — like a slightly shorter setback, a fence a couple of feet taller, or a modest lot coverage increase — apply for a minor exception (Director decides) when the change fits the caps in § 17.23.020(C); for anything larger or unusual you must pursue a variance (Planning Commission public hearing) and prove the four findings in § 17.23.060(C). All approvals can have conditions and expire if not acted on; check for overlays, parking rules, and other Title 17 standards that may still apply.

Source References

  • PMC § 17.23.010 (Purpose of variances and minor exceptions).
  • PMC § 17.23.020 (Applicability; minor exception list & caps).
  • PMC § 17.23.030 (Application procedures).
  • PMC § 17.23.040 (Review authority; notice for minor exceptions; Planning Commission for variances).
  • PMC § 17.23.050 (Possible conditions of approval).
  • PMC § 17.23.060 (Required findings for approval — minor exception and variance; text of the four findings).
  • PMC § 17.23.070 (Appeals; voiding; time limits; extension rules).
  • Development standards and zones cited: Table 17.36.010‑1 (Single‑Family; PMC § 17.36.010), Table 17.36.010‑2 (Multifamily), Table 17.48.010‑1 (Commercial/Office; PMC § 17.48.010), Table 17.55.010‑1 (Mixed‑Use; PMC § 17.55.010), Table 17.65.020‑1 (Industrial allowed uses).
  • Parking exception guidance: PMC § 17.87.220 (parking analysis / minor exceptions).
  • Download / host reference: Palmdale Zoning (Title 17) — downloaded from ecode360 (https://ecode360.com/PA4578).

Sources

Retrieved passages

  • Palmdale Zoning Code (CHAPTER 17.23) High relevance
  • Palmdale Zoning Code (§ 4) High relevance
  • Palmdale Zoning Code (§ 17.23.020) High relevance
  • Palmdale Zoning Code (§ 17.23.040) High relevance
  • Palmdale Zoning Code (§ 4) High relevance
  • Palmdale Zoning Code (§ 4) High relevance
  • Palmdale Zoning Code (§ 17.11.040.) High relevance
  • Palmdale Zoning Code (§ 4) High relevance
  • Palmdale Zoning Code (§ 17.87.070) Medium relevance
  • Palmdale Zoning Code (§ 4) Medium relevance
  • CFC § 17.17.030 (§ 17.17.030) Medium relevance
  • Palmdale Zoning Code (§ 17.24.040) Medium relevance
  • Palmdale Zoning Code (Section 65915) Medium relevance
  • Palmdale Zoning Code (§ 17.66.010) Medium relevance
  • CBC § 66314 (§ 66314) Medium relevance
  • Palmdale Zoning Code (§ 17.36.010) Medium relevance
  • Palmdale Zoning Code (§ 17.27.050) Medium relevance
  • Palmdale Zoning Code (Title 17) Medium relevance
  • Palmdale Zoning Code Medium relevance
  • Palmdale Zoning Code (§ 17.88.120) Medium relevance
  • CFC § 17.48.010 (§ 17.48.010) Medium relevance
  • Palmdale Zoning Code (§ 17.92.020) Medium relevance

Cited sections

Frequently asked questions

What is the difference between a variance and a minor exception in Palmdale?

A minor exception is a limited, Director‑level adjustment to specific development standards listed in PMC § 17.23.020(C) (e.g., +2 ft fence height, 10% setback or lot coverage adjustments, 10% off‑site parking within 300 ft). Anything not covered by those caps or more than the caps requires a full variance, which is heard by the Planning Commission and must meet the four findings in § 17.23.060(C).

Can I use a variance or minor exception to allow a commercial use in a residential zone?

No. Palmdale’s code explicitly states a variance or minor exception may not be used to allow a use that is not permitted in the zone — these instruments only adjust development standards, not allowable uses (see § 17.23.020(A)). Use determination, zone change, or Specific Plan amendment would be the proper paths.

How much time do I have to start construction after a variance is granted?

A granted variance or minor exception generally becomes null and void if the authorized construction has not been initiated within 36 months of the effective date; the Review Authority can grant extensions up to 24 months in limited circumstances (see § 17.23.070(C)(1)–(3)).

Can I request a parking reduction through a minor exception?

Yes — small reductions or reconfigurations (including ADA adjustments) can be handled as a minor exception. For larger, data‑driven reductions applicants must provide a parking analysis prepared by a qualified transportation professional; PMC § 17.87.220 explains the standards and that the minor exception process may be used for some parking changes.

If the Director denies my minor exception, can I reapply immediately?

No. After denial, an application for the same or substantially similar request on the same parcel cannot be filed for one year from the denial date (see § 17.23.070(B)). Appeals are available under the appeal provisions (PMC § 17.20.110).

Do variances expire if other project approvals expire?

Yes. If a variance or minor exception is granted along with other approvals, its effective time is tied to the timeframe of the other land‑use approvals and shall not exceed the initial 36‑month period; extensions are coordinated through the Review Authority but cannot extend beyond the expiration of the related entitlements — see § 17.23.070(C)(2)–(3).

Where do I find the specific height and setback numbers that matter for my lot?

Look to the development standards table for your zone (for single‑family, see Table 17.36.010‑1 under PMC § 17.36.010; for commercial see Table 17.48.010‑1 under PMC § 17.48.010). If you plan to request a variance/minor exception, quote the zone table line you need relief from and tie your justification to the required findings in § 17.23.060(C).

Is an ADU eligible for a minor exception for setbacks or lot coverage?

ADU standards are governed by PMC § 17.91.010 and California ADU law; Title 17 acknowledges ADU-specific rules and notes some limits on how lot coverage and setbacks may be applied. Where a proposed exception would conflict with state ADU provisions, state law or the ADU section controls. Check § 17.91.010 and coordinate with planning staff; ADU rules are also linked on the city ADU page.

Who can file a variance/minor exception application?

The application must be signed by the property owner, an authorized agent of the owner, or an applicant with owner authorization; submit the package and fee to the Department as required in § 17.23.030(A)–(B).

More in Palmdale code

Ask about any Palmdale property

Get a cited, plain-English answer on Palmdale zoning, setbacks, FAR, ADUs and permits — for any address.

Start Free Trial

More Palmdale zoning topics

Palmdale Zoning

Palmdale Land Use

Palmdale Development Standards

Palmdale Parking

Palmdale Design Review

Palmdale Overlay Districts

Palmdale Historic Preservation

Palmdale Signage

Palmdale Nonconforming Uses

Palmdale Landscaping and Screening

Palmdale overview