Local zoning · Shafter

Shafter — Design Review

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

Last reviewed: July 2, 2026

Overview

Shafter’s Design Review rules live in the City’s development code under § 2.80 and require aesthetic and site-planning review before most residential and commercial building permits are issued. The purpose is to avoid adverse visual or site-planning impacts, to promote compatibility with the General Plan and the code’s design criteria, and to ensure coordinated review for larger land‑use tools such as P.U.D. and specific plans. See the code for the controlling language at § 2.80 . (Practical: read the checklist below before preparing plans.)

This page explains what the Shafter code requires for design review, how decisions are made, how design standards are applied district-by-district where the code ties them to review, and the most important procedural and submittal items to avoid delay. Where the local Development Code does not state a parcel‑specific rule, the page tells you what could not be confirmed and to “Verify with the jurisdiction.”

Note: design review is a zoning/planning procedure — it is separate from work-permit technical compliance under the California Building Standards Code (Title 24).

Important related topics mentioned in the code: parking, development standards (setbacks, lot coverage, height), overlay districts, ADUs, landscaping and screening, and signage. Use these pages when you see design conditions tying into those standards.


What the ordinance requires (high‑level)

  • Design review is required before issuance of a building permit for residential or commercial development: “No building permit … shall be issued until the proposed development has received … design review approval” — § 2.80.2 .
  • Authority: the Planning Director reviews most design review applications and may approve/deny and impose conditions; the Planning Commission reviews projects that otherwise require Commission approval and may also act on design review (appeals permitted) — § 2.80.3–4 .
  • Approval findings and conditions may address open space, screening/buffering, fences/walls, landscaping, access/ circulation, signs, grading, phasing, and other measures necessary for compatibility — § 2.80.3–4 .
  • The code sets out general design criteria that all proposals must demonstrate (compatibility with surrounding development, respect for views and scale, materials/architectural coherence, lighting standards, screening of service areas, etc.) — § 2.80.5 .
  • Residential subdivisions have additional, prescriptive design expectations (variety of elevations, minimum house sizes for some large subdivisions, roof material guidance, landscape/tree requirements, etc.) and a numeric table describing minimum numbers of floor plans/elevations (Table 2.B) — § 2.80.6 and Table 2.B .
  • Planned Unit Developments and Specific Plan approvals explicitly rely on design review submittal requirements: preliminary and final development plans must include the information required for design review (referenced to Section 2.80) and final plans are processed under the same design review procedures — P.U.D. rules referencing Section 2.80 and .

District‑by‑district breakdown (how design review interacts with common Shafter districts)

This subsection lists the districts the Code references in the context of design review or site-specific development plans. For each district, I give the code‑stated purpose and typical uses where the ordinance states them and then identify whether the design review rules add district‑specific requirements. If a specific dimensional standard (front setback, lot coverage, height) is not present in the retrieved design-review material, I note that and tell you to verify.

R-1 (Single‑Family Residential)

  • Purpose / typical uses: single‑family dwellings and accessory uses; when combined with P.U.D. the P.U.D. may layer special standards (see P.U.D.) .
  • Design‑review interaction: residential building permits are subject to design review before issuing a permit per § 2.80.2; residential subdivision design criteria (variety of elevations, front/side yard landscaping, roof material standards, minimum house size rules in some subdivisions) apply under § 2.80.6 and Table 2.B .
  • Key dimensional standards: Not found in retrieved materials for exact R‑1 setbacks/coverage/height in the design‑review text — verify with the City’s Development Standards.

R-2 / R-3 (Two‑Family / Multi‑Family Residential)

  • Purpose / typical uses: multi‑family housing and duplexes; the code treats multifamily in the design criteria (landscaping, screening, stepping back taller structures to reduce massing) — § 2.80.5 .
  • Design‑review interaction: screening of trash enclosures, loading, mechanical equipment, and outdoor storage must be addressed in design review for multifamily developments — § 2.80.5(9)(c) .
  • Key dimensional standards: Not found in retrieved materials for precise R‑2/R‑3 numeric setbacks and lot coverage within the design‑review text — verify with Development Standards.

P.U.D. (Planned Unit Development)

  • Purpose / typical uses: permits mixed residential/commercial/amenity uses as part of a unified plan; the P.U.D. can be exclusive or a combining overlay with base zones such as R‑1/R‑2/R‑3 (example map symbol R‑2/P.U.D.) — P.U.D. purpose and uses listed in Chapter 3 .
  • Design‑review interaction: P.U.D. applications must include a preliminary development plan that “shall include all the information as required for design review pursuant to Section 2.80.” Final development plans are processed the same as design review (Planning Director review unless Commission requires otherwise) — P.U.D. subsections referencing § 2.80 .
  • Key dimensional standards: The P.U.D. section allows the Planning Commission/Council to require deviations or special standards (heights, coverage, parking ratios, access improvements, landscaping) as conditions in a final plan — see P.U.D. latitude of regulations and required findings .

CF (Community Facilities)

  • Purpose / typical uses: public/quasi‑public/institutional uses (schools, municipal facilities, parks) — CF district purpose language is in Chapter 3 .
  • Design‑review interaction: any new buildings or major alterations in CF that are “development” would be subject to the general design review requirement if they are residential or commercial in nature or otherwise trigger a building permit, because § 2.80.2 ties design review to building permits for development works; verify project‑type applicability with staff for institutional projects .
  • Key dimensional standards: Not found in retrieved materials in the design‑review text — verify with Shafter Zoning.

BP / C (Business Park / Commercial)

  • Purpose / typical uses: business park and commercial uses; the design criteria explicitly mention commercial areas (lighting to encourage pedestrian use, screening of service areas) — § 2.80.5 .
  • Design‑review interaction: Commercial developments require design review before a building permit and will be reviewed for circulation, parking layout (see parking), signage, lighting, and screening as part of conditions — § 2.80.2–5 .
  • Key dimensional standards: Not found in retrieved materials for numeric commercial setbacks/coverage in the design‑review portions — verify with Development Standards.

Specific Plan District

  • Purpose / typical uses: large‑scale, coordinated development subject to a Specific Plan; Specific Plan approvals are processed with design review elements and the Specific Plan becomes part of the zoning regulations — Specific Plan District language and relation to design review is in Chapter 15 and the PUD/Specific Plan cross references to Section 2.80 .
  • Design‑review interaction: Specific Plans require submission of development plans and these are handled under the same design review procedures; the City may impose lot‑specific standards by the Specific Plan or through design review on final development plans — verify Specific Plan maps/standards for parcel‑level requirements .

Quick reference table — most decision‑relevant design‑review rules

Topic / trigger What the code requires Code Reference
Design review required before permit No building permit for residential or commercial development until design review approval § 2.80.2
Decision authority Planning Director may approve/deny; Planning Commission reviews projects requiring Commission action and may hear design review; appeals per appeals rules § 2.80.3–4
Basic design criteria Compatibility with General Plan and Title 17; scale, materials, setbacks, view corridors, landscaping, lighting, screening of service areas § 2.80.5
Residential subdivision specifics Variety of elevations and house footprints; minimum house sizes in some subdivisions; roof material standards; Table 2.B for elevation/floor plan rules § 2.80.6 and Table 2.B
P.U.D. / Final plan process Preliminary/final P.U.D. plans must include design review information; final development plan processed same as design review P.U.D. rules referencing Section 2.80
Screening and service area treatment Trash enclosures, loading, mech. equipment must be screened in multifamily/commercial developments § 2.80.5(9)(c)

Checklist (what an applicant must satisfy for Design Review)

  • Prepare complete architectural elevations (all exterior wall elevations) and materials/finishes consistent with the design criteria — § 2.80.5(9)(a–b) .
  • Provide site plan showing building setbacks, parking layout, circulation, access points, and landscape/irrigation — design review references parking/landscape expectations and P.U.D. submittal requirements that refer to Section 2.80 .
  • Show screening for trash enclosures, loading docks, mechanical equipment, and outdoor storage so they are not visible from public streets — § 2.80.5(9)(c) .
  • Demonstrate how the project meets the general design criteria (compatibility, view corridors, stepping back tall elements, lighting controls, landscape buffering) — § 2.80.5 .
  • For residential subdivisions: include floor‑plan/elevation variety per Table 2.B and plans for tree/landscape installation and irrigation (front and street side yards) where applicable — § 2.80.6 and Table 2.B .
  • If the project is in a P.U.D. or Specific Plan area, include the preliminary/final development plan materials required and anticipate additional conditions or deviations imposed through the P.U.D./Specific Plan process — P.U.D. references § 2.80 .
  • If proposing lighting, signage, or right‑of‑way changes, include specifications consistent with the code’s lighting and sign expectations so Planning can make required findings — § 2.80.5 and related chapters (sign standards) .
  • Expect to receive conditions addressing open space, phasing, erosion control, and bonds if the Commission or Director finds them necessary — § 2.80.3–4 .

If you are submitting an ADU: review the State ADU rules that constrain local discretionary review; the local code does not override state ADU limitations — see ADUs and State ADU guidance .


Risks & Ambiguities

Issue Why it matters What to verify
Exact numeric setbacks, heights, lot coverage by district Design review requires showing compliance, but the design‑review text does not list district numeric standards Numeric dimensional standards not found in the retrieved design‑review excerpts — Verify with the City’s Development Standards
Which small projects are exempt from design review The ordinance references exemptions in § 2.80.6.e but text for each exemption is not fully in the retrieved materials The exemption list is “Not found in retrieved materials” — Verify with the Planning Department
ADUs and discretionary review State law limits discretionary review of ADUs; local design‑review requirements cannot conflict with state ADU constraints Local code interaction with State ADU law: city code references design review generally but ADU-specific limits are governed by state law — See State ADU guidance
P.U.D. latitude of standards P.U.D. and Specific Plan processes can add or relax standards; this creates project‑specific differences Confirm which P.U.D./Specific Plan map and development plan apply to a parcel — P.U.D. language references § 2.80 and grants latitude to Planning Commission/Council
Procedural timing (when design review must be completed relative to building permit) Code says no building permit until design review approval, but concurrent processing may be possible for some permit types The ordinance is explicit: § 2.80.2 requires design review approval before building permit for residential/commercial — verify whether ministerial permits (e.g., some ADUs) are processed differently due to state law

Plain‑English Summary

If you are building or altering a house, apartment, or commercial building in Shafter, you normally must get design review approval before the building permit — the Planning Director usually handles routine cases and the Planning Commission handles larger/discretionary projects. The code lays out compatibility, landscaping, screening, and architectural‑treatment requirements and requires extra submittal detail for subdivisions and P.U.D.s; check the City’s development standards and any P.U.D./Specific Plan that applies to your parcel to learn the exact numeric setbacks or any special rules. See § 2.80 for the controlling design‑review rules .


Source References

  • City of Shafter Development Code — Design Review (Chapter heading and full-purpose statement and subparts): § 2.80 .
  • Design criteria and specifics (compatibility, setbacks/stepping back tall elements, lighting, screening): § 2.80.5 .
  • Planning Director and Planning Commission authority, conditions and findings: § 2.80.3–4 .
  • Residential subdivision design standards and Table 2.B (floor plans/elevations): § 2.80.6 and Table 2.B .
  • P.U.D. requirements referencing design review, submittal contents, and final plan processing: P.U.D. Chapter (preliminary/final plan and design review references) .
  • Screening and service area criteria for multifamily/commercial: § 2.80.5(9)(c) .
  • State ADU guidance summarizing limits on local discretionary review: California ADU handbook / State law (for interaction with local design review) .
  • California Building Code (for building‑permit technical compliance separate from design review): 2025 California Building Code excerpts (reference only) .

Sources

Retrieved passages

  • Shafter Zoning Code (Section 2.90.) High relevance
  • Shafter Zoning Code (Title 17) High relevance
  • Shafter Zoning Code (CHAPTER 11) High relevance
  • Shafter Zoning Code (Section 2.80.) High relevance
  • Shafter Zoning Code (Section 2.180) High relevance
  • Shafter Zoning Code (CHAPTER 2) High relevance
  • Shafter Zoning Code (CHAPTER 2) High relevance
  • CEC § 11.85 (Section 11.85) High relevance

Cited sections

Frequently asked questions

Do I always need design review in Shafter before a building permit?

Generally yes for residential and commercial development: the code states “No building permit for residential or commercial development shall be issued until the proposed development has received … design review approval” — § 2.80.2 . Verify narrow exemptions (the ordinance references some exemptions in § 2.80.6.e but those specifics were not fully present in the retrieved excerpts — Verify with the City).

Who makes the decision on a design review application?

The Planning Director is authorized to approve or deny design review applications and impose conditions; the Planning Commission reviews projects that require Commission approval or when the Director refers a matter to the Commission — § 2.80.3–4 .

What kinds of design elements will the City evaluate?

Shafter evaluates architectural compatibility, siting and massing (stepping tall elements back), materials and finishes, view corridors, landscape buffering, lighting standards, and screening for trash and mechanical equipment — summarized in § 2.80.5 .

Does design review impose numeric setbacks or height limits?

Design review enforces compatibility and requires plans to show setbacks and height, but the design‑review chapter does not itself list the numeric setbacks/heights by district — those numeric standards live in the City’s development standards and zone tables. The design review chapter therefore requires compliance with those standards but does not replace them — check the Development Standards and the applicable zone for exact numbers (Not found in the retrieved design‑review excerpts) .

How does design review interact with a P.U.D. or Specific Plan?

P.U.D. and Specific Plan applications must include the information required for design review (the preliminary development plan “shall include all the information as required for design review pursuant to Section 2.80”), and final development plans are processed the same as design review — see the P.U.D. provisions referencing Section 2.80 .

Are ADUs subject to design review in Shafter?

The local code’s design review rules apply to residential development generally; however, State ADU law limits local discretionary review of ADUs in many cases. The City may have implementing ADU rules in its zoning/ADU chapter, but you should cross‑check local ADU procedures with state ADU requirements — see the State ADU guidance and the City ADU page ADUs (state ADU constraints summarized in guidance) .

What exactly must be in my submittal?

The code ties development plan and P.U.D. submittals to the information required by design review and requires architectural elevations, landscape plans, and other site information; residential subdivisions must submit materials per Table 2.B (floor plans/elevations rules) — see § 2.80 and Table 2.B for the submittal expectations .

Can the Planning Commission require deviations from the zoning code through design review?

For P.U.D.s and final development plans, the Planning Commission or City Council may require standards more or less restrictive than other code provisions as conditions of approval (height, bulk, coverage, parking, access, landscaping, etc.) — P.U.D. latitude of regulations and required findings explain this (see P.U.D. chapters referencing design review) .

Will lighting and signs be reviewed under design review?

Yes. The design criteria address lighting fixtures, lighting intensity (no nuisance glare), and festive/ pedestrian lighting in commercial areas; sign and lighting conditions may be imposed as conditions of design review approval — § 2.80.5 .

If the Planning Director approves my design review, can that be appealed?

Yes — the code authorizes conditions and permit decisions by the Director or Commission that are subject to the City’s appeal procedures (appeal references are in the design review and permits chapters) — see § 2.80.3–4 and the appeals procedures referenced in the Chapter (appeals procedure references appear with Planning Commission authority) .

More in Shafter code

Ask about any Shafter property

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

Start Free Trial

More Shafter zoning topics