Indio Zoning, Planning & Building Codes

Last reviewed: July 3, 2026

Overview

Indio’s land-use rules are consolidated in the local Title 17 — Unified Development Code (the "Development Code"), which is the city’s zoning and development rulebook (see § 1.01.01). The Code implements the General Plan and is organized into base zones, overlay zones, citywide (Article 3) standards, regulations for specific uses, and an administration/permit procedures article; use and entitlements are resolved by the Director, Planning Commission, and City Council depending on the permit type (see § 1.01.02, § 1.02.02, § 6.02.02, § 6.02.03). This page summarizes how to navigate Indio’s rules, the major district families and typical development controls, the overlays and specific plans that matter, the permit/review path, and how state housing rules (ADUs, density bonus, ministerial streamlining) interact with the Code.

How Indio's code is organized

• Code title and purpose: the local zoning code is titled Title 17. Unified Development Code (§ 1.01.01) and is adopted to implement the General Plan and standard land‑use authorities (§ 1.01.02, § 1.01.03).
• Quick user road‑map: the Code tells you first to check zoning on the Official Zoning Map, then consult the allowed‑use tables in Article 2, then apply Article 3 citywide standards, any Article 4 specific‑use rules, and the permit procedures in Article 6 (§ 1.03.01, § 2.01.02).
• Measurement and definitions: citywide measuring rules (fractions, measuring distances, height measuring) live in Article 3 (for example § 3.01.01) and definitions are in Article 7; these affect how setbacks, heights, and unit counts are interpreted.

(NOTE — quick links: the city’s zoning overview is at Indio Zoning and land‑use background is at Indio Land Use.)

Zoning district families (what the map means)

Indio groups its base zones into four broad families: Residential Neighborhood Zones, Mixed‑Use Zones, Commercial/Industrial Zones, and Public/Institutional Zones; each family contains named base districts and maps to General Plan “place‑types” in Table 1.02.03‑1 (§ 1.02.03). The Code implements these through the Article 2 use tables and per‑zone development tables.

Representative district names and where to find their numeric controls:

• Residential examples: DE‑1, DET‑3, SN‑4, SN‑8, MH — development tables show maximum heights, lot coverage, minimum lot sizes, and density (see TABLE 2.02.03‑1 for the detailed residential table and its attendant notes). The table lists: maximum height values such as 25 ft / 2 stories (or other values per zone), maximum lot coverage (e.g., 30%–70% depending on zone), and minimum lot sizes; the tables are found under the Article 2 residential zone chapters.
• Mixed‑use examples: CN‑14, CN‑20, NC, MUN, MT — the mixed‑use tables set residential density ranges (minimums and maximums in units/acre) and FAR caps for non‑residential uses (e.g., FAR 0.25–1.0 in various mixed zones) as shown in TABLE 2.03.03‑1 and TABLE 2.03.03‑2.
• Commercial/industrial and public/institutional zones are likewise tabulated; each table cross‑references the citywide standards (setbacks, parking, landscaping, signs) so the base zone tables act as a quick lookup for allowed uses and the default dimensional standards. See Article 2 use/permission tables and the “Other Standards” rows that refer to Article 3 chapters.

All allowed uses and permit requirements are shown in the Article 2 permission tables; when a parcel is inside a Special Planning Area (a specific plan or PD), the applicable special‑plan rules can override the base table (§ 2.01.02.B).

Citywide development standards (high‑level)

Indio separates zone‑specific numbers (Article 2 tables) from citywide standards (Article 3). Key citywide chapters and representative rules:

• Rules of measurement and rounding: general rounding rules and how to measure dimensions and height are in § 3.01.01 and related measurement provisions; these determine how lot coverage, FAR, and height are computed.

• Setbacks, lot coverage, heights, FAR and densities: those numeric standards are provided in the per‑zone tables (Article 2 tables such as TABLE 2.02.03‑1 for residential and TABLE 2.03.03‑1 for mixed‑use). For example, the residential tables list maximum primary building heights (commonly 25 ft or 2 stories for certain zones; maximum accessory building heights 20 ft) and maximum lot coverage values by zone; consult the applicable table under Article 2 for the exact numbers for any district.

• Parking: the citywide parking and loading rules are in Chapter 3.03 (Parking and Loading); the chapter requires parking for new buildings and sets rules for conversions/changes of use, timing of construction of parking, and maintenance of existing parking (§ 3.03.02, § 3.03.03). See the city parking standards and minimums in Chapter 3.03, and additional parking design guidance referenced from mixed‑use and other zone tables. The Code expressly contemplates shared parking and parking reductions for transit‑served areas (§ 3.03.02). For design‑level guidance see the mixed‑use design sections that reference Chapter 3.03.

  • (Quick link: first mention of parking here links to Indio Parking.)

• Landscaping, screening, lighting and other site standards: the citywide site standards live in Chapter 3.02 (landscaping §3.02.09, fences/walls §3.02.10, outdoor lighting §3.02.11) and are cross‑referenced from the tables; the public art program and water‑efficient landscape requirements are also referenced there.

  • (First mention of development standards / setbacks in the text linked to Indio Development Standards.)

• Design standards & objective design standards: mixed‑use and multi‑family projects have a dedicated design‑standard section (§ 2.03.06) that controls site layout, entries, connectivity, and block structure; the Planning Review rules require consistency with objective design standards and allow interpretive design guidelines during discretionary review.

Specific plans, overlays, and unique districts

• Overlays: Indio uses overlay zones to add site‑specific rules or environmental protection. Examples in the Code include the Resource Management and Open Space Overlay (R‑OS) and the Planned Development Overlay (PD); the overlay rules state they augment or supersede the underlying base zone where applicable (§ 2.07.03, § 2.07.04). A PD becomes the controlling zoning within its mapped boundaries and is established through a PD permit process in § 6.05.01.
  • (First mention of overlays linked to Indio Overlay Districts.)
• Specific plans & Special Planning Areas: when a parcel lies inside a Specific Plan or other adopted planning document, that special‑plan document controls over the base zone where there is conflict (§ 2.01.02.B). Planned Developments (PD) are subject to findings and procedures in § 6.05.01 and § 2.07.04 (note minimum PD acreage rules and required findings).
• Airport compatibility and other external constraints: certain districts and properties are subject to the Bermuda Dunes Airport Land Use Compatibility Plan; the Code directs applicants to coordinate with county Airport Land Use Commission staff where applicable (§ 2.01.02.D).

Building permits & review (how a project moves)

• Who decides: the Code identifies the decision bodies and staff roles — City Council, Planning Commission, and Community Development Director — and their duties, including that the Director issues zoning clearances as part of building permit review for ministerial compliance (§ 6.02.01, § 6.02.02, § 6.02.03).

• Typical permit path (practical orientation):

  1. Find the zone on the Official Zoning Map (§ 1.02.02) and consult the allowed‑use tables in Article 2 and related development standards (§ 1.03.01, § 2.01.02).
  2. Determine whether the proposed use is permitted, requires an Administrative Use Permit, a Conditional Use Permit, or other entitlement (Article 2 tables and § 6.04.04 on Use Permits). Conditional Use Permits typically go to the Planning Commission with public hearing and notice requirements (§ 6.04.04.E).
  3. Apply citywide standards (Article 3), special‑use rules (Article 4), and any Specific Plan/PD requirements; the Director will perform zoning clearance during building‑permit plan check for ministerial items (§ 6.02.03.E) and may issue administrative approvals where allowed.
  4. If the project is discretionary, it proceeds through Planning Review (administrative, ministerial/streamlined, or discretionary) — see the planning review rules in the Code (Planning Review — Administrative/Ministerial/Discretionary; see § 6.04.03 and the discussion of administrative vs. ministerial vs. discretionary review).
  5. Decisions can be appealed under the appeals provisions (see § 6.03.13 referenced throughout).

• Concurrent processing: the Code encourages concurrent processing of entitlements and building permits (the highest review authority takes final action) and requires that PD and tentative maps be filed together when tied to a PD approval (§ 6.05.01.C.3–4).

• Design review and discretionary criteria: discretionary Planning Review is governed by detailed criteria (General Plan consistency, standards consistency, site and building design, streetscape, parking, landscape and screening, lighting, etc.) — projects must meet those findings in order to obtain approval (§ 6.04.03 and the Discretionary Planning Review criteria).

  • (First mention of design review linked to Indio Design Review.)

State housing law in Indio — how ADUs, SB‑driven streamlining, density bonus and other state rules layer on local rules

Summary: Indio’s Development Code folds state housing statutes into the local process: ADUs/JADUs are regulated in Article 4, Chapter 4.02 with specific local standards but with an explicit statement that State law controls where inconsistent; ministerial ADU review is done through the building permit process and Director compliance determinations are final (§ 4.02.01, § 4.02.03, § 4.02.08, § 4.02.09). Density bonus rules are referenced to Indio Municipal Code Chapter 154.

• ADUs and JADUs: the Code allows one ADU and one JADU on a single‑family lot (and provides multi‑family conversion/limits), sets size limits for attached/detached ADUs, and sets default setbacks and heights for detached ADUs (e.g., detached ADUs maximum height 18 ft in many circumstances; ministerial review and issuance timelines apply) — see § 4.02.03 (Development Standards) and § 4.02.08 (Application Review and Approval); the Code also explicitly defers to state ADU law when inconsistent (§ 4.02.09).
  • (First mention of ADUs linked to Indio ADUs.)
• Ministerial streamlining / SB 35 / State ministerial approvals: the Code contains a ministerial planning review track for projects qualifying under State streamlining laws (SB 35 and related statutes) and explains timelines, objective standards, and the limits on conditions that would prevent the project from being built as‑proposed (§ 6.04.03, Planning Review — Ministerial / Streamlining). The Code requires objective design standards for housing projects seeking streamlining and explains appeal and correction paths if Staff finds non‑compliance.
  • (First mention of California housing laws linked to California housing laws.)
• Density bonus and incentives: the Code references Indio Municipal Code Chapter 154 (Density Bonuses and Other Incentives for Low Income and Senior Housing) in the zone tables and density discussions; projects may use the city’s density bonus chapter consistent with state law (Government Code § 65915 references appear in the Code's rounding/fractions rules).
• Local rent rules / rent control: the Development Code does not create rent control rules — those are typically in other municipal titles or state law; the Development Code’s relevant references are to housing incentives, entitlements, and permit processing (no local rent‑control code section appears in the retrieved Development Code). Verify with the City Attorney/municipal code index for any separate residential tenancy or rent ordinance (Not found in retrieved Development Code materials).

(For ADU technical limits and the state building code interplay, the Development Code instructs applicants to comply with the California Building Standards and references that state law controls where inconsistent — see § 4.02.09. Link to California Building Standards Code and to the California ADU law for state specifics.)

Practical takeaways for an Indio property owner or developer

• Start at the Official Zoning Map and the Article 2 permission table for your parcel — the table tells you if your use is permitted, requires an administrative use permit, or requires a Conditional Use Permit (§ 1.03.01, § 2.01.04).
• Price in required parking and consult Chapter 3.03 early — parking is a citywide chapter and influences plan layout and permitting (§ 3.03.02, § 3.03.03).
• If you need flexibility (different setbacks, mixed uses), a Planned Development (PD) overlay is available but requires City Council adoption plus findings in § 6.05.01 and §2.07.04; PDs commonly require a PD Permit and can set site‑specific rules.
• ADUs are generally ministerial and processed with building permits under § 4.02.08; if in doubt, rely on the ADU checklist and the Director’s compliance determination (Director’s decision on ADU compliance is final per § 4.02.08.B).
• For housing developments seeking streamlining (SB 35 etc.), read the Code’s ministerial/streamlined planning review provisions — the city requires objective standards and sets timelines for approval (§ 6.04.03).

Information Gaps / Items to Verify with City staff

• Specific numeric parking minimums by use class and the full parking‑table schedules are located in Chapter 3.03 but the full table rows (e.g., spaces per 1,000 sf for a specific retail use) were not excerpted here; consult Chapter 3.03 in the full Code or staff for precise parking ratios (§ 3.03.02).
• The Code references Indio Municipal Code Chapter 154 for density‑bonus specifics — for step‑by‑step bonus calculations and local incentives consult Chapter 154 directly (referenced repeatedly in zone tables).

Source References

• Title 17. Unified Development Code — Indio Development Code: § 1.01.01, § 1.01.02, § 1.01.03
• How to use this Code; Zoning Map & Zone establishment: § 1.03.01, § 1.02.02, § 1.02.03
• Zone tables & residential development standards (TABLE 2.02.03‑1): residential heights/coverage/density examples — see Article 2 tables (TABLE 2.02.03‑1)
• Mixed‑use tables and standards (TABLE 2.03.03‑1 / 2): § 2.03.03 and tables for CN/MUN/MT/NC zones
• Citywide measurement rules and rounding: § 3.01.01 and measurement notes
• Parking & loading chapter: Chapter 3.03 (applicability and general requirements § 3.03.02, § 3.03.03)
• Design standards / Mixed‑use & multi‑family design: § 2.03.06 (mixed‑use design standards)
• Planning Review, ministerial/administrative/discretionary tracks and criteria: § 6.04.03 and the Discretionary Planning Review criteria/conditions of approval (planning review sections)
• Review and decisionmaking bodies; Director powers and zoning clearance in building permit review: § 6.02.02, § 6.02.03 (Director powers, zoning clearance)
• Planned Development Overlay (PD): § 2.07.04 and PD procedures in § 6.05.01
• Accessory Dwelling Units (ADUs): Article 4, Chapter 4.02 (Development Standards § 4.02.03, Application Review § 4.02.08, Compliance with State Law § 4.02.09)