Corrections
Correction · 11 September 2026 · internal review
Record → Statewide count
Changed correction
From Ohio's consumer advocate repeats a commercial directory count. It is useful as a market signal, but the underlying unit can include buildings, suites and campuses and is not a state census. DataCenterData does not adopt 200+ as its own count.
To Added the wording difference between OCC's web fact sheet and its PDF fact sheet. Verdict unchanged.
Why Added the wording difference between OCC's web fact sheet and its PDF fact sheet. Verdict unchanged.
Evidence Evidence →
Correction · 11 September 2026 · internal review
Record → Power / rates
Changed correction
From The PUCO-approved AEP Ohio tariff allocates substantial underuse and cancellation risk to new loads over 25 MW. That is real protection against stranded distribution investment; it is not proof that generation, transmission or wholesale-market costs can never affect household bills.
To Added how the 85% minimum-demand term works by contract size and AEP's count of pre-tariff contracted load. Verdict unchanged. The 72.5% and 82.5% shares are DataCenterData arithmetic from AEP's published formula (15,000 kW plus 85% above 25,000 kW up to 75,000 kW; 57,500 kW plus 100% above 75,000 kW; capped at 85% of contract capacity).
Why Added how the 85% minimum-demand term works by contract size and AEP's count of pre-tariff contracted load. Verdict unchanged. The 72.5% and 82.5% shares are DataCenterData arithmetic from AEP's published formula (15,000 kW plus 85% above 25,000 kW up to 75,000 kW; 57,500 kW plus 100% above 75,000 kW; capped at 85% of contract capacity).
Evidence Evidence →
Correction · 11 September 2026 · internal review
Record → Water / permits
Changed correction
From Draft Ohio data-center general NPDES permit treated as if it were a final, measured water authorization.
To Ohio EPA said on July 21, 2026 that it would not finalize draft OHD000001 and would continue with individual NPDES permits. A permit is not measured discharge.
Why Correction chronology uses the recorded date, not the 21 July agency-event date.
Evidence Evidence →
Correction · 11 September 2026 · internal review
aws-new-carlisle → permanent jobs
Changed correction
From At least 1,000 baseline; AWS's own July 2026 account says nearly 1,000 operations staff hired; an undated Chamber project page says 1,056 full-time AWS employees
To 2026-09-11: status was 'supported-as-delivered' with value 'At least 1,000 baseline; 1,056 full-time AWS employees later reported'. The company-linked counts sit on either side of the baseline (AWS op-ed: 'We have also hired nearly 1,000 operations staff so far'; Chamber page: '1,056 full-time AWS employees', undated), so the reviewed record does not support a delivery conclusion. Evidence level unchanged.
Why 2026-09-11: status was 'supported-as-delivered' with value 'At least 1,000 baseline; 1,056 full-time AWS employees later reported'. The company-linked counts sit on either side of the baseline (AWS op-ed: 'We have also hired nearly 1,000 operations staff so far'; Chamber page: '1,056 full-time AWS employees', undated), so the reviewed record does not support a delivery conclusion. Evidence level unchanged.
Evidence Evidence →
Correction · 11 September 2026 · internal review
coreweave-hammond → expansion design
Changed locator-changed
From Previous locator
To pp. 3–11 (resolution 25R-16 introduced p. 3; lease, jobs, tax terms and community impact payment p. 4; NIPSCO contingency p. 6)
Why 2026-09-11: previously 'pp. 3–4'.
Evidence Evidence →
Correction · 11 September 2026 · internal review
coreweave-hammond → permanent jobs
Changed locator-changed
From Previous locator
To pp. 3–11 (resolution 25R-16 introduced p. 3; lease, jobs, tax terms and community impact payment p. 4; NIPSCO contingency p. 6)
Why 2026-09-11: previously 'pp. 3–4'.
Evidence Evidence →
Correction · 11 September 2026 · internal review
coreweave-hammond → community impact payments
Changed locator-changed
From Previous locator
To pp. 3–11 (resolution 25R-16 introduced p. 3; lease, jobs, tax terms and community impact payment p. 4; NIPSCO contingency p. 6)
Why 2026-09-11: previously 'pp. 3–4'.
Evidence Evidence →
Correction · 11 September 2026 · internal review
coreweave-hammond → community impact payments
Changed locator-changed
From Previous locator
To pp. 1–4 ($80 million community-payment total p. 1; $25 million announced p. 2; 'Right now it's not part of it' p. 4); extension resolution at p. 10
Why 2026-09-11: previously 'pp. 1–2; extension resolution at p. 10'.
Evidence Evidence →
Correction · 11 September 2026 · internal review
coreweave-hammond → additional payment
Changed locator-changed
From Previous locator
To pp. 1–4 ($80 million community-payment total p. 1; $25 million announced p. 2; 'Right now it's not part of it' p. 4); extension resolution at p. 10
Why 2026-09-11: previously 'pp. 1–2; extension resolution at p. 10'.
Evidence Evidence →
Correction · 11 September 2026 · internal review
coreweave-hammond → incentives
Changed locator-changed
From Previous locator
To pp. 3–11 (resolution 25R-16 introduced p. 3; lease, jobs, tax terms and community impact payment p. 4; NIPSCO contingency p. 6)
Why 2026-09-11: previously 'pp. 3–4'.
Evidence Evidence →
Correction · 11 September 2026 · internal review
coreweave-hammond → incentives
Changed locator-changed
From Previous locator
To pp. 1–4 ($80 million community-payment total p. 1; $25 million announced p. 2; 'Right now it's not part of it' p. 4); extension resolution at p. 10
Why 2026-09-11: previously 'pp. 1–2; extension resolution at p. 10'.
Evidence Evidence →
Correction · 11 September 2026 · internal review
coreweave-hammond → power agreement
Changed locator-changed
From Previous locator
To pp. 3–11 (resolution 25R-16 introduced p. 3; lease, jobs, tax terms and community impact payment p. 4; NIPSCO contingency p. 6)
Why 2026-09-11: previously 'pp. 3–4'.
Evidence Evidence →
Correction · 11 September 2026 · internal review
coreweave-hammond → power agreement
Changed locator-changed
From Previous locator
To pp. 1–4 ($80 million community-payment total p. 1; $25 million announced p. 2; 'Right now it's not part of it' p. 4); extension resolution at p. 10
Why 2026-09-11: previously 'pp. 1–2; extension resolution at p. 10'.
Evidence Evidence →
Correction · 11 September 2026 · internal review
microsoft-la-porte → Incentives
Changed correction
From 35-year state sales-tax exemption for at least $1B eligible capital, with possible extensions; local and NIPSCO incentives referenced but not yet reconciled.
To Minutes record unanimous adoption of R-3-2026 under a title describing rescission of the 2024 taxpayer agreement and termination of its tax abatement; adopted resolution text not obtained; IEDC DATA exemption pending.
Why Correction chronology uses the recorded date 2026-09-11; the source event date remains 2026-03-02.
Evidence Evidence →
Correction · 11 September 2026 · internal review
microsoft-la-porte → incentives_commitments
Changed correction
From 35-year state sales-tax exemption for at least $1B eligible capital, with possible extensions; local and NIPSCO incentives referenced but not yet reconciled.
To The 2 March 2026 council minutes record unanimous adoption of Resolution R-3-2026, whose agenda title describes rescission of the 2024 Microsoft taxpayer agreement, including termination of the tax abatement. DataCenterData has not obtained the adopted resolution text and therefore does not independently state its full legal effect. IEDC showed the state DATA exemption as a pending accepted offer when checked.
Why Primary municipal minutes record introduction and unanimous adoption of R-3-2026.
Correction · 11 September 2026 · internal review
Record → ohio-claim-checks.json:ohio-water-permit
Changed correction
From Draft Ohio data-center general NPDES permit treated as if it were a final, measured water authorization.
To Ohio EPA said on July 21 it would not finalize draft OHD000001 and would continue with individual NPDES permits. A draft permit is not measured discharge.
Why Stable public citation for the agency's July 21 notice.
Correction · 11 September 2026 · internal review
Changed correction
From Unknown pending parcel resolution
To Licking
Why County GIS parcels resolve the three campus counties. County is a typed field and may not hold a sentence.
Evidence Licking County parcel records for Google, Meta and Vantage OH1 New Albany campuses →
Correction · 11 September 2026 · internal review
microsoft-la-porte → stable_id
Changed correction
From Two Indiana project registers with different IDs for the same projects (microsoft-la-porte-1 vs microsoft-la-porte; digital-crossroads-hammond vs coreweave-hammond counted as parallel eights).
To One Indiana project file. microsoft-la-porte is canonical (alias microsoft-la-porte-1). Digital Crossroads Hammond is the campus; CoreWeave Hammond is the child expansion project; DX-1 remains the operating facility.
Why Remove the duplicate Indiana project authority before any further state expansion.
Correction · 11 September 2026 · internal review
Record → indianapolis_appendix
Changed correction
From Previous wording
To 2026-09-11: publisher was 'Indianapolis Metropolitan Development Commission filing' and kind 'municipal case record containing an existing Indianapolis facility list'.
Why 2026-09-11: publisher was 'Indianapolis Metropolitan Development Commission filing' and kind 'municipal case record containing an existing Indianapolis facility list'.
Evidence None recorded
Correction · 11 September 2026 · internal review
databank-cle1 → facility location
Changed correction
From Previous wording
To 2026-09-11: suite and ZIP added from the cited DataBank page ('1255 Euclid Ave Suite #200 - Cleveland, OH 44115'); CLE1 is a suite in a multi-tenant building, so the building should be counted once if other providers there are added.
Why 2026-09-11: suite and ZIP added from the cited DataBank page ('1255 Euclid Ave Suite #200 - Cleveland, OH 44115'); CLE1 is a suite in a multi-tenant building, so the building should be counted once if other providers there are added.
Evidence None recorded
Correction · 11 September 2026 · internal review
Changed correction
From Previous value
To County resolved from Licking County parcel records. County is a typed field and may not hold a sentence.
Why County resolved from Licking County parcel records. County is a typed field and may not hold a sentence.
Evidence None recorded
Correction · 11 September 2026 · internal review
Changed correction
From Previous value
To County resolved from Licking County parcel records. County is a typed field and may not hold a sentence.
Why County resolved from Licking County parcel records. County is a typed field and may not hold a sentence.
Evidence None recorded
Correction · 11 September 2026 · internal review
vantage-oh1-new-albany → county
Changed correction
From Previous value
To County resolved from Licking County parcel records. County is a typed field and may not hold a sentence.
Why County resolved from Licking County parcel records. County is a typed field and may not hold a sentence.
Evidence None recorded
Correction · 11 September 2026 · internal review
Changed correction
From Previous wording
To 2026-09-11: previously 'Thousands of construction jobs and hundreds of full-time positions; company projection'. Quantified figures are from the FAQ answer 'How many jobs will this project create?' on https://q.com/data-centers/van-wert/.
Why 2026-09-11: previously 'Thousands of construction jobs and hundreds of full-time positions; company projection'. Quantified figures are from the FAQ answer 'How many jobs will this project create?' on https://q.com/data-centers/van-wert/.
Evidence None recorded
Correction · 11 September 2026 · internal review
Changed correction
From Previous value
To previously '35-year state sales-tax exemption for at least $800M eligible capital, with extensions tied to additional eligible investment up to 50 years.' The $800M figure is the announcement's wording; the executed agreement (Exhibit A, section 2.A, page 13 of 18) says $845,000,000. The IEDC portal's separate 'expected qualified investment' field ($830M) is a different field and is not used here.
Why previously '35-year state sales-tax exemption for at least $800M eligible capital, with extensions tied to additional eligible investment up to 50 years.' The $800M figure is the announcement's wording; the executed agreement (Exhibit A, section 2.A, page 13 of 18) says $845,000,000. The IEDC portal's separate 'expected qualified investment' field ($830M) is a different field and is not used here.
Evidence None recorded
Correction · 11 September 2026 · internal review
Changed correction
From Previous value
To The Common Council minutes record 'Motion/Vote – Adopt Resolution R-3-2026' and say the motion was unanimously carried. The LEAP director states that the resolution refers to the taxpayer agreement approved in 2024 with Microsoft.
Why The Common Council minutes record 'Motion/Vote – Adopt Resolution R-3-2026' and say the motion was unanimously carried. The LEAP director states that the resolution refers to the taxpayer agreement approved in 2024 with Microsoft.
Evidence None recorded
Correction · 11 September 2026 · internal review
Changed correction
From Previous value
To status was 'Approved; construction not verified' while the only linked source was the petitioner's appendix, which shows a request rather than a decision. The verification source is now the commission's hearing results. Prior verification_url: https://indianapolis-in.municodemeetings.com/sites/indianapolis-in.municodemeetings.com/files/fileattachments/mdc_hearing_examiner/meeting/5368/2025-cap-856_2025-cvr-856_petitioner_appendix_mdc_3-18-26_final.pdf; prior verified_fields: local filing, cooling claim, cost commitment.
Why status was 'Approved; construction not verified' while the only linked source was the petitioner's appendix, which shows a request rather than a decision. The verification source is now the commission's hearing results. Prior verification_url: https://indianapolis-in.municodemeetings.com/sites/indianapolis-in.municodemeetings.com/files/fileattachments/mdc_hearing_examiner/meeting/5368/2025-cap-856_2025-cvr-856_petitioner_appendix_mdc_3-18-26_final.pdf; prior verified_fields: local filing, cooling claim, cost commitment.
Evidence None recorded
Correction · 11 September 2026 · internal review
aws-new-carlisle → permanent_jobs
Changed correction
From Previous value
To status was 'supported-as-delivered' with value 'At least 1,000 baseline; 1,056 full-time AWS employees later reported'. The company-linked counts sit on either side of the baseline, so the reviewed record does not support a delivery conclusion.
Why status was 'supported-as-delivered' with value 'At least 1,000 baseline; 1,056 full-time AWS employees later reported'. The company-linked counts sit on either side of the baseline, so the reviewed record does not support a delivery conclusion.
Evidence None recorded
Lifecycle events
acquisition · databank-cle1
DataBank says it acquired the Cleveland facility from 365 Data Centers in 2017. The former operator is history, not a second facility.
acquisition · stack-nal01-oh
STACK announced acquisition of a New Albany campus containing an existing purpose-built Tier III data center. The reviewed record does not establish whether that building is today's NAL01A or NAL01B.
operator portfolio addition · expedient-cmh3
Expedient announced that it added the former Nationwide facility to its portfolio in 2024. Nationwide remained the landlord while Expedient took operational control.
energization · google-fort-wayne
Indiana Michigan Power told the IURC that the site was energized in November 2024. The same 2026 order says Google had begun operation while construction continued, but it does not date the start of operation to November 2024.
development agreement approved · coreweave-hammond
Hammond approved a development agreement for a proposed CoreWeave-occupied expansion at 301 Digital Crossroads.
partial operation · aws-new-carlisle
Amazon says the multi-site Project Rainier compute cluster is operational and identifies New Carlisle as one site. Full New Carlisle campus completion is not established.
groundbreaking · meta-lebanon
Meta and Indiana reported the Lebanon campus groundbreaking. Operation and promised outcomes are not yet due or established by this event.
groundbreaking · microsoft-la-porte
Microsoft reported groundbreaking in La Porte. Its job and cooling statements remain projections or design claims rather than observed outcomes.
agreement expired · coreweave-hammond
Hammond says required milestones were not satisfied and the expansion agreement expired after two extensions. The existing DX-1 facility remains a separate operating record.
Machine-readable files: corrections.json and lifecycle-events.json.