Porterville — Design Review

Last reviewed: July 2, 2026

Overview

This page explains how design review, architectural/site-plan review, and related discretionary design controls operate under Porterville’s local zoning ordinance (Title 17). It summarizes which districts require compliance with design guidelines, which city bodies perform design or plan review, and what submittals and thresholds trigger discretionary review. Where the code is silent or unclear in the available materials I note the gap and advise verification with the city. Bolded terms and the first time key related topics are mentioned are linked to the city guidance pages for easy navigation.

How Porterville’s ordinance treats "design review" (quick summary)

• Porterville embeds design control inside district development standards and discretionary-plan processes rather than a single standalone "design review board" chapter. See the downtown design guideline requirement (§ 202.04) and the Planned Development development-plan requirement (§ 207.11) for explicit design-review mandates.
• Thresholds for multi‑department review (which performs design and technical checks) are established by the Project Review Committee and the Zoning Administrator; projects meeting those thresholds are routed to discretionary review or administrative decision processes. See § 600.04 and § 600.03.

(Note: when this page mentions design, it also points to the city’s pages on development standards, parking, overlays, and ADUs to help applicants navigate adjacent rules: see Porterville Development Standards, Porterville Parking, Porterville Overlay Districts, and Porterville ADUs.)

District-by-district design-review summary

The ordinance groups districts into base classes and applies design-related rules either directly in each district article or via cross-cutting standards in the 300 and 500 series. The district names and the code’s grouping are listed in § 101.02 (district listings).

Below are Porterville-specific district subsections. For each district I (A) summarize the stated PURPOSE or intent; (B) list typical permitted uses from the code narrative (not exhaustive); (C) give the key design / dimensional standards that the code text or tables explicitly provide in the retrieved materials; (D) identify where design guidelines / review are referenced. If a particular numeric standard was not present in the retrieved excerpts I state "Not found in retrieved materials" so you can verify with the city.

RS-1 (Very Low Density Residential)

• Purpose: Implement very low density residential areas; part of the R district family. § 101.02 defines RS-1 as a residential base district.
• Typical permitted uses: single-family dwellings and customary accessory uses. Not all use lists were pulled in the retrieved excerpts; check the base R-district use table in the code. Verify with the jurisdiction.
• Key dimensional standards: Not found in retrieved materials. Verify with the zoning table for RS districts.
• Design-review triggers: Projects that become discretionary (for example, variances or subdivision-level changes) will be subject to the Project Review process; see § 600.04.

RS-2 (Low Density Residential)

• Purpose and uses: Similar structure to RS-1; intended for low density neighborhoods (see § 101.02).
• Key dimensional standards: Not found in retrieved materials. Verify with the jurisdiction.

RM-1, RM-2, RM-3 (Low‑medium to High Density Residential)

• Purpose: Higher-density multifamily residential districts (RM-1 through RM-3) within the R district family. § 101.02.
• Typical permitted uses: multifamily housing types, accessory uses; specific use limits appear in district tables that were not fully returned. Verify with the jurisdiction.
• Key dimensional standards: Not found in the retrieved materials for RM tables. Verify with the city’s zoning tables.
• Design-review triggers: Multi-family developments of four (4) or more units are explicitly routed to the Project Review process; see § 600.04(B).

RN (Residential Neighborhood)

• Purpose: Create compact neighborhoods with a defined mixed-use center and variety of housing types. § 206.01 describes this intent.
• Typical permitted uses: Mixed residential types, neighborhood-support commercial in the center—see Article 206.
• Key dimensional standards: RN requires master planning and specific design elements (e.g., porches, garage location, open space minimums) described in Article 206 supplemental regulations; see § 206.04–206.07 (excerpts describing porches, variable garage entries, open space).
• Design-review triggers: RN projects are expected to meet master plan or PD-like review where design elements are tested; see Planned Development and PD plan requirements. § 207.11 applies where PD plans exist.

PD (Planned Development)

• Purpose: Allows a tailored plan for larger sites; intended to produce quality urban design and flexibility. § 207.01–207.04 describe the PD regime and intent.
• Typical permitted uses: Any use in the Chapter that is included in an approved PD Plan or Specific Plan; otherwise no new uses allowed without conforming to the PD Plan. § 207.03.
• Key dimensional standards: PD districts have flexible standards; the PD Plan establishes specifics. § 207.04 sets minimum area and unit density constraints (e.g., typical minimum area 4 acres, council can approve smaller in some cases).
• Design-review triggers: Development Plan Review is mandatory in PD districts; plans must be consistent with an approved PD Plan or Specific Plan before building permits are issued (§ 207.11).

Downtown districts (DR‑N, DR‑S, DR‑D, D‑MX, D‑PO, D‑GC, D‑PS, DRM‑2, DRM‑3)

• Purpose: Downtown districts regulate urban form, pedestrian orientation, and a mix of retail/professional/residential uses. The downtown districts list and table appear in Article 202 and Table 202.03.
• Typical permitted uses: Retail, professional offices, mixed-use residential above ground floor (with specific limitations on Main Street and ground-floor residential), and other downtown-appropriate uses listed in Article 202. § 202.03 and Table 202.03.
• Key dimensional standards: Table 202.03 prescribes lot area, setbacks, parking location rules, open space, and block-length limits for the downtown districts. For example, downtown Supplemental Regulations require that development comply with Downtown Design Guidelines (§ 202.04.A) and limit block length (max 500 ft) to encourage pedestrian connections (§ 202.04.B).
• Design-review triggers: All development in downtown districts must comply with the Downtown Design Guidelines by resolution (§ 202.04.A) — that is the primary design-review standard for downtown projects.

(First time the page mentions downtown design guidelines: compliance is required — see the Downtown Design Guidelines; link to Porterville Development Standards.)

C districts (CN, CR, CG, CMX — Commercial)

• Purpose: Serve neighborhood commercial, retail centers, general/service commercial, and commercial mixed‑use needs. § 101.02 provides the list.
• Typical permitted uses: Neighborhood-serving retail and services; precise lists live in the land-use tables (not fully retrieved). Verify with the code.
• Key dimensional standards & design controls: Parking location, screening and landscaping requirements in Article 300 and Chapter 304 apply to C districts; see § 300.10 (screening), the parking article (Article 304) and Downtown supplemental parking rules for downtown commercial sites where applicable.
• Design-review triggers: Commercial additions 500 sf+ are subject to Project Review Committee per § 600.04(A); larger or discretionary commercial projects will require discretionary approvals and project/plan review.

E districts (PO, IP, IG, IA — Employment / Industrial)

• Purpose: Support professional office, industrial park, general industrial, and airport industrial uses. § 101.02.
• Design/dimensional standards: Transitional standards and setbacks from R districts apply (see transitional rules in Article 204/205). Specific industrial design controls are within performance standards and the 300 series. Not all numeric standards were returned. Verify with the city.

PS / REC / PK (Public & Open Space districts)

• Purpose: Public and semipublic, recreation, parks. Table 205.03 provides development standards for PS, REC, PK (e.g., minimum lot area and heights).
• Key dimensional examples from the table: PS minimum lot area 87,120 sq ft (2 acres) and maximum height 75 ft; PK maximum height 25 ft; minimum yards shown in Table 205.03. See § 205.03 and Table 205.03.
• Design-review triggers: Projects on public or semipublic land will be reviewed under the PD and project review procedures when they require discretionary approvals. See § 207.11 and § 600.04.

Overlays (AE, HZ, S)

• Purpose and applicability: Overlay districts (Airport Environs AE, HZ Hillside Development Zone, and S single-story) are listed in § 101.02.B and apply in addition to base districts. They impose additional design/technical submittal and review requirements when applicable.
• Key HZ example: HZ (Hillside) specifies applicability and required plans and specific submittal items for hillside developments (see § 501.02–§ 501.03). The HZ overlay requires topographical maps, conceptual grading, biological and geologic reports and other materials as part of discretionary reviews.

How review bodies handle design

• Project Review Committee (PRC): reviews development proposals meeting thresholds (new or additions of 500 sq ft+ to commercial/industrial structures; multi‑family of 4 or more units; and any project requiring discretionary approvals). See § 600.04(A–E).
• Zoning Administrator: may approve/deny administrative approvals, adjustments, or make zoning-conformance determinations; issues administrative regulations and can approve items subject to appeal. See § 600.03.
• City Council / Decision Bodies: conditional use permits, variances and tentative maps are decided by City Council or decision-making bodies as required. See the City Council duties list and appeals procedures in § 600 series.

Design guidance documents referenced in the code:

• Downtown Design Guidelines: compliance is required for downtown projects (§ 202.04.A) — the guidelines themselves are adopted by resolution and apply to design review decisions.
• Downtown development standards and block-length/parking location rules are explicit in § 202.04 and Table 202.03.

(First natural mention of "parking" in the paragraph above links to Porterville Parking; "development standards" links to Porterville Development Standards; "overlays" links to Porterville Overlay Districts; "ADUs" link later under checklist.)

Key standards & decision table

Applicant checklist (what you must satisfy or submit before design approval)

• Confirm zoning and any overlay(s) on the parcel (official zoning map; see § 101.02).
• Establish whether the project meets PRC thresholds (commercial 500+ sf, multi‑family 4+ units, discretionary permit) and prepare for Project Review if so (§ 600.04).
• For PD or Specific Plan sites: show project consistency with the approved PD Plan or Specific Plan (no permits issued unless consistent — § 207.11).
• For Downtown district projects: document compliance with the Downtown Design Guidelines and Downtown supplemental regulations (block length, parking location, ground-floor use rules) (§ 202.04, Table 202.03).
• If in the HZ overlay: include topographic map, conceptual grading plan, biological/geologic reports and all items listed in § 501.03.
• Submit full plot plans, exterior elevations, materials/finishes, landscape plans, site lighting, parking layout, and any other exhibits requested by the Zoning Administrator (Article 601 common procedures & specific PD/HZ submittal lists). § 601.02 and § 501.03.
• If your project will require discretionary approvals (CUP, variance, subdivision), prepare CEQA materials as applicable — the Zoning Administrator and PRC act as environmental coordinator per § 600.03.N and article 611 references.
• For design relating to parking, setbacks, or plantings, follow Article 304 (Parking), Article 300 (site regs), and Article 303 (landscaping) — these are common inputs to design review.

(First natural mention of "ADUs" appears next: ADU rules are separate; see Porterville ADUs and California ADU law.)

Risks & Ambiguities

Plain-English summary

Porterville does not use a single "design review board" in Title 17; instead design control is embedded in district rules (especially downtown and PD districts), overlay submittal lists (for example HZ), and the Project Review / Zoning Administrator procedures that review discretionary and large projects. For downtown projects follow the Downtown Design Guidelines; for planned developments follow the approved PD Plan; and for projects meeting the PRC thresholds expect a multi‑department design/technical review. Always confirm parcel-specific standards with the Community Development / Zoning Administrator.

Source References

• Title 17, Article 202 — Downtown districts, Table 202.03 and Supplemental Regulations (§ 202.03–202.04)
• Title 17, Article 207 — Planned Development, including § 207.11: Development Plan Review
• Title 17, Article 300 & Article 303 — General site regulations, screening, building projections, landscaping (§ 300.01; § 300.10; § 303.04–303.05)
• Title 17, Article 501 — Hillside (HZ) overlay applicability and required plans (§ 501.02–501.03)
• Title 17, Article 600 — Common procedures, Zoning Administrator, Project Review Committee (§ 600.03–600.05; § 601 series)
• Title 17, § 101.02 — Official zoning map and district list (district names used above)

Internal navigation (linked earlier in the page): Porterville Development Standards, Porterville Parking, Porterville Overlay Districts, Porterville ADUs, Porterville Zoning & Planning overview. External reference for construction standards: California Building Standards Code (Title 24). (Links embedded in text above.)

Retrieved passages

• Porterville Zoning Code Medium relevance show source text
• Porterville Zoning Code Medium relevance show source text
• Porterville Zoning Code (Article 304) Medium relevance show source text
• Porterville Zoning Code (chapter and) Medium relevance show source text
• Porterville Zoning Code (article 402) Medium relevance show source text
• Porterville Zoning Code (ARTICLE 207.) Medium relevance show source text
• CBC § 65450 (Section 65450.) Medium relevance show source text
• Porterville Zoning Code (chapter and) Medium relevance show source text
• Porterville Zoning Code (Chapter 304) Medium relevance show source text
• Porterville Zoning Code (ARTICLE 202.) Medium relevance show source text
• CBC § 300.10 Medium relevance show source text
• Porterville Zoning Code (section 300.01) Medium relevance show source text
• Porterville Zoning Code (chapter shall) Medium relevance show source text
• Porterville Zoning Code (Section 300.01) Medium relevance show source text
• Porterville Zoning Code (chapter and) Medium relevance show source text
• Porterville Zoning Code (Section numbers) Medium relevance show source text
• Porterville Zoning Code (Section 205.03) Medium relevance show source text
• Porterville Zoning Code (Section numbers) Medium relevance show source text
• Porterville Zoning Code (Section numbers) Medium relevance show source text
• Porterville Zoning Code (Section 301.21) Medium relevance show source text

Cited sections

• Title 17, Article 202 — Downtown districts, Table 202.03 and Supplemental Regulations (**§ 202.03–202.04**) (Title 17)
• Title 17, Article 207 — Planned Development, including **§ 207.11: Development Plan Review** (Title 17)
• Title 17, Article 300 & Article 303 — General site regulations, screening, building projections, landscaping (**§ 300.01; § 300.10; § 303.04–303.05**) (Title 17)
• Title 17, Article 501 — Hillside (HZ) overlay applicability and required plans (**§ 501.02–501.03**) (Title 17)
• Title 17, Article 600 — Common procedures, Zoning Administrator, Project Review Committee (**§ 600.03–600.05; § 601** series) (Title 17)
• Title 17, **§ 101.02** — Official zoning map and district list (district names used above) (Title 17)
• Porterville_ZoningCode.md
• 2025 California ADU handbook.md

• Official Porterville code library