What changed, and why.

Correction · 21 September 2026 · Editorial classification update

Sabey — Decatur Technology Park → Power / cost allocation

Field Power / cost allocation

From Partially supported

To Unknown

Why A developer-authored, site-specific commitment does not establish statewide customer protection. The question now separates what the petitioner promised from what remains unknown.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 21 September 2026 · Editorial classification update

Meta — Lebanon → City impact payment

Field City impact payment

From Supported

To Not independently verified

Why The economic-development announcement establishes that the term was announced, but the controlling agreement and any payment records remain unavailable.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 16 September 2026 · Editorial classification update

Meta — Jeffersonville → Cooling + water

Field Cooling + water

From Company claim

To Unknown

Why The page tests a common inference about what the announcement establishes; Meta did not make the cooling-and-water statement shown.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 14 September 2026 · Editorial classification update

Record → Power / rates

Field Power / rates

From Not independently verified

To Partially supported

Why The tariff supports part of the risk-allocation claim, but it does not prove that generation, transmission or wholesale-market costs can never affect household bills.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 14 September 2026 · Editorial classification update

Meta — Lebanon → City impact payment

Field City impact payment

From Not independently verified

To Supported

Why The government announcement supports the stated term. It does not establish an executed agreement, a due date or any payment received.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 14 September 2026 · Editorial classification update

Meta — Lebanon → Permanent jobs

Field Permanent jobs

From Not independently verified

To Company claim

Why The figure is a company projection; neither cited announcement is an observed payroll or employment record.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 14 September 2026 · Editorial classification update

Sabey — Decatur Technology Park → Power / cost allocation

Field Power / cost allocation

From Not independently verified

To Partially supported

Why The cited commitment supports cost allocation for one site, but it cannot establish the statewide generalization shown.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 14 September 2026 · Editorial classification update

AWS — New Carlisle → State incentives

Field State incentives

From Not independently verified

To Supported

Why The government announcement, portal fields and agreement support the carefully limited description of authorized terms. They do not prove delivery, jobs or completed investment.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 14 September 2026 · Editorial classification update

AWS — New Carlisle → Project status

Field Project status

From Not independently verified

To Unknown

Why This card tests a common inference, not an attributed outside statement. The operating milestone still does not establish completion of every planned building or the full campus.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 14 September 2026 · Editorial classification update

Meta — Lebanon → Investment

Field Investment

From Not independently verified

To Company claim

Why The exact investment figure is a Meta projection. The government announcement repeats it but does not establish completed or placed-in-service capital.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 14 September 2026 · Editorial classification update

Meta — Lebanon → State sales-tax exemption

Field State sales-tax exemption

From Not independently verified

To Supported

Why The government announcement supports the stated term. It does not establish the controlling agreement or exemptions actually claimed.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 14 September 2026 · Editorial classification update

Microsoft — La Porte → Jobs / timing

Field Jobs / timing

From Not independently verified

To Contradicted

Why The claim says the projected jobs already exist, while the cited company source still describes a forecast and the government source describes a different job scope.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 14 September 2026 · Editorial classification update

Meta — Lebanon → Construction jobs

Field Construction jobs

From Not independently verified

To Company claim

Why The peak construction-jobs figure is a company projection, not an observed workforce count or job-years measure.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 14 September 2026 · Editorial classification update

Meta — Lebanon → Water / cooling

Field Water / cooling

From Not independently verified

To Unknown

Why The prior label is defined for an unverified statement by a non-company party. This card tests a common inference instead; the reviewed company source does not establish annual or total campus water use.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 12 September 2026 · Software-assisted second check

AWS — New Carlisle → Project status

Field Project status

From Partially supported

To Not independently verified

Why The operating Project Rainier milestone does not establish completion of every planned New Carlisle building or the full campus.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 12 September 2026 · Software-assisted second check

Record → Taxes / incentives

Field Taxes / incentives

From Partially supported

To Contradicted

Why The reviewed statute remains in force, and the reported pause concerns new requests rather than repeal or cancellation of existing agreements.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 12 September 2026 · Software-assisted second check

Record → Taxes / incentives

Field Taxes / incentives

From Partially supported

To Contradicted

Why The statute authorizes a complete or partial equipment sales-and-use-tax exemption; it does not establish that a qualifying project pays no taxes.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 12 September 2026 · Software-assisted second check

Meta — Lebanon → Water / cooling

Field Water / cooling

From Partially supported; unknowns not recorded

To Not independently verified; operating water unknowns and the future design scope are explicit

Why The second review found that a literal zero-water conclusion is not established by Meta's narrower future design statement.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 12 September 2026 · Software-assisted second check

Sabey — Decatur Technology Park → Power / cost allocation

Field Power / cost allocation

From Partially supported

To Not independently verified

Why One site's cost commitment cannot establish the statewide claim shown.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 12 September 2026 · Software-assisted second check

Microsoft — La Porte → Jobs / timing

Field Jobs / timing

From Not yet due

To Not independently verified

Why The 600-plus first-phase forecast has no retrieved due date; the 2032 date belongs to a different 200-job scope.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 12 September 2026 · Software-assisted second check

Record → Power / rates

Field Power / rates

From Partially supported; framed as stranded distribution investment

To Not independently verified; scope narrowed to AEP Ohio and infrastructure/transmission risk

Why The second review found that the tariff supports risk allocation but not the absolute household-bill conclusion, and PUCO's own description is not limited to distribution.

Evidence re-reading of the sources already cited on this claim; no new source.

Correction · 3 November 2026 · DataCenterData review

QTS Data Centers — New Albany 1 campus → Record

Field Record

To Status wording now rests on QTS's U.S. locations page because the campus page no longer carries the In Development label. Lifecycle status unchanged; no opening or energization date is established.

Evidence No additional evidence link; see the linked record or claim.

Correction · 3 November 2026 · DataCenterData review

Microsoft — New Albany campus → Record

Field Record

To Updated from Microsoft's October 2026 construction update, which reports early construction works complete. Lifecycle status unchanged; the update does not establish operation.

Evidence No additional evidence link; see the linked record or claim.

Correction · 3 November 2026 · DataCenterData review

QTS Data Centers — New Albany 1 DC2 → Record evidence

Field Record evidence

To Status wording now rests on QTS's U.S. locations page because the campus page no longer carries the In Development label. Lifecycle status unchanged; no operating milestone inferred.

Evidence No additional evidence link; see the linked record or claim.

Correction · 3 November 2026 · DataCenterData review

QTS Data Centers — New Albany 2 DC2 → Record evidence

Field Record evidence

To Status wording now rests on QTS's U.S. locations page because the campus page no longer carries the In Development label. Lifecycle status unchanged; no operating milestone inferred.

Evidence No additional evidence link; see the linked record or claim.

Correction · 3 November 2026 · DataCenterData review

QTS Data Centers — New Albany 2 campus → Record

Field Record

To Status wording now rests on QTS's U.S. locations page because the campus page no longer carries the In Development label. Lifecycle status unchanged; no opening or energization date is established.

Evidence No additional evidence link; see the linked record or claim.

Correction · 3 November 2026 · DataCenterData review

QTS Data Centers — New Albany 2 DC1 → Record evidence

Field Record evidence

To Status wording now rests on QTS's U.S. locations page because the campus page no longer carries the In Development label. Lifecycle status unchanged; no operating milestone inferred.

Evidence No additional evidence link; see the linked record or claim.

Correction · 3 November 2026 · DataCenterData review

QTS Data Centers — New Albany 1 DC1 → Record evidence

Field Record evidence

To Status wording now rests on QTS's U.S. locations page because the campus page no longer carries the In Development label. Lifecycle status unchanged; no operating milestone inferred.

Evidence No additional evidence link; see the linked record or claim.

Correction · 27 October 2026 · DataCenterData review

Gilroy Data Center → Physical scale

Field Physical scale

To Restored the City's approximate qualifier for the planned Phase I building area: approximately 218,000 square feet. This corrects DCD's wording; it does not report a change to the project or an operating measurement.

Evidence No additional evidence link; see the linked record or claim.

Correction · 18 October 2026 · DataCenterData review

Record → Policy record: City of Oakland, California: interim data-center moratorium effective 6 October 2026 (27-0050)

Field Policy record: City of Oakland, California: interim data-center moratorium effective 6 October 2026 (27-0050)

From Recorded as adopted with effective status unverified; the effective date, duration and expiration remained unverified.

To The City Clerk Notice and Digest posted with file 27-0050 states adoption on 6 October 2026 with immediate effect. Recorded as in effect from 6 October 2026. The final ordinance text, scope and exceptions have not been independently read, and no expiration date is recorded for the 45-day term the digest describes.

Why Log the 18 October 2026 status update, which was published without a change-log row; this row was added on 30 October 2026.

Evidence Oakland City Clerk Notice and Digest for file 27-0050 →

Correction · 18 October 2026 · DataCenterData review

Record → Policy record: City of Milwaukee, Wisconsin: temporary data-center pause effective 17 October 2026 (File 251924)

Field Policy record: City of Milwaukee, Wisconsin: temporary data-center pause effective 17 October 2026 (File 251924)

From Milwaukee File 251924 (temporary data-center pause) described as proposed.

To Milwaukee's official matter record shows passage on 13 October 2026, signing on 14 October, publication on 16 October and effect on 17 October 2026. Recorded as in effect. The enacted Substitute 2 text and its final scope and exceptions have not been reviewed, and no expiration date is recorded.

Why Log the 18 October 2026 status update, which was published without a change-log row; this row was added on 30 October 2026.

Evidence Milwaukee Common Council File 251924 (Legistar) →

Correction · 13 October 2026 · DataCenterData review

Record → Policy record: City of Oakland, California: interim data-center moratorium effective 6 October 2026 (27-0050)

Field Policy record: City of Oakland, California: interim data-center moratorium effective 6 October 2026 (27-0050)

From Oakland file 27-0050 described as proposed and not adopted.

To The Council’s official record reports passage on 6 October 2026. Recorded as adopted with effective status unverified; the effective date, duration and expiration remain unverified.

Why Correct the outdated proposed status using the official matter page while preserving unknown legal effect and final terms.

Evidence Oakland City Council file 27-0050: recorded passage on 6 October 2026 →

Correction · 12 October 2026 · Editorial classification update

Vantage Data Centers — OH2 Millersport campus → Power / developer claim

Field Power / developer claim

From The evidentiary hearing is noticed for 17 September 2026.

To The previously reviewed notice scheduled the hearing for 17 September 2026; outcome and certificate remain unverified, with follow-up overdue.

Why Clarified historical notice and unresolved follow-up. No factual outcome, source date, substantive check date or company verdict changed.

Evidence https://fairfieldenergycenter.com/home/utility-facility →

Correction · 12 October 2026 · Editorial classification update

Vantage Data Centers — OH2 Millersport campus → OPSB / generation status

Field OPSB / generation status

From Application pending; hearing noticed for 2026-09-17. The evidentiary hearing is noticed for 17 September 2026.

To Proposal in evidence checked 17 September 2026; subsequent outcome unverified. The previously reviewed notice scheduled the hearing for September 17.

Why Replaced apparently upcoming hearing wording with historical context. No certificate, hearing outcome or factual review-date refresh established.

Evidence https://fairfieldenergycenter.com/home/utility-facility →

Correction · 9 October 2026 · DataCenterData review

Vantage Data Centers — OH1 campus → Location.address

Field Location.address

To Added the campus address printed on the independently reviewed Vantage OH1 page; preserved the competing Johnstown discovery label.

Evidence No additional evidence link; see the linked record or claim.

Correction · 3 October 2026 · DataCenterData review

Record → Power / rates

Field Power / rates

From The PUCO-approved AEP Ohio tariff allocates substantial underuse and cancellation risk to new loads over 25 MW. PUCO describes the concern as cost shifting from significant transmission infrastructure and other underused investment serving data centers. These protections are real, but the reviewed sources do not prove that residents can never be affected by generation, transmission, wholesale-market or pre-tariff costs. Under AEP's published contract-capacity formula, DataCenterData calculates a minimum of about 72.5% at 50 MW and 82.5% at 100 MW; a separate historical-demand ratchet can produce a higher billed demand. AEP reports that 12,219 of 17,861 MW of contracted data-center projects were signed before the tariff took effect; contracted projects are not current measured load.

To The PUCO-approved AEP Ohio tariff allocates substantial underuse and cancellation risk to new loads over 25 MW. PUCO describes the concern as cost shifting from significant transmission infrastructure and other underused investment serving data centers. These protections are real, but the reviewed sources do not prove that residents can never be affected by generation, transmission, capacity-market, wholesale-market or pre-tariff costs. The current Schedule DCT sheets (Ohio Power Company tariff P.U.C.O. No. 22, 1st Revised Sheets 223-1 to 223-8, issued and effective 28 August 2026 under the Commission's 1 April 2026 rate-case order and its 5 August 2026 order in Case No. 26-113-EL-ATA) set the minimum demand for new load after the ramp period at 15,000 kW plus 85% of the amount over 25,000 kW (25,001 to 75,000 kW) and 57,500 kW plus 100% of the amount over 75,000 kW, capped at 85% of total contract capacity; from that table DataCenterData calculates a minimum of about 72.5% at 50 MW and 82.5% at 100 MW, and a separate ratchet on the highest billing demand of the past 11 months can produce a higher billed demand. New-load contracts run for the load ramp period plus 8 years. Sheet 223-5 carries the interim standard-service-offer procedures the Commission granted on 5 August 2026: a Schedule DCT customer returning to the standard service offer must give 180 days' notice, AEP Ohio runs a separate procurement for that load at the customer's full cost, and if notice is not given AEP Ohio assigns the full cost of PJM spot-market purchases solely to that customer. The PUCO docket lists a 30 September 2026 entry denying the applications for rehearing of that order. AEP reports that 12,219 of 17,861 MW of contracted data-center projects were signed before the tariff took effect; contracted projects are not current measured load.

Why Cited the current Schedule DCT sheets (1st Revised Sheets 223-1 to 223-8, issued and effective 28 August 2026) for the minimum-demand table, the 85% cap and the Load Ramp Period plus 8 years term, and Sheet 223-5 for the interim standard-service-offer procedures; cited the PUCO docket listing for the 5 August 2026 order and the 30 September 2026 rehearing denial. Verdict unchanged. Household-bill, generation, transmission, capacity-market and pre-tariff-contract effects stay open; the missing documents are a PUCO or OCC household-bill analysis and the order texts.

Evidence https://www.aepohio.com/lib/docs/ratesandtariffs/Ohio/October_2026_Ohio_Power_Tariff_Book.pdf →

Correction · 1 October 2026 · DataCenterData review

Record → Policy record: Chicago, Illinois: adopted data center benchmarking ordinance; effect unverified

Field Policy record: Chicago, Illinois: adopted data center benchmarking ordinance; effect unverified

From Chicago Substitute Ordinance SO2026-0027165 (data center benchmarking and disclosure) described as proposed.

To The City Clerk's final matter record reports passage on 23 September 2026 as substituted and amended. Recorded as adopted with effect unverified; the final amended text and its effective clause have not been read.

Why Log the 1 October 2026 status update, which was published without a change-log row; this row was added on 30 October 2026.

Evidence Chicago City Clerk matter SO2026-0027165 →

Correction · 21 September 2026 · DataCenterData review

CoreWeave / Digital Crossroads expansion → Additional payment

Field Additional payment

From Minutes say it was not yet in the agreement.

To Discussed, not contracted, then the agreement lapsed. The 22 December 2025 minutes record the $25 million as announced but 'Right now it's not part of it'. The City announced on 1 July 2026 that the development agreement had expired after two extensions. No payment is shown as due or received in the saved record.

Why City of Hammond notice of 1 July 2026: the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026. The authorized terms (Resolution 25R-16, 8–0, 9 June 2025) are now recorded as lapsed; no payment, incentive or NIPSCO agreement is shown in the saved record. Verdict unchanged.

Evidence https://www.gohammond.com/hammond-announces-expiration-of-data-center-development-agreement/ →

Correction · 21 September 2026 · DataCenterData review

CoreWeave / Digital Crossroads expansion → Incentives

Field Incentives

From Claimed or received amounts not established.

To Authorized terms, then lapsed. The 9 June 2025 minutes describe the contemplated 10-year construction abatement and 20-year 100% technology deduction alongside the development agreement adopted by Resolution 25R-16 (8–0, one member absent); the scope and terms of the CoreWeave equipment deduction and the Decennial construction abatement requested at the same meeting were not part of that resolution's vote and are not reviewed. The City announced on 1 July 2026 that the agreement had expired after two extensions. No abatement or deduction is shown as adopted, claimed or received in the saved record.

Why City of Hammond notice of 1 July 2026: the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026. The authorized terms (Resolution 25R-16, 8–0, 9 June 2025) are now recorded as lapsed; no payment, incentive or NIPSCO agreement is shown in the saved record. Verdict unchanged.

Evidence https://www.gohammond.com/hammond-announces-expiration-of-data-center-development-agreement/ →

Correction · 21 September 2026 · DataCenterData review

CoreWeave / Digital Crossroads expansion → Community impact payments

Field Community impact payments

From Not shown due or paid.

To Authorized, then lapsed. The Common Council adopted Resolution 25R-16 approving the development agreement on 9 June 2025 by an 8–0 roll-call vote (one member absent); the 22 December 2025 minutes record an extension. The City announced on 1 July 2026 that the agreement for 301 Digital Crossroads had expired after two extensions because milestones were not satisfied by the 30 June 2026 deadline. No community impact payment is shown as due or received in the saved record, and the notice does not concern the operating DX-1 facility, which is a separate record.

Why City of Hammond notice of 1 July 2026: the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026. The authorized terms (Resolution 25R-16, 8–0, 9 June 2025) are now recorded as lapsed; no payment, incentive or NIPSCO agreement is shown in the saved record. Verdict unchanged.

Evidence https://www.gohammond.com/hammond-announces-expiration-of-data-center-development-agreement/ →

Correction · 21 September 2026 · Editorial classification update

Meta — Lebanon → City impact payment

Field City impact payment

From $1.5 million annually per completed phase, up to six phases

To Meta will make a $1.5 million annual city payment for each completed phase, up to six phases.

Why The revised wording tests the future payment described in IEDC's announcement while distinguishing it from an executed agreement or delivered payment.

Evidence No additional evidence link; see the linked record or claim.

Correction · 21 September 2026 · DataCenterData review

CoreWeave / Digital Crossroads expansion → Power agreement

Field Power agreement

From No executed agreement located; exact failed milestones undisclosed.

To The 9 June 2025 minutes describe a final NIPSCO agreement as gating the expansion. No executed NIPSCO agreement is in the saved record, and the City's 1 July 2026 notice says the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026, without naming which. The NIPSCO agreement remains unknown. The notice does not concern the operating DX-1 facility, which is a separate record.

Why City of Hammond notice of 1 July 2026: the development agreement expired after two extensions because milestones were not satisfied by 30 June 2026. The authorized terms (Resolution 25R-16, 8–0, 9 June 2025) are now recorded as lapsed; no payment, incentive or NIPSCO agreement is shown in the saved record. Verdict unchanged.

Evidence https://www.gohammond.com/hammond-announces-expiration-of-data-center-development-agreement/ →

Correction · 21 September 2026 · Editorial classification update

Sabey — Decatur Technology Park → Power / cost allocation

Field Power / cost allocation

From One Indianapolis developer cost commitment proves no Indiana data center can affect other customers' electricity costs.

To What electricity-system costs has the Sabey Indianapolis petitioner committed to cover, and does that establish statewide customer protection?

Why The prior wording framed a universal inference without citing anyone who made it. The replacement is an answerable research question.

Evidence No additional evidence link; see the linked record or claim.

Correction · 17 September 2026 · Editorial classification update

Vantage Data Centers — OH2 Millersport campus → OPSB / generation status

Field OPSB / generation status

From The source link used an OPSB case-summary URL that now returns 404.

To The working source link now opens Fairfield Energy's live project page, which identifies OPSB case 26-0160-EL-BGN.

Why The historical OPSB summary is described as preserved evidence rather than presented as a working page; the official case-summary URL returns 404 and the Docketing Information System rejected a direct case request during this check.

Evidence https://fairfieldenergycenter.com/home/utility-facility →

Correction · 17 September 2026 · Editorial classification update

Vantage Data Centers — OH2 Millersport campus → Power / developer claim

Field Power / developer claim

From The source link used an OPSB case-summary URL that now returns 404.

To The working source link now opens Fairfield Energy's live project page, which identifies OPSB case 26-0160-EL-BGN.

Why The historical OPSB summary is described as preserved evidence rather than presented as a working page; the official case-summary URL returns 404 and the Docketing Information System rejected a direct case request during this check.

Evidence https://fairfieldenergycenter.com/home/utility-facility →

Correction · 16 September 2026 · Editorial classification update

Google The Dalles → Cooling + water

Field Cooling + water

From Google The Dalles: Mixed evidence

To Google says The Dalles aquifer project added more than 100 million gallons a year of stored-water capacity for the community.

Why A source re-read replaced a generated status label with the exact company claim and separated community storage capacity from data-center water use.

Evidence No additional evidence link; see the linked record or claim.

Correction · 16 September 2026 · Editorial classification update

Meta — Jeffersonville → Cooling + water

Field Cooling + water

From Meta Jeffersonville: Not verifiable

To Meta's Jeffersonville announcement establishes the campus's cooling design and water use.

Why A source re-read converted a generated status label into the exact inference being tested and restored a concise unit boundary.

Evidence No additional evidence link; see the linked record or claim.

Correction · 16 September 2026 · Editorial classification update

Microsoft Mount Pleasant → Cooling + water

Field Cooling + water

From Microsoft Mount Pleasant: Announced

To Microsoft says its Mount Pleasant pilot will use closed-loop chip-level cooling without evaporating water for cooling.

Why A source re-read replaced a generated status label with the exact company claim and restored a concise unit boundary.

Evidence No additional evidence link; see the linked record or claim.

Correction · 16 September 2026 · Editorial classification update

Google — Fort Wayne → Cooling + water

Field Cooling + water

From Google Fort Wayne: Not verifiable

To The reviewed utility order establishes Google Fort Wayne's cooling design and water use.

Why A source re-read converted a generated status label into the exact inference being tested and restored a concise unit boundary.

Evidence No additional evidence link; see the linked record or claim.

Correction · 12 September 2026 · Software-assisted second check

Vantage Data Centers — OH2 Millersport campus → Power / developer claim

Field Power / developer claim

From Only company descriptions of the proposed adjacent power facility were cited.

To The preserved official OPSB case summary is cited separately from the developer's differing generation and storage figures.

Why Primary-record follow-up confirmed the proposal and hearing date while preserving the unresolved MW discrepancy and outcome hold.

Evidence https://fairfieldenergycenter.com/home/utility-facility →

Correction · 12 September 2026 · Software-assisted second check

Record → Water / permits

Field Water / permits

From The direct Ohio EPA decision notice had not been retrieved.

To The preserved official Ohio EPA Community Notice is cited with its dated heading and exact page location.

Why Primary-record follow-up recovered the agency's own notice, and the second review re-read it; a later live recheck was unavailable and is not treated as a retraction.

Evidence https://epa.ohio.gov/divisions-and-offices/surface-water/permitting/npdes-general-permits →

Correction · 12 September 2026 · Software-assisted second check

Record → Water

Field Water

From The evidence link opened the report landing page and described the unit as million US gallons.

To The evidence link opens the report PDF, cites the exact p. 97 table, and uses its printed unit, million gallons.

Why Independent re-extraction confirmed the three Google-reported Ohio rows without turning company reporting into municipal measurement.

Evidence https://sustainability.google/files/google-2026-environmental-report.pdf →

Correction · 12 September 2026 · Software-assisted second check

AWS — New Carlisle → State incentives

Field State incentives

From The contract split was held because no independent retrieval was recorded.

To Five Project 424567 portal instruments and the DATA agreement are cited with exact fields and contract locators.

Why The second review reproduced the portal records while preserving the difference between authorized terms, portal fields, and observed outcomes.

Evidence https://transparencyportal.iedc.in.gov/viewtaxgrantloancontract/8c0f68149feaee11904d001dd8306d4e →

Correction · 12 September 2026 · DataCenterData review

AWS — New Carlisle → Incentives commitments

Field Incentives commitments

To IEDC Project 424567 portal instruments and the DATA agreement were independently retrieved and separated by program, status, field name and contractual condition.

Evidence No additional evidence link; see the linked record or claim.

Correction · 12 September 2026 · DataCenterData review

STACK Infrastructure — NAL01B → Lifecycle status

Field Lifecycle status

To Changed from construction to approved. The city record establishes final development-plan approval, while the reviewed sources do not establish a construction start.

Evidence No additional evidence link; see the linked record or claim.

Correction · 12 September 2026 · Software-assisted second check

Microsoft Quincy → Cooling + water

Field Cooling + water

From Microsoft Quincy: Supported as delivered; combined measures and a 2021-2022 observation window

To EPA documents an operating reuse system; distinct estimates and dated observations are separated

Why The second review separated estimated savings, canal makeup and potable makeup share and removed an unsupported original-publication year.

Evidence No additional evidence link; see the linked record or claim.

Correction · 12 September 2026 · Software-assisted second check

Vantage Data Centers — OH1 campus → Opening status

Field Opening status

From The tested opening proposition was attributed directly to Vantage Data Centers.

To The proposition is labeled as a common reading; Vantage is cited only for its December 2025 opening target.

Why The operator page states a forecast and does not claim that the first building opened or is operating.

Evidence https://vantage-dc.com/data-center-locations/north-america/new-albany-ohio →

Correction · 12 September 2026 · DataCenterData review

EdgeConneX — New Albany location → Lifecycle status

Field Lifecycle status

To Corrected operating to construction. The prior basis itself said operation was not established; city records support an active building project and groundbreaking, not operation.

Evidence No additional evidence link; see the linked record or claim.

Correction · 12 September 2026 · Software-assisted second check

Record → Taxes / jobs

Field Taxes / jobs

From Statewide tax/jobs scope; underlying operator not specified

To One unnamed New Albany hyperscaler, tax year 2024 payable 2025; city-reported comparison

Why The second review narrowed the place, taxpayer and time scope and made the missing underlying records explicit.

Evidence No additional evidence link; see the linked record or claim.

Correction · 12 September 2026 · DataCenterData review

Sabey — Decatur Technology Park → Lifecycle status

Field Lifecycle status

To Changed from construction to approved. The commission record establishes approval subject to commitments, but no reviewed primary source establishes that construction began.

Evidence No additional evidence link; see the linked record or claim.

Correction · 12 September 2026 · Software-assisted second check

Record → Statewide count

Field Statewide count

From The directory denominator can include buildings, suites and campuses; March 2026 PDF

To The directory unit and deduplication are unreconciled; retained March-path PDF differs from the live page's current May-path target

Why The second review removed an unsupported description of the directory denominator and distinguished URL-path timing from publication date.

Evidence No additional evidence link; see the linked record or claim.

Correction · 12 September 2026 · Software-assisted second check

Vantage Data Centers — OH2 Millersport campus → OPSB / generation status

Field OPSB / generation status

From The claim cited only Fairfield Energy's application description.

To The claim now separates the preserved OPSB summary's 1,300/1,000 MW figures from Fairfield Energy's 1,350/1,040 MW figures.

Why The official and company summaries disagree; neither is converted to data-center IT capacity and the underlying filing remains unavailable.

Evidence https://fairfieldenergycenter.com/home/utility-facility →

Correction · 11 September 2026 · DataCenterData review

Record → Power / rates

Field Power / rates

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).

Evidence https://www.aepohio.com/company/about/rates/data-center-tariff/ →

Correction · 11 September 2026 · DataCenterData review

CyrusOne — CIN2 → Record evidence

Field Record evidence

To address was null ('address unresolved'). The current CyrusOne CIN2 page gives no street address; CyrusOne's archived CIN2 page (Internet Archive capture 2023-11-29, https://web.archive.org/web/20231129155948/https://www.cyrusone.com/data-centers/north-america/ohio/cin2-cincinnati) gives '229 West 7th St., Cincinnati'. A directory lead lists a 209-229 W 7th St range; the building extent is not resolved.

Why address was null ('address unresolved'). The current CyrusOne CIN2 page gives no street address; CyrusOne's archived CIN2 page (Internet Archive capture 2023-11-29, the cited source gives '229 West 7th St., Cincinnati'. A directory lead lists a 209-229 W 7th St range; the building extent is not resolved.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

AWS — New Carlisle → Permanent jobs

Field Permanent jobs

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.

Evidence https://iedc.in.gov/events/news/details/2024/04/25/gov.-holcomb-announces-amazon-web-services-plans-to-invest-11b-to-create-a-new-data-center-campus-in-northern-indiana →

Correction · 11 September 2026 · DataCenterData review

Google — New Albany campus → County

Field County

To County resolved from Licking County parcel records. County is a typed field and may not hold a sentence.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

QTS Data Centers — New Albany 1 DC1 → Record evidence

Field Record evidence

To locality resolved from the current Licking County parcel record; no operating milestone inferred.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

Record → Water / permits

Field Water / permits

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 https://www.clermontsun.com/2026/07/22/ohio-epa-will-not-finalize-proposed-data-center-general-permit →

Correction · 11 September 2026 · DataCenterData review

Microsoft — La Porte → Incentives

Field Incentives

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 https://www.cityoflaporte.com/uploads/minutes/m_1932_Council-Mar.2-2026-Minutes.docx →

Correction · 11 September 2026 · DataCenterData review

Meta — New Albany campus / Prometheus expansion → County

Field County

To County resolved from Licking County parcel records. County is a typed field and may not hold a sentence.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

CoreWeave / Digital Crossroads expansion → Additional payment

Field Additional payment

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 https://www.gohammond.com/document_library/meeting_minutes_and_agendas/city_council/2025/12-22-25_minutes.pdf →

Correction · 11 September 2026 · DataCenterData review

Google — Fort Wayne → Record

Field Record

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.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

Lumen Indianapolis 1 → Record evidence

Field Record evidence

To evidence_tier was 'municipal-list-only' and status 'Listed in municipal appendix; current service scope not verified'. The only source is a petitioner's exhibit whose list cites DataCenterMap; no Lumen first-party or government record for this site was found.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

STACK Infrastructure — NAL01A → Record evidence

Field Record evidence

To address resolved from the current Franklin County parcel record.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

DataBank — CLE1 → Facility location

Field Facility location

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.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

Microsoft — La Porte → Record

Field Record

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.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

STACK Infrastructure — NAL01B → Record evidence

Field Record evidence

To address and approval status resolved from the city planning record and current county parcel record; no construction milestone inferred.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

Record → Indianapolis appendix

Field Indianapolis appendix

To 2026-09-11: publisher was 'Indianapolis Metropolitan Development Commission filing' and kind 'municipal case record containing an existing Indianapolis facility list'.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

CoreWeave / Digital Crossroads expansion → Incentives

Field Incentives

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 https://www.gohammond.com/document_library/meeting_minutes_and_agendas/city_council/2025/06-09-25_minutes.pdf →

Correction · 11 September 2026 · DataCenterData review

QTS Data Centers — Van Wert campus → Jobs

Field Jobs

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 the cited source

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

Record → Statewide count

Field Statewide count

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.

Evidence https://occ.ohio.gov/factsheet/quick-facts-data-centers-ohio →

Correction · 11 September 2026 · DataCenterData review

CoreWeave / Digital Crossroads expansion → Power agreement

Field Power agreement

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 https://www.gohammond.com/document_library/meeting_minutes_and_agendas/city_council/2025/12-22-25_minutes.pdf →

Correction · 11 September 2026 · DataCenterData review

Vantage Data Centers — OH1 campus → County

Field County

To County resolved from Licking County parcel records. County is a typed field and may not hold a sentence.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

CoreWeave / Digital Crossroads expansion → Incentives

Field Incentives

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 https://www.gohammond.com/document_library/meeting_minutes_and_agendas/city_council/2025/12-22-25_minutes.pdf →

Correction · 11 September 2026 · DataCenterData review

CoreWeave / Digital Crossroads expansion → Power agreement

Field Power agreement

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 https://www.gohammond.com/document_library/meeting_minutes_and_agendas/city_council/2025/06-09-25_minutes.pdf →

Correction · 11 September 2026 · DataCenterData review

AWS — New Carlisle → Permanent jobs

Field Permanent jobs

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.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

CoreWeave / Digital Crossroads expansion → Expansion design

Field Expansion design

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 https://www.gohammond.com/document_library/meeting_minutes_and_agendas/city_council/2025/06-09-25_minutes.pdf →

Correction · 11 September 2026 · DataCenterData review

Lumen Indianapolis 2 → Record evidence

Field Record evidence

To evidence_tier was 'municipal-list-only' and status 'Listed in municipal appendix; current service scope not verified'. The only source is a petitioner's exhibit whose list cites DataCenterMap; no Lumen first-party or government record for this site was found.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

CoreWeave / Digital Crossroads expansion → Community impact payments

Field Community impact payments

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 https://www.gohammond.com/document_library/meeting_minutes_and_agendas/city_council/2025/06-09-25_minutes.pdf →

Correction · 11 September 2026 · DataCenterData review

CoreWeave / Digital Crossroads expansion → Community impact payments

Field Community impact payments

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 https://www.gohammond.com/document_library/meeting_minutes_and_agendas/city_council/2025/12-22-25_minutes.pdf →

Correction · 11 September 2026 · DataCenterData review

Sabey — Decatur Technology Park → Record

Field Record

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 source: 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 fields with recorded verification: 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 source: the cited source prior fields with recorded verification: local filing, cooling claim, cost commitment.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

Flexential — Cincinnati → Record evidence

Field Record evidence

To address was null ('address unresolved'). Flexential's Cincinnati page (Internet Archive capture 2025-03-28, https://web.archive.org/web/20250328101315/https://www.flexential.com/data-centers/oh/cincinnati/data-center) gives '5307 Muhlhauser Rd, West Chester, OH 45011' and a 43,551 sq ft data-center footprint; the live page refuses automated requests and was not retrieved again. Whether one or two buildings stand at the address is unresolved.

Why address was null ('address unresolved'). Flexential's Cincinnati page (Internet Archive capture 2025-03-28, the cited source gives '5307 Muhlhauser Rd, West Chester, OH 45011' and a 43,551 sq ft data-center footprint; the live page refuses automated requests and was not retrieved again. Whether one or two buildings stand at the address is unresolved.

Evidence No additional evidence link; see the linked record or claim.

Correction · 11 September 2026 · DataCenterData review

CoreWeave / Digital Crossroads expansion → Permanent jobs

Field Permanent jobs

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 https://www.gohammond.com/document_library/meeting_minutes_and_agendas/city_council/2025/06-09-25_minutes.pdf →

Correction · 11 September 2026 · DataCenterData review

Microsoft — La Porte → Incentives commitments

Field Incentives commitments

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.

Evidence La Porte Common Council minutes, March 2, 2026 →

Correction · 11 September 2026 · DataCenterData review

Microsoft — La Porte → Stable id

Field Stable id

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.

Evidence DataCenterData coherent-core registry →

Correction · 11 September 2026 · DataCenterData review

Record → Ohio-claim-checks.json:ohio-water-permit

Field Ohio-claim-checks.json:ohio-water-permit

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.

Evidence Ohio EPA will not finalize proposed data-center general permit (agency notice republished by The Clermont Sun) →

Correction · 11 September 2026 · DataCenterData review

Google — New Albany campus → County

Field County

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 →