Local zoning · Temecula

Temecula — Overlay Districts

Q: Where do I check whether my use is allowed in a PDO?

Each PDO includes a use schedule (Tables such as Table 17.22.106 , Table 17.22.126 , Table 17.22.216 , Table 17.22.276 ) listing permitted ("P"), conditional ("C"), and prohibited uses; check the applicable table and the PDO’s “Relationship with the development code” clause. See the relevant Table § in the PDO.

Q: Are there numeric exceptions in any Temecula PDOs I should watch for?

Yes — for example the Temecula Hospital PDO ( PDO‑9 ) contains a specific building height exception: up to 30% of roof area may exceed 75 ft and such portions are capped at 115 ft ; see § 17.22.206 . Always check the specific PDO text for numeric exceptions.

Overlay Districts under the Temecula local zoning and planning code, with the controlling citations.

Ask a question free See coverage

Last reviewed: July 2, 2026

Overview

Temecula’s overlay districts are implemented primarily as Planned Development Overlay (PDO) zoning districts within Title 17 (Zoning). PDOs supplement the base zoning by allowing site‑specific mixes of uses, design standards, and performance rules while generally deferring to the underlying zoning and the citywide design guidelines except where a PDO explicitly modifies them. Key procedural and standards rules for PDOs are in § 17.22.040 and § 17.22.050.

This page summarizes what the Temecula zoning ordinance actually says about each codified PDO (where available in the retrieved material), highlights the most decision‑relevant numeric or procedural modifications, and points you to the exact code sections to verify for a parcel. For underlying development rules (setbacks, lot coverage, height) consult the Temecula Development Standards and the base zone cited in each PDO; PDOs either adopt those standards or state explicit exceptions. See Temecula Development Standards. (/us/california/temecula/development-standards)

How to read this page

Bolded district names (for example PDO-1) are the city’s actual overlay labels in the municipal code.
Every built requirement below is tied to the Temecula code by a § citation and the file citation returned from the ordinance search (those markers show the underlying ordinance excerpt I used).
Links to related Temecula topic pages are provided where the ordinance refers to those topics in practice (for example procedures, parking, design review, ADUs, and state building code). Use those as next steps when preparing an application: Temecula Zoning & Planning Overview (/us/california/temecula), Temecula Zoning (/us/california/temecula/zoning), Temecula Parking (/us/california/temecula/parking), Temecula Design Review (/us/california/temecula/design-review), Temecula ADUs (/us/california/temecula/adu), California Building Standards Code (/us/california/building-codes).

General PDO rules that apply citywide

The PDO tool and adoption procedure: applications for a planned development overlay follow the zoning amendment procedure; a concurrent development plan may be required by the Director of Planning. See § 17.22.040.
Development standards default to the underlying zone, unless a PDO explicitly modifies them; the city allows modifications for flexibility to achieve the PDO vision. See § 17.22.050.
A PDO normally incorporates the citywide design guidelines; where the PDO modifies design rules it states so explicitly (PDO text frequently contains a "Relationship with the development code and citywide design guidelines" clause). Examples: § 17.22.204, § 17.22.214, § 17.22.274.
Objective design standards for multifamily and mixed‑use projects apply when a PDO or specific plan does not already establish objective criteria: § 17.22.080.

District-by-district (codified PDOs found in the retrieved ordinance)

Below are the PDO districts that appear in the retrieved Title 17 excerpts. Each subsection gives: purpose (ordinance language summary + citation), typical permitted uses (an illustrative summary with the controlling table citation), key dimensional or special standards (what the PDO changes or calls out), and where the PDO applies (location note when supplied).

Note: For full permitted‑use matrices and detailed numeric standards consult the cited table § in each entry.

PDO-1 — Pala Road Planned Development Overlay District (PDO-1)

Purpose: To regulate a constrained commercial area (easements, floodplains, faults) allowing neighborhood convenience uses and limited outdoor storage while protecting adjacent residential; intent to supplement the development code. § 17.22.102
Typical permitted uses: A detailed permitted/conditional/prohibited use table is provided in Table 17.22.106 / § 17.22.106 (e.g., small studios, retail, select service uses; alcoholic sales and certain outdoor uses may be conditional). § 17.22.104 and § 17.22.106
Key standards: The PDO defers to the development standards for a neighborhood commercial zoning district except where § 17.22.108 provides modifications; applicants must follow citywide design guidelines unless modified. § 17.22.104 and § 17.22.108
Where it applies: The Pala Road PDO is a site‑specific overlay described in the ordinance; see Table 17.22.106 for the parcel‑level use list. § 17.22.100–108

PDO-3 — Nicolas/Winchester Planned Development Overlay (PDO-3)

Purpose: Permit a limited range of low‑impact business, office, and commercial uses on a constrained corner; ensure protections for adjacent residential. (See purpose text preceding § 17.22.124.)
Typical permitted uses: The PDO supplies a site‑specific use table: Table 17.22.126 / § 17.22.126 lists permitted ("P"), conditional ("C"), and prohibited ("-") uses. Example entries and many prohibitions reflect a narrow commercial/office focus. § 17.22.126
Key standards: Development standards are those that apply to a business park zone unless specifically modified by the PDO; citywide design guidelines apply. § 17.22.124
Where it applies: The northwest corner of Nicolas and Winchester Roads; see the PDO use schedule for parcel boundaries. § 17.22.124–126

PDO-5 — Rendezvous Planned Development Overlay District (PDO-5)

Purpose: Create a unique medium‑density residential area (7–12.9 du/ac) with pedestrian scale, signage and transit provisions; ensure compatibility with surrounding multifamily and single‑family neighborhoods. § 17.22.142–143
Typical permitted uses: Multifamily residential per the PDO vision; the PDO also sets a maximum unit count and internal design requirements (see § 17.22.143 and exhibits). § 17.22.142–143
Key standards: Project‑level standards are in the PDO (unit counts, landscape buffers, site plan requirements); the PDO may alter typical development standards as part of the development plan process. § 17.22.143
Where it applies: A defined 22.97‑acre area south of Rancho California Road (site description in § 17.22.142). § 17.22.140–156

PDO-6 — Rancho Pueblo Planned Development Overlay District (PDO-6)

Purpose: Guide a comprehensively planned mixed‑use village concept consistent with the General Plan Z1 overlay; underlying zoning remains Professional Office (PO) except where the PDO modifies standards. § 17.22.162
Typical permitted uses: The PDO contains a Matrix of Uses (a site‑specific Table) that governs permitted and conditionally permitted uses; consult Table 17.22.166A (as referenced in the PDO text). § 17.22.162
Key standards: The PDO may allow alternative development standards and contains procedures for minor variations and PDO amendment (site plan review, director/commission review as described). § 17.22.162 (Procedures A–E)
Where it applies: Rancho Pueblo planning area (site‑specific maps/exhibits in the PDO). § 17.22.160–178

PDO-7 — Linfield Christian School Planned Development Overlay District (PDO-7)

Purpose: Regulate school facilities and adjacent development with tailored standards (see the PDO preamble and special standards). § 17.22.180–181
Typical permitted uses: School and ancillary educational/institutional uses; the PDO also specifies parking/landscape/fence exceptions for school uses (see text). § 17.22.181
Key standards: Parking lot tree ratios, exemptions to fence height for school facilities, and landscape rules are included in the PDO text (see the section on parking and fencing). § 17.22.181 (subsections on parking/fencing)
Where it applies: Linfield Christian campus area as identified in the PDO. § 17.22.180–188

PDO-8 — De Portola Road Planned Development Overlay District (PDO-8)

Purpose: Provide a commercial‑residential transitional area permitting office and medical uses while buffering large‑lot residential neighbors. § 17.22.192
Typical permitted uses: A use table governs permitted and conditional uses: Table 17.22.196 / § 17.22.196 (see the PDO for the matrix). § 17.22.194–196
Key standards: The PDO references the citywide design guidelines and may impose supplemental performance standards to protect adjacent residential uses. § 17.22.194
Where it applies: De Portola Road transition area; see the PDO tables and exhibits. § 17.22.190–198

PDO-9 — Temecula Hospital Planned Development Overlay District (PDO-9)

Purpose: Provide design flexibility for hospital projects while generally remaining consistent with the General Plan land use designation. § 17.22.202
Typical permitted uses: Hospital and related medical services consistent with professional/institutional land use; the PDO instructs that development standards for a professional office district apply except where the PDO modifies them. § 17.22.204
Key standards (notable modification): Building height — no more than 30% of total roof area may exceed the 75‑foot building height limit, and the portions within that 30% cannot exceed 115 feet. This specific height exception is in § 17.22.206. § 17.22.206
Where it applies: Temecula Hospital PDO area as mapped and described in the PDO sections. § 17.22.200–206

PDO-10 — Temecula Education Center Planned Development Overlay District (PDO-10)

Purpose: Allow higher education uses, high‑density residential, and project‑serving commercial uses with performance standards to protect neighbors. § 17.22.212
Typical permitted uses: A comprehensive permitted/conditional use schedule is provided in Table 17.22.216 / § 17.22.216 (includes accessory dwelling units as permitted, educational uses, retail, services, and many other uses; the director can decide for unspecified uses). § 17.22.216
Key standards: Except as modified in the PDO, development standards for the public/institutional zoning district apply; the PDO may add performance standards (noise, odor, screening). § 17.22.214–218
Where it applies: The Temecula Education Center site as identified in the PDO exhibits. § 17.22.210–218

PDO-14 — Gateway to Temecula Planned Development Overlay District (PDO-14)

Purpose: Regulate a roughly 8.82‑acre local/tourist commercial project with cohesive architectural, landscape, monumentation, and signage themes. § 17.22.274–276
Typical permitted uses: The PDO contains a site‑specific Schedule of Permitted Uses (Table 1 in § 17.22.276), which shows specific retail, restaurant, lodging, and service uses with "P" and "C" designations. § 17.22.276
Key standards: Buffering and setback requirements may go beyond the underlying zone; signage and monument design are called out in the PDO text. § 17.22.274–276
Where it applies: North of Temecula Parkway at Bedford Court / La Paz / Vallejo Ave (see PDO map). § 17.22.276

PDO-16 — Bedford Court Planned Development Overlay District (PDO-16) (recent)

Purpose: Permit creative mixes of uses on smaller properties where a specific plan or village center overlay is not appropriate; provides flexibility and supplemental standards for local‑serving commercial uses. § 17.22.304
Typical permitted uses: A Schedule of Permitted Uses (Table in § 17.22.308) lists permitted and conditional uses for this ~1.88‑acre site. § 17.22.308
Key standards: PDO‑level site standards, architectural theming, and buffering/setback requirements are included; the PDO also references Temecula Objective Design Standards for multifamily/mixed use. § 17.22.306
Where it applies: Bedford Court terminus area east of I‑15 and west of Temecula Parkway. § 17.22.302–316

Quick table — selected decision‑relevant items (illustrative)

Overlay (code)	Primary purpose (short)	Notable modification or decision trigger	Code reference
PDO-1 (Pala Road)	Constrained neighborhood commercial rules	Site use table controls permitted/conditional uses; defers to NC standards unless modified	§ 17.22.100–108
PDO-9 (Hospital)	Hospital design flexibility vs GP consistency	Height exception: up to 30% roof area may exceed 75 ft, capped at 115 ft for that 30%	§ 17.22.200–206
PDO-10 (Education Center)	Higher ed + high‑density residential + commercial mix	Comprehensive use matrix; ADUs shown as permitted in the PDO matrix	§ 17.22.210–218 and § 17.22.216
PDO-14 (Gateway)	Tourist/local serving commercial with unified design	Supplemental setbacks, signage/monument standards beyond base zoning	§ 17.22.274–276

Checklist (what an applicant must satisfy for a property in a PDO)

Confirm the site is within a listed Planned Development Overlay and identify the specific PDO number on the official zoning map (PDO labeling and mapping rules: § 17.22.070).
Read the PDO’s permitted/conditional use table (e.g., Table 17.22.106, Table 17.22.126, Table 17.22.216, Table 17.22.276) and confirm your proposed use status. § 17.22.104, § 17.22.126, § 17.22.216, § 17.22.276.
Review whether the PDO explicitly modifies dimensional rules (heights, setbacks, lot coverage) or defers to the underlying zone; if modified, use the PDO standard (e.g., hospital height rules in § 17.22.206).
Check whether the PDO requires a development plan, site plan review, or a concurrent submittal at time of PDO application (procedures: § 17.22.040).
Determine if a Conditional Use Permit (CUP) or planning commission action is required for your use per the PDO’s use table. (See relevant PDO use table and § 17.22.214 for director discretion provisions where present.)
Confirm design and objective standards to be applied (citywide design guidelines and Temecula Objective Design Standards for multifamily/mixed use where stated: § 17.22.080). See Temecula Design Review. (/us/california/temecula/design-review)
Verify parking requirements per the development code and any PDO‑specific parking/landscape rules before preparing a parking analysis. See Temecula Parking. (/us/california/temecula/parking)

Risks & Ambiguities

Issue	Why it matters	What to verify
Use not listed in a PDO table	The PDO often reserves discretion to the planning director to classify unlisted uses; this can lead to unexpected CUP requirements	Verify whether the PDO text explicitly allows director discretion and get a pre‑application interpretation. See § 17.22.216 for PDO‑10 and similar clauses in other PDOs.
PDO defers to underlying zone standards	The default standards (setbacks, FAR, lot coverage) come from the base zone; failure to cross‑check can lead to incorrect assumptions	Confirm underlying zoning district (e.g., PO, BP, NC) and apply the base standards unless the PDO explicitly modifies them (§ 17.22.050, § 17.22.214).
Parcel‑specific mapping / uncodified PDOs	Some PDOs are approved but not fully codified; official zoning map controls	Check the official zoning map and the ordinance adopting the PDO; see § 17.22.070 (approved planned development overlays and mapping).
PDO amending vs. director approval thresholds	The PDO text frequently allows minor variations by the Director but requires a PDO amendment for larger departures	Review the PDO’s procedures (e.g., Rancho Pueblo PDO: director may approve minor variations; amendments require commission/council) to gauge likely review path and timeline. See PDO procedural clauses (examples in § 17.22.162 and the Rancho Pueblo PDO text).
Numeric exceptions embedded in PDO text	Numeric rules (like the hospital height rule) are potentially unique and control over base code	Never assume base zone heights apply — confirm whether the PDO has explicit numeric exceptions such as § 17.22.206 for PDO‑9.

Plain-English Summary

Temecula’s overlays are mostly Planned Development Overlays (PDOs) that sit on top of the base zoning to allow site‑specific mixes of uses and design rules; you must read the PDO’s use table and any PDO‑specific standards (for example special height rules in the Temecula Hospital PDO) because the PDO will either adopt the underlying zone’s development standards or explicitly change them. Key procedural steps and where to look first are § 17.22.040 (application procedure) and § 17.22.050 (how PDOs relate to the base standards).

Source References

Temecula Municipal Code, Title 17 — Planned Development Overlay provisions: § 17.22.040 (procedures) and § 17.22.050 (development standards).
Pala Road PDO (PDO‑1): § 17.22.100–108 and Table 17.22.106 (Schedule of Permitted Uses).
Nicolas/Winchester PDO (PDO‑3): § 17.22.124–128 and Table 17.22.126.
Rendezvous PDO (PDO‑5): § 17.22.140–156.
Rancho Pueblo PDO (PDO‑6): § 17.22.160–178, procedural text and use matrix references.
Temecula Hospital PDO (PDO‑9): § 17.22.200–206 (notable height exception at § 17.22.206).
Temecula Education Center PDO (PDO‑10): § 17.22.210–218, Table 17.22.216 (use schedule).
Gateway to Temecula PDO (PDO‑14): § 17.22.274–276 and Table 1 (Schedule of Permitted Uses).
Bedford Court PDO (PDO‑16): § 17.22.302–316 (recently added PDO).

Sources

Retrieved passages

Temecula Zoning Code (§ 3) High relevance
Temecula Zoning Code (§ 2) High relevance
Temecula Zoning Code (§ 4) High relevance
Temecula Zoning Code (title for) High relevance
Temecula Zoning Code (§ 3) High relevance
Temecula Zoning Code (§ 17.22.070.) High relevance
Temecula Zoning Code (§ 17.22.124.) High relevance
Temecula Zoning Code (§ 2) High relevance

Cited sections

Official Temecula code library

Frequently asked questions

What is a Planned Development Overlay (PDO) in Temecula and where is it defined?

A PDO is a site‑specific overlay that supplements the base zoning to allow mixed uses and alternative standards; procedures and general rules are codified in § 17.22.040 (application/procedure) and § 17.22.050 (how PDOs relate to base development standards).

Do PDOs change the underlying zoning rules (setbacks, lot coverage, height)?

Often the PDO defers to the underlying zone but may explicitly modify particular development standards; the general rule is in § 17.22.050, and specific PDOs state their own exceptions (for example, the hospital PDO height modification in § 17.22.206). Verify the PDO text for any numeric exception.

Where do I check whether my use is allowed in a PDO?

Each PDO includes a use schedule (Tables such as Table 17.22.106, Table 17.22.126, Table 17.22.216, Table 17.22.276) listing permitted ("P"), conditional ("C"), and prohibited uses; check the applicable table and the PDO’s “Relationship with the development code” clause. See the relevant Table § in the PDO.

If a use is not listed in the PDO, what happens?

Several PDOs state that unlisted uses may be allowed or treated as conditional at the discretion of the planning director; for example PDO‑10 allows the planning director to determine unlisted uses. See § 17.22.216 (PDO‑10) for an example of that language.

Do PDOs require special design review or different parking rules?

PDOs generally incorporate the citywide design guidelines and may add PDO‑specific design or parking performance standards; where a PDO is silent the normal development code parking standards apply. See the PDO relationship clauses (e.g., § 17.22.214, § 17.22.274) and the citywide design/objective standards § 17.22.080. For parking specifics, consult the Temecula Parking guidance. (/us/california/temecula/parking)

Are there numeric exceptions in any Temecula PDOs I should watch for?

Yes — for example the Temecula Hospital PDO (PDO‑9) contains a specific building height exception: up to 30% of roof area may exceed 75 ft and such portions are capped at 115 ft; see § 17.22.206. Always check the specific PDO text for numeric exceptions.

How do I apply for a PDO or changes to an existing PDO?

Applications for PDOs follow the zoning amendment procedures; the Director may require a concurrent development plan. Some PDOs allow minor variations by the Director while major changes require PDO amendments via planning commission and city council. See § 17.22.040, § 17.22.050, and PDO procedural text (example: Rancho Pueblo PDO procedural clauses).

Can a PDO be expanded or repealed?

Yes. PDOs include amendment and repeal procedures: amendments normally require planning commission and city council approval, and the ordinance that repeals a PDO must reassign zoning to the area. See § 17.22.060 and PDO amendment clauses (e.g., Rancho Pueblo). § 17.22.060 (amendments) is in the PDO chapter.

Are accessory dwelling units (ADUs) allowed in PDO areas?

Some PDOs explicitly list ADUs in their use schedule (for example, PDO‑10’s Table shows Accessory dwelling unit as permitted); however ADU rules are also governed by state law — verify both the PDO table (§ 17.22.216) and California ADU law. See Temecula ADUs and California ADU law. (/us/california/temecula/adu)

Where do I find the official map that shows PDO locations?

The official zoning map will show PDO boundaries and the PDO prefix numbering; the municipal code states approved PDOs are shown on the official zoning map and lists currently approved overlays. See § 17.22.070. ---

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