Tax-Sharing, Abatements, and the Number Nobody Photographs

Now the balance sheet. A data center is, from a local government's perspective, an enormous pile of taxable property: land, buildings, and above all the equipment inside, which depreciates but is initially worth staggering sums. The servers, the transformers, the cooling plant. In many jurisdictions this personal property is taxable, and the tax on it dwarfs anything a community investment fund will ever hold. This is the real negotiation, and it's conducted in the language of abatements, exemptions, and payments in lieu of taxes.

Start with why abatements exist. Data centers are mobile in the sense that they choose their location, and jurisdictions compete for them by offering to reduce or eliminate the tax on that equipment for a period, often ten to twenty years. The operator's pitch is straightforward: without the abatement, we build elsewhere, and you get nothing, so a reduced tax on a facility that exists beats full tax on a facility that doesn't. Sometimes that's true. Sometimes it's a bluff, because the site was chosen for power and fiber and water reasons that no other jurisdiction can match, and the operator was always going to build there. The community's job is to figure out which, and most communities can't, because they don't have the analytical capacity and the operator does. That asymmetry is the whole story of how towns give away more than they had to.

The instrument to understand is the payment in lieu of taxes, the PILOT. Instead of paying the full assessed property tax, the operator negotiates a fixed or formula-based annual payment. A PILOT can be a good deal for both sides if it's structured with discipline: it gives the operator predictability and the community a guaranteed, escalating revenue stream that doesn't depend on annual reassessment fights over fast-depreciating equipment. The danger is a PILOT set too low and locked too long. Twenty years is a long time to be bound to a number negotiated when the community didn't fully understand what it was giving up. Read for the escalator and the term, same discipline as the host agreement.

Here's the modeling every community should do and few do. Take the facility's full assessed value. Apply the normal tax rate. That's the tax the operator would owe with no abatement, call it the gross liability. Now subtract what they'll actually pay under the abatement or PILOT. The difference, summed over the life of the deal, is the subsidy the community is granting. Put that number next to the community investment fund and the host agreement payments. In nearly every deal I've examined, the tax subsidy is several times larger than all the visible benefits combined. The community is giving up, say, eighty million in forgone tax over twenty years to receive twenty million in fund and host payments. That can still be a good deal if the alternative was genuinely nothing, but the community should at least know the ratio it's accepting, and most don't, because nobody made them do the subtraction.

Tax-sharing among jurisdictions adds another layer. Property tax often splits among overlapping bodies: county, school district, city, special districts. An abatement negotiated by the county can gut the school district's revenue, and the school district may not even be at the table. Data centers strain local schools less than housing developments do, since they employ few people, so the schools sometimes come out ahead even with an abatement, but only if the deal is structured to protect their share. The sophisticated arrangement carves out the school district's portion, abating only the county and city shares, so the schools receive closer to full value. Watch who's at the table and whose revenue is being spent by someone else, because the body that negotiates is often not the body that pays.

The rate-impact question belongs here too. Residents fear that a facility drawing hundreds of megawatts will raise their electricity bills, either by straining supply or by socializing the cost of grid upgrades built to serve the data center across all ratepayers. This is sometimes real. The enforceable answer is a clause requiring the operator to bear the cost of dedicated interconnection and grid upgrades directly rather than through the general rate base, plus a rate-impact study. It's not strictly a tax term, but it lives in the same fiscal conversation, and it's often the objection that actually motivates the retired schoolteacher at the microphone.

The empiricist's closing instruction: measure the whole flow. Add up the tax subsidy granted, subtract the host payments received, subtract the fund, subtract the value of in-kind infrastructure the community actually keeps, and adjust for the rate impact. That net figure, discounted over the life of the facility, is whether the community came out ahead. It's not a number anyone photographs. It's the only number that tells the truth, and the towns that compute it before they vote are the towns that stop losing at the planning commission.