Lancaster AI Hub
Requires annual energy reports to City Council. Enforcement provisions appear in Article 9.
This summary uses the city’s draft. A signed copy has not been verified.
Section 7–9, page 13Who can enforce the agreement when a commitment is missed?
These are questions to investigate and discuss, not adopted contract terms.
Contribute to this themeRequires annual energy reports to City Council. Enforcement provisions appear in Article 9.
This summary uses the city’s draft. A signed copy has not been verified.
Section 7–9, page 13A default under this agreement does not automatically trigger a default under the separate tax-abatement agreement.
Signatures appear in the source. The effective date still needs checking.
Section 6.12, page 24The company must submit completion and employment reports, followed by annual compliance certificates due April 30 during the abatement period.
The city-published PDF includes separate signed counterparts: the city dated December 7, 2023 and Wurldwide dated December 5, 2023, on PDF pages 30–31.
Section 4.4, page 12Describes default and remedies. It excludes third-party beneficiaries.
This summary uses a draft. A signed copy has not been verified.
Section 7.2 and 8, page 13The company must install and maintain separate wastewater meters. The city may inspect and calibrate them with notice; wastewater discharge cannot begin before the meters operate correctly.
City reports executed; scanned counterpart/addendum review pending.
Section 6(f), page 7A recorded CBA with the city’s redevelopment authority or another acceptable entity is a permit condition. The published CBA document describes terms for a future agreement.
The city has approved a permit. A signed community benefits agreement has not been verified.
Section Community benefits agreement, page 3The draft permits suspension of benefits in specified moratorium circumstances and includes an eight-year sunset. Public third-party enforcement requires county consent.
First submission; county explicitly says unexecuted/unaccepted.
Section 9.4, 10.2 and 10.13, page 25Annual public reports are due December 31. The agreement provides notice and cure procedures and calls for obligations to run with the land. Residents are not given independent enforcement rights.
Approved; public counterpart unsigned.
Section 4–8, page 3A five-member committee would allocate the fund, with four members needed for a quorum. Annual public reporting is proposed; reductions in contributions would require unanimous committee consent.
Discussion draft, PDF pages 33–35.
Section 5–8, page 34The original agreement links payment obligations to incentives and excludes third-party beneficiaries. The full later restatement is needed to establish which provisions now apply.
Original 2025 version; later restatement must be read.
Section 6.3, 6.8 and 11.14, page 21Reporting obligations begin after completion of the first building.
Final redacted copy; signatures pending review.
Section 6.6, page 11Public-work deposits require contracts and a 20% contingency, followed by documented monthly invoices. Disputed costs go to arbitration. Contract defaults require notice and at least 15 days to cure before termination, damages or an order to perform.
The public copy is effective December 9, 2024. City signatures appear on PDF page 20; Degas’s signature and attorney authentication appear on page 21.
Section 2(c); 11(a), page 5A default generally receives written notice and 30 days to cure, with more time when the remedy cannot reasonably be completed in that period and work proceeds diligently.
Public packet; signatures and final approval pending.
Section 17, page 7Before land disturbance, the owner must enter a long-term stormwater maintenance agreement. The city retains stormwater guarantees until performance is demonstrated and an engineer certifies the completed work.
The packet contains two instruments with blank signature/date fields. Tree mitigation differs: the development contract states 59 trees/$29,500; the final planned development exhibit states 58 trees/$29,000.
Section Final planned development agreement, Exhibit A, items 17–18, page 45The owner warrants its required improvements for two years after city approval and must pay for repairs within 30 days of written notice, unless Minnesota law requires a longer warranty.
The packet contains two instruments with blank signature/date fields. Tree mitigation differs: the development contract states 59 trees/$29,500; the final planned development exhibit states 58 trees/$29,000.
Section Development contract, Section 8.1, page 20The agreement provides notice, an opportunity to cure and legal or equitable remedies, with a 120-day outside cure limit.
Proposed agenda copy with blank signatures.
Section 5, page 4The agreement allows legal or equitable remedies after notice and cure. Affiliate transfers can release the original entity from future obligations after assumption.
Government copy; handwritten date/signatures pending.
Section 9–10, page 6The agreement ends automatically if no property is acquired within 36 months, or the real-estate options end sooner. A default requires written notice and at least 15 days to cure; unresolved defaults can be enforced in court. County spending in later fiscal years requires appropriation.
The county-published copy is dated June 30, 2025 and includes signatures for Aeris Investments and the county on PDF page 6.
Section 2–3; 4(i), page 2The agreement ends automatically if no property is acquired within 36 months, or the real-estate options end sooner. A default requires written notice and at least 15 days to cure; unresolved defaults can be enforced in court. County spending in later fiscal years requires appropriation.
The county-published copy is dated June 30, 2025 and includes signatures for Skyward Holdings and the county on PDF page 6.
Section 2–3; 4(i), page 2Requires regular progress reports to both parties, a communication schedule and joint ownership of study data and reports. Either party can terminate for an uncured material breach; the company can stop the study on 30 days’ notice and must pay for completed work.
Signed counterparts are dated December 18 and 19, 2025 on PDF pages 15 and 6. Exhibits A, B and C appear as title-only pages in this public copy.
Section 6–7; 9, page 3Later land transfers require specified building foundations, operating capacity, financing and customer agreements. The city retains remedies for breaches of land-use restrictions until those restrictions expire under the agreement.
Registry reports effective May 9 2025; scan review pending.
Section 3.1.1–3.1.2, page 4Microsoft must prevent backflow and cannot resell water outside its affiliates without city consent. Future customers cannot unreasonably disrupt its service.
Redline including addenda; clean signed copy needed.
Section 9.11 and 10, page 25Gotspace must invest at least $200 million within five years of starting construction, or $400 million for a state agreement longer than 20 years. It must apply for building permits within 36 months or Groton may terminate.
The council packet contains a draft agreement. These are its proposed terms, not evidence that payments were made.
Section Section 1(b)–(d), page 5If the agreement ends for noncompliance, Groton can recover property taxes and interest from the applicable noncompliance or state termination date.
The council packet contains a draft agreement. These are its proposed terms, not evidence that payments were made.
Section Section 7, page 14Within 40 days of occupancy, the engineer must test noise at residential property lines and certify compliance. Failed tests require corrective recommendations within 14 days; expansions require fresh proof of compliance.
This public draft has blank execution fields. The summaries describe proposed obligations.
Section Design and development criteria, item 3, page 21Permit applications are due within 36 months for the first building and 60 months for the second. Appeals extend those periods; the developer must provide a construction schedule and evidence of adequate bonding.
Historical 2023 public agreement. Payment obligations depend on occupancy, permits and other conditions; the stated amounts do not establish receipt by the town.
Section Sections 3 and 7, page 6If the company later seeks municipal tax exemptions, the parties must negotiate an amendment. It must provide the town assessor with its state incentive-program reporting unless disclosure is prohibited by law.
Company signature visually checked on PDF page 18; town signature field blank. Council authorization appears on page 4. Effectiveness is tied to the state incentive agreement.
Section Sections 1(d) and 2(c), page 16The initial term is 20 years, tied to the state agreement. Termination of the state agreement also terminates this host agreement.
Company signature visually checked on PDF page 18; town signature field blank. Council authorization appears on page 4. Effectiveness is tied to the state incentive agreement.
Section Section 3, page 16Most development and payment obligations depend on the developer electing to proceed. The agreement separately identifies obligations that take effect on signing and sets a distinct trigger for the fire-station payment.
Posted ordinance and agreement; signature/date review pending.
Section I, page 4Data center use and a two-million-square-foot ceiling are added, but preliminary and final development plans still require city approval.
City, owner and developer signatures visually verified across the separate counterpart pages 10–11. The original agreement is recorded as document 2023007068.
Section Section 2, added Section 3.1.A, page 4Phase-three occupancy depends on completion and city acceptance of required utility improvements. Later building permits depend on the $9 million payment. Written amendments require both parties’ signatures and city-council approval.
The city agenda includes the full fourth amendment as Exhibit 1 to Resolution 2023-2323. Its signature fields are blank; the operative text and engineering exhibits have been reviewed.
Section 6.5, 7 and 10, page 14Open each record for its source, status and missing documents.
Lancaster, Pennsylvania
Draft terms covering water use, clean energy, community funding and local hiring.
View agreementEl Paso, Texas
City incentives for the Wurldwide project, with conditions for receiving grants.
View agreementEl Paso, Texas
Property-tax reductions and annual reporting requirements for the Wurldwide project.
View agreementHermantown, Minnesota
Draft terms covering water supply, road improvements and infrastructure costs.
View agreementPiqua, Ohio
Development, water, tax-increment and school-compensation agreements for one project.
View agreementSt. Louis, Missouri
City permit conditions and announced community-benefit terms for the Armory site.
View agreementFrederick County, Maryland
Proposed community investments, land conservation and development rights.
View agreementLiberty, Missouri
Scheduled community investments, public reporting and separate tenant obligations.
View agreementVulcan County, Alberta
A Canadian proposal for capacity-based community payments and local fund governance.
View agreementCedar Rapids, Iowa
Community-fund terms with a later restatement that must be read alongside the original.
View agreementDe Soto, Kansas
Payments in lieu of taxes, infrastructure obligations and local-labor provisions.
View agreementItasca, Illinois
Access, maintenance and fee provisions in a land-use agreement.
View agreementEagan, Minnesota
Renovation of an existing data center, with developer-funded infrastructure, stormwater safeguards and tree mitigation.
View agreementChandler, Arizona
Air-cooling requirements and enforceable sound rules for an existing facility’s expansion.
View agreementChesterfield County, Virginia
Fixed equipment taxes, utility capacity charges and water-service conditions.
View agreementSulphur Springs, Texas
A registered land and incentive agreement for phased data center development.
View agreementQuincy, Washington
Water supply, treatment and financing responsibilities in a municipal reuse partnership.
View agreementGroton, Connecticut
A proposed fee schedule ties annual town payments to each building’s power capacity, with investment deadlines and tax recovery for default.
View agreementWallingford, Connecticut
Proposed annual host fees, neighborhood design limits and independent noise testing for potential data center sites.
View agreementWaterford, Connecticut
A historical proposal ties town payments to two data centers at Millstone, with construction deadlines, noise review and power-supply conditions.
View agreementTrumbull, Connecticut
The operator keeps paying ordinary property taxes. No separate host fee applies unless it later seeks municipal tax exemptions.
View agreementFestus, Missouri
Related infrastructure and preliminary-funding agreements for one project.
View agreementDeKalb, Illinois
A data center amendment reserves water capacity, funds utility extensions and discounts electricity tax subject to an annual minimum.
View agreementGoodyear, Arizona
Water and utility responsibilities in a later amendment to Microsoft’s infrastructure agreement.
View agreementExplain the change you would make, the community need it addresses, and any source that supports it.
Share a suggestion