Zoning › Alabama › Montgomery County › Montgomery

Montgomery, AL Zoning

Rewrite-in-flight-zoning. 32 districts · 9 overlays · 6 applicable state preemptions.

Overview

Code type
rewrite-in-flight
Naming convention
lot-size-encoded

The 1985 legacy code uses lot-width-encoded district names: the number in R-125, R-100, R-85, R-75, R-65, R-60, R-50 is the minimum lot width in feet (NOT a sequential index). The existing V1 file contained fabricated district names R-1, R-2, R-30, C-1, C-2, I-1, I-2 — those codes do NOT exist in Montgomery's 1985 ordinance and represent template-bleed from other cities. The actual district list uses width-based codes (R-50 through R-125) for single-family, plus variants (R-75-s/d/m, R-65-s/d/m, R-60-s/d/m/a), mobile/townhouse/PUD/PGH specialty residential, B-1-a/b through B-5 commercial, M-1 through M-3 industrial, O-0/O-1/O-2 office, INST institutional, AGR-1/AGR-2 agricultural, FH flood hazard, WR waterfront, U utility. The Jan 2025 SmartCode adds T1/T2/T3/T4-R/T4-O/T4-C/T5 transect zones for new community plans — a second coexisting code system. The GIS layer at gis.montgomeryal.gov confirms the legacy codes are still active. Classification: rewrite-in-flight (two coexisting systems).

Worth knowing
  • TEMPLATE-BLEED CONFIRMED: The existing V1 profile contained fabricated district names R-1, R-2, R-30, C-1, C-2, I-1, I-2. These codes do NOT exist in Montgomery's zoning ordinance. The actual system uses lot-width-encoded names (R-125, R-100, R-85, R-75, R-65, R-60, R-50) derived from minimum lot width in feet. Fabrication was likely imported from a generic template; all V1 district dimensions have been discarded.
  • DUAL CODE SYSTEM: The 1985 legacy ordinance (Appendix C, Municode) coexists with the Jan 28, 2025 SmartCode. The GIS zoning map at gis.montgomeryal.gov still uses legacy codes (R-50, R-100, B-1 through B-5, M-1 through M-3) confirming the legacy code governs all existing parcels. SmartCode applies to new community plans only.
  • LOT-WIDTH NAMING: The digit in each residential district code equals the minimum lot width in feet (R-50 = 50 ft min, R-125 = 125 ft min). This is Montgomery's local naming convention — not density-encoded, not use-type-indexed.

+ 6 more in Quirks & notes

Districts

res_sf 13res_mf 4com 4ind 3cbd 2off 2ag 2spec 2
CodeNameCategory Min lotHeight CoverageFAR Du/acParking Setbacks F/S/R
R-125Single-Family Residential (125-ft lot width)res_sf20,000 sf[4]35 ft[5]0.2[6]——3[7]50[1] / 20[2] / 40[3]
R-100Single-Family Residential (100-ft lot width)res_sf14,000 sf[11]35 ft[12]0.25[13]——2[14]35[8] / 12[9] / 30[10]
R-85Single-Family Residential (85-ft lot width)res_sf12,000 sf[18]35 ft[19]0.25[20]——2[21]35[15] / 10[16] / 30[17]
R-75-sSingle-Family Residential (75-ft lot width, single-family)res_sf10,000 sf[25]35 ft[26]0.4[27]——2[28]30[22] / 10[23] / 30[24]
R-75-dTwo-Family Residential (75-ft lot width, duplex)res_sf10,000 sf[32]35 ft[33]0.4[34]——2[35]30[29] / 10[30] / 30[31]
R-75-mMulti-Family Residential (75-ft lot width)res_mf10,000 sf[39]35 ft[40]0.4[41]——2[42]30[36] / 10[37] / 30[38]
R-65-sSingle-Family Residential (65-ft lot width)res_sf8,400 sf[46]35 ft[47]0.4[48]——1[49]30[43] / 10[44] / 30[45]
R-65-mMulti-Family Residential (65-ft lot width)res_mf8,400 sf[53]35 ft[54]0.4[55]——1[56]30[50] / 10[51] / 30[52]
R-60-sSingle-Family Residential (60-ft lot width)res_sf7,200 sf[60]35 ft[61]0.5[62]——1[63]20[57] / 10[58] / 20[59]
R-60-mMulti-Family Residential (60-ft lot width)res_mf7,200 sf[67]35 ft[68]0.6[69]——1[70]20[64] / 10[65] / 20[66]
R-60-aMulti-Family Residential High Density (60-ft lot width, apartment)res_mf7,200 sf[74]35 ft[75]0.6[76]——1[77]20[71] / 10[72] / 20[73]
R-50Single-Family Residential (50-ft lot width)res_sf6,000 sf[81]35 ft[82]0.5[83]——1[84]20[78] / 9[79] / 20[80]
R-99-pMobile Dwelling Parkres_sf4,000 sf[85]———8[86]2[87]— / — / —
R-24-tTownhouse Residential (24-ft lot width)res_sf2,400 sf[90]35 ft[91]———2[92]20[88] / 16[89] / —
R-20-tTownhouse Residential (20-ft lot width)res_sf2,000 sf[95]35 ft[96]———2[97]20[93] / 10[94] / —
PGH-35Patio-Garden Home (35-ft lot width)res_sf3,500 sf[101]35 ft[102]1[103]——2[104]20[98] / 8[99] / 15[100]
PGH-40Patio-Garden Home (40-ft lot width)res_sf4,000 sf[108]35 ft[109]1[110]——2[111]20[105] / 10[106] / 15[107]
B-1-aCentral Business District (B-1-a)cbd——[114]1[115]——0.5[116]0[112] / — / 0[113]
B-1-bCentral Business District (B-1-b)cbd——[119]0.6[120]——0.5[121]0[117] / — / 0[118]
B-2Business District (Individual Stores)com—45 ft[124]0.5[125]——0.5[126]—[122] / — / —[123]
B-3Highway Commercial Districtcom—45 ft[129]0.3[130]——1.25[131]30[127] / — / 20[128]
B-4Planned Commercial (Local Shopping)com—35 ft[134]0.25[135]——1.25[136]60[132] / — / 30[133]
B-5Planned Commercial (Shopping Community)com—35 ft[139]0.2[140]——1.5[141]60[137] / — / 30[138]
M-1Light Industryind—50 ft[145]0.5[146]——0.5[147]20[142] / —[143] / —[144]
M-2Industrial Park (Planned Area)ind—50 ft[151]0.25[152]——0.5[153]30[148] / 30[149] / 30[150]
M-3General Industryind—150 ft[157]0.25[158]——0.5[159]—[154] / —[155] / —[156]
O-1Office Districtoff7,200 sf[163]45 ft[164]0.5[165]——1[166]20[160] / 10[161] / 20[162]
O-2Office Park (Planned Area)off25,000 sf[170]45 ft[171]0.25[172]——1[173]40[167] / 20[168] / 40[169]
AGR-1Residential Agricultureag65,340 sf[176]35 ft[177]0.2[178]——3[179]50[174] / 25[175] / —
AGR-2General Agricultureag217,800 sf[182]35 ft[183]0.2[184]——3[185]50[180] / 25[181] / —
INSTInstitutional Areaspec40,000 sf[188]—[189]0.25[190]———50[186] / 50[187] / —
FHFlood Hazard Districtspec—[191]—[192]————— / — / —

Confidence: confirmed partial under review not found

Overlays

FH
Flood Hazard District / NFIP Floodplain Overlay
FP
Art.VII §8 (FH District, 1985 ordinance); Article VIII (airport cross-ref); NFIP participation

Properties within FEMA-mapped Special Flood Hazard Areas (SFHAs) in Montgomery County — Flood Insurance Rate Maps adopted under NFIP. Major flood corridors include Alabama River, Catoma Creek, Town Creek, and Vaughn Road watershed areas.

OCD
Old Cloverdale Historic District
HP
Montgomery City Ordinance #49-96 (December 17, 1996); Ala. Code §§11-68-1 et seq.

Old Cloverdale neighborhood, centrally located Montgomery (Cloverdale Road area). Designated December 17, 1996 per city ordinance.

AHZ-MGM
Airport Hazard Zones — Montgomery Regional Airport (MGM)
AP
1985 ordinance Article VIII (Airport Hazard Areas); Ala. Code §§4-6-1 et seq.

Properties within approach, transitional, horizontal, and conical surfaces of Montgomery Regional Airport (MGM / Dannelly Field). FAA Part 77 imaginary surfaces apply.

AICUZ-MAX
Maxwell AFB / Gunter Annex AICUZ Zones
AP
Montgomery-Maxwell AFB Joint Land Use Study (JLUS, approved June 14, 2017); DoDI 4165.57; FAA Part 77

Maxwell AFB proper and Gunter Annex are located within the City of Montgomery. JLUS Study Area encompasses approximately 10-mile radius around the installations in all directions. AICUZ noise contours (65-75 dB DNL Zone 2; ≥75 dB DNL Zone 3) and APZ-I/APZ-II accident potential zones apply to surrounding development.

TOD
TOD / Transit-Oriented Development
TOD
Not identified in 1985 ordinance or SmartCode as a formally designated TOD overlay district

No identified geographic trigger

ENV
Environmental / Aquifer / Riparian Overlay
ENV
Not identified in 1985 ordinance as a standalone environmental overlay

No identified standalone overlay

CBD
Downtown / CBD Overlay
DT
B-1-a Central Business District (1985 ordinance Art.VII §3) functions as the downtown zone; Vending District overlay (Ord. No. 5-2004) applies in defined downtown area

Central Montgomery downtown core bounded by South Court St, Commerce St, Bibb St, Molton St, Water St, North Court St, Madison Ave, Coosa St, Monroe St, North Union St, Washington Ave (per Ord. 5-2004 vending district boundary description).

COR
Corridor / Highway Overlay
COR
B-3 Highway Commercial District (1985 ordinance Art.VII §3) is the primary highway corridor district; no specific named corridor overlay for individual roads found

B-3 district applies to highway commercial corridors; no named corridor overlay (e.g., Montgomery Highway, Taylor Road) identified in 1985 ordinance index

AHB
Affordable Housing Bonus Overlay
SPD
Not identified in 1985 ordinance or SmartCode

No identified overlay

State preemptions

AL-11-52-75.1 (group home zoning)applies
Qualifying condition
Montgomery's 1985 legacy code includes multi-family districts (R-60-m, R-60-a, R-65-m, R-75-m) and the R-99-p/R-99-s mobile dwelling districts, plus SmartCode T4 and T5 transect zones which permit multi-family uses. Per Ala. Code §11-52-75.1, group homes of ≤10 unrelated persons with intellectual disabilities or mental illness must be permitted in multi-family districts statewide, subject to 1,000-ft lot-line spacing. Montgomery population: 195,818 (Census PEP 2024-07-01); threshold: statewide applies to all cities with MF districts.
Source
Ala. Code §11-52-75.1; zoning/us/alabama/preemptions.md; 1985 ordinance Article VII §2 district tables (R-60-m, R-60-a, R-65-m, R-75-m confirmed MF districts)
Effect
Montgomery cannot exclude qualifying group homes (≤10 unrelated persons with ID/MI) from R-60-m, R-60-a, R-65-m, R-75-m, R-50 (permitted on appeal), and SmartCode T4/T5 mixed-use zones. 1,000-ft spacing between group homes applies.
AL-HB281-2025 (Act 2025-331 — BZA appeal procedure)applies
Qualifying condition
Procedural preemption applies to all Alabama municipalities with a Board of Adjustment. Every Montgomery BZA appeal filed after June 1, 2025 follows the new 30-day window, de novo circuit review, and no-automatic-stay procedure. Substantive zoning standards unchanged.
Source
Ala. Code §11-52-81 as amended by HB 281 (2025RS), Act 2025-331
Effect
Sets uniform BZA appeal mechanics statewide; does not affect Montgomery's substantive zoning standards.
AL-AIRPORT-HAZARD-4-6 (Airport Hazard Zoning enabling)applies
Qualifying condition
Montgomery Regional Airport (MGM) is located within Montgomery city limits / immediate vicinity. Maxwell AFB (including Gunter Annex) is located within the City of Montgomery. Both trigger Ala. Code §4-6-8 airport hazard zoning requirements and FAA Part 77 imaginary surfaces. The 1985 ordinance Article VIII codifies Airport Hazard Areas (cited pp. 61+). The Montgomery-Maxwell AFB Joint Land Use Study (JLUS, approved June 14, 2017) applies to Maxwell AFB proper and all lands extending approximately 10 miles from the installation. Montgomery hosts two separate airport influences: (1) civilian MGM and (2) Maxwell AFB military airfield.
Source
1985 ordinance Article VIII (Airport Hazard Areas, p.61); overlays.json AL_AIRPORT_HAZARD_ZONING_4_6; overlays.json AL_MILITARY_INFLUENCE_REDSTONE_AICUZ (Maxwell AFB); Montgomery-Maxwell AFB JLUS (2017) via https://oldcc.gov/sites/default/files/2024-12/Maxwell%20Air%20Force%20Base.pdf
Effect
Height caps and airport hazard permit requirements apply in defined airport hazard zones. Maxwell AFB AICUZ noise/safety zones affect residential use suitability in surrounding areas.
AL-HISTORIC-PRESERVATION-11-68applies
Qualifying condition
Montgomery has adopted historic preservation regulation under Ala. Code §§11-68-1 et seq. The City's Architectural Review Board (ARB) reviews exterior alterations in locally designated historic districts. Old Cloverdale was designated by Montgomery City Ordinance #49-96 (December 17, 1996). Montgomery is a Certified Local Government (CLG) under the NPS program. Additionally, Montgomery is on the Selma-to-Montgomery National Historic Trail (federal non-regulatory overlay).
Source
overlays.json AL_HISTORIC_PRESERVATION_11_68; Old Cloverdale Association (https://oldcloverdale.org/historic-district-compliance/); City ARB page (https://www.montgomeryal.gov/government/city-government/city-departments/community-development/land-use-division/architectural-review-board)
Effect
Certificate of Appropriateness required for exterior alterations in designated historic districts. ARB review process applies per Ala. Code §§11-68-1 et seq.
AL-SELMA-MONTGOMERY-NHTapplies
Qualifying condition
Montgomery is the terminal city of the Selma to Montgomery National Historic Trail (P.L. 104-333 §602, 1996). City of St. Jude, Brown Chapel AME Church (Selma), and related sites are along the route. Federal NHT designation is non-regulatory; does not preempt local zoning. Noted as city_attribute trigger for heritage overlays.
Source
overlays.json AL_SELMA_MONTGOMERY_NHT_VIEWSHED; NPS (https://www.nps.gov/semo/index.htm)
Effect
Non-regulatory federal heritage trail designation. NPS consultation recommended for development near trail-related sites. No direct zoning preemption.
AL-BLACK-BELT-NHAapplies
Qualifying condition
Montgomery County is one of the 19 counties in the Alabama Black Belt National Heritage Area (P.L. 117-339, Title VIII §8001, 2022). The designation is non-regulatory partnership-based and does not impose federal land-use controls.
Source
overlays.json AL_BLACK_BELT_NHA_HERITAGE_NON_REGULATORY; NPS (https://www.nps.gov/places/alabama-black-belt-national-heritage-area.htm)
Effect
Non-regulatory federal heritage area. Authorizes NPS matching grants for heritage tourism. No zoning preemption.
Non-applicable laws (4)
AL-STR (short-term-rental local control)does_not_apply
Qualifying condition
No statewide STR preemption enacted through 2026RS adjournment (April 9, 2026). Montgomery retains full Chapter 52 authority to regulate STRs via zoning overlay or licensing.
Source
zoning/us/alabama/preemptions.md (April 2026 review); LegiScan AL 2026RS index
AL-MH (manufactured-housing zoning)does_not_apply
Qualifying condition
No state preemption of municipal MH zoning siting. Montgomery's 1985 ordinance creates dedicated mobile dwelling districts (R-99-p mobile dwelling parks, R-99-s mobile dwelling subdivisions) — a local policy choice under Chapter 52 authority. HUD Code governs construction standards; Ala. Code §40-12-255 governs taxation/registration only.
Source
Ala. Code §40-12-255; zoning/us/alabama/preemptions.md; 1985 ordinance Article VII §2 (R-99-p and R-99-s districts confirmed)
AL-ADU / AL-DENSITY / AL-IZ / AL-DESIGN-REVIEWdoes_not_apply
Qualifying condition
No statewide ADU mandate, density preemption, inclusionary zoning preemption, or design review preemption enacted through 2026RS. Alabama strict Dillon's Rule. HB 281/Act 2025-331 was procedural only (§11-52-81 BZA appeal).
Source
zoning/us/alabama/preemptions.md (April 2026 review)
AL-ACAMP (Alabama Coastal Area Management Program)does_not_apply
Qualifying condition
Montgomery is in Montgomery County (central Alabama). ACAMP applies only in Mobile and Baldwin counties (coastal area defined as continuous 10-ft contour seaward to 3-mile limit in those counties only).
Source
zoning/us/alabama/preemptions.md (ACAMP section); Ala. Code §§9-7-10 through 9-7-22

Adopted building codes

Statewide

IBC
2021
IRC
2021
NEC
2020
IFC
2021
IECC (Residential)
2015
IECC (Commercial)
2015

Click a code label to open its state-by-state adoption atlas.

Amendment history

DateKindCitation
2026-05-26retrieved at
2025-01-28supplement effectiveSmartCode adopted January 28, 2025 — SmartCode cover page (PDF accessed from Wayback: https://web.archive.org/web/20251106204157/https://www.montgomeryal.gov/home/showpublisheddocument/18542/638779752912700000)
1985-08-12last amendedAmended by City Council August 6, 1985, Effective August 12, 1985 — title page of 1985 PDF
1963-09-21adoptionAdopted by Board of City Commissioners September 17, 1963, effective September 21, 1963 — title page

Quirks & notes

  • TEMPLATE-BLEED CONFIRMED: The existing V1 profile contained fabricated district names R-1, R-2, R-30, C-1, C-2, I-1, I-2. These codes do NOT exist in Montgomery's zoning ordinance. The actual system uses lot-width-encoded names (R-125, R-100, R-85, R-75, R-65, R-60, R-50) derived from minimum lot width in feet. Fabrication was likely imported from a generic template; all V1 district dimensions have been discarded.
  • DUAL CODE SYSTEM: The 1985 legacy ordinance (Appendix C, Municode) coexists with the Jan 28, 2025 SmartCode. The GIS zoning map at gis.montgomeryal.gov still uses legacy codes (R-50, R-100, B-1 through B-5, M-1 through M-3) confirming the legacy code governs all existing parcels. SmartCode applies to new community plans only.
  • LOT-WIDTH NAMING: The digit in each residential district code equals the minimum lot width in feet (R-50 = 50 ft min, R-125 = 125 ft min). This is Montgomery's local naming convention — not density-encoded, not use-type-indexed.
  • SUFFIX VARIANTS: Residential districts have -s (single-family), -d (duplex), -m (multi-family), and -a (apartment/unlimited density) variants that share the same base lot width. R-60-m and R-60-a are the primary multi-family districts at moderate lot width.
  • MAXWELL AFB DUAL OVERLAY: Montgomery hosts both a civilian airport (MGM / Dannelly Field) and Maxwell AFB (Air University) with Gunter Annex. Both generate separate FAA Part 77 and AICUZ constraints. The 2017 JLUS is advisory; local adoption of specific compatibility standards would make AICUZ recommendations enforceable.
  • SMARTCODE TRANSECT T4 VARIANTS: Montgomery's SmartCode uses T4-R (restricted), T4-O (open), and T4-C (corridor) as sub-variants of T4, unlike the standard CNU model. T4-O and T4-C allow zero-setback front; T4-R requires 6 ft minimum.
  • PGH ZERO-LOT-LINE HOMES: PGH-35 and PGH-40 Patio-Garden Home districts allow one zero side yard — an explicit zero-lot-line form predating modern 'missing middle' policy. Unusual feature of the 1985 code.
  • CLOVERDALE HISTORIC DESIGNATION: Old Cloverdale was designated a local historic district by Ordinance #49-96 (December 17, 1996). The existing V1 profile cited 'Cloverdale Historic District' with NRHP 1985 — the NRHP date could not be confirmed in primary sources; the confirmed local designation is 1996. Cottage Hill historic designation referenced in V1 could not be independently verified as a local ordinance-based designation in this research pass.
  • SMARTCODE APPLICABILITY: The SmartCode (Jan 2025) applies to new community plans and is opt-in for individual lots (§1.3). It does not retroactively rezone existing parcels. Development of an existing R-65-s parcel continues under the 1985 legacy code unless a property owner applies to convert to SmartCode.

Formulas

Definitions

height
Maximum building height in feet as specified per district in Article VII §2-9 of the 1985 ordinance. Church steeples, flag poles, public utility poles, radio/TV towers, cooling towers, water tanks, and industrial structures required by manufacturing process are exempted from height limits per Article I §8. [confirmed §Art.I §8]
lot_coverage
Expressed as 'Maximum building area, percent of gross lot area' in the 1985 ordinance district tables. [confirmed §Art.VII §2-4]
far
du_ac
Maximum density implied by minimum lot area per dwelling unit. Not expressed as du/ac in the ordinance — derivable as 43,560 / min_lot_sf_per_unit.
setback_front
Minimum depth of front yard in feet, measured from front lot line (or future street ROW line if established) per Article I §7 general provisions. Corner lots: narrower side is treated as front regardless of main entrance location. [confirmed §Art.I §7]
setback_side
Minimum width of each side yard in feet. In R-60 and R-50 districts, asymmetric requirements apply (one side larger than the other). [confirmed §Art.VII §2]
setback_rear
Minimum depth of rear yard in feet per district tables. [confirmed §Art.VII §2-9]
parking
Expressed as car spaces per family dwelling unit (residential) or spaces per 200 sq ft gross floor area (commercial/office). [confirmed §Art.VII §2-5]

Capacity calculations

max_footprint_sf
lot_area_sf * lot_coverage_pct
max_units_lot_area
lot_area_sf / min_lot_area_per_additional_family
buildable_width_ft
lot_width_ft - setback_side_ft * 2
buildable_depth_ft
lot_depth_ft - setback_front_ft - setback_rear_ft

Massing explorer

Interactive 3D comparison across every district. Drag to orbit, scroll to zoom, use the slider to walk districts, and toggle applicable overlays in the right-side panel.

—
—
Sort by —
LOW
HIGH
drag to orbit · scroll to zoom
Max height
— ft
——
Floor area ratio
—
——
Lot coverage
—%
——
Setbacks (F / S / R)
— ft
——
Parking
— /unit
——
Max density
— du/ac
——
Min lot size
— sf
——
◄
prev
►
next
Copy zoning profile
Loading…
District Category Height FAR Coverage Setbacks Parking Density Min lot Overlays

Sources & references

Primary source
https://library.municode.com/al/montgomery/codes/code_of_ordinances?nodeId=APXCZO
Citations
  1. [1] §Art.VII §2 R-125 table
  2. [2] §Art.VII §2 R-125 table
  3. [3] §Art.VII §2 R-125 table
  4. [4] §Art.VII §2 R-125 table
  5. [5] §Art.VII §2 R-125 table
  6. [6] §Art.VII §2 R-125 table
  7. [7] §Art.VII §2 R-125 table
  8. [8] §Art.VII §2 R-100 table
  9. [9] §Art.VII §2 R-100 table
  10. [10] §Art.VII §2 R-100 table
  11. [11] §Art.VII §2 R-100 table
  12. [12] §Art.VII §2 R-100 table
  13. [13] §Art.VII §2 R-100 table
  14. [14] §Art.VII §2 R-100 table
  15. [15] §Art.VII §2 R-85 table
  16. [16] §Art.VII §2 R-85 table
  17. [17] §Art.VII §2 R-85 table
  18. [18] §Art.VII §2 R-85 table
  19. [19] §Art.VII §2 R-85 table
  20. [20] §Art.VII §2 R-85 table
  21. [21] §Art.VII §2 R-85 table
  22. [22] §Art.VII §2 R-75-s/d/m table
  23. [23] §Art.VII §2 R-75-s/d/m table
  24. [24] §Art.VII §2 R-75-s/d/m table
  25. [25] §Art.VII §2 R-75-s/d/m table
  26. [26] §Art.VII §2 R-75-s/d/m table
  27. [27] §Art.VII §2 R-75-s/d/m table
  28. [28] §Art.VII §2 R-75-s/d/m table
  29. [29] §Art.VII §2 R-75-d table
  30. [30] §Art.VII §2 R-75-d table
  31. [31] §Art.VII §2 R-75-d table
  32. [32] §Art.VII §2 R-75-d table
  33. [33] §Art.VII §2 R-75-d table
  34. [34] §Art.VII §2 R-75-d table
  35. [35] §Art.VII §2 R-75-d table
  36. [36] §Art.VII §2 R-75-m table
  37. [37] §Art.VII §2 R-75-m table
  38. [38] §Art.VII §2 R-75-m table
  39. [39] §Art.VII §2 R-75-m table
  40. [40] §Art.VII §2 R-75-m table
  41. [41] §Art.VII §2 R-75-m table
  42. [42] §Art.VII §2 R-75-m table
  43. [43] §Art.VII §2 R-65-s/d/m table
  44. [44] §Art.VII §2 R-65-s/d/m table
  45. [45] §Art.VII §2 R-65-s/d/m table
  46. [46] §Art.VII §2 R-65-s/d/m table
  47. [47] §Art.VII §2 R-65-s/d/m table
  48. [48] §Art.VII §2 R-65-s/d/m table
  49. [49] §Art.VII §2 R-65-s/d/m table
  50. [50] §Art.VII §2 R-65-m table
  51. [51] §Art.VII §2 R-65-m table
  52. [52] §Art.VII §2 R-65-m table
  53. [53] §Art.VII §2 R-65-m table
  54. [54] §Art.VII §2 R-65-m table
  55. [55] §Art.VII §2 R-65-m table
  56. [56] §Art.VII §2 R-65-m table
  57. [57] §Art.VII §2 R-60-s/d/m/a table
  58. [58] §Art.VII §2 R-60-s/d/m/a table
  59. [59] §Art.VII §2 R-60-s/d/m/a table
  60. [60] §Art.VII §2 R-60-s/d/m/a table
  61. [61] §Art.VII §2 R-60-s/d/m/a table
  62. [62] §Art.VII §2 R-60-s/d/m/a table
  63. [63] §Art.VII §2 R-60-s/d/m/a table
  64. [64] §Art.VII §2 R-60-m table
  65. [65] §Art.VII §2 R-60-m table
  66. [66] §Art.VII §2 R-60-m table
  67. [67] §Art.VII §2 R-60-m table
  68. [68] §Art.VII §2 R-60-m table
  69. [69] §Art.VII §2 R-60-m table
  70. [70] §Art.VII §2 R-60-m table
  71. [71] §Art.VII §2 R-60-a table
  72. [72] §Art.VII §2 R-60-a table
  73. [73] §Art.VII §2 R-60-a table
  74. [74] §Art.VII §2 R-60-a table
  75. [75] §Art.VII §2 R-60-a table
  76. [76] §Art.VII §2 R-60-a table
  77. [77] §Art.VII §2 R-60-a table
  78. [78] §Art.VII §2 R-50 table
  79. [79] §Art.VII §2 R-50 table
  80. [80] §Art.VII §2 R-50 table
  81. [81] §Art.VII §2 R-50 table
  82. [82] §Art.VII §2 R-50 table
  83. [83] §Art.VII §2 R-50 table
  84. [84] §Art.VII §2 R-50 table
  85. [85] §Art.VII §2 R-99-p table
  86. [86] §Art.VII §2 R-99-p table
  87. [87] §Art.VII §2 R-99-p table
  88. [88] §Art.VII §2 R-24-t/R-20-t table
  89. [89] §Art.VII §2 R-24-t/R-20-t table
  90. [90] §Art.VII §2 R-24-t/R-20-t table
  91. [91] §Art.VII §2 R-24-t/R-20-t table
  92. [92] §Art.VII §2 R-24-t/R-20-t table
  93. [93] §Art.VII §2 R-24-t/R-20-t table
  94. [94] §Art.VII §2 R-24-t/R-20-t table
  95. [95] §Art.VII §2 R-24-t/R-20-t table
  96. [96] §Art.VII §2 R-24-t/R-20-t table
  97. [97] §Art.VII §2 R-24-t/R-20-t table
  98. [98] §Art.VII §2 PGH-35/40 table
  99. [99] §Art.VII §2 PGH-35/40 table
  100. [100] §Art.VII §2 PGH-35/40 table
  101. [101] §Art.VII §2 PGH-35/40 table
  102. [102] §Art.VII §2 PGH-35/40 table
  103. [103] §Art.VII §2 PGH-35/40 table
  104. [104] §Art.VII §2 PGH-35/40 table
  105. [105] §Art.VII §2 PGH-35/40 table
  106. [106] §Art.VII §2 PGH-35/40 table
  107. [107] §Art.VII §2 PGH-35/40 table
  108. [108] §Art.VII §2 PGH-35/40 table
  109. [109] §Art.VII §2 PGH-35/40 table
  110. [110] §Art.VII §2 PGH-35/40 table
  111. [111] §Art.VII §2 PGH-35/40 table
  112. [112] §Art.VII §3 B-1-a/b table
  113. [113] §Art.VII §3 B-1-a/b table
  114. [114] §Art.VII §3 B-1-a/b table
  115. [115] §Art.VII §3 B-1-a/b table
  116. [116] §Art.VII §3 B-1-a/b table
  117. [117] §Art.VII §3 B-1-a/b table
  118. [118] §Art.VII §3 B-1-a/b table
  119. [119] §Art.VII §3 B-1-a/b table
  120. [120] §Art.VII §3 B-1-a/b table
  121. [121] §Art.VII §3 B-1-a/b table
  122. [122] §Art.VII §3 B-2/B-3 table
  123. [123] §Art.VII §3 B-2/B-3 table
  124. [124] §Art.VII §3 B-2/B-3 table
  125. [125] §Art.VII §3 B-2/B-3 table
  126. [126] §Art.VII §3 B-2/B-3 table
  127. [127] §Art.VII §3 B-2/B-3 table
  128. [128] §Art.VII §3 B-2/B-3 table
  129. [129] §Art.VII §3 B-2/B-3 table
  130. [130] §Art.VII §3 B-2/B-3 table
  131. [131] §Art.VII §3 B-2/B-3 table
  132. [132] §Art.VII §3 B-4/B-5 table
  133. [133] §Art.VII §3 B-4/B-5 table
  134. [134] §Art.VII §3 B-4/B-5 table
  135. [135] §Art.VII §3 B-4/B-5 table
  136. [136] §Art.VII §3 B-4/B-5 table
  137. [137] §Art.VII §3 B-4/B-5 table
  138. [138] §Art.VII §3 B-4/B-5 table
  139. [139] §Art.VII §3 B-4/B-5 table
  140. [140] §Art.VII §3 B-4/B-5 table
  141. [141] §Art.VII §3 B-4/B-5 table
  142. [142] §Art.VII §4 M-1/M-2/M-3 table
  143. [143] §Art.VII §4 M-1/M-2/M-3 table
  144. [144] §Art.VII §4 M-1/M-2/M-3 table
  145. [145] §Art.VII §4 M-1/M-2/M-3 table
  146. [146] §Art.VII §4 M-1/M-2/M-3 table
  147. [147] §Art.VII §4 M-1/M-2/M-3 table
  148. [148] §Art.VII §4 M-1/M-2/M-3 table
  149. [149] §Art.VII §4 M-1/M-2/M-3 table
  150. [150] §Art.VII §4 M-1/M-2/M-3 table
  151. [151] §Art.VII §4 M-1/M-2/M-3 table
  152. [152] §Art.VII §4 M-1/M-2/M-3 table
  153. [153] §Art.VII §4 M-1/M-2/M-3 table
  154. [154] §Art.VII §4 M-1/M-2/M-3 table
  155. [155] §Art.VII §4 M-1/M-2/M-3 table
  156. [156] §Art.VII §4 M-1/M-2/M-3 table
  157. [157] §Art.VII §4 M-1/M-2/M-3 table
  158. [158] §Art.VII §4 M-1/M-2/M-3 table
  159. [159] §Art.VII §4 M-1/M-2/M-3 table
  160. [160] §Art.VII §5 O-0/O-1/O-2 table
  161. [161] §Art.VII §5 O-0/O-1/O-2 table
  162. [162] §Art.VII §5 O-0/O-1/O-2 table
  163. [163] §Art.VII §5 O-0/O-1/O-2 table
  164. [164] §Art.VII §5 O-0/O-1/O-2 table
  165. [165] §Art.VII §5 O-0/O-1/O-2 table
  166. [166] §Art.VII §5 O-0/O-1/O-2 table
  167. [167] §Art.VII §5 O-0/O-1/O-2 table
  168. [168] §Art.VII §5 O-0/O-1/O-2 table
  169. [169] §Art.VII §5 O-0/O-1/O-2 table
  170. [170] §Art.VII §5 O-0/O-1/O-2 table
  171. [171] §Art.VII §5 O-0/O-1/O-2 table
  172. [172] §Art.VII §5 O-0/O-1/O-2 table
  173. [173] §Art.VII §5 O-0/O-1/O-2 table
  174. [174] §Art.VII §9 AGR-1/AGR-2 table
  175. [175] §Art.VII §9 AGR-1/AGR-2 table
  176. [176] §Art.VII §9 AGR-1/AGR-2 table
  177. [177] §Art.VII §9 AGR-1/AGR-2 table
  178. [178] §Art.VII §9 AGR-1/AGR-2 table
  179. [179] §Art.VII §9 AGR-1/AGR-2 table
  180. [180] §Art.VII §9 AGR-1/AGR-2 table
  181. [181] §Art.VII §9 AGR-1/AGR-2 table
  182. [182] §Art.VII §9 AGR-1/AGR-2 table
  183. [183] §Art.VII §9 AGR-1/AGR-2 table
  184. [184] §Art.VII §9 AGR-1/AGR-2 table
  185. [185] §Art.VII §9 AGR-1/AGR-2 table
  186. [186] §Art.VII §6 INST table
  187. [187] §Art.VII §6 INST table
  188. [188] §Art.VII §6 INST table
  189. [189] §Art.VII §1 d
  190. [190] §Art.VII §6 INST table
  191. [191] §Art.VII §8 FH
  192. [192] §Art.VII §8 FH

Research status

Publication gates

primary url presentpassedsource.primary_url = https://library.municode.com/al/montgomery/codes/code_of_ordinances?nodeId=APXCZO (Appendix C Zoning, official Municode). Legacy PDF and SmartCode PDF are secondary sources from official city domain.
no aggregator citedpassedscan clean — no Zoneomics, Steadily, SitePlanGuide, Propwire, Zonara, or Unzoned citations. All citations are to 1985 ordinance §Art.VII tables, SmartCode Table 14, Ala. Code, overlays.json, and preemptions.md.
confidence tags full formpassed142/142 confirmed fields carry §Art.VII section-and-table citations or SmartCode Table 14 citations. All partial fields carry what_is_confirmed + what_is_missing. All not_found fields carry search_performed.
overlays have parameters trigger confidencepassed8 overlay entries processed: FH confirmed with §Art.VII §8 citation; OCD confirmed with Ord.#49-96; AHZ-MGM confirmed with §Art.VIII + §4-6-8; AICUZ-MAX confirmed with JLUS 2017 + DoDI 4165.57; TOD not_found with search_performed; ENV not_found with search_performed; CBD partial with §Art.VII §3 B-1-a/b + Ord.5-2004; COR not_found with search_performed; AHB not_found with search_performed. All have parameters[], geographic_trigger, status, citation.
preempt section city specificpassed9 preemption entries with city-specific qualifying_condition_checked: §11-52-75.1 mapped to R-60-m/R-60-a/R-65-m/R-75-m/R-50 MF districts with population input (195,818); HB281/Act 2025-331 procedural; STR non-preemption confirmed; MH non-preemption confirmed with §40-12-255 reference; ADU/density/IZ/design non-preemption confirmed; ACAMP inapplicable (Montgomery County, central AL); Airport §4-6-8 applies with MGM + Maxwell specific inputs; Historic §11-68 applies with Ord.#49-96 Cloverdale confirmation; NHT and NHA federal overlays documented.

Data quality

82%completeness142 confirmed6 partial5 not found
Documented gaps
  • Cottage Hill historic district local ordinance designation not independently verified (V1 cited but not found in primary sources this pass)
  • SmartCode Article 1 §1.6 Incentives not fully extracted (affordable housing incentives unknown)
  • FH (Flood Hazard) district dimensional standards not specified in Article VII §8 beyond use restrictions
  • O-0 Office Complex dimensional standards depend on specific complex plan rules (Art.VI §10.10) — not fully extracted
  • R-99-s (Mobile Dwelling Subdivision) mobile dwelling subdivision standards partially different from R-99-p; clearances 25/20 ft vs 20/15 ft; confirmed from table but not independently detailed above
  • PUD (Planned Unit Development) dimensional standards set case-by-case by Planning Commission — no fixed table to extract

Other cities in this state

Nearest-alphabetical profiles. Click through to compare zoning patterns side-by-side.

BirminghamHuntsvilleMobile