Wildomar — Design Review

Last reviewed: July 3, 2026

Overview

Wildomar treats "design review" under the umbrella of its Development Review process in Title 17 (the Wildomar Development Code). Design- and site-level review is split between Minor Development Review and Major Development Review, with findings that require consistency with the General Plan, the intent of the zone, and applicable design/development standards. Key enabling and procedural rules appear at § 17.85.010–§ 17.85.020 (major), § 17.90.010–§ 17.90.020 (minor), and the Pre-Application Review (PAR) procedures in § 17.116.010–§ 17.116.050.

Design review in Wildomar must also be read with the city's objective design standards and design guideline documents (referenced in Chapter 17.136) and the zone-specific development standards (see the residential and commercial development tables in Article II).

(Links: the page below links to related Wildomar topic pages in context — design review here is discussed within the city's zoning framework.) design review parking development standards overlay districts ADUs California Building Standards Code landscaping

How Wildomar organizes "design review" (short map to the rules)

• "Design review" is implemented through the Development Review process:
  • Major Development Review: required when a project does not qualify as minor; approved by the Planning Commission; approval findings are in § 17.85.020.
  • Minor Development Review: administrative review by the Community Development Director for smaller projects; triggers and exemptions listed in § 17.90.020.
  • Pre-application review (PAR) is available/required for many discretionary proposals to identify applicable standards up front (§ 17.116.010–§ 17.116.050).
  • Projects must meet the zone development standards (e.g., setback, height, lot coverage in Table 17.35.030-1) and any objective design standards and guidelines referenced in Chapter 17.136.

Below is a district-by-district breakdown showing where design review typically applies and the most relevant dimensional/design triggers. Each district subsection cites the specific code references that the Development Review process repeatedly uses (findings require compliance with adopted design and development standards).

R-1 (Single-Family Residential)

Purpose: low-density single-family housing; preserve single-family neighborhood character.

Typical permitted uses: single-family dwellings, accessory buildings, home-based businesses (see Table 17.35.020-1).

Key dimensional/design standards (high-level):

• Minimum lot size 7,200 sf, lot width 60 ft, front setback 20 ft, max height 40 ft (see Table 17.35.030-1 / § 17.35.030).
• For single-family homes, note that many small projects (including most single-family homes and routine remodels) are expressly exempt from Minor/Major Development Review; they may instead require Zoning Clearance or must meet objective standards. See § 17.90.020.B for exemptions and Chapter 17.136 for guidelines.

Where it applies: Citywide residential neighborhoods mapped as R-1 (see Article II—Chapter 17.35).

R-2 (Restricted Single-Family / Small Multi‑Family)

Purpose: medium-density residential; allows some multifamily where appropriate.

Typical permitted uses: single-family dwellings, multi-family where listed, accessory uses; see Table 17.35.020-1.

Key dimensional/design standards:

• Lot size 7,200 sf, front setback 20 ft (1st story)/25 ft (2+ stories), max height 40 ft (Table 17.35.030-1 / § 17.35.030).
• Larger multifamily or projects that add units may trigger Minor or Major Development Review depending on unit count and square footage (see § 17.90.020.A triggers).

Where it applies: R-2 map areas in Article II (residential zones).

R-3 and R-4 (Multi‑Family Residential)

Purpose: higher-density multi-family housing; designed for apartments and larger residential complexes.

Typical permitted uses: multi‑family dwellings, community uses that serve residential neighborhoods; see Table 17.35.020-1.

Key dimensional/design standards:

• Setbacks generally 20 ft front (with two-story exceptions requiring 25 ft), side/rear dimensions vary; max heights 50 ft in some multi-family zones (Table 17.35.030-1).
• New multifamily of fewer than 10 units may be processed as Minor Development Review; larger projects will be Major. See § 17.90.020.A.2 and § 17.85.020.A.

Where it applies: R-3 / R-4 mapped zones in Chapter 17.35.

R-T (Townhouse / Attached Residential)

Purpose: attached/townhouse-style development with generally smaller lots and shared open space.

Typical permitted uses: attached single-family/townhomes, community recreation areas, accessory uses.

Key dimensional/design standards:

• Minimum lot size can be 3,600 sf (under subdivision with open space), lot width variable (40–60 ft), front setback often 20 ft (can be reduced to 10 ft on interior streets when community recreation provided) — see Table 17.35.030-1.

Where it applies: R‑T mapped areas identified in Chapter 17.35.

Mixed-Use / Commercial / Industrial (selected)

The city has multiple commercial and mixed‑use zones with their own development tables. Design review expectations differ because projects are often nonresidential, have higher FAR allowances, and can trigger different review thresholds.

• MUL / MUH (Mixed-Use Low / High) — objective requirements for ground-floor commercial, minimum landscaping, FAR caps in Table 17.40.040-1 and development standards at § 17.36.040.
• C-G / C-H (Commercial - General / Heavy) — typical commercial setbacks, max building heights ~50 ft, parking references to Chapter 17.155, site buffering when next to residential shown in Table 17.40.030-1.
• M-I / M-C (Industrial / Medical Center) — larger lot/height rules in Table 17.45.030-1 and specific screening/landscaping expectations; these projects frequently require Major Development Review.

Where it applies: See Chapters 17.36, 17.40, 17.45 for zone-specific standards and the mixed‑use/commercial/industrial tables referenced above.

Decision‑relevant table (what triggers design/site review and who decides)

Checklist (what an applicant must provide / satisfy for Development Review)

• Demonstrate consistency with the Wildomar General Plan and any applicable specific plan (§ 17.85.020.E.1, § 17.90.020.F.1).
• Show compliance with the intent of the applicable zone and with all applicable Title 17 provisions (zone standards from Table 17.35.030-1, Table 17.40.030-1, etc.). § 17.85.020.E.2, § 17.90.020.F.2.
• Plans and exhibits that meet PAR/site-plan requirements if PAR required: site plans, elevations, landscaping, grading, utility, vicinity map (§ 17.116.030–§ 17.116.050).
• Demonstrate compliance with the City’s objective design standards and adopted Single-Family / Multi-Family / Commercial design guidelines (Chapter 17.136).
• Parking plan that meets Chapter 17.155 requirements and landscape plan per Chapter 17.165 where applicable.
• If project is exempt from Development Review (e.g., most single-family homes, accessory dwelling units consistent with Title 17), provide required Zoning Clearance documentation (§ 17.90.020.B, § 17.135.010).

Risks & Ambiguities

Plain‑English Summary

In Wildomar, "design review" is applied through a two-tier Development Review system: small projects go through Minor Development Review (staff-level) and larger or non-conforming projects go through Major Development Review (Planning Commission). All projects must meet the relevant zone's development standards (setbacks, heights, lot coverage) and the City's objective design standards; single-family homes and many ADUs are generally exempt from discretionary development review but still must comply with the code and may need Zoning Clearance. Key rules live in § 17.85.010–§ 17.85.020, § 17.90.010–§ 17.90.020, and Chapter 17.136.

Information Gaps

• The city's specific Single‑Family Design Guidelines, Multi‑Family Objective Design Standards, and Commercial Objective Design Standards are referenced (Chapter 17.136) but the guideline documents themselves were not included in the retrieved materials. Not found in retrieved materials.
• Table 17-125.110-1 (Designated Authority for Approval) is referenced in multiple places as the location of specific approving authority assignments, but the table contents were not provided in the excerpts. Not found in retrieved materials.
• Fee amounts, exact application forms, and the current decision‑maker roster (staff names/desk assignments) are not in the code file and must be confirmed with the Planning Department. Not found in retrieved materials.

Source References

• Wildomar Development Code (Title 17) — Major Development Review and findings: § 17.85.010–§ 17.85.020.
• Wildomar Development Code — Minor Development Review (triggers, exemptions, findings): § 17.90.010–§ 17.90.020.
• Wildomar Development Code — Residential zone allowed uses and approval requirements (Table 17.35.020-1) and development standards (Table 17.35.030-1, § 17.35.030).
• Wildomar Development Code — Pre-Application Review (PAR) procedures and required exhibits: § 17.116.010–§ 17.116.050.
• Wildomar Development Code — Objective Design Standards reference and guidelines: Chapter 17.136.
• Wildomar Development Code — Zoning Clearance and applicability: § 17.135.010–§ 17.135.040.
• Wildomar Development Code — Landscape requirements (Chapter 17.165) and implementation: § 17.165.030–§ 17.165.060.
• Wildomar Development Code — Parking chapter reference (Chapter 17.155).

If you want, I can extract the exact application submittal checklist language from the City's forms or prepare a packable PAR exhibit checklist tailored to your parcel — tell me the parcel address and the preliminary scope (e.g., new 8‑unit apartment, ADU, 1,200 sf retail shell) and I will map the specific code triggers and typical studies required.

Retrieved passages

• CBC § 17.90.010 (Chapter 17.90.) High relevance show source text
• Wildomar Zoning Code (§ 17.165.040.) High relevance show source text
• Wildomar Zoning Code High relevance show source text
• CFC § 17.236.050 (Section 401) High relevance show source text
• CBC § 17.85.010 (Chapter 17.85.) Medium relevance show source text
• Wildomar Zoning Code (§ 17.165.030.) Medium relevance show source text
• Wildomar Zoning Code (§ 17.190.020.) Medium relevance show source text
• Wildomar Zoning Code (Chapter 17.76.) Medium relevance show source text
• Wildomar Zoning Code Medium relevance show source text
• Wildomar Zoning Code Medium relevance show source text
• Wildomar Zoning Code (Section 17.175.020) Medium relevance show source text
• Wildomar Zoning Code (Title 16) Medium relevance show source text
• Wildomar Zoning Code Medium relevance show source text
• Wildomar Zoning Code (§ 17.35.030.) Medium relevance show source text
• Wildomar Zoning Code (Chapter 17.35.) Medium relevance show source text
• Wildomar Zoning Code (Chapter 17.45.) Medium relevance show source text

Cited sections

• Wildomar Development Code (Title 17) — Major Development Review and findings: **§ 17.85.010–§ 17.85.020**. (Title 17)
• Wildomar Development Code — Minor Development Review (triggers, exemptions, findings): **§ 17.90.010–§ 17.90.020**. (§ 17.90.010)
• Wildomar Development Code — Residential zone allowed uses and approval requirements (Table **17.35.020-1**) and development standards (Table **17.35.030-1**, **§ 17.35.030**). (§ 17.35.030)
• Wildomar Development Code — Pre-Application Review (PAR) procedures and required exhibits: **§ 17.116.010–§ 17.116.050**. (§ 17.116.010)
• Wildomar Development Code — Objective Design Standards reference and guidelines: **Chapter 17.136**. (Chapter 17.136)
• Wildomar Development Code — Zoning Clearance and applicability: **§ 17.135.010–§ 17.135.040**. (§ 17.135.010)
• Wildomar Development Code — Landscape requirements (Chapter **17.165**) and implementation: **§ 17.165.030–§ 17.165.060**. (§ 17.165.030)
• Wildomar Development Code — Parking chapter reference (Chapter **17.155**). (chapter reference)
• Wildomar_ZoningCode.md

• Official Wildomar code library