Tree replacement requirements in Arizona
Mitigation obligations across 18 verified Arizona cities, ranked ascending by replacement ratio. Numbers come directly from each city's published ordinance — heritage and specimen trees typically carry higher ratios than standard protected trees.
Replacement obligations across 18 verified cities are published as text rules rather than fixed numeric ratios — see each row below for the underlying ordinance language.
Replacement obligation comparison
Sorted ascending by minimum n:1 ratio. Cities with text-only or retention-percentage rules appear last. Click a city for the full ordinance page or the ordinance link for the underlying municipal code.
| City | Replacement ratio | Replacement details | In-lieu fee/tree | Processing | Code |
|---|---|---|---|---|---|
| Flagstaff | Caliper-inch mitigation per Division 10-50.60 for removed qualifying trees; preservation percentages by zone | On-site replacement preferred with ponderosa pine or approved native; off-site replacement or in-lieu contribution permitted under some conditions. | — | 6-10 weeks for Forest Resource review as part of development submittal | Ordinance |
| Prescott | Caliper-inch or DBH-inch mitigation for removed qualifying trees per Land Development Code | On-site replacement preferred with ponderosa pine or approved native species; payment to city tree fund where applicable. | — | 4-8 weeks for tree preservation review as part of development submittal | Ordinance |
| Tempe | Caliper-inch replacement or mitigation for significant tree removal during development (site-specific) | On-site replacement with comparable caliper; payment to city landscape or streetscape fund where applicable. | — | 3-6 weeks for landscape plan review | Ordinance |
| Oro Valley | Chapter 27 establishes preservation-in-place percentages and transplant/replacement standards; replacement required when preservation infeasible | Preserve-in-place preferred; transplant on-site next; replacement with equivalent native species when transplant fails. Arizona Native Plant Law applies independently on undeveloped land. | — | 6-10 weeks for ESL-subject development reviews | Ordinance |
| Scottsdale | ESLO sets preservation percentages and transplant requirements by plant category; on-site replacement required when preservation infeasible | Preserve-in-place preferred; transplant on-site next; replacement with equivalent native species when transplant fails. In-lieu provisions limited. | — | 6-10 weeks for ESLO-subject development reviews | Ordinance |
| Phoenix | Landscape code-based replacement (site-specific by zone and project type); salvaged native plants reused on-site where feasible | On-site preservation and transplant preferred; replacement plantings per landscape standards. No dedicated city tree-mitigation fund. | — | 4-8 weeks for landscape plan review as part of development submittal | Ordinance |
| Buckeye | Landscape-code replacement per Buckeye landscape standards (site-specific) | On-site replacement to meet landscape coverage and shade standards. | — | 3-6 weeks for landscape plan review | Ordinance |
| Chandler | Landscape-code replacement per Chandler landscape standards (site-specific) | On-site replacement to meet landscape coverage, shade, and species standards. | — | 3-6 weeks for landscape plan review | Ordinance |
| Gilbert | Landscape-code replacement per Gilbert landscape standards (site-specific) | On-site replacement to meet landscape coverage and shade standards. | — | 3-6 weeks for landscape plan review | Ordinance |
| Glendale | Landscape-code replacement per Glendale landscape standards (site-specific) | On-site replacement to meet landscape coverage and shade standards. | — | 3-6 weeks for landscape plan review | Ordinance |
| Goodyear | Landscape-code replacement per Goodyear landscape standards (site-specific) | On-site replacement to meet landscape coverage and shade standards. | — | 3-6 weeks for landscape plan review | Ordinance |
| Mesa | Landscape-code replacement per Mesa landscape standards (site-specific by zone) | On-site replacement required to meet landscape coverage and shade standards. | — | 3-6 weeks for landscape plan review | Ordinance |
| Peoria | Landscape-code replacement per Peoria landscape standards (site-specific) | On-site replacement to meet landscape coverage and shade standards. | — | 3-6 weeks for landscape plan review | Ordinance |
| Queen Creek | Landscape-code replacement per Queen Creek landscape standards (site-specific) | On-site replacement to meet landscape coverage and shade standards. | — | 3-6 weeks for landscape plan review | Ordinance |
| Sierra Vista | Landscape-code replacement per Sierra Vista landscape standards (site-specific) | On-site replacement with drought-tolerant native or adapted species. | — | 3-6 weeks for landscape plan review | Ordinance |
| Surprise | Landscape-code replacement per Surprise landscape standards (site-specific) | On-site replacement to meet landscape coverage and shade standards. | — | 3-6 weeks for landscape plan review | Ordinance |
| Yuma | Landscape-code replacement per Yuma landscape standards (site-specific) | On-site replacement with drought-tolerant native or adapted species. | — | 3-6 weeks for landscape plan review | Ordinance |
| Tucson | UDC 7.6 establishes preservation-in-place percentages and transplant/replacement standards; replacement required when preservation is not feasible | Preserve-in-place preferred; transplant on-site next; replacement with equivalent native species when transplant fails or is infeasible. Arizona Native Plant Law applies independently on undeveloped land. | — | 4-8 weeks as part of development review | Ordinance |
How Arizona replacement obligations work
- Which city requires the highest replacement ratio in Arizona?
- Replacement ratios in Arizona are published as text rules rather than fixed numeric ratios — see each row for the underlying ordinance language.
- What's the typical replacement obligation when a tree is removed?
- Replacement obligations in Arizona are published as text rules — most reference retention percentages or assessed-value mitigation rather than fixed n:1 ratios. Check each city's row for the exact ordinance language.
- Can I pay an in-lieu fee instead of replanting trees in Arizona?
- Most cities in Arizona accept in-lieu mitigation deposits to a tree planting fund when on-site replanting isn't feasible, but the per-tree dollar amount isn't published as a flat fee — it's calculated case-by-case (often based on caliper inches or assessed value). Verify with the municipal forester.
Documenting a removal in Arizona?
Capture an ISA TRAQ Level 1, 2, or 3 assessment in the field and export a municipality-ready PDF that fits each city's required mitigation report sections. Free, no account required.
Start a TRAQ assessment