Facility or project event · Development plan approved · Official record
Development plan approved on 15 December 2025: STACK Infrastructure — NAL01B (New Albany, OH) — planning commission minutes dated 15 December 2025
The New Albany Planning Commission voted 5-0 to approve, with conditions, final development plan FDP-96-2025 (PLFDP20250096) for a new two-story, approximately 330,000 sq ft STACK Infrastructure data center on the east side of Souder Road (parcel 222-005106); applicant EMH&T c/o Nicholas Ovens.
- Event date
- Minutes of the Monday, December 15, 2025 meeting record the roll-call vote; the appended action record also says action was taken 12/15/2025.
- Source dated
- Minutes header 'Monday, December 15, 2025 Meeting Minutes - Approved' (approval date of the minutes not shown); action letter in the appendix dated December 16, 2025; PDF created 2026-01-22.
- Source accessed
- Retrieved by DataCenterData; not an event date.
- Added to Latest updates
- When this entry entered the updates log; not an event date.
- Event type
- Development plan approved · Approvals
- Evidence basis
- Official record · New Albany Planning Commission
- Confidence
- HighVote, plan number, parcel and date are in the approved minutes and the commission's action record.
- State
- Ohio
- Linked records
- STACK Infrastructure — NAL01B
stack-nal01b - Linked claims
- None linked
What the source says
Upon roll call: Mr. Schell yes, Mr. Kirby yes, Mr. Wallace yes, Mr. Larsen yes, Ms. Briggs yes. Having five yes votes the motion passed and FDP-96-2025 was approved.
Where: PDF p. 3, section VI Cases, FDP-96-2025 motion and roll call; appendix action record 'Final Development Plan, PLFDP20250096 was Approved with Conditions, by a vote of 5-0'
Internet Archive copy (captured 21 September 2026)
What this does not establish
- Construction start
- Operation
Still unknown
- Building permit status
- Construction start
- Which STACK building designation (DCD uses NAL01B) the city plan corresponds to beyond the parcel match
Identifiers
Event ID c927451d149848b0167536951effa1fdc041f870863637520dad9d88c62fbaed. The ID is derived from the event itself and never changes. A later correction would be published as a separate, linked entry.