NewsOpinion

The Rays agreement was rewritten the day before the vote. Here’s my updated model.

A substitute Development and Funding Agreement landed on the agenda late Wednesday afternoon including the tax-sharing formula. My numbers from Sunday are out of date, so here are new ones.

Artist rendering of proposed Rays baseball depicting a triangular shaped building with a clear geometric pattern on roof.
via Rays

Note: the amount of change in the document is beyond what I could safely evaluate in a couple of hours. One of those changes however goes directly to what I wrote in Sunday’s preview. I’m not going to rewrite that post, there’s a note linking here. But I want to be perfectly clear: this time, it’s not a correction or clarification. The language changed in a funding agreement the day before the vote. I’m providing updated numbers based on the changes in the language. I will leave it up the paid professionals at the city to explain what else has changed right before council votes on it in (checks watch) 14 hours.

On Wednesday afternoon, less than 24 hours before City Council are scheduled to vote on item 80, the City Clerk posted a memo from the City Attorney sent Council a with three substitute agreements to replace the ones published Friday. The memo says “negotiations have continued between the City, the County, and the owners/consultants for the Tampa Bay Rays.” To their credit, the city also posted a redline so you can see every change.

That doesn’t change it’s not the document that was by their own requirement posted by 5 PM Friday. It was part of the motion to put the item on the agenda. Not a placeholder, but “provided that it’s in Onbase by five o’clock tomorrow.” Setting that aside, the purpose of this is to accurately represent the same model with the new language. The goal is to demonstrate how much tax revenue would be generated from a 70 gross acre parcel at different levels of density developed at different paces.

Community Sponsor

What’s not included in the new agreement are any details about what is being proposed as far as any mixed-use development. I’ve read suggestions that there aren’t any obligations in the agreement to build any mixed-use development at all. So this has always been speculation to a degree. It could turn out to be 50 gross acres or they relegate the school to the same footprint as a couple of parking garages and build 90 gross acres of mixed-use. I went off the static little map they shared with the roll out; I also attended the presentation at HCC, so I settled on 70 acres.

But if you’re going to argue that the development is going to “pay back” the city, I want to accurately reflect what that might look like over 30 years. Maybe it does.

Exhibit E is the table that says how the property tax increment from the Stadium District gets divided between the city and county on one side and the Rays’ Community Development District (CDD) on the other. The tiers didn’t change: 70/30 under $350M in taxable value, 50/50 between $350M and $650M, 15/85 above $650M. What changed is how the tiers are applied.

Friday’s version:

The increment sharing percentages set forth above are applied based on the highest tier reached, so for example, once Taxable Assessed Value enters the second tier, the 50%/50% split set forth above applies from the first dollar of increment.

Wednesday’s version:

The increment sharing percentages set forth above are applied to each respective tier as provided in the increment dedication schedule. For example, the first Tier Schedule shall apply to the first $350 M in Taxable Assessed Value and the second Tier Schedule shall apply to the remaining Taxable Assessed Value above 350M and below 650M.

Friday’s version worked like a cliff. The moment the district crossed $650M, the city’s share of everything dropped to 15%. My tables showed the city’s annual check going down as the district got more valuable, and why I wrote that once the district hits $650M the bulk of the money goes to the CDD no matter what.

Wednesday’s version works like income tax brackets. The city and county keep 70% of the increment on the first $350M, 50% on the next $300M, and 15% on everything above that.

Here’s the same scenario I used Sunday, a 20-year build-out to Channelside density with 3% annual growth, under the updated version of Exhibit E.

20-year ramp at Channelside density, 3%/yr growth, both millages

Year Taxable value Total collected City County District
1 $25M $0.29M $0.11M $0.09M $0.09M
5 $139M $1.62M $0.60M $0.53M $0.49M
10 $322M $3.76M $1.40M $1.23M $1.13M
11 $365M $4.26M $1.57M $1.38M $1.31M
16 $616M $7.18M $2.35M $2.06M $2.77M
17 $674M $7.86M $2.47M $2.17M $3.21M
20 $867M $10.10M $2.65M $2.33M $5.12M
30 $1.16B $13.58M $2.93M $2.58M $8.07M
30-yr total -- $208M $57M $50M $101M

Under Friday’s language I estimated at most the city would see $29 million in revenue. Under the new language the Channelside level development scenario is $57M.

In the scenario Council Member Bill Carlson suggested, more density and a faster ramp up.

10-year ramp at Water Street density, 3%/yr growth, both millages

Year Taxable value Total collected City County District
1 $111M $1.29M $0.48M $0.42M $0.39M
3 $352M $4.10M $1.53M $1.34M $1.24M
5 $622M $7.26M $2.37M $2.08M $2.81M
6 $769M $8.97M $2.56M $2.25M $4.16M
10 $1.44B $16.82M $3.19M $2.80M $10.83M
20 $1.94B $22.61M $3.65M $3.21M $15.75M
30 $2.61B $30.39M $4.27M $3.75M $22.36M
30-yr total -- $551M $96M $84M $371M

Sunday I wrote that the best the city would see is $48M. Under Wednesday’s formula, it gets the city to $80M in nominal dollars around year 26, and $96M by year 30.

Year 1 is still whenever the first buildings hit the tax roll, 2030 give or take, so year 26 is the mid-2050s.

Our stories may be republished online or in print under Creative Commons license CC BY-NC-ND 4.0. We ask that you edit only for style or to shorten, provide proper attribution and link to our website.

Support Tampa Monitor

Reader-funded and independent. Every contribution keeps the reporting going.

Choose an amount

Secure payment via Stripe. Other ways to give →

What we're monitoring

The toolshed

Always-on data tools that keep watch between the stories — built and maintained by the Monitor.

The AgendaA reimagined version of council's weekly agenda.Updated weekly
Capital ProjectsThe city's five-year capital plan & life-to-date spending, every project.FY27 snapshot
Agenda KeywordsEmail notification only if keyword appears on the agenda.Public Beta