NickO Report
CitiesExplore

Project history · Sandy Springs · RZ22-0003

Residential Townhouse

Follow the official record for case RZ22-0003: filings, scheduled hearings, recorded actions and the reporting that connects them.

Dated records · Jul 27, 2026

Official record ↗

Case summary

This retained record is not automatically updated. Check the linked official sources and related reporting for later developments.

A proposal or recommendation does not establish approval.

What is proposed
Residential TownhouseSource · page 6 ↗
Recorded outcome
approvedSource · page 3 ↗
Planning recommendation
approvalSource · page 3 ↗
Existing zoning in this record
RD-18Source · page 1 ↗
Site area (acres)
1.15Source · page 7 ↗
Housing units listed
2Source · page 10 ↗
Staff recommendation
approvalSource · page 5 ↗
Requested zoning
RT-3Source · page 5 ↗

Some details have no verified date. Their source links remain available.

Final-decision evidence is incomplete. The timeline may contain individual actions or recommendations. Check the official record for the complete decision and any later action.

Zoning definitions

RD-18 · RD-18
RD-18 18,000 sf* 100 30 50 20 10 35 3/40*Official code citation ↗
RT-3 · Residential Townhouse
The Residential Townhouse district is intended for neighborhood-scale development including single unit attached and neighborhood unit residences on individual lots.Official code citation ↗

Case timeline

Oldest to newest, using dates in the official sources. Scheduled hearings do not establish that a hearing took place.

  1. filedOfficial filing record

    Official evidence linked · Official record ↗

Supporting records

These facts and documents have no separately verified date for the timeline. Dates mentioned in their text retain their original context.

NickO Report archive

Reporting history

Newest published first. Each article reflects what was known at publication. Reports are linked by verified case identity or a source-cited reference to this case; an article may discuss more than one case.

  1. Published · Case reporting

    Sandy Springs filing centers on residential Townhouse →

    The accepted official record for RZ22-0003 lists proposal purpose as Residential Townhouse.

  2. Published · Case reporting

    Sandy Springs filing involves residential Townhouse →

    The accepted official record for RZ22-0003 lists proposal purpose as Residential Townhouse.

  3. Published · Case reporting

    Sandy Springs files a rezoning request for residential Townhouse →

    An official Sandy Springs filing identifies RZ22-0003 as a rezoning request for residential Townhouse.

  4. Published · Case reporting

    Sandy Springs rezoning request for residential Townhouse is approved →

    The accepted official record for RZ22-0003 lists final outcome as approved.

  5. Published · Case reporting

    Sandy Springs rezoning request for Residential Townhouse is approved →

    The accepted official record for RZ22-0003 lists final outcome as approved.

  6. Published · Case reporting

    Sandy Springs files a rezoning request for Residential Townhouse →

    An official Sandy Springs filing identifies RZ22-0003 as a rezoning request for Residential Townhouse.

  7. Published · Case reporting

    Sandy Springs staff recommends approval →

    The accepted official record for RZ22-0003 lists staff recommendation as approval.

  8. Published · Case reporting

    Sandy Springs filing involves Residential Townhouse →

    The accepted official record for RZ22-0003 lists proposal purpose as Residential Townhouse.

  9. Published · Case reporting

    Sandy Springs files a rezoning request →

    An official Sandy Springs filing identifies RZ22-0003 as a rezoning request.

  10. Published · Case reporting

    Sandy Springs files a rezoning case →

    An official Sandy Springs filing identifies RZ22-0003 as a rezoning case.

  11. Published · Case reporting

    Sandy Springs: RZ22-0003 — new filing for a rezoning case →

    An official Sandy Springs filing identifies RZ22-0003 for a rezoning case.

Source coverage

This history grows as official records are verified and reporting is published. It may not include every filing or later action. An absent record does not mean an action never occurred.

Source follow-up: Source Gap.

Missing records

  • Agenda — missing from our current sources
  • Final decision — missing from our current sources
  • Hearing — missing from our current sources
  • Minutes — missing from our current sources
  • Recommendation — missing from our current sources

Case coverage

Covered means we have linked official evidence for that step. Source gap means we track that type of record but have not verified it for this case.

  1. Filing / applicationCovered
    Exact accepted official evidence is linked to this case.
  2. Agenda / hearingCovered
    An accepted official hearing-date fact is linked to this case.
  3. Packet + attachmentsSource gap
    The launch source declares this checkpoint, but no exact case-linked evidence is accepted yet.
  4. Minutes + voteSource gap
    The launch source declares this checkpoint, but no exact case-linked evidence is accepted yet.
  5. Recommendation / decisionCovered
    An accepted official outcome fact is linked to this case.
  6. Follow-up changeSource gap
    The launch source declares this checkpoint, but no exact case-linked evidence is accepted yet.
Document coverage details
Packet incompleteNo packet or attachment evidence links are available.The launch source declares this checkpoint, but no exact case-linked evidence is accepted yet.

Filings, agendas and recommendations are not final decisions. Methodology →