Arvin Zoning, Planning & Building Codes

Last reviewed: July 4, 2026

Overview

Arvin’s land-use and zoning rules are codified in Title 17 (Zoning) of the Arvin Municipal Code and are organized as a chaptered zoning ordinance covering zone districts, overlay districts, site development and design rules, administrative permits, and procedures for variances, conditional uses and planned unit developments. The code defines a discrete set of zone districts (residential, commercial, industrial, agricultural, public and overlays) and then places citywide standards, permit paths, and specialized review chapters alongside district-specific development standards. The ordinance assigns primary application review roles to the city planner, planning commission, and city council, and ties building‑permit issuance to planner clearances for approved land‑use approvals. § 17.06.010 • § 17.05.070 .

---

How Arvin's code is organized

• Title and chapter structure: Zoning material appears under Title 17, broken into chapters for zones (e.g., chapters beginning with 17.06 and zone-specific chapters such as 17.10, 17.12, 17.14), and separate chapters for PUDs, parking, signage, conditional uses, variances, and site development standards. See § 17.06.010 (zones established) and the chapters referenced throughout the code. § 17.06.010 .
• Procedural chapters: Administrative approvals and building‑permit clearances are handled in chapter 17.05 (uses permitted subject to administrative approval) and require planner clearances before a building permit or certificate of occupancy. § 17.05.070 and § 17.05.080 .
• Discretionary review and remedies: Conditional use permits are controlled by chapter 17.56, variances and modifications by chapter 17.54, and site development permits and standards by chapters referenced throughout (example cross‑references appear in chapters 17.60 and 17.70). § 17.56.025 • § 17.54.050 .

---

Zoning district families

Arvin explicitly lists the municipal zoning districts (the code’s canonical district names appear in the zones chapter). The city’s zone families include (bold = code name as used in the ordinance):

• R-1 (Single‑family dwelling zone) — § 17.06.010
• R-2 (Two‑family dwelling zone) — detailed standards such as 15 ft front setback, 5 ft side yards, 5 ft rear yard, 50% lot coverage, minimum lot 2,700 sq ft are in § 17.10.040–17.10.080 .
• R-3 (Limited multiple family) — see chapter for specific uses and standards § 17.12 (referenced throughout the code) .
• R-4 (Multiple family) — maximum 5 stories / 50 ft height and 10 ft front yard minimum are set in § 17.14.030–17.14.040 .
• R‑S (Suburban residential) and multiple E‑1–E‑5 (Estate) zones — enumerated in § 17.06.010 .
• Commercial family: C-O, N-C, C-1, C-2 — listed in § 17.06.010 .
• Industrial family: M-1, M-2, M-3 — listed in § 17.06.010 .
• Other: A-1, A-2 (agriculture), OS (open space), PF (public facility), SZ (school zone), PUD (planned unit development), and the pedestrian mixed‑use overlay MUO. § 17.06.010 .

Practical note: the code frequently defers detailed numeric standards (setbacks, lot coverage, heights) to the individual zone chapters (for example, R-2 standards in chapter 17.10) or to site development standards chapters; always check the zone chapter that applies to your parcel. § 17.10.030–17.10.080 .

---

Citywide development standards

High‑level framing and where to find the numbers:

• Where the numbers live: baseline dimensional controls (setbacks, heights, lot coverage, minimum lot sizes) are expressed within each zone chapter (example: R‑2 standards § 17.10.040–17.10.080, R‑4 height & front yard § 17.14.030–17.14.040) and supplemental rules such as site development standards appear in chapters cross‑referenced from those zone chapters. § 17.10.040–17.10.080 • § 17.14.030–17.14.040 .
• Setbacks and lot coverage examples: R‑2 front setback 15 ft, side 5 ft, rear 5 ft, lot coverage 50% — § 17.10.040–17.10.070 . R‑4 front yard 10 ft, max height 50 ft / 5 stories — § 17.14.040 and § 17.14.030 .
• Parking: Off‑street parking requirements are administered by the city’s parking chapter (see Arvin Parking); many zone chapters direct applicants to the parking chapter — for example, the school zone references compliance with chapter 17.48 for parking (§ 17.42.060) and multiple other zones cross‑reference chapter 17.48 for parking standards. § 17.42.060 .
• Lot sizes and densities: Minimum lot area rules (for example R‑2 minimum lot 2,700 sq ft) and density rules appear in each residential zone chapter; planned developments may use the general plan’s density guidance and PUD provisions to depart from standard lot sizes where consistent with the general plan. § 17.10.080 • § 17.45.040 .
• Design and materials: Multiple‑family design standards (façade materials, articulation, color counts) are given in the multiple‑family design chapter and may be applied objectively for ministerial review for projects that meet the chapter’s objective standards. See § 17.72.020–17.72.030 and the multiple‑family design chapter for details (linked below). § 17.72.020–17.72.030 .

Link: the city’s high‑level development standards and dimensional rules are summarized in Arvin Development Standards.

---

Specific plans & overlays

• Planned Unit Development (PUD) is a discrete district with its own purpose, application steps and standards in chapter 17.45; PUDs must be at least 1 acre, require a preliminary and a master plan, and mapping onto the official zoning map when approved. See § 17.45.010, § 17.45.030, and § 17.45.140. § 17.45.010 • § 17.45.030 • § 17.45.140 .
• Overlay districts: the code lists a pedestrian‑oriented mixed‑use overlay MUO and other overlays; overlay application and standards are handled where the overlay is adopted and by the underlying zone rules as cross‑referenced. See the zones list § 17.06.010 for overlay names. § 17.06.010 . More on overlays at Arvin Overlay Districts.
• Area/specific plans: the municipal code and the city’s general plan/spatial framework (e.g., South Arvin/Sycamore‑Meyer framework guidance cited in the code) are used to determine residential densities and design guidance for target sites under specific plans. See the South Arvin design guidance excerpts and the PUD nexus provisions § 17.45.040 and related policies. § 17.45.040 • planning guidance excerpts § 17.06 / framework .

---

Building permits & review

• Typical permit paths: the code separates ministerial (administrative) approvals, objective design review, and discretionary approvals.
  • Administrative permits and ministerial administrative approvals are processed by the city planner under chapter 17.05; some smaller additions and accessory uses are eligible for administrative approval and must conform to site development standards. § 17.05.080 and § 17.05.070 .
  • Site development permits and discretionary permits (including conditional use permits) follow chapters 17.60 (site development permit) and 17.56 (conditional use permits). Conditional use permits require the findings in § 17.56.025. § 17.56.025 .
  • Variances and permitted modifications are handled in chapter 17.54; modest modifications (up to 5% of setback or lot area) may be allowed by modification procedures in § 17.54.050. § 17.54.050 .
• Design review & objective design standards: the multiple‑family design review chapter (17.72) establishes objective standards so qualifying multi‑family projects can be reviewed on an objective/ministerial basis; projects that meet those objective standards are processed under the administrative pathway noted in chapter 17.055. See § 17.72.010–17.72.030 and § 17.055.070 for permit‑to‑building clearances. § 17.72.010 • § 17.055.070 . See Arvin Design Review.
• Clearances before building permits: the building division must obtain written clearance from the city planner that a proposed building conforms with the administrative or design approval before issuing a building permit or certificate of occupancy. § 17.05.070 and § 17.055.070 .
• Timeframes and hearing bodies: the planning commission is the primary hearing body for most discretionary approvals; some actions can be appealed to the city council. PUD preliminary review has a 60‑day review window for the planning commission (§ 17.45.070) and the specific development plan decision is expected within 60 days (§ 17.45.150.C). § 17.45.070 • § 17.45.150.C .

---

State housing law in Arvin

Summary and what the municipal code shows (what is present vs. what is missing):

• SB‑qualified objective review: the city’s multiple‑family design review chapter explicitly includes projects that meet Senate Bill 35 eligibility among the project types addressed by that chapter’s objective standards; the chapter expressly applies to projects meeting SB35 rules. § 17.72.010 .
• Building code interactions: the zoning code defers to the California Building Code for certain technical standards (for example, building separation references the California Building Code). See the multiple‑family chapter’s cross‑reference to the state building code for separation rules. § 17.72.030 . See California Building Standards Code.
• ADU / JADU: the municipal code text provided in the retrieved materials does not contain a clear, dedicated ADU/JADU chapter or specific local numeric ADU rules in the snippets reviewed. I could not find an Arvin ADU chapter in the retrieved file excerpts. Not found in retrieved materials — verify with the city planning department and the local ADU page Arvin ADUs and the state ADU rules California ADU law.
• SB 9, density bonus, rent rules: the ordinance excerpts explicitly tie certain procedures to SB35‑eligible projects (see § 17.72.010), but I did not find a local implementation chapter for SB 9 lot‑splits or a local density bonus ordinance in the provided excerpts. Local rent regulation (rent control) is not apparent in the retrieved materials. Not found in retrieved materials — verify with the city clerk/planning department and the state's housing law summaries California housing laws. § 17.72.010 .

Practical guidance: because Arvin’s code cross‑references the state building code and SB35 within its multiple‑family chapter, projects that rely on state housing streamlining should coordinate early with city planning to confirm which local objective standards apply and whether the project meets the objective standard lists in chapter 17.72. § 17.72.020–17.72.030 .

---

Quick practical orientation (how to navigate a project)

1. Identify the parcel’s zone on the official map (official map on file at the city clerk) and read the corresponding zone chapter for numeric standards: § 17.06.020 and the relevant zone chapter (e.g., § 17.10 for R‑2) .
2. Confirm applicable overlays (e.g., MUO) and special zones such as SZ (school zone) whose standards (height, front/side yards) are spelled out in their chapter § 17.42 .
3. Determine if your project is ministerial (administrative approval per chapter 17.05), subject to objective multiple‑family design review (17.72), or requires discretionary review (CUP, site development permit, variance). § 17.05.080 • § 17.72.010 • § 17.56.025 .
4. Confirm parking requirements in chapter 17.48 (many zone chapters point to chapter 17.48); consult Arvin Parking. § 17.42.060 .
5. Submit application to the city planner (forms per chapter 17.45, 17.05 or the applicable chapter), expect planner review and required clearances before the building permit is issued; the building division will require written planner clearance. § 17.05.070 and § 17.055.070 .

---

Information Gaps (what to verify with Arvin planning)

• Local ADU / JADU ordinance text (specific numeric ADU standards, owner‑occupancy, parking waivers, etc.) — Not found in the retrieved code excerpts; check the city’s ADU page or planning counter. Not found in retrieved materials. See Arvin ADUs.
• Local implementation of SB 9 lot‑splits and objective ministerial procedures for two‑unit development — Not clearly present in the retrieved excerpts; confirm with city staff. Not found in retrieved materials. See California housing laws.
• A local density bonus ordinance or implementation details tied to state density bonus law was not located in the retrieved excerpts — verify. Not found in retrieved materials.
• Full text of parking chapter 17.48, signage chapter 17.62, site development standards 17.70, and site development permit chapter 17.60 (the code references these but the numerical tables and fine print should be read in the full code). See Arvin Parking and Arvin Signage.

---

Source References

• Arvin Municipal Code (Title 17 — Zoning), zones list and zone chapters (e.g., § 17.06.010 listing zones).
• Planned Unit Development chapter § 17.45.010–17.45.150.
• School zone development standards (height, yards) and parking cross‑reference § 17.42.050–17.42.070 and § 17.42.060.
• Multiple‑family design review (objective standards and SB35 cross‑reference) § 17.72.010–17.72.030.
• Administrative approvals and building‑permit clearances § 17.05.070–17.05.080 and building permit clearance for multi‑family § 17.055.070.
• Variance/modification procedures § 17.54.050–17.54.060 and conditional use permit findings § 17.56.025.