Local zoning · Goleta

Goleta — Variances and Exceptions

Variances and Exceptions under the Goleta local zoning and planning code, with the controlling citations.

Last reviewed: July 2, 2026

Overview

Variances and related exceptions in Goleta live in Title 17 (the Zoning Ordinance). A Variance lets a property owner seek relief from specific dimensional or development regulations where strict application would cause undue hardship; it cannot be used to allow a use that is otherwise prohibited (§ 17.60.010 – § 17.60.020) . Other paths for limited departures include Adjustments to development standards as part of Development Plans (§ 17.59.040) and Adjustments/Waivers based on takings claims (§ 17.28.100) . Variances require findings and a public hearing (Zoning Administrator or higher) and generally expire after five years if not exercised (§ 17.60.030, § 17.60.040, § 17.60.050) .

This page explains the code rules (what the Review Authority must find), how the variance/exception tools differ, how they interact with district standards (so you can assess prospects by zone), and practical checklists for applicants. It links to related city topics — the rules interact with the city's zoning & planning overview, Goleta Zoning (Title 17), development standards, parking, design review, overlay districts, ADUs, and the California Building Standards Code.

What the Code Requires — mechanics and findings

Purpose and scope
- Variances are intended to relieve practical difficulties caused by unique property characteristics (size, shape, topography, etc.): § 17.60.010 .
- Variances apply to all zone districts but may not be used to permit a use otherwise prohibited in the zone: § 17.60.020 .
Review process and limits
- The Review Authority (Zoning Administrator or higher if combined with another discretionary review) holds a public hearing to decide a Variance: § 17.60.030 .
- Variances expire five years after they become effective unless substantial construction occurs or a time extension is granted: § 17.60.050 .
Findings required (all must be made)
- The Review Authority must find: (1) the variance does not conflict with the intent of Title 17 or the General Plan; (2) special circumstances apply to the property (size, shape, topography, location, surroundings); (3) strict application would deprive the property of privileges enjoyed by similar properties in the zone; and (4) the variance does not grant special privileges inconsistent with nearby properties. For Coastal properties, a conformity finding with the Coastal Act is added: § 17.60.040 .
Adjustments versus Variances
- As part of a Development Plan (a different approval type), the city allows Adjustments to a confined list of development standards (maximum residential density, height, lot coverage, buildings separation, setbacks, parking, landscaping, screening). To approve an adjustment the Review Authority must find the adjustment is justified and consistent with General Plan intent; deviations to height or lot coverage must be approved by Planning Commission resolution: § 17.59.040 .
Takings-based Waivers / Adjustments
- The city has a written process for an applicant to request an Adjustment or Waiver on constitutional takings grounds; the applicant bears the evidentiary burden and the City must make a written decision within 90 days (appealable): § 17.28.100 .
Modifications (minor, different track)
- The Planning Commission/Zoning Administrator can grant Modifications for minor deviations (setback reductions, parking layout, sign area, limited height/lot coverage increases) with specific findings that the modification is needed due to property physical characteristics and will produce a design or resource protection benefit: § 17.62.040, §17.24.040 and related tables .

District-by-district analysis (how Variances interact with each zone)

Variances are available in every district, but the practical prospect depends on the district’s purpose, permitted uses, and dimensional standards that applicants ask relief from. Below are the primary base districts where variance requests are common; each subsection lists the district purpose, typical allowed uses, key dimensional standards that are often the subject of requests, and where each zone applies or special rules to check.

Note: the city's TABLE 17.07.030 and land use tables provide the authoritative development and use rules for each district; see the citations after each district description for the controlling code reference .

RS (Single‑Unit Residential) — RS

Purpose: Reserve for single‑unit dwellings and accessory structures; preserve lower‑density neighborhood character (TABLE 17.07.030 and land use rules) .
Typical permitted uses: One primary dwelling and accessory uses (home occupations, small family day care, animal keeping) — see TABLE 17.07.020 .
Key dimensional standards often at issue: minimum lot area (varies by RS subzone: RS‑43.6, RS‑20, RS‑12, RS‑10, RS‑8, RS‑7), maximum height 25 ft, front yard setback 20 ft, rear 25 ft, interior side variable (10% of lot width; min 5 ft); lot coverage limits and accessory structure rules (max 800 sq ft for accessory structures in many cases) — see § 17.07.030 and accessory rules § 17.24.030–17.24.040 .
Where it applies: City single‑family neighborhoods per the Zoning Map; RS setbacks and allowed projections are in § 17.24.040 and TABLE 17.07.030 .

RP (Planned Residential) — RP

Purpose: Medium‑density multiple dwelling residential with planned development flexibility (see TABLE 17.07.030) .
Typical permitted uses: Multiple‑unit dwellings (subject to density limits), supportive public uses, accessory uses (home occupations), limited conditional uses per TABLE 17.07.020 .
Key standards commonly varianced: maximum density (13 du/acre), max height 35 ft, lot coverage 30%, setbacks 20 ft front / 10 ft side / 10 ft rear (see TABLE 17.07.030) — variances or Development Plan adjustments are the typical routes for deviations .

RM (Medium‑Density Residential) — RM

Purpose: Higher density housing (multifamily), often near services and transit; similar uses to RP but higher base density (up to 20 du/acre) .
Typical permitted uses: Multifamily apartments, accessory uses, some public uses — see land use table § 17.07.020 .
Key standards: 35 ft height, parking standards per Chapter 17.38 (applicants commonly request parking modifications), lot coverage 30%, front 20 ft, side 10 ft, rear 10 ft; transitional height rules apply next to RS (§ 17.07.050) .

RH (High‑Density Residential) — RH

Purpose: Highest base residential density in the City; supports more intensive housing and special‑needs housing where appropriate (§ 17.07.050 for special needs density allowances) .
Typical uses: Multifamily residential, some community services; accessory uses as listed in TABLE 17.07.020 .
Key standards: max density 30 du/acre, max height 35 ft, lot coverage 50%, typical setbacks (front 20 ft, side 10 ft, rear 10 ft). Variance requests for density/height/coverage in RH require careful General Plan consistency findings and sometimes Planning Commission review .

RMHP (Mobile Home Park) — RMHP

Purpose: Land designated for manufactured/mobile home parks; tailored setbacks, coverage and minimum lot size (TABLE 17.07.030) .
Typical uses: Mobile home sites, accessory uses to support parks. Standards include minimum lot area 4,000 sq ft, max lot coverage 75%, max height 25 ft, and special perimeter setback rules; Variances are rare but possible for site layout constraints .

C (Commercial) — C

Purpose: Non‑residential uses serving neighborhood to regional needs; tables for permitted commercial uses are in Part II land use tables (see TABLE 17.07.020 and Part II) .
Typical permitted uses: Retail, offices, services, limited non‑residential structures under 5,000 sq ft for ministerial review in some cases; parking, signs, and frontage treatments are frequent sources of variance/modification requests (see Chapter 17.38 for parking and Chapter 17.24 for setbacks and projections) .
Key standards: Height, lot coverage, parking minimums (Chapter 17.38), and frontage/setback rules (including Old Town frontage zero‑setback rules in the -OTH Overlay) are the most relevant targets for variance or modification .

AG (Agricultural) — AG

Purpose: Preserve agricultural production and related accessory uses; some large‑format development exceptions apply (TABLE 17.07.030) .
Typical permitted uses: Farming, greenhouses, agricultural processing under limits. Development standards typically include large setbacks and special buffers; variances typically focus on siting of farm structures, setbacks from waterways, or development in floodplains (see Chapter 17.31, Floodplain Management) .

If your parcel is also inside a Specific Plan or an overlay (for example, the -OTH Old Town Heritage Overlay with its Hollister Avenue zero‑setback rule), the Specific Plan/overlay can control or change what standards apply; always check the overlay rules before assuming which standard the variance targets — see § 17.20.020 and the -OTH rules (§ 17.19.040) .

Quick reference table — decision‑relevant code points

Topic	What it controls / allowed relief	Code Reference
Variance purpose / applicability	Variances for practical hardship; cannot permit prohibited uses; apply to all districts	§ 17.60.010, § 17.60.020
Variance required findings	Four mandatory findings (consistency, special circumstances, deprivation, no special privilege); Coastal Act finding if applicable	§ 17.60.040
Review authority / public hearing	Zoning Administrator or higher (PC/CC when concurrent)	§ 17.60.030
Adjustments (Dev Plan)	Allow targeted adjustments to density, height, lot coverage, setbacks, parking, landscaping, screening; additional finding required	§ 17.59.040
Takings-based waiver / adjustment	Procedure and 90‑day written decision for constitutional takings claims; developer bears burden	§ 17.28.100
Time limits	Variance or Development Plan approvals generally expire after 5 years if not acted upon	§ 17.60.050, § 17.59.050
District dimensional standards	Minimum lot area, setbacks, height, lot coverage per zone (TABLE 17.07.030) — frequent variance targets	TABLE 17.07.030 / § 17.07.030

Checklist — what an applicant must demonstrate (documents and findings)

Identify the exact code standard you seek relief from (cite the district rule in TABLE 17.07.030 or the applicable overlay/Special Plan) and explain how the request fits within Title 17 — Verify with the jurisdiction (see § 17.07.030) .
Narrative demonstrating special circumstances of the parcel (size, shape, topography, location, surroundings) with photographs and site plan — supports § 17.60.040(2) .
Analysis showing strict application would deprive the parcel of privileges enjoyed by similar properties in the zone (comparables) — supports § 17.60.040(3) .
Consistency memo with the General Plan and Title 17 objectives — supports § 17.60.040(1) .
For Coastal Zone parcels, a Coastal Act consistency exhibit/analysis — § 17.60.040(B) .
Site plans, elevations, and a shaded massing diagram showing minimum‑necessary relief and mitigation measures (to show the variance is the least relief needed).
Parking and loading exhibit when parking standards are at issue; coordinate with parking rules and Chapter 17.38 — § 17.59.040 when requesting adjustments to parking .
If claiming a takings adjustment/waiver, submit legal evidence and facts at application intake per § 17.28.100 (City requires substantial evidence from the applicant) .
Payment of fees and, if within a Specific Plan area, any required Specific Plan submittals — see § 17.20.020 for Specific Plan applicability .
Expect design review if the project is subject to discretionary design requirements (check design review rules); some ministerial housing tracks narrow design review to objective standards only (§ 17.59.030–040) .

Risks & Ambiguities

Issue	Why it matters	What to verify
Variance cannot legalize a prohibited use	A variance may relax development standards but cannot permit a use not allowed in the zone (e.g., a commercial use in RS)	Check the land use table (TABLE 17.07.020) and confirm the use is permitted or conditionally allowed — § 17.60.020(B)
Coastal Zone overlay	Additional Coastal Act finding is mandatory; the Coastal Commission/Local Coastal Program may add requirements	Confirm Coastal Zone status and prepare Coastal Act consistency analysis — § 17.60.040(B)
Specific Plans / Overlays controlling	Where a Specific Plan or overlay is in effect it may supersede Title 17 standards	Check whether the parcel sits inside an adopted Specific Plan or overlay (e.g., -OTH) — § 17.20.020 and § 17.19.040
ADU and ministerial housing tracks	State ADU law and ministerial housing programs may limit what discretionary relief the City can require or deny	Verify whether the project qualifies for ministerial review or ADU streamlined rules; discretionary variances may be inappropriate — see § 17.59.0xx and ADU standards § 17.41.030 (Not all intersections fully described in retrieved materials; Verify with the jurisdiction)
Takings waiver evidentiary burden	The city requires the developer to present substantial evidence for a waiver/adjustment claim; failure to meet that burden risks denial	Prepare legal analysis and documentation at application time per § 17.28.100
Time limits	Approvals lapse (typically 5 years) if not exercised	Confirm timelines and request Time Extension if construction will not be underway within the period — § 17.60.050, § 17.59.050

Plain‑English summary

If a dimensional rule (setback, height, lot coverage, parking, etc.) on your Goleta property would make reasonable development impossible because of your lot’s shape, size or topography, you can apply for a Variance — but the city will only grant it if you prove the situation is special, the relief is minimal, it won’t conflict with the General Plan or give you a special privilege, and coastal properties must also meet Coastal Act consistency (§ 17.60.040) . If the change is limited (for example, an adjustment to height, lot coverage or parking within a Development Plan) the city’s Adjustment path may be quicker but has its own required finding (§ 17.59.040) .

Source References

Title 17, Zoning — introductory provisions and organization: § 17.01.010–§ 17.01.030
Chapter 17.60, VARIANCES — Purpose, Applicability, Review Authority, Findings, Time Limit: § 17.60.010, § 17.60.020, § 17.60.030, § 17.60.040, § 17.60.050
Chapter 17.59 — Development Plans, Required Findings and Adjustments to Development Standards: § 17.59.030, § 17.59.040, § 17.59.050
Chapter 17.28 — Adjustments and Waivers (takings procedure): § 17.28.100 (application, evidence, 90‑day decision)
Chapter 17.62 — Modifications and required findings: § 17.62.040 (modification findings)
Development regulations and dimensional/table references — TABLE 17.07.030 and § 17.07.030 (Residential district standards and the development regulations table)
Land use regulations table — TABLE 17.07.020 (Allowed uses by residential district)
Old Town Heritage (-OTH) Overlay and Hollister frontage zero setback rule: § 17.19.040
Floodplain management & setbacks (where floodplain siting issues arise): Chapter 17.31 and § 17.31.030 (development standards) — Not all variance interactions here are fully enumerated in the retrieved snippets; verify for specific floodplain variance needs

Sources

Retrieved passages

Goleta Zoning Code (Title apply) High relevance
Goleta Zoning Code (§ 17.59.030.) High relevance
Goleta Zoning Code (chapter apply) High relevance
Goleta Zoning Code (section by) High relevance
Goleta Zoning Code (§ 17.60.040.) High relevance
Goleta Zoning Code (§ 6) High relevance
Goleta Zoning Code (§ 17.59.050.) High relevance
CBC § G107 (SECTION G107) High relevance
Goleta Zoning Code Medium relevance
Goleta Zoning Code (§ 6) Medium relevance
CBC § 6 (Title 15) Medium relevance
Goleta Zoning Code (Title or) Medium relevance
Goleta Zoning Code (§ 6) Medium relevance
Goleta Zoning Code Medium relevance
Goleta Zoning Code (Title must) Medium relevance

Cited sections

Official Goleta code library

Frequently asked questions

What is a Variance in Goleta and when should I use one?

A Variance is discretionary relief from a specific development regulation (setback, height, coverage, etc.) when strict application would impose an undue hardship because of special property circumstances. Use it when you cannot meet an objective development standard for reasons tied to the parcel’s physical characteristics; a variance cannot be used to allow a use that’s prohibited in the zone (§ 17.60.010–§ 17.60.020) .

What findings does the City require to approve a Variance?

All four findings must be made: (1) consistency with Title 17/General Plan, (2) special circumstances of the property, (3) strict enforcement would deprive the property of privileges like nearby similar parcels, and (4) no granting of special privileges; Coastal properties also need Coastal Act consistency (§ 17.60.040) .

Can a Variance change the allowed uses on my R‑1/RS lot?

No. The code expressly forbids granting a Variance to allow a use not otherwise permitted in the zone; Variances only modify regulations on land, buildings, and structures, not land‑use permissibility (§ 17.60.020(B)) .

How does an Adjustment (Development Plan) differ from a Variance?

An Adjustment is requested as part of a Development Plan and can modify a limited list of standards (density, height, lot coverage, separation, setbacks, parking, landscaping, screening); the Review Authority must find the adjustment is justified and consistent with General Plan intent. Height/lot coverage deviations require a Planning Commission resolution (§ 17.59.040) .

If my lot is in the Old Town Heritage overlay, does that change how I request relief?

Yes — overlays and Specific Plans can change baseline standards (for example the -OTH overlay has a zero Hollister front setback under § 17.19.040) and may impose different design review rules; check the overlay/Special Plan rules before filing to know which standards you must variate from (§ 17.19.040, § 17.20.020) .

Can I seek a waiver because strict compliance would be a constitutional taking?

Yes. The City has a takings adjustment/waiver procedure; the developer must submit substantial evidence with the project application and the City must issue a written decision within 90 days (appealable to Council and then to court) (§ 17.28.100) .

If I need a setback reduction of more than 20% is that possible?

Setback reductions are handled through Modifications/Adjustments, but the code caps some reductions (e.g., total setback area not reduced by more than 20% in certain contexts) and sets absolute minimums (e.g., front setback not less than 16.5 ft, side not less than 5 ft, rear not less than 15 ft) — review § 17.24.040 and modification rules; some relief may instead require a full Variance (§ 17.24.040, § 17.62.040) .

How long does a Variance last if approved?

A Variance generally expires five years after its effective date unless substantial physical construction has been completed or a time extension has been requested and granted (§ 17.60.050) .

Do Variances affect parking requirements?

Yes — Variances or Modifications/Adjustments can address parking quantity, design, or location, but bicycle parking minimums cannot be reduced and compact‑space allowances are capped; adjustments to parking as part of a Development Plan require the adjustment finding in § 17.59.040 and parking rules in Chapter 17.38 apply (§ 17.59.040, Chapter 17.38) .

Can I combine a Variance with another entitlement?

Yes — but if the Variance is processed concurrently with an action that requires Planning Commission or City Council review, the higher authority must hear the Variance; concurrent processing can change the Review Authority and public hearing requirements (§ 17.60.030) .

Ask about any Goleta property

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

Start Free Trial