Local zoning · Arroyo Grande

Arroyo Grande — Variances and Exceptions

Q: What is the difference between a variance and a minor exception in Arroyo Grande?

A variance is a discretionary, public‑hearing approval by the Planning Commission that can adjust standards such as setbacks, height, coverage and parking; it requires the findings in § 16.16.070 . A minor exception is an administrative Minor Use Permit granted by the Community Development Director (no public hearing) for limited adjustments—examples include up to 10% setback or coverage changes, +2 ft fence height, or small parking waivers—under § 16.16.100 .

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

Ask a question free See coverage

Last reviewed: July 3, 2026

Overview

This page explains how the City of Arroyo Grande allows departures from strict zoning and subdivision rules through variances, minor exceptions, and other adjustments under the City’s Development Code (commonly called Title 16). It summarizes who decides, what findings must be made, where the rules are used (including floodplain and subdivision exceptions), and how the major mixed‑use and residential districts interact with variance/exception requests. The controlling variance rules are at § 16.16.070 and the minor/administrative exceptions are at § 16.16.100.

Note: this page sticks only to what the Arroyo Grande Development Code says about variances, exceptions, adjustments, waivers and the required findings. For building-code (Title 24) issues, see the California Building Standards Code.

Key rules (short)

Formal, discretionary variances come to the Planning Commission and are governed by § 16.16.070 (authority, submittal requirements, and required findings).
Administrative minor exceptions (no public hearing) are available from the Community Development Director for a limited list of items (e.g., modest fence height increases, small setback reductions, lot coverage, height increases and limited parking waivers) under § 16.16.100.
Subdivision/land‑division exceptions (design/improvement standards) are handled under § 16.20.050; the Planning Commission may grant exceptions for site constraints.
Floodplain variances follow the city’s flood chapter and require special findings and applicant notification (flood insurance consequences). See the flood provisions in the Development Code (flood variance criteria and findings).
Density‑bonus related waivers/modifications for affordable housing follow Chapter 16.82 and state law (Government Code § 65915). The Planning Commission hears those waiver/modification requests.

Because many decisions hinge on district standards (setbacks, height, coverage, parking), applicants should review the district tables in Chapter 16.36 and the city’s Development Standards and Parking pages early in the process.

How the rules work (plain process)

Variance application and fee; public hearing before the Planning Commission; resolution with findings and conditions required. § 16.16.070
Minor exception requests use a Minor Use Permit (administrative) with notice to neighbors (300 ft) and appeal rights; findings closely mirror the variance findings but are administrative and limited in scope. § 16.16.100
Subdivision exceptions (e.g., improvement design or lot layout departures) are requested with tentative maps and decided by the Planning Commission per § 16.20.050.

When parking standards are implicated, the code requires an additional finding that the variance will not cause parking on public streets to interfere with traffic; see Chapter 16.56 and the parking waiver language in § 16.16.070 and § 16.16.100.

Also check the city’s Design Review, Overlay Districts and Historic Preservation pages if your property is in a design or historic overlay, since overlays can affect what will be approved.

District-by-district implications for variances and exceptions

Below are the districts called out in the Development Code (Chapter 16.36). For each district I list the district name (bolded), the purpose, typical permitted uses, key dimensional standards applicants most often ask variances about, and where it generally applies. All district standards come from the Chapter 16.36 tables referenced in the Code.

Note: where you see references to setbacks, height, lot coverage, or parking, consult the city’s Development Standards and Parking pages for the full numeric regime and any overlay exceptions.

TMU — Traffic Way Mixed Use

Purpose: accommodate vehicle sales/services, retail, offices, visitor‑serving uses and limited live/work residential at the southern gateway.
Typical permitted uses: auto sales/service, repair, equipment rental, offices, motels, restaurants, limited residential/live‑work.
Common dimensional standards that drive variance requests: Minimum lot size 10,000 sf, front setback 0–15 ft, side setback 0 ft (20 ft where abutting residential), max height 30 ft (36 ft possible via CUP), site coverage up to 75%, FAR .75. Applicants commonly request variances for setbacks, height, or coverage.

VMU — Village Mixed Use

Purpose: small‑scale pedestrian‑oriented mix of commercial and residential near the village core.
Typical uses: single & multi‑family, specialty retail, professional offices, services, neighborhood markets.
Key standards: minimum lot size 5,000 sf, front setback 0–15 ft, max height 30 ft/3 stories (36 ft by MUP), FCD: coverage up to 100%, FAR = 1. Setback and height variances are common.

VCD — Village Core Downtown

Purpose: downtown combination of commercial, office, and upper‑story residential to promote pedestrian activity and preserve historic character.
Typical uses: second‑story residential, small retail, offices, restaurants (no drive‑through).
Standards: similar to VMU (tight setbacks 0–15 ft, max height 30 ft, high coverage allowed). Variances that affect the historic character may trigger Historic Preservation review.

GMU — Gateway Mixed Use

Purpose: mixed retail, office and multi‑family near E. Grand Avenue; encourages intensified mixed‑use projects.
Typical uses: financial institutions, retail, offices, multi‑family residences.
Standards: min lot 20,000 sf, min lot width 100 ft, front setback 0–10 ft, height up to 35 ft (40 ft by discretionary action). Variances often requested for height and setback transitions where projects abut residential districts.

FOMU — Fair Oaks Mixed Use

Purpose & uses: a larger mixed‑use area emphasizing home‑improvement retail, restaurants, offices and multi‑family; see Table 16.36.020(F). Applicants often request parking, setback, and coverage adjustments.

Residential districts — RR, RS, SF, MF, MFA

Purpose and uses: rural, single‑family, and multi‑family residential zones with rules governing front/side/rear setbacks, lot coverage, height, and parking. The code explicitly applies the viewshed/minor use permit review to RR, RS, SF (and some MF) for second‑story additions. See § 16.16.110 for viewshed/minor use permit details.
Typical standards that trigger variance or minor exception requests: modest setback reductions (administrative up to 10% under § 16.16.100), accessory structure height, and lot coverage increases (administrative up to 10%).

(If your parcel sits in a design overlay or historic overlay, consult Overlay Districts and Historic Preservation early — these overlays change how variances and minor exceptions are assessed.)

Decision‑relevant standards and permit types (quick reference table)

Permit / Rule	What it can adjust	How decided	Code Reference
Variance (discretionary)	Setbacks, height, coverage, parking, signs, etc.	Planning Commission (public hearing)	§ 16.16.070
Minor exception / Minor use permit (administrative)	Fence height (+2 ft), residential setback reduction (≤10%), lot coverage (≤10% increase), height (≤10% increase), parking waivers	Community Development Director (no public hearing; 300 ft notice; appealable)	§ 16.16.100
Subdivision / land division exceptions	Improvement design, street layout, minor map exceptions for size/shape/topography	Planning Commission with tentative map	§ 16.20.050
Floodplain variance	Elevation/floodproofing departures; special findings and applicant notice required (insurance)	Flood administrator / Planning Commission per flood chapter	Flood provisions in Development Code (see flood variance findings)
Density‑bonus waiver/modification	Waivers or reductions in development standards necessary for affordable housing	Planning Commission (per § 16.82 & state law)	§ 16.82.020 and related provisions

Checklist — What an applicant must satisfy (variance or minor exception)

Submit a completed planning application and fee (see § 16.12.030 procedure references). Verify fee level with Planning.
Provide a written statement describing the precise nature of the variance/exception and the hardship / practical difficulty that would result from strict enforcement. § 16.16.070(C)(1)(b).
Include scaled site plans, elevations, and photographs that clearly show the proposal and nearby context. § 16.16.070(C)(1)(c).
If applicable, show how the request avoids causing on‑street parking impacts (additional parking finding required). § 16.16.070(D)(7) and Chapter 16.56 (parking).
Demonstrate each required affirmative finding for variances (all six/ seven findings) or the corresponding minor‑exception findings. § 16.16.070(D) and § 16.16.100(D).
If in a floodplain, provide flood studies and accept flood insurance premium notifications (flood variance front‑sheet and findings). See flood chapter.
If part of a housing density bonus or waiver request, submit the waiver concurrently with the housing application per § 16.82.120.

Verify with the Planning Department for current forms, fees and completeness checklists; some projects require additional studies (e.g., noise, geotechnical, biological) as part of the submittal.

Risks & Ambiguities

Issue	Why it matters	What to verify
Parking variance leading to spillover on public streets	The code requires an extra finding that on‑street parking won't interfere with traffic for parking variances. Failure to do so can cause denial.	Verify § 16.16.070(D)(7) and consult Chapter 16.56 for required parking counts and how the Planning Commission applies the additional finding.
Floodplain variances	Grants may increase flood insurance premiums and risk; the city must record and report variances and notify applicants.	See flood variance findings and required applicant notice in the flood chapter; request floodplain administrator guidance.
Administrative vs. discretionary path	Applicants sometimes assume a minor exception is available but the requested modification exceeds the administrative thresholds.	Confirm the item and magnitude against § 16.16.100 administrative caps (e.g., 10% setback or coverage, +2 ft fence height). If over threshold, prepare for a variance (Planning Commission).
Overlay or historic district constraints	Overlays may add design standards or prohibit certain departures even if a variance would normally be allowed.	Check the overlay (Design/ Historic) provisions and the Historic Preservation guidance early. Verify whether the project needs design review in addition to a variance.
Subdivision exceptions vs. lot‑line adjustments	Subdivision exceptions (tentative map) have different findings and a longer discretionary timeline vs. administrative lot adjustments.	For land divisions, confirm the applicable process under § 16.20.050 and related map timing and notice requirements.
State law overlays (density bonus/ADU law)	State laws can override or alter local discretion (e.g., density bonus waivers are governed by state law and must be processed accordingly).	See Chapter 16.82 for density bonus waivers and the city’s ADU provisions; verify interplay with state law (Government Code § 65915) and § 16.82.020.

Plain-English Summary

If your lot’s shape, slope, or other special condition prevents you from meeting a setback, coverage, height or parking rule, Arroyo Grande lets you ask for a variance from the Planning Commission (formal public hearing) or a minor exception from the Community Development Director for small adjustments; both require showing hardship and that neighbors and public safety won’t be harmed. The formal variance rules are at § 16.16.070 and the administrative minor‑exception rules are at § 16.16.100.

Source References

§ 16.16.070 — Variances (purpose, authority, submittal, required findings).
§ 16.16.100 — Minor use permits — Minor exceptions (administrative scope, findings, notice).
§ 16.16.110 — Minor use permits — Viewshed review (applies to RR, RS, SF and some MF).
§ 16.20.050 — Standards of land divisions (exceptions to subdivision/land‑division requirements).
Flood variance and flood chapter provisions — flood variance findings and applicant notice (flood chapter excerpts).
Chapter 16.36 (Tables 16.36.020(B)–(F), etc.) — District purpose and minimum site development standards for TMU, VMU, VCD, GMU, FOMU.
Chapter 16.82 — Density bonus waivers, procedures and findings (state law interplay).

Helpful in‑site pages (link once where topic is first used above): Design Review, Overlay Districts, Historic Preservation, Development Standards, Parking, ADUs, California Building Standards Code.

Sources

Retrieved passages

Arroyo Grande Zoning Code (chapter are) High relevance
Arroyo Grande Zoning Code (section is) High relevance
Arroyo Grande Zoning Code (section where) High relevance
Arroyo Grande Zoning Code (Section 16.12.155.) High relevance
Arroyo Grande Zoning Code (section are) High relevance
Arroyo Grande Zoning Code (§ 3) High relevance
CFC § 9 (title for) High relevance
Arroyo Grande Zoning Code (title or) High relevance
CBC § G107 (SECTION G107) Medium relevance
Arroyo Grande Zoning Code (Section 16.82.090) Medium relevance

Cited sections

Official Arroyo Grande code library

Frequently asked questions

What is the difference between a variance and a minor exception in Arroyo Grande?

A variance is a discretionary, public‑hearing approval by the Planning Commission that can adjust standards such as setbacks, height, coverage and parking; it requires the findings in § 16.16.070. A minor exception is an administrative Minor Use Permit granted by the Community Development Director (no public hearing) for limited adjustments—examples include up to 10% setback or coverage changes, +2 ft fence height, or small parking waivers—under § 16.16.100.

What affirmative findings must I prove for a variance in Arroyo Grande?

You must establish that strict enforcement causes practical difficulty or unnecessary hardship; that exceptional circumstances apply to the subject property; that the variance won’t grant an inconsistent special privilege; that it won’t be detrimental to public health, safety or welfare; and that it’s consistent with the General Plan and Development Code. For parking variances, an additional finding about on‑street parking impacts is required. See § 16.16.070(D).

Can the Community Development Director reduce residential setbacks?

Yes — for residential districts the Director may decrease minimum setbacks by up to 10% via a minor exception where the change improves design, views, or amenities and will not unreasonably affect adjacent sites. See § 16.16.100(B)(2).

If my property is in the floodplain, can I apply for a variance to build lower than base flood elevation?

Flood variances are possible but require special flood‑chapter findings, conditions to minimize flood damage, written applicant notification about increased flood insurance risk, and the flood administrator must maintain records. Refer to the flood provisions in the Development Code (flood variance findings and notice requirements).

Do subdivision/lot‑split applications have exceptions?

Yes. Exceptions from subdivision design or improvement standards (e.g., layout, road width) can be granted by the Planning Commission when special circumstances (size, shape, topography) justify them; the rules are at § 16.20.050 and exceptions must not harm public health, safety or neighboring properties.

How are density‑bonus waiver requests handled if they need a reduction in development standards?

Requests for waivers/modifications required by a density‑bonus project are heard by the Planning Commission; the Code follows state density‑bonus law (Chapter 16.82) and the Commission must approve unless the waiver is not needed to make the affordable units feasible or would have a specific adverse impact. See § 16.82.020 and related provisions.

Can a variance be appealed?

Yes. Variance decisions by the Planning Commission are subject to the appeal provisions in the Development Code (appeals to City Council per the appeals code procedures). See § 16.12.150 and the variance authority in § 16.16.070(B).

Will a minor exception require neighbourhood notice?

Yes. Although the Community Development Director issues minor exceptions without a public hearing, the code requires mailed notice to property owners within 300 feet and the decision is reported per notice rules; it is appealable to the Planning Commission. See § 16.16.100(C)(3).

If my home is in a historic overlay, how does that affect variance requests?

Historic overlays can impose design standards that affect whether a variance is appropriate — discrete departures may still be allowed, but design review and historic resource findings may apply. Consult the city’s Historic Preservation program and the applicable overlay rules in Chapter 16 (see design review/minor use permit provisions).

What happens if a parking variance is granted but parking spills onto the street?

The code requires a specific finding that parking variances will not cause on‑street parking that interferes with traffic; granting a parking variance without this protection risks enforcement actions or conditions that require mitigation (e.g., on‑site parking improvements). See § 16.16.070(D)(7) and Chapter 16.56.

Ask about any Arroyo Grande property

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

Start Free Trial