Local zoning · Arvin

Arvin — Design Review

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

Last reviewed: July 3, 2026

Overview

Arvin’s code treats "design review" primarily as part of its site development permit and multiple‑family residential design review processes: site layout, building appearance and structural design are explicit review factors under the site development permit rules, while multi‑family projects have a stand‑alone objective design review chapter. For practical project planning you must track three places in the code: the general administrative/appeals rules in § 17.05, the site development permit rules in § 17.60, and the Multiple Family Residential Design Review rules in § 17.72 (and the ministerial multiple‑family permit rules in § 17.055).

Note: this page links you to Arvin pages for related topics as they appear in the code: the page uses the city’s zoning landing for "design review", and links for practical topics such as parking, development standards, overlay districts, ADUs, and the California Building Standards Code where building‑code compliance is ultimately confirmed.


How Arvin’s code handles Design / Architectural / Site Plan Review (quick map)

  • Review authority and appeals: city planner (administrative), planning commission, city council — appeals and de novo reviews are handled under § 17.05.
  • Site development permits: triggers, application contents, and review criteria are in § 17.60.030–040. Review explicitly considers building appearance and structural design.
  • Multiple‑family projects: objective design standards and ministerial review pathway are in § 17.72 and § 17.055; ministerial approvals that meet the objective standards are permitted and have their own completeness/timing rules.

District‑by‑district breakdown (where design review most commonly applies)

Note: each district subsection below summarizes the district purpose, typical permitted uses that commonly trigger design review, key dimensional/development standards (as used by planners when reviewing design), and where design review authority lives in the code.

R‑2 — R‑2 (Two‑family dwelling zone)

  • Purpose / common uses: small multi‑family and duplex housing (two‑unit). See applicability and permitted residential uses in § 17.12 and § 17.10 references for R‑2 standards.
  • Typical dimensional standards used in design review: minimum side yards 5 ft (10 ft on street side of corners), minimum rear yard 5 ft, lot coverage ≤ 50%, and minimum lot size and width (e.g., min lot width 45 ft, min lot area 2,700 sq ft where updated). See § 17.10.050–080 for the standards that govern building placement and separation the planner enforces during review.
  • Where design review applies: multi‑family design features are checked against the general site development permit and multiple‑family rules where applicable; if the proposal is a two‑unit change requiring site improvements it will be reviewed under § 17.60 and the planner’s findings in § 17.05.

R‑3 — R‑3 (Limited multiple‑family)

  • Purpose / common uses: multiple‑family residential at moderate densities (minimum/maximum units per acre spelled out in the chapter). Multiple‑family development proposed in R‑3 is tracked against the Multiple Family Design Review standards in § 17.72 and the ministerial pathway § 17.055 when objective standards are met.
  • Dimensional standards used by reviewers: density bands (e.g., minimum/maximum units per acre listed in the R‑3 chapter), setbacks, lot coverage, and building separation; these base standards are applied by reference in § 17.72.030.A.

R‑4 — R‑4 (Multiple‑family)

  • Purpose / common uses: higher density multi‑family (R‑4 allows 3–5 stories in some cases); multi‑family projects in R‑4 must comply with § 17.72 or obtain a site development permit if they don’t meet the objective standards. Height limit example: 5 stories / 50 ft in R‑4. Front yard minimum 10 ft in R‑4. See § 17.14.030–040 for these dimensional controls.

PUD — Planned Unit Development (PUD) (17.45)

  • Purpose: flexible, master‑planned mixed uses where the planning commission adopts project‑specific standards; design review is integral to master plan approval. PUDs require detailed master and specific plans and are reviewed by the planning commission and council; design guidelines and standards are adopted as part of the PUD approval. See § 17.45.010–030.

PF — PF (Public Facilities)

  • Purpose / uses: parks, libraries, governmental and public service facilities. The PF district requires internal design coordination — the city manager or designated staff shall advise the council of proposed public facility design and development under § 17.38.030. Project design for public facilities is therefore subject to a different internal review step rather than the standard private site development permit.

OS / A‑2 / commercial and other districts

  • OS (Open Space), A‑2 (Agricultural), neighborhood commercial (N‑C), and commercial zones each have their own permitted uses and may require site development permits for new buildings; when site improvements are required the planner evaluates building appearance and integration with surroundings per § 17.60.040 and the district standards (e.g., neighborhood commercial design standards in § 17.46.x or specific sections of Part 2). See the district chapters (e.g., § 17.37 for OS, § 17.36 for A‑2) for permitted uses and cross‑reference to site development review rules.

Key code standards & decision triggers (table)

Topic What the planner/commission looks at Code reference
Site development permit triggers & review criteria When new development or expansions require site improvements; review must consider site layout, building appearance/structural design, landscaping, utilities, drainage, fire protection, access and parking. § 17.60.030–040
Multiple‑family objective design review Multi‑family buildings (and residential component of mixed‑use) must meet objective standards in § 17.72; meeting those standards enables ministerial review under § 17.055. § 17.72.010–030, § 17.055.020–040
Application submittal contents Scaled site plans, elevations (N/S/E/W), floor plans, landscape plans, parking layout, ingress/egress, signs, lighting, utility/trash locations, will‑serve letters, Kern County Fire clearance. § 17.60.030, § 17.055.020, § 17.05.020
Timelines — completeness & decision Planner determines completeness within 30 working days for certain multiple‑family ministerial applications; planner issues decision in 45 days (site dev and multiple‑family ministerial review timelines appear in § 17.055.020 and § 17.60.040). § 17.055.020.B–C, § 17.60.040.A
Appeals Planner decisions are appealable to the planning commission (file within 15 calendar days) and then to city council as provided in § 17.05.050–060. § 17.05.050–060
Architectural style controls Some districts impose style controls (for example, code language directing Mediterranean or approved architectural styles as a standard to be applied to facades and materials); these are enforced during design review. See provisions referencing building design and design standards in § 17.70.010 and district design subsections (examples in the code). Verify with the planning department.

Notable objective details the planner will use in design review

  • Façade & materials: minimum number of architectural elements, permitted cladding (stucco, concrete siding, stone, wood, composite) and limits on color counts for street‑facing elevations; planners require at least three architectural elements on street facades in some multiple‑family guidelines. See design elements list in § 17.72.x.
  • Fenestration: minimum 30% of street‑facing façades must be windows/entries/balconies in multiple‑family standards; windows must be recessed or trimmed for visual appeal. § 17.72 contains these objective measures.
  • Open space / amenities: minimum 150 sq ft of open space per unit (can be a mix of private patios and common areas); patios counted must be usable and at least 75 sq ft.
  • Landscaping: minimum 10% of developed area landscaped for multi‑family projects; interior parking planters and tree spacing rules apply.

Checklist — what to include in your design review / site development application

  • Scaled site plan, full plot plan and vicinity map (three paper prints + electronic) — § 17.60.030 / § 17.055.020.
  • Elevations (north/south/east/west), floor plans and roof forms — § 17.055.020.
  • Landscape plan and irrigation details (automatic irrigation for planters where required) — § 17.055.020 / § 17.72 landscaping.
  • Parking plan showing stalls, circulation, ADA and bicycle parking — parking rules + § 17.60.030 and multiple‑family parking cross‑references.
  • Lighting plan, photometrics, and hooding details — § 17.60.030.
  • Trash/storage, loading and utility locations with screening details — § 17.60.030 and district screening rules.
  • Will‑serve letter from Arvin Community Services District and Kern County Fire clearance where required — § 17.60.030.
  • Materials and color schedule (show architectural elements, cladding materials, and fenestration ratios) — § 17.72 objective elements; include elevation callouts.
  • Proof of fees paid; if ministerial multiple‑family route claimed, include checklist demonstrating compliance with the objective standards in § 17.72 so planner can treat the application as ministerial under § 17.055.040.

Risks & Ambiguities

Issue Why it matters What to verify
Ministerial vs discretionary review Meeting objective standards lets a multifamily project be ministerial (faster, CEQA exemption may apply); missing an objective standard converts the project to discretionary review and public hearings. Verify whether your specific design fully complies with the § 17.72 objective standards and whether you qualify under § 17.055.
Completeness / timing Planner completeness and decision clocks (30/45 days) are statutory but depend on a truly complete submittal; missing items delay review. Confirm planner completeness determination under § 17.055.020.B–C and § 17.60.040.
District style mandates (e.g., "Mediterranean") Some district subsections require a particular architectural character; that can force material or elevation changes during review. Check the district chapter that applies to your site (see language referencing building design in § 17.70.010 and district subsections); if unclear, verify with the planning director.
Conflicts between PUD/project standards and base zones PUD approvals adopt project‑specific development standards — these supersede base standards where applicable, but the PUD must be consistent with the general plan. For PUDs, inspect the adopted PUD standards in § 17.45 and adopted exhibits; confirm which standards control.
CEQA treatment for ministerial multifamily The code states ministerial multifamily approvals meeting objective standards are CEQA‑exempt by reference to CEQA Guideline §15268; but project specifics (e.g., related offsite improvements) may still trigger review. Confirm applicability of § 17.055.060 and coordinate early with the planner and CEQA lead agency.

Plain‑English summary

If you are building or changing a multi‑family building or any project that needs site improvements in Arvin, expect the planner to check your site plan, elevations, landscaping, parking, lighting, utility and trash details against the city’s site development rules (§ 17.60) and the multiple‑family design standards (§ 17.72). Provide full scaled plans, a will‑serve letter and fire clearance, meet the objective design standards if you want the faster ministerial route, and be prepared to appeal if the planner’s decision is adverse.


Source References

  • Arvin Municipal Code — Administrative approval, findings, appeals: § 17.05.030–070.
  • Arvin Municipal Code — Site development permits and application contents: § 17.60.020–040 and § 17.60.030 (application information).
  • Arvin Municipal Code — Multiple Family Residential Design Review: § 17.72.010–030 (objective design standards).
  • Arvin Municipal Code — Multiple Family Residential Design Review ministerial permit: § 17.055.020–060 (application, timing, ministerial findings, CEQA exemption).
  • Arvin Municipal Code — District standards and PUD rules: § 17.10 (R‑2), § 17.12 (R‑3), § 17.14 (R‑4); § 17.45 (PUD); § 17.38 (PF).
  • Arvin Municipal Code — Design elements, façade, fenestration, open space and landscaping metrics used in multi‑family review (design guidelines embedded in the multiple‑family and targeted design sections). See the design elements and facade requirements referenced in § 17.72.x and related design subsections.

Sources

Retrieved passages

  • Arvin Zoning Code (chapter 17.72) Medium relevance
  • Arvin Zoning Code (chapter 17.055) Medium relevance
  • Arvin Zoning Code (chapter 17.72) Medium relevance
  • Arvin Zoning Code (chapter 17.72) Medium relevance
  • Arvin Zoning Code (§2) Medium relevance
  • Arvin Zoning Code (§3) Medium relevance
  • Arvin Zoning Code (chapter 17.60) Medium relevance
  • Arvin Zoning Code (§2) Medium relevance
  • Arvin Zoning Code (Title 17) Medium relevance
  • Arvin Zoning Code (section L) Medium relevance
  • Arvin Zoning Code (section L) Medium relevance
  • Arvin Zoning Code (§ 3) Medium relevance
  • Arvin Zoning Code (Title 17) Medium relevance
  • Arvin Zoning Code (section 17.05.080) Medium relevance

Cited sections

Frequently asked questions

Do I need design review in Arvin for a new duplex on my lot?

If the duplex requires site improvements or is a multi‑family structure it will be reviewed against the site development permit rules in § 17.60 and the multiple‑family design review standards if applicable; two‑unit projects in R‑2 will trigger the planner’s checklist items (site plan, elevations, landscaping) and could be subject to administrative approval under § 17.05. Verify with the planner whether your project qualifies as an administrative approval or requires a site development permit.

What are the key submittal plans the city will require for design review?

Arvin requires scaled site plans, plot plans, elevations (N/S/E/W), floor plans, landscape plans, parking layout, access/driveway details, signs, lighting/photometrics, and utility/trash locations; ministerial multifamily applications list the same detailed items in § 17.055.020 and § 17.60.030.

What triggers a site development permit (and design review) in Arvin?

New development that requires site improvements, new structures over 1,000 sq ft, expansions over 50% in many cases, or changes of use requiring site improvements will trigger a site development permit; the level of review (planner, commission, council) is spelled out in § 17.60.040.C.

Can a multifamily project be approved ministerially (no public hearing)?

Yes — if the project fully meets the objective multiple‑family residential development standards in § 17.72, it can be reviewed ministerially under § 17.055; the planner’s decision is then ministerial provided the listed criteria are met. Check the completeness and the specific objective standards carefully.

What style or material rules should I expect during design review?

The code includes objective design elements (façade materials lists, minimum architectural elements, fenestration percentages, and open space/landscape percentages) used by the planner during review; some district subsections reference an architectural character (example language directing a Mediterranean or approved style). Always confirm with the planning director which district‑level style rules apply to your parcel.

How long does the planner have to decide on a complete design review application?

For multiple‑family ministerial applications the planner’s completeness determination and decision timelines are described in § 17.055.020 (completeness within 30 working days; decision within 45 days after acceptance of a complete application). Site development permit reviews similarly use a 45‑day planner review window in § 17.60.040.

If the planner denies my design review, how do I appeal?

Planner decisions are appealable to the planning commission (file within 15 calendar days) under § 17.05.050; the commission reviews the administrative permit de novo and may affirm, modify, or reverse the planner’s decision; further appeals to council follow code notice procedures.

Are ministerial multifamily approvals exempt from CEQA?

The code states that multiple family projects approved ministerially under the objective standards are considered ministerial and are exempt from environmental review pursuant to CEQA Guidelines § 15268 in § 17.055.060, but always verify project‑specific circumstances with the planner (offsite improvements or cumulative impacts can change CEQA treatment).

More in Arvin code

Ask about any Arvin property

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

Start Free Trial

More Arvin zoning topics