Local zoning · Palm Desert

Palm Desert — Design Review

Q: What triggers ARC review for a two‑story home in an R‑2 neighborhood?

All new two-story residences and second-story additions in R‑2 require ARC review; the ordinance specifically requires massing compatibility, a line-of-sight analysis, and a planting plan to mitigate privacy impacts (§ 25.68.020(3)) .

Q: Where do I verify parcel-specific setbacks and lot coverage?

Check Table 25.10-3 and its notes for lot-size categories and special setbacks, and confirm with Planning Division staff for parcels that lack a specific square-foot allocation in the table (§ 25.10-3 notes) .

Design Review under the Palm Desert local zoning and planning code, with the controlling citations.

Ask a question free See coverage

Last reviewed: July 2, 2026

Overview

In Palm Desert, design review is a formal review process administered primarily by the Architectural Review Commission (ARC) and by staff when objective design standards apply; its purpose is to ensure new development meets the City's design objectives and zoning standards before permits are issued (§ 25.68.010, § 25.68.020) . Projects subject to the City’s Objective Design Standards route are handled ministerially by the Director; other projects go to the ARC for discretionary review (§ 25.42.050) . Design review interacts with parking, setbacks and other development standards, overlays, and sign or landscape approvals — see the City’s pages on parking, development standards, overlay districts, and signage as you prepare submittals.

How Palm Desert’s design-review system works (key rules)

Design review is required for most building or site plans prior to permit issuance except for single-family residential zones and projects entirely governed by Chapter 25.42 Objective Design Standards (§ 25.68.020) .
The ARC may approve, approve with conditions, or disapprove applications; the ARC must make specific findings before approving design review (§ 25.68.040) .
Projects subject to objective design standards (large multifamily or mixed-use in specific zones) are reviewed ministerially by the Director for conformance; appeals of ministerial decisions go to the Planning Commission with ARC involvement on appeal (§ 25.42.050, § 25.42.060) .
Certain sign types, monument signs, awnings, comprehensive sign programs, and other unique signs must come to the ARC for design review (§ 25.68.050) .
Landscape and irrigation plans are submitted through the architectural review process (§ 25.52.070) .

District-by-district breakdown

Note: the municipal code names numerous zones. Below are the zones most relevant to design review and the Objective Design Standards; each district entry summarizes the code's stated purpose, typical uses, important development-review triggers, and where design review applies. Citations follow each district heading.

R-1 (Single-Family Residential) — R-1

Purpose/typical uses: low-density single-family detached housing; the code treats single-family detached homes as generally exempt from ARC design review except where Objective Design Standards or other local rules apply (§ 25.42.040) .
Design-review trigger: the general rule is that single-family detached homes are exempt from ARC review (§ 25.42.040(A)(1)) — verify if a property has special overlay or specific plan rules that require review (§ 25.10-3 notes and map clarifications) .
Key standards/examples to confirm: lot-size-specific setbacks and maximum coverage in Table 25.10-3 (confirm with Planning staff for parcels without explicit lot-area allocations) (§ 25.10-3) .

R-2 (Mixed Residential) — R-2

Purpose/typical uses: medium-density residential including duplexes and small multifamily forms; used for mixed residential development (§ 25.42.020) .
Design-review trigger: all new two-story residential dwellings and second-story additions within the R-2 district are explicitly required to be reviewed by the ARC for neighborhood compatibility, massing, privacy, and require a planting plan and line-of-sight analysis (§ 25.68.020(3)) .
Key dimensional standards: consult Table 25.10-3 for R-2 setbacks, lot coverage and other dimensional measures; the ARC can approve increased lot coverage in some circumstances (§ 25.10-3; notes) .

R-3 (Multifamily Residential) — R-3

Purpose/typical uses: multifamily residential development (apartments, condominiums); the zone is one of the areas where Objective Design Standards apply (§ 25.42.020) .
Design-review trigger: multifamily projects in R-3 are subject to the Objective Design Standards chapter (Chapter 25.42) and are reviewed by the Director under those objective rules (§ 25.42.020, § 25.42.050) .
Key standards: objective standards (unit sizes, landscape, parking ratios, etc.) and Table 25.10-3 development standards apply and may supersede other guidelines where stated (§ 25.42.030, Table 25.10-3) .

PR (Planned Residential) — PR

Purpose/typical uses: flexible planned developments mixing residential densities and community facilities; applicant typically pursues a precise plan and the PR designation establishes project-level standards (§ 25.11 and PR-specific notes) .
Design-review trigger: all development in PR is subject to precise plan review and ARC site/precise-plan review; screening and many design features are determined through ARC review for precise plans (§ 25.11 / PR standards) .
Key standards: PR projects must meet base-zone development standards and off-street parking (Chapter 25.46); screening and site-plan issues are ARC-determined (§ 25.11 summary, § 25.46.010) .

OP (Office Professional) — OP

Purpose/typical uses: business, office, professional uses in an urban streetscape context; listed among zones where multifamily/mixed-use objective standards may apply (§ 25.16.020, § 25.42.020) .
Design-review trigger: where mixed-use or multifamily housing is proposed in OP, Chapter 25.42 may apply and the Director will review for objective-standard conformance (§ 25.42.020, § 25.42.050) .
Key standards: ensure conformance with OP development standards and the Objective Design Standards where housing is part of the project (§ 25.16.020, § 25.42.030) .

PC, PC-1, PC-2, PC-3, PC-4 (Planned Commercial / Commercial Centers) — PC, PC-1, PC-2, PC-3, PC-4

Purpose/typical uses: planned commercial centers at different scales (specialty, district, regional, resort) with associated retail, service, and possibly mixed-use residential components (§ 25.42.020) .
Design-review trigger: mixed-use or multifamily housing components in these commercial districts fall under Chapter 25.42 (Objective Design Standards → Director review). Otherwise, commercial projects, signage, landscaping, and building elevations normally need ARC review prior to permits (§ 25.42.020, § 25.68.020) .
Key standards: consult chapter-specific commercial standards (e.g., sign rules, parking, landscaping) and the Objective Design Standards when housing is present (§ 25.56, § 25.46, § 25.52, § 25.42.030) .

SI (Service Industrial) — SI

Purpose/typical uses: service industrial uses and certain outdoor display/storage uses; the code requires architecture and landscaping compatibility and subjects exterior facades and site design to ARC review for certain uses (§ 25.34.200, § 25.34) .
Design-review trigger: development of industrial/commercial facades, outdoor display areas, and screening are subject to ARC review to mitigate visual impacts (§ 25.34.200(D–E)) .

HOD (Housing Overlay District) — HOD

Purpose/typical uses: overlay to incent affordable housing with optional standards and incentives; where applied, the HOD may allow flexibility and density bonus rules but still uses ARC/precise-plan processes for design guidance (§ 25.28.015 et seq.) .
Design-review trigger: projects using HOD incentives still require Architectural Review and must follow design guidance; ARC may consider flexibility to base-zone standards as part of design review (§ 25.28.015(D–F)) .

Quick reference table — decision-relevant items

Decision item / permitted use	What matters for design review	Code reference
Design review required before permits (general rule)	Nearly all plans except single-family detached and projects under Objective Design Standards require ARC/staff review prior to permit issuance	§ 25.68.020
ARC approval findings	ARC must find conformance with development standards, neighborhood compatibility, aesthetics, use conformity, and public welfare	§ 25.68.040
Objective Design Standards applicability	R-2, R-3, PR, OP, PC, PC-1/2/3/4 multifamily/mixed-use projects; Director conducts ministerial ODS review	§ 25.42.020; § 25.42.050
Two-story R-2 dwellings / second-story additions	ARC review required; must include line-of-sight analysis and planting plan to mitigate privacy impacts	§ 25.68.020(3)
Sign types requiring ARC	Monument signs, new awnings, comprehensive sign programs, signs on long frontages, or special signs as determined by ZA	§ 25.68.050(C)
Landscape & irrigation plan submittal	Landscape plans required through architectural review and must comply with water-efficiency standards	§ 25.52.070; Ch. 24.04
Parking requirements	Off-street parking must be provided for new uses/additions and designed to be usable on site	§ 25.46.020; § 25.46.030

Practical guidance & interpretation (plain-English but code-grounded)

If you are building anything other than a detached single-family home, or if your single-family parcel falls under an overlay or specific-plan requirement, plan on a design-review submittal. The baseline requirement is in § 25.68.020 .
If your project is a multifamily or mixed-use project in R-2, R-3, PR, OP, or any PC district, first check whether the Objective Design Standards (Chapter 25.42) apply — if they do, the Director will do a ministerial objective review; if you seek deviations from those objective standards, you will need ARC design review per Chapter 25.68 (§ 25.42.040–050) .
For two-story homes or additions in R-2, expect to submit a planting plan and line-of-sight analysis and to receive scrutiny on massing and privacy (§ 25.68.020(3)(c–e)) .
Sign and landscape elements have their own ARC sub-rules: certain signs and all landscape/irrigation plans are routed through the architectural review process (§ 25.68.050, § 25.52.070) .
Parking and off-street layout must be coordinated with design review because parking counts and layouts are development standards the ARC/Director will verify (§ 25.46.020) . See the City parking guidance page for practical parking layouts and submittal expectations parking.

Checklist — what an applicant must satisfy (minimum, code-grounded)

Confirm zoning district and any overlay/specific-plan rules for the parcel; consult Table 25.10-3 for district dimensional standards (§ 25.10-3) .
Determine whether the project is subject to Objective Design Standards (Chapter 25.42). If yes, submit materials required to the Director per § 25.42.050 .
If not subject to objective standards (or seeking exceptions), prepare full ARC design review submittal: site plan, elevations, materials/finishes, colors, landscaping, lighting, and line-of-sight/privacy analysis for second-story work (§ 25.68.020, § 25.68.040) .
Include a planting/landscape plan where required (two-story R-2, PR projects, any wall facing a public street): see § 25.68.020(3)(e) and § 25.52.070 .
If signs are proposed, confirm whether the type requires ARC review and include the signed owner approval statement for sign applications (§ 25.68.050(A–C)) .
Demonstrate conformance with parking and loading requirements in Chapter 25.46; include parking calculations and layout in the site plan (§ 25.46.020) .
If seeking an exception to an objective standard, prepare a parallel ARC discretionary package (exceptions are treated as design-review matters) (§ 25.42.040(A)) .
Expect ARC findings before approval — plan conditions to address the ARC findings in § 25.68.040 .

Risks & Ambiguities

Issue	Why it matters	What to verify
Applicability to single-family lots	Single-family detached homes are generally exempt from Chapter 25.68, but specific plans, overlays, or lot-size notes may impose review	Confirm whether the parcel has an overlay, is in a specific plan, or has special lot-size notes in Table 25.10-3 (§ 25.42.040, § 25.10-3)
Objective Design Standards vs. ARC discretion	Projects subject to objective standards are ministerial; deviations require discretionary ARC review, which can add hearings and conditions	Verify whether the project qualifies for ministerial ODS review (§ 25.42.020–050)
Two‑story R‑2 privacy requirements	Code mandates planting/line-of-sight analysis; inadequate submittals will delay approval (§ 25.68.020(3))	Prepare a clear planting plan and sight-line diagrams and confirm species/spacing meet the planting requirements (§ 25.68.020(3)(e–i))
Sign types requiring ARC	Some signs (monument, awnings, comprehensive programs) are specifically routed to ARC; missing that step blocks sign permitting	Verify sign type against § 25.68.050(C) and include owner approval statement (§ 25.68.050(A))
Lot‑size specific standards	Notes to Table 25.10-3 indicate special lot-size rules and that staff confirmation is needed; misreading these leads to incorrect setbacks	Contact Planning Division staff to confirm applicable lot-size category and setbacks (§ 25.10-3 notes)
Timeline and fees	The ordinance establishes process flows but fee schedules and precise hearing timelines are set elsewhere (city resolutions)	Verify current ARC hearing schedule and fee resolution with the Planning/Department staff — Not found in retrieved materials

Information Gaps

Current City fee schedule and specific application filing fees for ARC/design-review filings — Not found in retrieved materials.
Exact checklists and required drawing scales/formats provided by the City’s Department (the code references departmental checklists but the checklist itself is outside the ordinance) — Not found in retrieved materials.
Any locally adopted “design review” web page or procedural handout distinct from the Zoning Code (the internal site pages for applicants) — Not found in retrieved materials.
Up-to-date parcel-specific interpretations of Table 25.10-3 lot-area allocations for certain R-1 parcels — code notes instruct to verify with staff (§ 25.10-3 notes) .

Plain-English Summary

Most non-single-family projects in Palm Desert must get design review approval before permits: the ARC handles discretionary design-review decisions and must make findings that the project meets zoning and neighborhood compatibility goals (§ 25.68.020, § 25.68.040) . Multifamily and mixed-use projects in certain zones follow the Objective Design Standards and are reviewed ministerially by the Director unless variances or exceptions are requested (§ 25.42.020–050) .

Source References

§ 25.68.010; § 25.68.020; § 25.68.030 — Chapter on Decisions by the Architectural Review Commission (Design-review requirements & exceptions) .
§ 25.68.040; § 25.68.050 — ARC findings and sign-design-review rules .
Chapter 25.42 (Objective Design Standards): § 25.42.020, § 25.42.030, § 25.42.040–070 — applicability and ministerial review rules .
Table 25.10-3 and associated notes — residential district development standards, lot-size notes, and applicability references § 25.10-3 .
§ 25.46.010–030 — Off-street parking purpose and applicability relevant to design-review coordination .
§ 25.52.070 — Landscape and irrigation plan submittal through architectural review .
PR district standards and precise-plan/ARC references — PR chapter and site-plan review notes (§ references within PR discussion) .
HOD (Housing Overlay District) provisions — optional standards, incentives, and ARC/precise-plan considerations § 25.28 .

Sources

Retrieved passages

Palm Desert Zoning Code (§ 25.68.020.) High relevance
Palm Desert Zoning Code (§ 1) High relevance
Palm Desert Zoning Code (§ 1) High relevance
Palm Desert Zoning Code (§ 25.42.030.) Medium relevance
Palm Desert Zoning Code (§ 25.42.020.) Medium relevance
Palm Desert Zoning Code (§ 25.42.060.) Medium relevance
Palm Desert Zoning Code (§ 1) Medium relevance
Palm Desert Zoning Code (§ 4) Medium relevance

Cited sections

Official Palm Desert code library

Frequently asked questions

Do I need design review in Palm Desert?

If your project is not a detached single-family home and is not entirely covered by Chapter 25.42 objective standards, then yes — design review by the ARC or Director is required before a permit will be issued (§ 25.68.020) .

What triggers ARC review for a two‑story home in an R‑2 neighborhood?

All new two-story residences and second-story additions in R‑2 require ARC review; the ordinance specifically requires massing compatibility, a line-of-sight analysis, and a planting plan to mitigate privacy impacts (§ 25.68.020(3)) .

Are accessory dwelling units (ADUs) subject to design review?

The Objective Design Standards chapter exempts accessory dwelling units pursuant to § 25.34.030 from the ODS provisions; whether an ADU needs ARC review depends on the parcel’s zoning and whether the ADU triggers other discretionary approvals — verify with the Planning Department; the code exemption is in § 25.42.040 .

Which sign types must go to the ARC before a sign permit?

Monument (freestanding) signs, new awnings, comprehensive sign programs, individual signs on buildings with more than 100 feet of frontage, and any sign the Zoning Administrator deems appropriate must be submitted to the ARC (§ 25.68.050(C)) .

What are the ARC’s required findings to approve design review?

The ARC must find that the proposal conforms to adopted development standards, is compatible with the neighborhood and traffic conditions, preserves desirable character and aesthetics, conforms to the zone, and protects public health and welfare (listed in § 25.68.040) .

If my multifamily project meets Objective Design Standards, who reviews it?

Projects subject to the Objective Design Standards (e.g., in R‑2, R‑3, PR, OP, PC districts where applied) are reviewed by the Director under a ministerial process; appeals of the Director’s objective-design decisions go to the Planning Commission and may involve ARC review on appeal (§ 25.42.050–060) .

Can the ARC waive standard development rules (setbacks, coverage)?

The ARC may approve exceptions to certain standards when the findings for an exception are met (unique circumstances, no damage to adjacent property, notification of adjacent owners). Specific exceptions procedures are in the code and exceptions to objective standards require design-review approval (§ 25.42.040(A); exception procedures referenced in applicable sections) .

What do I need to include for landscaping in a design‑review submittal?

Landscape and irrigation plans must be submitted through the architectural review process and comply with the City’s water-efficiency landscape chapter; two-story R‑2 projects specifically require planting plans that identify species and canopy diameters (§ 25.52.070; § 25.68.020(3)(e–i)) .

Does site plan/precise-plan review replace design review?

No — precise plan or site plan review may be required in addition to ARC design review; certain overlay districts and PR projects require precise-plan review and that review is coordinated with ARC standards (§ 25.72.030 and PR notes) — check PR and overlay sections for how the reviews interlock (§ 25.11, precise-plan notes) .

Where do I verify parcel-specific setbacks and lot coverage?

Check Table 25.10-3 and its notes for lot-size categories and special setbacks, and confirm with Planning Division staff for parcels that lack a specific square-foot allocation in the table (§ 25.10-3 notes) .

Ask about any Palm Desert property

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

Start Free Trial