Public statement checked
Answer
Verdict on the wording above: Outdated It referred to a date, trigger or plan that has since passed or lapsed; newer evidence not yet checked. Not a finding that it is now false. How verdicts work →
- Who stated it
- Said by the City of Hammond · government record · 10 June 2025 →
- What the evidence establishes
- Stated 10 June 2025; it referred to a plan, deadline or agreement that has since passed or lapsed. Development agreement expired; expansion not delivered. It was accurate as of the date shown as far as the record goes; this is not a finding that it is now false.
- Biggest limitation
- Exact unsatisfied milestones.
- Checked
- 11 September 2026 · Next review: replacement proposal, new NIPSCO docket or new development agreement · History (1) →
Evidence
What the evidence supports
Development agreement expired; expansion not delivered.
Still unknown
Exact unsatisfied milestones.
Sources
-
City of Hammond → Archived copy Gov. record
Exact location https://www.gohammond.com/hammond-approves-development-agreement-for-new-data-center/
What it supports Approval, proposed building, tenant, power requirement and contingencies.
-
Hammond Common Council minutes, 9 June 2025 → Archived copy Gov. record
Exact location pp. 3–11 (resolution 25R-16 introduced p. 3; lease, jobs, tax terms and community impact payment p. 4; NIPSCO contingency p. 6)
What it supports Proposal, contemplated lease, jobs, tax terms, community payments and explicit power-agreement gating.
Corrections and history
Correction · 11 September 2026 · DataCenterData review
coreweave-hammond → 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'.
Review details
Scope
- Unit
- expansion design
- Geography
- CoreWeave / Digital Crossroads expansion
- Period
- None recorded
- Confidence
- medium — city-approved proposal
- Kind
- Public statement checked
Conflicting evidence
None recorded when this claim was checked. That records what we logged, not a finding that no conflicting record exists.
Outdated — the as-of date is not recorded. This is not a finding that it is now false.
Chronology
- Stated by City of Hammond
- Published — City of Hammond
- 2 sources retrieved
- Changed source locator recorded
- Checked by DataCenterData
- Date not established Next review: replacement proposal, new NIPSCO docket or new development agreement
Data
Suggest a correction
Suggest a correction → Claim ID claim:coreweave-hammond:expansion-design and this page are prefilled. Accepted material corrections appear publicly on Changes.