Local zoning · Orinda
Orinda — Variances and Exceptions
Variances and Exceptions under the Orinda local zoning and planning code, with the controlling citations.
Last reviewed: July 2, 2026
Overview
This page explains how the City of Orinda handles variances and exceptions under Title 17 (Zoning). It summarizes what each permit type is for, who decides, the findings the decision‑maker must make, key code triggers and limits, and how the rules interact with district standards (setbacks, heights, parking, overlays, ADU rules, and design review). For procedure and decision‑maker roles see the Orinda Zoning overview linked below. (§ 17.32—17.33)
Note: this page strictly covers the Title 17 zoning/planning rules about Variances and Exceptions; building code (Title 24), permitting forms and ministerial reviews live elsewhere. For design and permit contexts referenced here see the city's pages on design review, parking, development standards, overlay districts, and ADUs. When this page mentions construction standards it links to the California Building Standards Code.
What Title 17 calls them, and the basic difference
Exception — a discretionary permit to deviate from quantitative development standards (setbacks, height, lot coverage, fences, certain parking and sign limits) to allow design flexibility for site constraints or to preserve neighborhood character. The city calls this a Chapter 17.32 Exception; the intent and general rules are established in § 17.32.1—§ 17.32.5.
Variance — a discretionary permit to modify a regulation of Title 17 when strict application would deprive a parcel of privileges enjoyed by nearby parcels because of special circumstances of the property (size, shape, topography, surroundings). The variance standards and limits are set out in § 17.33.1—§ 17.33.3.
Both are discretionary (require findings), both may carry conditions, and both are discouraged unless they meet the listed findings. (§ 17.32.4; § 17.33.2)
Who decides / basic procedure
The Zoning Administrator (or Planning Director delegate) hears and decides many exceptions and minor matters; the Planning Commission hears appeals and larger/permitted-by-commission matters. See the allocation of authority in § 17.40.3—§ 17.40.5.
An exception permit must be obtained prior to a building permit and, if the project is being reviewed by the Planning Commission, the Commission may issue the exception. § 17.32.3.
Variances require the findings listed in § 17.33.2 and are processed subject to the public‑notice/hearing rules in Chapter 17.42 (notice/hearing procedures referenced throughout Title 17). (§ 17.33.2)
Standards and findings — what the city requires (plain list)
Exception findings (each must be made): the strict application either (A) deprives the property of rights enjoyed by nearby identical district properties due to unique site characteristics, or (B) serves no land‑use planning purpose given no negative impacts to Orinda’s semi‑rural character; the exception must substantially comply with the district intent and—where affecting an existing structure—must not substantially increase nonconformity or must preserve an appropriate architectural/functional feature. § 17.32.4(A)–(C).
Exceptions for signs have a tailored sign proportionality standard. § 17.32.4(D).
Exceptions are conditioned to avoid granting special privileges inconsistent with surrounding properties. § 17.32.5.
Variance findings (all four required): (1) special circumstances (size/shape/topography/location/surroundings) causing deprivation of privileges, (2) no special privilege not generally available, (3) variance substantially complies with zoning district intent (i.e., does not authorize an otherwise prohibited use), and (4) if open‑space rules are varied, no conflict with general plan open‑space policies. § 17.33.2(A)(1)–(4).
Parking variances in the downtown districts (DC and DO) may allow payment of an in‑lieu fee instead of providing spaces, subject to special findings under Government Code § 65906.5; the fee schedule is by City Council resolution. § 17.33.2(B).
Small project exemptions: certain small renovations, attic/basement conversions and small additions are exempt from needing a variance for preexisting nonconformities. § 17.33.2(C).
Quick comparison table — Exception vs Variance (decision‑relevant)
| Topic | Exception (Ch. 17.32) | Variance (Ch. 17.33) | Code Reference |
|---|---|---|---|
| Primary purpose | Deviate quantitative standards for design flexibility (setbacks, height, coverage, signs, some parking) | Relieve strict application where special property circumstances cause unique hardship (size/shape/topography/etc.) | § 17.32.1—17.32.5; § 17.33.1—17.33.3 |
| Findings required | Site constraints/no adverse impacts; district intent compliance; not increase nonconformity for existing structures | Four specific findings including special circumstances and no special privilege | § 17.32.4; § 17.33.2 |
| Decision maker | Zoning Administrator or Planning Commission (if tied to a Commission review) | Decision‑maker per Chapter 17 rules; Planning Commission commonly involved; appeals to Council | § 17.32.3; § 17.40.3 |
| Typical scope | Minor setback reductions, modest height or projection allowances, sign size, limited parking adjustments | Larger changes that alter dimensional standards where property features cause deprivation (e.g., narrow hillside lot) | § 17.32.2—17.32.5; § 17.33.2 |
| Conditions permitted | Yes — to avoid special privilege | Yes — conditions and limitations common; may be denied | § 17.32.5; § 17.33.3 (conditions) |
District‑by‑district breakdown (how variances/exceptions interact with each district)
Below are the actual Orinda district names used in Title 17. Each subsection lists the district purpose, typical permitted uses, the key dimensional standards you will see in the code, and where that district applies or is commonly used. When exceptions/variances are requested, decisionmakers evaluate compliance with the district intent set in the cited code and with the development standards in the schedules referenced.
Note: District development standards are summarized from Schedule 17.4.2 and related chapters; consult the zoning map for parcel‑specific districting (Planning Director determines uncertain map boundaries). § 17.1.7—17.1.8; Schedule 17.4.2.
RVL‑E (Resource/Very Low density—Environmental)
- Purpose: very low density resource/residential with large minimum lot sizes (environmental emphasis). § 17.4.2 / Schedule 17.4.2(A).
- Typical uses: very low density single‑family residential, open space/resource uses. § 17.4.2.
- Key dimensional standards: Prescribed Lot Area: 10 acres; Front Yard: 25 ft; Side Yard: 50 ft; Max Height 27 ft; aggregate building height and other controls per Schedule 17.4.2(A).
- Where it applies: large rural parcels and protected resource lands; variances are tightly judged against hillside/ridgeline rules (see overlays). § 17.7; § 17.5.
RVL (Resource/Very Low density)
- Purpose/uses/dimensions: similar to RVL‑E but with 5 acre minimum lot area and comparable setbacks/height controls in Schedule 17.4.2(A). § 17.4.2.
RL‑40, RL‑20, RL‑15, RL‑12, RL‑10, RL‑6 (Residential Low density series)
- Purpose: single‑family neighborhoods with varying minimum lot sizes (40,000 → 6,000 sq ft). Typical permitted use is single‑family residential; accessory dwellings per ADU rules. Schedule 17.4.2(A).
- Typical base setbacks and limits (examples from the Schedule): Front yard 20–25 ft, Side yards 5–50 ft depending on zone, Max Height 27 ft, Aggregate height allowances defined. See Schedule 17.4.2(A).
RM (Medium‑density Residential)
- Purpose: allow multifamily and moderate density residential development; Schedule 17.4.2(A) and Schedule 17.4.2(B) contain RM standards. § 17.4.2; Schedule 17.4.2(B).
- Typical uses: duplexes, small apartments, accessory units permitted; design review often applies. § 17.30.
- Key standards: Prescribed Lot Area often 20,000 sq ft; Front yard setbacks may be 15 ft for multifamily; Max building heights 27 ft/2½ stories typical; parking per Chapter 17.16. Schedule 17.4.2(B).
RH‑25 / RH‑40 (High‑density Residential overlays)
- Purpose: higher density multifamily options (25–40 du/ac) where the General Plan and overlays permit. Schedule 17.4.2(B).
- Uses: multifamily housing, senior housing (special rules apply — see special design review). § 17.30.11.
- Standards: minimum densities, specific building height/story limits (RH‑25: up to 3 stories/36 ft; RH‑40 up to 5 stories/50 ft) in the schedule. Schedule 17.4.2(B).
DC, DCOR, DG, DO (Downtown / Commercial / Office / Downtown General)
- Purpose: commercial downtown and office districts; encourage pedestrian, transit‑oriented uses and mixed commercial/residential forms downtown. Chapter 17.8.
- Uses: retail, restaurants, offices, limited residential above ground floor (subject to design review and downtown guidelines). § 17.30.10; 17.30.5.
- Standards: downtown design guidelines apply; parking variances (fee‑in‑lieu) are available in DC and DO under special findings. § 17.33.2(B).
PD (Planned Development)
- Purpose: site‑specific flexibility under an approved PD plan; deviations from base district regulations are allowed when the PD plan demonstrates compensating benefits. Chapter 17.12 (PD).
- Uses/dimensions: governed by the adopted PD plan; PD applications include findings about public services, utilities and consistency with general plan. § 17.12.
SP (Specific Plan)
- Purpose: apply a specific plan to an area where special planning solutions are needed; controls derive from the adopted specific plan. Chapter 17.13.
OS, PR, PS (Open Space / Park / Public & Semi‑Public)
- Purpose: parks, public facilities, open space and semi‑public uses. Development standards and the need for exceptions/variances follow specific use permit and design review rules. See Chapters 17.8 / 17.30 where those districts intersect design review requirements.
Overlay districts (Ridgeline/Environmental “-R” overlay, HD, SH, etc.)
- Purpose: overlays add site‑specific restrictions or heightened review (example: the -R overlay for ridgelines/environmental areas limits floor area and height and requires visual analysis). Overlays can be combined with any base district; exceptions/variances must be analyzed against overlay policies. § 17.5.1—17.5.4.
- Where they matter most: ridgelines, steep slopes, environmental preservation zones — requests to exceed overlay caps are reviewed under special design review and may still require exception/variance findings. § 17.5.4(B); § 17.30.7.
(If you need a parcel‑level district summary, verify the zoning map and the Planning Director’s district determinations — map boundary uncertainties are resolved by the Planning Director per § 17.1.8.)
How Exceptions & Variances interact with specific standards you care about
Setbacks & building projections: exceptions are the tool used to allow a building projection or setback reduction when the exception findings (unique lot shape/topography and no adverse impacts) are met. See § 17.32.2—17.32.4 and the dimensional tables in Schedule 17.4.2.
Water channel setbacks and riparian setbacks: building or grading inside channel setbacks is only allowed if the City Engineer approves and an exception under Chapter 17.32 is granted. § 17.4.6(C); see Chapter 17.32 for exception standards.
Design review interplay: many projects that request exceptions/variances still must clear design review standards; decision‑makers may impose adjustments as conditions of design review (e.g., changing height/setback in exchange for design mitigation). § 17.30.5; § 17.30.6.
ADUs: If an ADU cannot meet local quantitative ADU provisions, applicants may seek a variance but not an exception for ADUs (Title 17 expressly allows variances for ADUs, not exceptions). See § 17.3.4(F). ADUs also have ministerial state‑law timelines and limits; check the ADU chapter and state ADU law as needed. § 17.3.4.
Decision‑relevant examples (how findings look in practice)
Narrow hillside lot: an exception to reduce side yard setback for a garage swing entry may be supported by demonstrating lot width/shape constraints and no off‑site impacts; findings per § 17.32.4(A)–(C).
Downtown shop converting to a restaurant lacking required parking: a parking variance in DC/DO could be approved (fee‑in‑lieu) if it meets the special downtown findings in § 17.33.2(B).
ADU behind a nonconforming setback: ADU rules permit ministerial processing if state and local ADU criteria are met; if a local standard blocks the ADU and cannot be addressed under the ADU ministerial path, the owner may apply for a variance (not an exception) under § 17.33. § 17.3.4(F).
Checklist — what an applicant must satisfy (practical)
- Demonstrate the specific code basis for the requested deviation (cite the exact setback/height/coverage schedule) — see Schedule 17.4.2.
- For an exception, prepare written findings showing the unique site constraint or lack of planning purpose and show district intent compliance per § 17.32.4.
- For a variance, prepare evidence for all four variance findings in § 17.33.2(A)(1)–(4).
- If in the DC/DO downtown area and seeking parking relief, include transit access evidence and pay required in‑lieu fee resolution if approved (see § 17.33.2(B)).
- If in an overlay (e.g., -R ridgeline), include a visual analysis and comply with overlay submittal requirements; be prepared for special design review (§ 17.5; § 17.30.7).
- Confirm which decision‑maker will hear the application and prepare for public noticing/hearing rules (Ch. 17.42 and § 17.40 authority allocation).
- If the project triggers design review, coordinate exception/variance narratives to show how design mitigations offset the requested numeric relief (§ 17.30.5).
Risks & Ambiguities
| Issue | Why it matters | What to verify |
|---|---|---|
| Whether relief should be an exception or a variance | Different findings and legal standards; wrong path wastes time and may be denied. | Confirm code trigger: exceptions are for quantitative design flexibility (setbacks/coverage/signs); variances are for special property circumstance hardship. Cite § 17.32.2—17.32.4 and § 17.33.2. |
| Overlay rules (e.g., Ridgeline -R) | Overlays can impose stricter caps (floor area, height) and require visual analysis; even if you get an exception, overlay policy may block relief. | Verify applicable overlay on the parcel and the overlay submittal/visual analysis rules in § 17.5 and § 17.30.7. |
| ADU-specific limits and remedies | State ADU law interacts with local zoning; Title 17 allows variances for ADUs but not exceptions in some contexts. | Check § 17.3.4(F) and ministerial ADU timelines; confirm whether relief must be a variance. |
| Which decision‑maker has jurisdiction | Zoning Administrator vs Planning Commission changes public hearing and appeal pathway. | Confirm allocation under § 17.40.4—17.40.7 and whether the application is coupled to a Planning Commission review. |
| Parking in downtown (DC/DO) | Parking in‑lieu is discretionary and fee amounts set by Council resolution; fee and findings must be satisfied. | Verify fee schedule and make the special downtown findings required by § 17.33.2(B). |
| Parcel‑specific nonconformities and small project exemptions | Some small additions/renovations don’t require a variance; mischaracterizing the project can trigger unnecessary discretionary review. | Check § 17.33.2(C) for exemptions and the definitions in Chapter 17.2. |
Plain‑English summary
In Orinda, an exception is the route to ask to bend numeric rules (setbacks, some heights, coverage, sign size) when your lot shape, topography, or an existing structure makes strict compliance pointless or harmful; a variance is the stronger relief used when a parcel’s unique characteristics would otherwise be unfairly deprived of rights that nearby, similar parcels enjoy. Both require written findings and may carry conditions; downtown parking and ADU requests have special rules. See the code chapters 17.32 (Exceptions) and 17.33 (Variances) for the exact findings.
Source References
- Orinda Municipal Code — Exceptions (Title 17), § 17.32.1—17.32.5 (Intent, permit requirement, standards, conditions)
- Orinda Municipal Code — Variances (Title 17), § 17.33.1—17.33.3 (Intent, standards/findings, conditions)
- Orinda Municipal Code — Permit allocation and decision‑makers, § 17.40.3—17.40.7 (Planning Commission, Zoning Administrator, Planning Director)
- Orinda Municipal Code — Residential development standards and Schedule 17.4.2 (RVL, RL, RM, RH tables) § 17.4.2; Schedule 17.4.2.
- Orinda Municipal Code — Design review standards and special design review (Chapter 17.30, incl. § 17.30.5, 17.30.7)
- Orinda Municipal Code — Ridgeline / Environmental preservation overlay § 17.5.1—17.5.6.
- Orinda Municipal Code — ADU provisions and ADU/variance interplay § 17.3.4.
Internal reference pages (first natural mention links used in this page): Orinda Zoning, design review, parking, development standards, overlay districts, ADUs, California Building Standards Code.
Sources
Retrieved passages
- CFC § 2 (§ 2) High relevance
- Orinda Zoning Code (§ 2) High relevance
- Orinda Zoning Code (§ 4) High relevance
- CFC § 33 (§ 33) High relevance
- Orinda Zoning Code (Chapter 17.32.) Medium relevance
- Orinda Zoning Code (§ 2) Medium relevance
- Orinda Zoning Code (Section 65906.5) Medium relevance
- Orinda Zoning Code (§ 2) Medium relevance
- Orinda Zoning Code (Section 17.4.27) High relevance
- Orinda Zoning Code (Chapter 17.8) High relevance
- Orinda Zoning Code (Section 17.6.3) Medium relevance
- Orinda Zoning Code (Section 17.44.1.) Medium relevance
- Orinda Zoning Code (§ 33) Medium relevance
- Orinda Zoning Code (§ 7) Medium relevance
- Orinda Zoning Code (Chapter 17.43) Medium relevance
- Orinda Zoning Code (Section 17.30.8) Medium relevance
- Orinda Zoning Code (§ 33) Medium relevance
- Orinda Zoning Code (§ Exh.) Medium relevance
- Orinda Zoning Code (§ 2) Medium relevance
- Orinda Zoning Code (Section 17.4.2) Medium relevance
- Orinda Zoning Code (Section 17.22.4.) Medium relevance
- Orinda Zoning Code (§ 3) Medium relevance
- Orinda Zoning Code (§ 26) Medium relevance
- Orinda Zoning Code (§ 2) Medium relevance
- Orinda Zoning Code (section 17.33.2.) Medium relevance
- Orinda Zoning Code (Section 17.6.8) Medium relevance
Cited sections
- Orinda Municipal Code — Exceptions (Title 17), **§ 17.32.1—17.32.5** (Intent, permit requirement, standards, conditions) (Title 17)
- Orinda Municipal Code — Variances (Title 17), **§ 17.33.1—17.33.3** (Intent, standards/findings, conditions) (Title 17)
- Orinda Municipal Code — Permit allocation and decision‑makers, **§ 17.40.3—17.40.7** (Planning Commission, Zoning Administrator, Planning Director) (§ 17.40.3)
- Orinda Municipal Code — Residential development standards and Schedule 17.4.2 (RVL, RL, RM, RH tables) **§ 17.4.2; Schedule 17.4.2**. (§ 17.4.2)
- Orinda Municipal Code — Design review standards and special design review (Chapter 17.30, incl. § 17.30.5, 17.30.7) (Chapter 17.30)
- Orinda Municipal Code — Ridgeline / Environmental preservation overlay **§ 17.5.1—17.5.6**. (§ 17.5.1)
- Orinda Municipal Code — ADU provisions and ADU/variance interplay **§ 17.3.4**. (§ 17.3.4)
- Orinda_ZoningCode.md
Frequently asked questions
What is the difference between a variance and an exception in Orinda?
A variance relieves a property from a zoning regulation because of a special circumstance of the property (size/shape/topography) and requires the four findings listed in § 17.33.2(A)(1)—(4); an exception lets you deviate from quantitative development standards (setbacks, height, coverage, sign size) when site design flexibility is needed and must meet the standards of § 17.32.4.
Who decides exceptions and variances in Orinda?
The Zoning Administrator (Planning Director delegate) handles many exception matters; the Planning Commission hears larger items, appeals, and Commission‑level reviews. See the allocation of authority in § 17.40.3—17.40.7.
Can I get a reduction in setbacks for a narrow hillside lot?
Yes — if you meet the exception standards showing the lot’s unique size/shape/topography and no adverse impact to Orinda’s semi‑rural character and neighboring privacy/views; the relevant findings are in § 17.32.4(A)–(C). If hardship rises to the variance standard, a variance per § 17.33.2 is the alternative.
Do downtown businesses ever get relief from parking requirements?
For nonresidential uses in the DC and DO downtown districts, Orinda may allow a parking variance with payment of an in‑lieu fee if the special downtown findings are met; the rules and fee authority are in § 17.33.2(B).
If my lot lies in the Ridgeline/Environmental overlay, can I seek an exception?
Overlay districts like the -R overlay add stricter caps and require visual analysis; you can seek exception/variance relief, but the overlay rules and special design review requirements (visual analysis and floor‑area/height caps) apply and are found in § 17.5 and § 17.30.7.
Can I use an exception to approve an ADU that doesn't meet local ADU quantitative requirements?
Title 17 treats ADUs specially: when a proposed ADU doesn't meet local ADU provisions, the code allows seeking a variance under Chapter 17.33 but not an exception under Chapter 17.32 in the contexts described in § 17.3.4(F). Also watch state ADU timelines and ministerial paths.
What findings will the Planning Commission look for on a variance application?
They will require the four findings in § 17.33.2(A): special circumstances of the property, no grant of special privilege, substantial compliance with district intent (no unauthorized use), and (if open space is affected) no conflict with general plan open‑space policies.
Are small additions exempt from needing a variance for a preexisting nonconformity?
Yes — certain small renovations, attic/basement conversions and small home additions are exempt from requiring a variance for existing nonconformities; see the exemptions in § 17.33.2(C) and the definitions in Chapter 17.2.
Do design review standards replace the need for variance/exception findings?
No. Design review assesses visual and contextual design standards (Chapter 17.30); decisionmakers may still require findings for an exception or variance and may tie adjustments as conditions of design review. See § 17.30.5 and the interaction in § 17.32.4.
If I get a variance, does it run with the land?
Variances are discretionary permits and may carry conditions; whether they "run with the land" depends on the specific decision and conditions. Reasonable accommodations (a different permit type) are personal in some cases and do not run with the land unless physically integrated — see § 17.46.5 for reasonable accommodations. For variances, review the decision language and conditions.
More in Orinda code
Ask about any Orinda property
Get a cited, plain-English answer on Orinda zoning, setbacks, FAR, ADUs and permits — for any address.
Start Free Trial