Local zoning · Temecula

Temecula — Design Review

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

Ask a question free See coverage

Last reviewed: July 2, 2026

Overview

Design review in Temecula is implemented primarily through the city’s Development Plan/Development Plan Review process (commonly called “design” or “site plan” review) and through project-specific Planned Development Overlays (PDOs) that carry their own design guidelines. The city requires formal development-plan-level review for almost all commercial, industrial and multifamily projects and applies objective design standards where state law or a PDO does not provide them. Key triggers, decision authorities, and applicable standards are found throughout Title 17 of the Temecula Development Code (Zoning). See the summary of triggers and authorities below and the district-level notes that follow. Core rules on when a development plan / design review is required are in § 17.05.010 .

Important links (first natural mention of each topic):

  • The city’s approach to zoning and review is described in the Temecula Zoning framework.
  • Parking expectations that attach to development plans are set out in Temecula Parking rules and Chapter 17.24 as referenced in the PDOs and development-plan sections (§ 17.22.144; § 17.05.010) .
  • Dimensional and setback reference tables live in the Temecula Development Standards tables (e.g., Table 17.06.040) .
  • When a project sits inside a special overlay, consult the Overlay Districts rules and the applicable PDO (examples below) .
  • Landscaping and irrigation plans required as part of design review are addressed under the Landscaping and Screening requirements and Chapter 17.32 references (§ 17.06.060; § 17.08.060) .
  • Signage design and limits are enforced via the Temecula Signage chapter when signs are part of the review package (§ 17.28.010 et seq.) .
  • Accessory dwelling units (ADUs) are regulated separately; see Temecula ADUs and the state California ADU law; jurisdictional interplay is called out in several PDOs (§ 17.22.146) .
  • Structural, life-safety, and code compliance are handled under the California Building Standards Code (Title 24) — design review is not a substitute for Title 24 approvals. Notably, Temecula’s zoning text cross-references Title 24 where appropriate. Not found in retrieved materials: building-code technical requirements for construction-level permits.

How Temecula’s “Design Review” works (core rules)

  • When design review is required: A formal development plan / development-plan-review (the vehicle Temecula uses for architectural/site plan review) is required for all commercial, industrial and multifamily projects and for residential projects except individual single-family homes (i.e., individual single-family homes are exempt) — see § 17.05.010(B) .
  • Decision authority and thresholds:
    • The Director of Planning may approve projects under 10,000 sq ft (or single-family tract homes, subject to CEQA) at a noticed hearing; director decisions are appealable to the Planning Commission — see § 17.05.010(D)(1) .
    • Projects of 10,000 sq ft or greater are reviewed by the Planning Commission at a noticed public hearing — see § 17.05.010(D)(2) .
  • Mandatory findings for approval (design quality & public welfare): The approving body must make findings that the proposal conforms to the General Plan, protects public health/safety/welfare and meets applicable code standards — see § 17.05.010(F) and related findings language .
  • Expiration and time extensions: Development plan approvals expire if construction has not commenced within 3 years; administrative time extensions are available (director may grant up to 1 year per extension; multiple extensions allowed up to limits) — see § 17.05.010(G–H) .
  • Objective design standards: For multifamily and mixed-use projects (including those eligible for ministerial/state streamlined approvals), Temecula requires compliance with the Temecula Objective Design Standards where a PDO or specific plan does not provide standards — § 17.06.090 .
  • Development-plan contents & application: Applicants must submit materials per the general application rules (Section 17.03.030) and specific development-plan requirements (site plan, elevations, landscape/irrigation plans, parking calculations, materials/colors, lighting, signage, etc.) — see § 17.05.010(C) and cross-references to § 17.06.060, § 17.08.060, and PDO implementating sections .

Decision‑relevant summary table (what typically triggers design review and where to look in the code)

Trigger / Topic Typical outcome / standard Code reference
Development plan required for commercial/industrial/multifamily Formal development-plan review (site, architecture, landscaping, parking, signage) required § 17.05.010(B)
Approval authority threshold Director for projects < 10,000 sq ft; Planning Commission for ≥ 10,000 sq ft § 17.05.010(D)
Objective design standards for multifamily/mixed-use Apply Temecula Objective Design Standards if PDO or specific plan silent § 17.06.090
PDO-specific design rules PDO may set its own architecture/site standards and can allow minor deviations; PDO may require separate site plan/CUPs PDO examples: PDO-6 Rancho Pueblo design guidelines § 17.22.176 / § 17.22.178
Landscape/irrigation required All development plans in residential/commercial/industrial must include landscape & irrigation plans per water‑efficient ordinance § 17.06.060; § 17.08.060; Chapter 17.32
Accessory structure setbacks and residential dimensions Accessory-structure setbacks and residential dimensional table included in Table 17.06.050A and Table 17.06.040 Table 17.06.050A and Table 17.06.040

District-by-district breakdown (how design review applies by district)

Below are Temecula districts and PDOs that contain explicit design-review guidance in the retrieved code excerpts. For each district I list purpose, typical permitted uses (high-level), key dimensional/design points available in the code snippets and where the district or PDO applies. For parcel-specific questions verify with the jurisdiction.

Residential base districts — HR, RR, VL, L-1, L-2, LM, M, H, HR‑SM

  • Purpose: These zones implement the residential land use designations and residential performance standards; multifamily/mixed-use projects in these zones are subject to development-plan review when they are not single‑family detached homes. See Table 17.06.040 for the full dimensional schedule. § 17.06.040 and related residential performance sections carry the standards.
  • Typical permitted uses: Ranging from very low-density open‑space/residential in HR to high‑density multifamily in H; accessory dwelling units (ADUs) are governed by Chapter 17.23 and PDOs may add rules. § 17.06.040; PDO cross-references in the PDO articles.
  • Key dimensional/design notes:
    • Minimum lot areas and density ranges are tabulated in Table 17.06.040 (e.g., LM and M show 7,200 sq ft lot references in the table excerpt) — review Table 17.06.040 for parcel-specific numbers § 17.06.040 .
    • Accessory structure setbacks and separations are given in Table 17.06.050A (e.g., garages, carports, sheds setback rules) — see § 17.06.050 and Table 17.06.050A .
  • Where it applies: Citywide; consult the Zoning Map to confirm the applicable base district and any overlying PDO.

Public institutional — PI

  • Purpose: Governs schools, institutional uses and campus‑style development; specific PDO‑7 (Linfield Christian School) overlays and supplements PI standards. § 17.12 and PDO‑7 cross‑references.
  • Design notes: Development plans in PI districts must include landscaping and may be governed by plan area standards in PDOs (PDO‑7 contains planning-area rules and ties to Chapter 17.12). § 17.22.184 .

Planned Development Overlay — PDO-6 Rancho Pueblo and other PDOs (PDO-5, PDO-7, PDO-11 (Mira Loma), PDO-16, PDO-15, etc.)

  • Purpose: PDOs allow a tailored, area‑specific design program that can supersede or refine base-zone standards and supply architectural themes and site-specific design guidelines. See PDO introductory language § 17.22.040 – § 17.22.070.
  • Typical uses: Each PDO contains its own permitted/conditional/prohibited uses tables (e.g., Tables 17.22.166A, 17.22.196, 17.22.294). See the PDO tables for exact use lists. § 17.22.106, § 17.22.196, § 17.22.294
  • Key design features (examples):
    • PDO‑6 Rancho Pueblo places a Spanish‑American architectural expectation and includes architectural exhibits and site plan review rules; the city will use these PDO guidelines when reviewing site plans and architectural submittals — see § 17.22.176 and § 17.22.178 .
    • PDO‑11 (Mira Loma) provides a specific residential development standards table (Table 17.22.228) with minimum lot sizes, setbacks, building separation and maximum heights — see § 17.22.228 and § 17.22.232 .
    • PDO‑16 (Bedford Court) includes a development-standards table (FAR, setbacks, building separation, maximum heights) that will govern design review within that PDO in lieu of some base standards — see Table 2 in § 17.22.310 .
  • Where it applies: To the geographic area depicted on the official zoning map and described in the PDO ordinance text. PDOs routinely require or reference a separate site-development-plan process; see § 17.22.178(B) for site plan review process rules specific to Rancho Pueblo and analogous PDO language in other PDOs .

Checklist (what an applicant must prepare to clear Temecula design review)

  • Confirm zoning/PDO and required discretionary permits (verify base zone and any PDO overlays) — verify via the zoning map and PDO text § 17.22.040–070 .
  • Complete application per § 17.03.030 and pay fees; include a cover sheet listing requested approvals (development plan, CUP, variances, etc.) — see § 17.05.010(C) .
  • Scaled site plan with building footprints, parking layout, emergency access, trash enclosures and grading notes (parking rules reference Chapter 17.24) — see § 17.05.010 and PDO parking cross-references .
  • Architectural elevations, materials and color palette; indicate how the design follows PDO or citywide design guideline objectives — see § 17.06.070 and PDO design guidelines (e.g., § 17.22.176) .
  • Landscape and irrigation plans prepared to Chapter 17.32 water‑efficient standards — see § 17.06.060 and § 17.08.060 .
  • Lighting cut sheets and photometrics showing no off-site glare per the performance standards — see § 17.08.070(B) and PDO exterior lighting cross-references .
  • Sign program (if signs included) complying with Chapter 17.28 sign standards — see § 17.28.010 .
  • Parking calculation worksheets and loading/service area layouts per Chapter 17.24 — see PDO cross‑references to Chapter 17.24 and § 17.22.144 .
  • CEQA checklist / environmental document (if applicable) and any technical reports referenced by the PDO or development code (noise, drainage, traffic) — see approval/CEQA cross‑references in § 17.05.010(D) and PDO notes .

Risks & Ambiguities

Issue Why it matters What to verify
Director vs. Commission review (10,000 sq ft rule) Director approval (streamlined) v. Planning Commission hearing affects timing and appeal rights Check proposed gross new building area and whether the Director has exercised discretion to refer the file; see § 17.05.010(D)
PDO-specific standards may modify citywide rules PDOs can change setbacks, heights, allowed uses and design themes; relying on base zone only may miss PDO requirements Confirm whether the parcel lies inside a PDO and read the PDO’s development standards and design guidelines (e.g., PDO‑6 § 17.22.176 / § 17.22.178; PDO‑11 Table 17.22.228)
Objective (state-mandated) standards vs. discretionary standards State streamlined/ministerial approvals and objective standards can preempt discretionary design rules for qualifying housing If the project seeks ministerial/state streamlined approval, apply § 17.06.090 and confirm whether objective standards are in effect; otherwise discretionary review applies
ADU treatment ADUs are governed by Chapter 17.23 and state ADU law; local design review applicability may be limited Verify ADU-specific rules in Chapter 17.23 and consult staff; PDOs note ADUs may be permitted but must meet Chapter 17.23 (e.g., § 17.22.146(E))
Missing numeric standards in excerpts Many tables exist (Table 17.06.040, Table 17.06.050A) but parcel‑specific numeric values may be absent from excerpts Consult Table 17.06.040 and the full development‑standards tables on the City’s zoning pages for exact setbacks, lot sizes and densities § 17.06.040
Director’s authority to approve minor deviations in PDOs PDO implementation text allows the Director to approve certain alternatives but may refer major deviations to Commission/Council If proposing alternatives to PDO standards, verify scope of Director’s authority in the specific PDO (see § 17.22.178(C) for Rancho Pueblo example)

Plain-English Summary

If you’re building anything other than a single-family detached house in Temecula (for example, apartments, condos, retail, office, or industrial), you’ll almost always need a development-plan-level design review where the city checks site layout, architecture, landscaping, parking and signs. Small projects under 10,000 sq ft are often handled administratively by the Planning Director; bigger ones go to the Planning Commission. Project‑area overlays (PDOs) can add or change rules, so check the PDO text that applies to your parcel. See § 17.05.010, § 17.06.090, and the relevant PDO sections for the exact rules and tables.

Source References

  • Temecula Municipal Code — Development Plans: § 17.05.010 (development plans; when required; hearing authority) .
  • Temecula Municipal Code — Administrative approval of development plans: § 17.05.020 .
  • Temecula Municipal Code — Objective design standards for multifamily/mixed‑use projects: § 17.06.090 .
  • Temecula Municipal Code — Residential Development Standards (Table 17.06.040) and accessory structure setbacks (Table 17.06.050A) — Table excerpts and references § 17.06.040 / § 17.06.050 .
  • Temecula Municipal Code — Commercial / Office / Industrial performance & landscape rules: § 17.08.070; § 17.08.060 (landscaping) .
  • Rancho Pueblo PDO design guidelines and implementation: § 17.22.176 and § 17.22.178 (PDO‑6) .
  • PDO examples with project tables and architectural guidelines (Mira Loma PDO‑11, Cypress Ridge PDO‑15, Bedford Court PDO‑16): § 17.22.228, § 17.22.294, § 17.22.310 and related tables .
  • Sign standards and design intent for signage: § 17.28.010 (Sign Standards—purpose & intent) .
  • Definitions and “development plan review (design)” phrasing (definitions and code terms) — definitional references in the development-code text (see definition excerpts) .

Sources

Retrieved passages

  • Temecula Zoning Code Medium relevance
  • Temecula Zoning Code (Section 17.05.010) Medium relevance
  • Temecula Zoning Code (§ 2) Medium relevance
  • Temecula Zoning Code (section that) Medium relevance
  • Temecula Zoning Code (Title 18) Medium relevance
  • CBC § 4 (§ 4) Medium relevance
  • Temecula Zoning Code (§ 3) Medium relevance
  • Temecula Zoning Code (§ 17.22.070.) Medium relevance
  • Temecula Zoning Code (§ 17.22.228.) Medium relevance
  • Temecula Zoning Code (§ 2) Medium relevance
  • Temecula Zoning Code (§ 2) Medium relevance
  • Temecula Zoning Code (§ 17.08.070.) Medium relevance
  • Temecula Zoning Code (§ 4) Medium relevance

Cited sections

Frequently asked questions

Do I need design review in Temecula?

If your project is commercial, industrial or multifamily (or any development other than an individual single‑family home), yes — you must submit a development plan for design/site review. The rules are in § 17.05.010(B) .

Who approves design review in Temecula: director or planning commission?

Projects under 10,000 sq ft (and single‑family tract-home reviews in certain CEQA situations) are typically decided by the Director of Planning (notice + appealable); projects 10,000 sq ft or larger are heard by the Planning Commission — see § 17.05.010(D) .

What design standards apply to a new apartment building?

Multifamily/mixed‑use projects must meet Temecula’s Objective Design Standards where a PDO or specific plan does not supply standards; see § 17.06.090 for the objective‑standards requirement and follow any PDO design criteria that apply to your parcel .

Where do I find setbacks, densities and lot-size numbers for my lot?

Check Table 17.06.040 (Development Standards—Residential Districts) and the corresponding tables for nonresidential zones and PDOs; the code’s Table 17.06.040 contains the lot area, density ranges and other dimension schedules referenced by § 17.06.040 .

If my property is in a PDO, which rules control design?

PDO text and exhibits control within the PDO area; PDOs commonly incorporate or modify base-code rules and may set architectural themes and unique setbacks. If the PDO is silent on an issue, the development code rules apply. See PDO implementation language such as § 17.22.178 (Rancho Pueblo) and other PDO sections .

Are landscape and irrigation plans required for design review?

Yes. Development plans for residential, commercial and industrial projects must include landscape and irrigation plans consistent with the city’s Water Efficient Landscape Design Ordinance (Chapter 17.32) — see § 17.06.060 and § 17.08.060 .

How long does a development-plan approval last?

A development-plan approval expires if construction has not commenced within 3 years; time extensions can be requested per the director’s authority and the code’s extension rules — see § 17.05.010(G–H) .

Do ADUs require design review in Temecula?

ADUs are regulated under Chapter 17.23 and the PDOs may specifically reference ADU permissibility; however, the base development‑plan rule exempts individual single‑family homes from the development-plan process. Whether an ADU requires design review depends on the ADU type and local Chapter 17.23 rules — see § 17.22.146(E) and § 17.05.010(B). Verify with the Planning Department for parcel‑specific direction .

Can the Director approve deviations from PDO standards?

Some PDOs explicitly allow the Director limited authority to approve minor deviations or alternative standards; larger deviations or standards outside the Director’s scope will require Planning Commission or City Council action (PDO implementation language). See § 17.22.178(C) for the Rancho Pueblo approach as an example .

Where can I see Temecula’s design guidelines and examples?

Many PDOs include architectural exhibits and citywide design guidelines are referenced in the PDOs; specific PDO sections (e.g., § 17.22.176, § 17.22.232) and Chapter 17.06 performance standards discuss desirable architectural features and palettes — consult those sections for examples and the city’s design exhibits . ---

More in Temecula code

Ask about any Temecula property

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

Start Free Trial

More Temecula zoning topics

Temecula Zoning

Temecula Land Use

Temecula Development Standards

Temecula Parking

Temecula Overlay Districts

Temecula Historic Preservation

Temecula Signage

Temecula Nonconforming Uses

Temecula Variances and Exceptions

Temecula Landscaping and Screening

Temecula overview