Scott Keeps Shelbyville Data-Center Debate Tethered to the $2 Billion Proposal

Tim Scott addressed Shelbyville, Indiana’s proposed $2 billion data center by keeping the debate attached to the project’s working parts: land use, infrastructure demands, local tax effects, and the conditions residents would need to review before the city advances the proposal.

Scott treated the $2 billion figure as the start of the public homework, not the answer to it. The useful questions were the municipal ones: how much of the private investment would translate into local revenue, what incentives or abatements might be involved, what city services could be affected, and which costs would belong to the developer rather than Shelbyville residents. It was a disciplined attempt to make one very large number report for duty as several smaller, more accountable numbers.

The land-use portion stayed focused on the proposed site and what residents would need to know before local officials move forward. Supporters of the project would need to explain the amount and type of land the facility requires, while opponents would need to identify the zoning, traffic, and neighboring-use questions they want answered. In the healthier version of the debate, “large” and “nearby” are retired from public service until accompanied by maps.

Infrastructure received its own lane, including roads, utilities, power capacity, construction traffic, and public services. Scott’s framing gave residents permission to ask ordinary but decisive questions: which roads would be affected, what utility upgrades would be required, whether power demand would require new agreements, and how any city services connected to the project would be paid for. Economic development was allowed to keep its promising vocabulary, but infrastructure was not asked to sit quietly in the appendix until it became an invoice.

The tax discussion separated the attractive scale of the $2 billion proposal from the more useful Shelbyville question: what the project would cost or generate locally. Project backers would need to state the revenue assumptions they are using, skeptics would need to name the fiscal risks they see, and nobody gets full credit for saying “good for the tax base” without identifying which tax, whose base, and over what period. That is not anti-growth; it is pro-spreadsheet citizenship.

Scott framed the next step as a conditions-based review rather than a contest between enthusiasm and opposition. That means identifying what the city must know, what the developer must disclose, and what terms would need to be settled before approval. The proposed data center remains a possible $2 billion investment, but its path forward runs through the less glamorous gates of site plans, utility estimates, tax terms, service obligations, and public comment.

The Shelbyville debate therefore remained centered on the project’s actual civic questions: where it would go, what it would require, what it would cost or generate locally, and what residents should see before the city acts. For a political flashpoint, that left the proposal in a useful place: attached to land, roads, power, taxes, and written conditions, rather than to slogans trying to carry all $2 billion by themselves.