How a Council Member Defends a TIF Vote

A council member told us that she’d voted yes on a TIF and spent the following eight months regretting how she’d explained it. Not the vote. The explanation. A resident at a town hall asked why the city was writing a check to a developer, and she gave an answer that was technically correct, ran ninety seconds, and convinced nobody.

That’s the part of this job I think gets underestimated. The vote takes a minute. Defending it takes two years. And the difference between a vote you can defend and one you can’t is mostly decided before the packet is final, not after.

So here’s what I’d want in front of me if I were sitting in that seat.

The Objection You’ll Actually Hear

It won’t be a technical question. It’ll be some version of: you gave our tax money to a developer.

The most useful thing to know is that the premise is wrong, and you can say so plainly. TIF doesn’t create a new tax or raise anyone’s rate. It doesn’t redirect a dollar of revenue the city is currently collecting. The property’s existing assessed value — the base — keeps flowing to the city, the county, the schools, everyone, exactly as it does today.

What gets pledged is the increment: the additional taxes generated by value that doesn’t exist yet and won’t exist unless the project gets built.

That’s a sentence worth memorizing. We are not redirecting existing revenue. We are pledging revenue the project itself creates.

The Follow-Up: “What If It Fails?”

This is the harder one, and the honest answer depends entirely on how your bonds are structured. Which is why you need to know the answer before the vote rather than at the town hall.

If the bonds are general obligations backed by the city’s full faith, credit, and taxing power, then a shortfall is a general fund problem, and you should say so.

If the bonds are developer-backed and non-recourse — payable solely from pledged increment — the answer is different and much better. The city isn’t pledging its credit or taxing power. The obligation doesn’t count against your constitutional or statutory debt limits. If the increment underperforms, the developer and its lender absorb it, because that’s the risk they priced for.

Then there’s the piece that’s newest and least understood. Legislation in a number of states now lets the developer sign a taxpayer agreement: a binding commitment to cover any shortfall between actual increment and scheduled debt service, recorded against the property and enforced in the same manner as delinquent property taxes.

The distinction matters more than it sounds. Most redevelopment agreements already contain some developer backstop. But an unsecured promise is worth whatever the developer’s balance sheet is worth on the day you need to collect — and if the project is struggling, that’s the day it’s weakest. A recorded lien is a claim on the land itself.

So ask this before you vote: is the developer’s shortfall obligation a promise, or is it recorded? If you can answer that in one sentence at a town hall, you’ve handled the hardest question you’ll get.

“This Hurts Our Schools”

Expect this one, especially from parents and anyone on the school board.

The base keeps flowing to every taxing body, including the district. Several states go further and protect school levies from capture outright — Kansas, for instance, shields 20 mills for schools and 1.5 for the state. Your state may have a comparable carve-out; find out which before the meeting.

And the counterfactual is worth stating out loud: if the project doesn’t get built, there’s no increment for anyone to share. The school district isn’t losing revenue it would otherwise have received.

“You’re Locking Us In Forever”

You’re not, and the statute says so. TIF allocation periods are capped by state law and typically run somewhere between fifteen and thirty years depending on the state and the type of district. When the period ends, all of it — including what was the increment — flows back to the taxing bodies.

Taxpayer agreements are also voluntary in every state that has adopted them. One state expressly prohibits an agency from conditioning plan approval on a developer signing one. Nobody is being compelled.

Build the Record Before You Need It

Three things I’d push for while the item is still in committee.

Get the but-for analysis in writing. Most states require a feasibility study or cost-benefit analysis showing the project wouldn’t happen without assistance. That document is your best friend eighteen months later. Don’t let it stay a verbal assurance from staff.

Ask your questions in open session. An answer you got in a hallway conversation is worthless when a resident challenges you. An answer in the minutes is a citation.

Ask who holds the risk, out loud, on the record. Not because you doubt the deal, but because your constituents deserve to hear the answer from staff rather than from you secondhand.

What This Comes Down To

You don’t need to become a municipal finance expert to cast this vote well. You need to know three things: that no existing revenue is being redirected, that the increment only exists if the project does, and who is on the hook if the projections miss.

The third one is the whole ballgame, and it’s answerable in a single sentence if somebody asks the right question early enough.

We work on the capital side of these transactions, so we read a lot of these structures. If it would help to talk through what your documents actually obligate before a vote, we’re glad to. There’s nothing to sign.