Property Snapshot
Maximum Buildable Capacity
| Max Building Area (Gross) | 267,326 SF |
| Max Footprint | 133,663 SF |
| Max Height | 2 floors · 30 ft |
| Parking Required | 1,069 spaces |
| Net Leasable | 214,261 SF |
Development Standards
Source: Phoenix Zoning Ordinance §622 — phoenix.municipal.codes/ZO/622 (C-1 Neighborhood Retail). Default by-right max 2 stories / 30 ft; up to 4 stories / 56 ft via City Council
Permitted & Allowable Uses
Variance Risk Analysis
Standard by-right development is likely permissible.
- Drive-through requires CUP
Active Overlay Districts
Entitlement Risk
Entitlement Flags
Drive-through use (e.g., for a restaurant or bank) is not permitted by right in C-1 and requires a Conditional Use Permit per the known variance triggers from code.
The proposed gross building area of 267,326 SF is inconsistent with C-1's retail unit size cap of under 5,000 SF per store. Any single anchor tenant exceeding 5,000 SF would not be a permitted use in C-1 and would require rezoning to a compatible commercial zone (e.g., C-2 or C-3) or a use permit if available under Phoenix code.
Parking demand at full buildout is estimated at 1,069+ spaces. Surface parking at standard stall ratios would require approximately 353,000–374,000 SF, exceeding the total lot size of approximately 267,326 SF. The project cannot meet code-required parking on-site through surface parking alone, triggering a potential variance or requiring structured parking. If structured parking is not feasible, a parking variance or alternative parking plan will be required.
Side and rear setback requirements in C-1 range from 0 ft to 10–150 ft depending on adjacency to residential parcels. Until a boundary survey and adjacency analysis are completed, it is unknown whether the proposed site plan can meet setback requirements. If residential parcels are adjacent, setbacks up to 150 ft may apply and the building footprint may not comply, triggering a variance.
Residential use is not a permitted use in C-1 and the maximum residential units is listed as null. If the developer wishes to include any residential component, a rezoning or overlay district designation will be required.
A height bonus of up to 56 ft / 4 stories (above the base 30 ft limit) requires City Council approval. If the developer pursues increased height to achieve up to approximately 534,652 SF gross building area, a formal height bonus approval or specific plan amendment process must be initiated.
At the scale of 6.137 acres in Phoenix, environmental review, a traffic impact analysis (TIA), and a drainage/stormwater study are likely required before entitlement or building permit issuance. These are typically handled through staff-level administrative review but must be completed and approved prior to project advancement.
APN 12701003E must be verified with the Maricopa County Assessor for current ownership, parcel boundaries, recorded easements, and deed restrictions. Any recorded encumbrances could further constrain buildable area or permitted uses and may require separate legal or administrative resolution before entitlements can proceed.
Opportunity Brief
A straightforward multi-tenant C-1 retail project that respects the 5,000 SF tenant cap proceeds by-right with administrative approval and no public hearing required, placing this on the faster end of the 3–9 month estimated entitlement timeline. However, the discretionary review path for a height bonus requires City Council approval, which introduces public hearing risk and schedule uncertainty that could push the timeline toward the outer range. Medium risk overall, with the primary risk flags being: (1) the parking deficit at full buildout — if surface parking cannot accommodate 1,069 spaces within the lot, the city may require a parking study, structured parking, or a reduced building program before permits are issued; (2) setback adjacency conditions that remain unresolved and must be confirmed against the final site plan; and (3) potential traffic study and environmental review requirements triggered by project scale. The recommended first move is a pre-application meeting with Phoenix Planning to confirm setback requirements, establish the parking compliance strategy, and determine whether a traffic impact analysis will be required — do this before finalizing site control.
Approval& RISK: A straightforward multi-tenant C-1 retail project that respects the 5,000 SF tenant cap proceeds by-right with administrative approval and no public hearing required, placing this on the faster end of the 3–9 month estimated entitlement timeline. However, the discretionary review path for a height bonus requires City Council approval, which introduces public hearing risk and schedule uncertainty that could push the timeline toward the outer range. Medium risk overall, with the primary risk flags being: (1) the parking deficit at full buildout — if surface parking cannot accommodate 1,069 spaces within the lot, the city may require a parking study, structured parking, or a reduced building program before permits are issued; (2) setback adjacency conditions that remain unresolved and must be confirmed against the final site plan; and (3) potential traffic study and environmental review requirements triggered by project scale. The recommended first move is a pre-application meeting with Phoenix Planning to confirm setback requirements, establish the parking compliance strategy, and determine whether a traffic impact analysis will be required — do this before finalizing site control.
Program OptimizationThe parking math is the financial fulcrit of this project: 1,069 required spaces at surface-parking land consumption will eat most or all of the lot at full buildout, so the real question is whether a podium or structured parking solution pencils. A podium garage or below-grade deck would allow a larger retail building footprint and potentially justify the height bonus entitlement process, but structured parking costs must be weighed against the incremental revenue from the additional leasable SF — at a 5,000 SF per-tenant cap, the rent per-SF profile is driven by small-format tenants, not anchors, which limits rent upside per square foot. If structured parking does not pencil, the optimal move is to right-size the building footprint to what surface parking can support within the lot coverage limit, accepting a smaller program in exchange for a faster, lower-cost by-right path. No FAR is specified in the C-1 code, so lot coverage and parking — not FAR — are the levers to optimize; a land-use attorney or parking consultant should model the surface-vs.-structured tradeoff before schematic design begins. Residential uses are prohibited in C-1, so no density bonus or affordable-housing overlay strategy applies here.
Market ConsiderationIndian School Road is a proven retail arterial in Phoenix, and a 6.137-acre multi-tenant retail center serving a dense residential catchment is a fundable product type — but the 5,000 SF tenant cap shapes the tenant mix toward service retail, medical, food-and-beverage, and specialty users rather than soft goods or junior anchors, which typically means shorter lease terms and higher turnover risk relative to grocery-anchored formats. At full buildout (267,326 SF), soft costs spread favorably across a large program, but the realistic buildable program — constrained by parking — is likely materially smaller, which compresses the cost-per-SF efficiency. Developers should model the project at multiple footprint sizes (surface-parking-constrained vs. structured-parking-enabled) to identify the breakeven threshold where structured parking costs are justified by the incremental leasable SF. The by-right retail path is straightforward enough to attract merchant builders and neighborhood retail developers; the height bonus path is a longer-horizon play that requires council relationships and a compelling public-benefit narrative.
Bottom LineYellow-light — the C-1 zoning supports a viable multi-tenant retail program by-right, but the parking deficit at full buildout and unresolved setback and traffic study requirements must be resolved before the project is financeable. Schedule a pre-application meeting with Phoenix Planning this week to confirm parking compliance options, setback conditions, and traffic study triggers before site control lapses.
Optimize for a Specific Use
Every report includes tailored analysis for 8 use types. Click any chip below to see the brief — no account needed on this sample.
Impact & Development Fees
Infill incentive district may reduce fees — verify with Planning
⚠️ These are approximate published fee schedules (2024 data). Actual fees vary by project type, size, and location within the city. Verify current rates with the city’s Development Services department before budgeting.
Property Tax
Tax rate for Phoenix: ~$8.15 per $100 of assessed value. Parcel record not located by address. This is common for PUDs, master-planned campuses, recently subdivided lots, and addresses that geocode to a campus rather than a single parcel. The standard tax rate for this jurisdiction is shown below.
Comparable Sales
| Address | Sale Date | Price | Lot Size | $/SF |
|---|---|---|---|---|
| 2935 N 68TH ST CONDOS/TH GRADE 070-3 COM AREA NOT PA |
2026-03-01 | $350,500 | 1,035 SF | $338.65 |
| 3816 N PUEBLO WAY SFR GRADE 010-3 URBAN SUBDIVIDED |
2026-02-01 | $715,000 | 7,281 SF | $98.2 |
| 6545 E 1ST ST SFR GRADE 010-3 URBAN SUBDIVIDED |
2025-12-01 | $730,000 | 6,497 SF | $112.36 |
| 6723 E 1ST AVE SFR GRADE 010-3 URBAN SUBDIVIDED |
2025-12-01 | $745,000 | 6,746 SF | $110.44 |
| 6706 E 1ST AVE SFR GRADE 010-3 URBAN SUBDIVIDED |
2025-11-01 | $700,000 | 6,539 SF | $107.05 |
| 6736 E 1ST AVE SFR GRADE 010-4 URBAN SUBDIVIDED |
2025-10-01 | $1,275,000 | 6,593 SF | $193.39 |
| 7630 E BONNIE ROSE AVE CONDOS/TH GRADE 070-4COM AREA PARCELE |
2025-10-01 | $640,000 | 2,127 SF | $300.89 |
| 3831 N PUEBLO WAY SFR GRADE 010-3 URBAN SUBDIVIDED |
2025-08-01 | $700,000 | 7,235 SF | $96.75 |
Search radius: 4.0 miles · 8 sales found.
Development Pipeline
Phoenix has a very active development pipeline with 79 pending applications — expect competition for contractors, materials, and tenant demand
Entitlement Probability Score
Approval rate: 100.0% across 68 decided cases. (small sample - a 100% rate may not be statistically reliable)
Entitlement Processing Times
Based on 2 cases with recorded processing times in Phoenix (excludes 1 case type(s) below plausibility floor)
Neighborhood Opposition Risk
0% of decided cases in Phoenix have been denied — favorable entitlement environment — good conditions for new applications.
Regulatory Conflicts & Notes
No state preemptions or overlay conflicts identified for this zone.
Regulatory conflict flags are informational only. Laws change; always verify current statute text and obtain legal counsel before relying on any preemption right. Zoning Assist is not a law firm and this is not legal advice.
Location Intelligence
Topography & Slope
Minimal grading costs expected — site is essentially flat
Stormwater & Drainage
High runoff potential (Group C soils) — commercial development will require stormwater detention/retention per city ordinance. Plan for approximately 1 acre-foot of storage per 5 acres of impervious surface.
Natural Hazards
Natural hazard risk levels are regional estimates. Site-specific assessments (geotechnical, flood study, wildfire assessment) recommended for final due diligence. FM Data Sheet references are provided for informational purposes — access full standards free at fm.com/datasheets.
Government Land Status
No state trust, federal, or DOT ROW land detected within 0.5 mile — parcel appears to be private land
Utility Providers
Contact providers directly to verify service availability and capacity for your specific parcel
Offsite Improvements
Principal Arterial — major through-road; traffic impact study very likely required
Major arterial or freeway frontage — traffic impact study and significant offsite improvements (turn lanes, signals, medians) very likely required
Road classification sourced from FHWA HPMS (Federal Highway Administration). Street name via Google Geocoding. Verify improvement requirements with city Engineering/Public Works.
City CIP: Check Phoenix's Capital Improvement Program at phoenix.gov/pdd/cip for planned road improvements
Soil & Foundation Risk
Ideal drainage for most construction
Soil data is generalized from survey maps — site-specific geotechnical report recommended before design
Residential Density Tools
Planning Jurisdiction
Disclaimers & Verification
Verify before acting. Confirm zoning, dimensional standards, and overlay applicability directly with the Phoenix planning department (602-262-7811) before making investment decisions or filing applications.
What does "Governed by site plan / overlay" mean? When this report shows Governed by site plan / overlay — determined at site plan review, that standard is not defined as a fixed number in the base zoning code. This is normal for planned developments, overlay districts, form-based codes, and certain downtown or beach districts where dimensional standards are set individually at the time of site plan approval. It is not a system error or a data gap — the code itself does not publish a single number for that field. Contact the planning department directly to confirm what applies to your specific parcel.
Data Source: City API (live GIS) · Confirmed 2026-05-05
Informational use only. This report uses publicly available GIS and government data. AI-generated sections reflect pattern-matching, not expert judgment. Always obtain an official zoning verification letter and retain licensed professionals before making investment decisions. Full Disclaimer →
Generated 2026-05-15 03:12:34 · Report ID fe635353-8f9b-46e3-b217-1c53123f2ef4 · My Reports · Disclaimer · Data Practices · Contact