On September 22, Jacksonville's City Council introduced an ordinance that would have put $2,773,815 into three affordable housing accounts. Before the meeting ended, the council voted 19 to 0 to withdraw it. The city's action record for that bill runs to two lines, and neither of them says why.

Here is the part that changes the story, and it had been sitting on the city's website for six days. The bill's own text went up on September 16, and it is not a rescue package for the affordable housing money a council committee cut in August. It is expiring money. The ordinance appropriates out of the 2025-2026 fiscal year, and it gives its reason for demanding emergency passage in a single sentence: the funds "will lapse on September 30, 2026, if not appropriated before the end of the fiscal year."

So this is a different pot from the one everybody was arguing about that night. Different fiscal year, different accounts, different instrument.

And then the numbers do something the bill does not explain, and neither does anything else the city has posted.

The Receipt

Ordinance 2026-0754 was item 150 on the council's marked agenda for September 22, page 58, introduced by council member Moné Holder. The agenda marks it Emergency and marks it as needing a two-thirds vote.

The bill itself is three pages, prepared by the Office of General Counsel, and the city posted it with its exhibit on September 16, six days before the meeting. Read it in order.

Section 1 opens "For the 2025-2026 fiscal year." That is the year ending September 30, not the budget the council adopted the same night.

The money comes out of a single general-fund account, in two pieces. The bill's name for that account runs "CIP Debt Service Repayment" straight into "ISA-Debt Management Fund," and the bill takes $1,680,015 from its "Principal account" and $1,093,800 from its "Interest Account." Those are lines a city budgets to make debt payments with. The two add to $2,773,815 exactly.

The money goes into three accounts, and Exhibit 1, the city's own budget transfer form, gives each one its account code:

  • $1,358,615 to "Housing Services, FY27 GR Capital Stack, Miscellaneous Grants and Aids"
  • $849,065 to "Housing Services, FY27 GR Downpayment Assistance, Miscellaneous Grants and Aids"
  • $566,135 to "Housing Services, FY27 GR Tap Fee, Miscellaneous Grants and Aids"

Those three also add to $2,773,815 exactly. Both columns balance.

Section 3 is the one that matters most, because it is the bill telling you why it had to move that night. "The nature of the emergency is that the funds appropriated herein will lapse on September 30, 2026, if not appropriated before the end of the fiscal year." This was money with eight days left on it.

Then the city's record for the matter, which is two action lines: "9/22/26 CO Introduced: NCSPHS, F" and then "9/22/26 CO Withdraw 19-0". Introduced and withdrawn, unanimously, at the same meeting. It never reached a committee. The matter's status still reads "Introduced" and it shows no passage date, so those two lines are the entire public record of what became of it.

And nineteen to nothing was a vote to withdraw. That is not a bill being voted down, and this piece will not call it one. Withdrawal takes a bill off the board; it does not rule on it. What the record does not do is name who moved it, or say one word about why.

Two things in the city's own paperwork that are not findings, said here so nobody mistakes them for one later. Exhibit 1's narrative description reads "$2,772,815" while the form's net-amount field and all five of its line items read $2,773,815. That is a $1,000 transposition in a city form, a typo rather than a real disagreement. And Exhibit 1's "transfer from" and "transfer to" totals both read $5,547,630, exactly twice the appropriation, because the interfund transfer gets counted on both sides of the form. There is no $5.5 million here.

It Is Not the $4.9 Million

You need the August story to see why the next section is strange, so here it is, short, from the Finance Committee's own minutes.

On August 13, sitting in budget hearings on next year's budget, the committee took the affordable housing trust money out in three separate motions: remove "$1.5 million for the Down Payment Assistance Home-Ownership Program," remove "$2.4 million for the Local Capital Stack for Attainable Housing Program," remove "$1 million related to the Attainable Housing Tap Fee Fund." Each carried 7 to 1, with council member Johnson recorded against every time. Three programs, $4.9 million.

Then, in the same meeting, the committee unanimously approved a Council Auditor recommendation "Moving $4,900,000 in funding for the Affordable Housing Trust to a Designated Contingency pending the legislation being filed related to the changes on how this fund will be set up," and the minutes add that "These funds can be moved out of the designated contingency with the upcoming separate legislation."

That is the honest version of August, and it is the one that survives a hostile read: the committee did not burn the money. It parked it behind a condition. Somebody had to file a bill.

Ordinance 2026-0754 is not that bill. It does not touch the designated contingency, does not mention it, and takes its money from somewhere else entirely, in a fiscal year the contingency has nothing to do with. And when this desk searched the city's legislative database on September 23, no matter in it, going back to 2017, carried "Housing Trust" in its title at all, against control searches on "Affordable Housing," "Attainable Housing" and "Trust Fund" that returned 48, 5 and 149.

So hold the two apart, because the city's documents do. August was next year's budget and a parked $4.9 million. Ordinance 2026-0754 was this year's leftover debt-service money with a week to live.

Then Why Does Every Line Land on 56.6 Percent?

Because here is what happens when you set the two sets of numbers beside each other anyway.

Program2026-0754August cut0754 as a share of it
Capital stack$1,358,615$2,400,00056.6090%
Down payment assistance$849,065$1,500,00056.6043%
Tap fees$566,135$1,000,00056.6135%
All three$2,773,815$4,900,00056.6085%

Three different programs, three different dollar amounts, and every one of them lands within a hundredth of a percentage point of the same figure. The widest gap between any two is nine one-thousandths of a point.

That is one fact wearing three hats, and it is worth saying what the fact is. If every line comes to the same share of what August cut from that program, then the bill's internal split is the August split. Run it that way and you can see it plainly. Ordinance 2026-0754 puts 48.98 percent of its money on capital stack, 30.61 percent on down payment assistance and 20.41 percent on tap fees. August's three cuts were 48.9796 percent, 30.6122 percent and 20.4082 percent of $4.9 million. Same proportions, to four figures.

Now the part that rules something out. The bill was not built by taking the three August numbers and scaling them by one multiplier. Test it. Multiply each August figure by 2,773,815 divided by 4,900,000 and you get $1,358,603.27, $849,127.04 and $566,084.69, each one off from what the bill says by $12 to $62. Rounding to the nearest dollar cannot open a $62 gap. So whatever produced these three lines ran from the total down, not from the August figures up.

Here is a calculation that does reproduce all three, and read the caveat attached to it before you decide what it means. Take the August shares rounded to two decimal places: 48.98 percent, 30.61 percent, 20.41 percent, which sum to exactly 100.00. Apply the first two to $2,773,815 and round to the nearest dollar, and you get $1,358,615 and $849,065. That is what the bill says, to the dollar, both times. Subtract both from the total and the remainder is $566,135, which is the third line. Nothing in any document the city has posted says that is how it was done. It is one calculation that lands on all three figures, it is checkable on a phone, and what it accounts for is the split. It does not account for the total.

And the total is the whole question. Where $2,773,815 came from, and why a pot of expiring debt-service money should come to 56.6 percent of an unrelated budget cut in an unrelated fiscal year, is not in the bill, not in Exhibit 1, not in the August minutes, and not in anything else posted on this matter. The bill's own explanation is a lapse date, and a lapse date is a deadline, not a percentage. This desk is not going to invent a reason for you, and you should be careful with anyone who does.

Why It Costs You

Set the strangeness aside for a second and look at what those three accounts actually do, because the minutes are specific about one of them.

The committee's August minutes describe down payment assistance as a program for workforce residents who do not qualify for the state and federally funded programs, and they name teachers and nurses as the example. Utility tap fees are what it costs to connect a house to water and sewer, a charge that lands on a project before anybody lives in it. Capital stack money closes the financing gap that decides whether a project gets built at all.

So the bill would have put $849,065 toward people buying houses, $566,135 toward the cost of hooking those houses up, and $1,358,615 toward getting them built. That is what was on the table for the few hours the ordinance existed.

The other half of the sentence is the calendar. By the bill's own account, the money it was moving expires on September 30. The ordinance came off the board on September 22 with no appropriation made, eight days before the deadline it was written to beat. What became of those two account balances afterward is not on the public record either, and it is the single most answerable open question here.

How the Machine Works

Now look at the fund, because it turns out this bill is one of a crowd.

Pull every ordinance introduced in Jacksonville since August 1 whose title names the ISA-Debt Management Fund and you get eight. Seven of them take money out of that fund's Interest account: $25,000 for a Unity Classic sponsorship, $150,000 to the Salvation Army for a homeless-to-work program, $204,000 to a child abuse prevention center, $50,000 split between two 2027 event sponsorships, $250,000 toward a clubhouse at Blue Cypress Golf Course, $20,310.25 as part of a grant to a chamber music society, and $237,427 for the city's dues to four government associations. Five of the seven carry an explicit provision carrying the money over into fiscal 2026-27. And three of the seven carry Council withdrawal actions of their own, two of them dated September 22, the same night as this one.

That is the shape of year-end housekeeping. Money budgeted for debt service that the city did not end up spending, moved into things the city does want to spend on, before the fiscal year takes it back. It is ordinary, it is not a housing maneuver, and an honest read of Ordinance 2026-0754 has to start there.

Two things still make 2026-0754 the odd one out. Add all seven of the others together and our math puts them at $936,737.25. Ordinance 2026-0754 asked for $1,093,800 out of the Interest account by itself, more than all seven combined, and then asked for $1,680,015 on top of that.

That $1,680,015 is the second thing. It comes out of the Principal account, and 2026-0754 is the only one of the eight bills that touches Principal at all. Search all 59 pages of the September 22 marked agenda for the Principal account and it appears exactly once, in item 150.

So: a routine sweep, run at roughly three times the size of every other sweep in the same window put together, and reaching into a part of the fund that nothing else reached into.

The Strongest Version of the Other Side

Make the best case here, because there is a real one and most of it is on the documents.

Nothing was taken from anybody by 2026-0754, because 2026-0754 never took effect. All nineteen members agreed to take it off the board, which is about as clean a disposition as a bill gets.

The housing money itself was not riding on this either. The city's record for the budget ordinance, 2026-0504, carries the action line "9/22/26 CO PH Substitute/Amend(2x)(FL)/Approve 18-1 (Diamond)". The budget was substituted, amended twice on the floor, and approved 18 to 1 that night. Whatever else happened to item 150, the council was doing its housing business in public a few dozen items earlier on the same agenda.

And a year-end sweep is a year-end sweep. The seven other bills on the same fund in the same window are the proof that this was a season, not a scheme, and a withdrawn sweep bill is about the least sinister object in a city hall.

Here is the answer, and it is narrow on purpose. All of that can be true and two things still sit on the record unexplained. Why a housekeeping bill for expiring debt-service money came out to the exact proportions of an unrelated budget cut in a different fiscal year. And why it went off the board eight days before the money it was chasing ran out.

What the Record Doesn't Say

Four gaps, named, so nobody has to guess which parts are known.

Why it was withdrawn. The record says "Withdraw 19-0" and stops. No reason, and no name for whoever moved it. Two things sit under the same date on the city's record: a budget substituted and amended twice on the floor, and this bill withdrawn. Neither action is timestamped, and the agenda printed the budget as item 80 and this bill as item 150. Reading the withdrawal as a consequence of the amendments is an inference. It is this desk's inference, it is not the city's, and the city has not said it.

Where $2,773,815 came from. The bill says the money lapses. It does not say the amount is what was left in those two accounts, and no posted document shows either balance.

Where 56.6 percent came from. Nowhere. Not one document opened for this piece references the $4.9 million at all.

What happened to the money after September 22. The bill's own deadline was September 30. Nothing posted says whether those balances were appropriated some other way or simply lapsed.

One more thing worth knowing about the condition of the record. The budget ordinance's status fields are behind too. It still reads "Public Hearing," with no enactment number and no passed date. The 18-1 survives only in the free-text action line quoted above. So this piece says the council approved the budget, which is what the city's own line says, and does not say it was enacted, which the city's record does not yet show.

What You Can Actually Do

Read the bill. It is three pages and it is right there, with the transfer form behind it. Section 3 is four lines long and it is the entire reason the bill was an emergency.

Ask for what is not posted. Florida's public records law reaches the council's own files. The September 22 minutes have not published, so the withdrawal motion and whoever made it exist only in a draft. The marked agenda lists the Council Secretary's office at (904) 255-5133.

Ask your own council member two questions. What was actually left in those two debt-service accounts on September 22? And where did the split come from?

Watch the contingency, not the headline. The August minutes say the $4.9 million can be released by legislation. That mechanism is a separate thing from this bill, and it is still sitting there.

The So-What

A bill existed for a few hours and then stopped existing, and it is still the most interesting document in the room.

It says, in its own words, that it was chasing money about to expire. That is a boring reason and it is almost certainly a true one, because seven other bills in the same window were chasing money out of the same fund. But somebody, somewhere between a fund balance and a filing, decided that this particular pile of expiring debt-service money should be cut into thirds in the exact proportions of a housing cut made six weeks earlier, in a different fiscal year, out of different money. That decision is on the paper. The reasoning for it is on nothing.

And then all nineteen of them agreed to take it off the board, eight days before the money it was written to save ran out.

That is what a public record is. It preserves what the process happened to write down, which is never the same as what the process knew. Jacksonville will tell you, to the dollar, that this bill would have moved $1,358,615 into capital stack funding. It will not tell you who picked the number, or why it stopped.

Bless their hearts.

Come back for the rest

This show does it every week. Every figure in this piece is tied to the document it came from, and every division is printed so you can run it yourself. So pull up a chair, pour something cold, then subscribe to The Long Pour, our free newsletter, and the week's receipts arrive together in your inbox.

Y'all come back, now.


The Receipts

Each claim above links to a document you can open yourself, with the access date on each line.

  • "2026-754 Original Bill" (City of Jacksonville, Ordinance 2026-0754, attachment 40055, posted September 16, 2026; accessed September 23, 2026): the fiscal year, both source accounts, all three destinations and the lapse-date emergency.
  • "2026-754 Exhibit 1" (City of Jacksonville, Ordinance 2026-0754, attachment 40056, posted September 16, 2026; accessed September 23, 2026): the account codes, the sponsoring department, the $1,000 narrative typo and the doubled form totals.
  • Ordinance 2026-0754 matter record (City of Jacksonville, Legistar WebAPI, matter 8863; accessed September 23, 2026): the two action lines and the status field.
  • City Council Agenda - Marked, September 22, 2026 (City of Jacksonville, EventId 3731, 59 pages; accessed September 23, 2026): item 150 on page 58, the emergency markings, and the budget at item 80.
  • "Finance Committee - Budget Hearings, Meeting Minutes, August 13, 2026" (City of Jacksonville, EventId 3865, Final; accessed September 23, 2026): the three removal motions, the tallies, and the designated contingency.
  • Matters introduced on or after August 1, 2026 (City of Jacksonville, Legistar WebAPI query, 163 matters; accessed September 23, 2026): the eight bills drawing on the ISA-Debt Management Fund, and their amounts.
  • Ordinance 2026-0504 matter record (City of Jacksonville, Legistar WebAPI, matter 8595; accessed September 23, 2026): the September 22 action line, and the status fields that have not caught up.