City CouncilTuesday, May 5, 2026 · 11:30 AM · Council Chambers

Context: Section 8 of the adopted resolution sets the general fund's contribution level to the residential street reconstruction fund, amended to add a 25 percent aspirational goal and passed 8-1 on 2026-05-05.

Recommended: The city's new general-fund policy targeting 25% support for the residential street reconstruction fund signals intent to grow that fund — paving and infrastructure contractors should monitor the next CIP or bond package for expanded street reconstruction bid opportunities.

Context: Item 14 was withdrawn 2026-03-24; the same measure returned as Item 23 on 2026-05-05 with an added 25 percent funding goal, passing 8-1 against Hernandez each time.

Recommended: This budget policy was pulled from the agenda as 'Withdrawn' on 2026-03-24, then came back six weeks later amended and passed 8-1 — ask staff what changed in the interim and why Council Member Hernandez was the lone no vote on both the amendment and final passage.

Context: Council Member Paxson's amendment added the 'aspirational goal of 25 percent' to Section 3 before the resolution passed 8-1 on 2026-05-05.

Recommended: Council adopted an aspirational goal that 25% of general fund revenue support the residential street reconstruction fund — watch the city's next Capital Improvement Program update to see whether your street's repaving timeline moves up.

Context: Council passed the ordinance 9-0 on second reading via consent agenda on 2026-05-12 with no floor debate, leaving the board-approval sequence undocumented in the council record.

Recommended: Pull the TIRZ Number 7 board's minutes to confirm it approved this reimbursement plan amendment before council's May 12 ratification — under Chapter 311 of the Texas Tax Code, financing plan changes must clear the zone board first, and an out-of-sequence vote exposes the revenue diversion to a validity challenge.

Context: The agreement commits half of Subzone B's annual tax increment revenue to reimbursing the London Proper developer's public infrastructure costs, per the 9-0 May 12 second-reading approval.

Recommended: Pull the executed development agreement to see which infrastructure costs qualify for reimbursement and the dollar cap — if you hold land elsewhere in TIRZ Subzone B, this is the template terms to cite when requesting your own reimbursement deal.

Context: Mayor Guajardo opened and closed the May 5 public hearing with the record showing no comments before an 8-0 vote, and the item then cleared consent agenda 9-0 on May 12 without discussion.

Recommended: File a request for the TIRZ Subzone B revenue projections to find out how many total dollars the 50% pledge represents over the life of the agreement — a recurring tax-revenue commitment to one developer drew zero public or council comment.

Context: Council's 9-0 May 12 vote directs half of Subzone B's annual tax increment revenue to a single development, leaving only the remaining half for other claims in the zone.

Recommended: With half of Subzone B's annual increment revenue now pledged to London Proper, get any competing infrastructure reimbursement request in front of the TIRZ Number 7 board before the remaining capacity is allocated elsewhere.

Context: Item 9 was withdrawn April 28 per Deputy City Manager Rodriguez's announcement, then returned as Item 10 and passed 9-0 on the May 5 consent agenda.

Recommended: Verify the TIRZ No. 7 board of directors formally recommended this development agreement before council approval — the item was pulled from the agenda, then returned a week later to pass unanimously on consent with no public discussion, a fast path that can skip the zone board's required recommendation step.

Context: The approved agreement funds public infrastructure costs for a specific development through reimbursement of 50% of annual tax increment revenue, per the May 5 consent item passed 9-0.

Recommended: Don't wait for a city RFP on the public infrastructure tied to this TIRZ No. 7 agreement — these reimbursement deals typically have the developer build and get repaid from tax increment revenue, so the construction contract comes from the developer, not a competitive city bid.

Context: Item 10 passed 9-0 on the May 5 consent agenda as one of two TIRZ No. 7 development agreements each granting 50% of annual tax increment revenue for infrastructure costs.

Recommended: If you have a project inside TIRZ No. 7, request the executed agreement now — city staff just set a precedent of reimbursing 50% of annual tax increment revenue toward public infrastructure costs, and future applicants will likely be held to the same split.

Context: Item 9 was withdrawn April 28 per Rodriguez's announcement, then returned as Item 10 and passed 9-0 on the May 5 consent agenda without separate discussion.

Recommended: Ask the city why an item Deputy City Manager Rodriguez pulled and postponed on April 28 came back nine days later, renumbered, and passed 9-0 on the consent agenda with zero discussion — request the staff memo or agreement redline showing what changed between the two meetings.

Context: Deputy City Manager Rodriguez announced the postponement of Item 9 on April 28; the same item returned as Item 10 and passed 9-0 on the May 5 consent agenda.

Recommended: If you represent another TIRZ No. 7 applicant, take your ask to the City Manager's office rather than individual council members — Deputy City Manager Rodriguez was the one who pulled this item on April 28 and cleared it for the consent agenda where it passed 9-0 without a single council question.

Context: This ordinance and a second TIRZ No. 7 agreement, each pledging 50% of annual increment revenue, both carried 9-0 on the 2026-05-05 consent agenda.

Recommended: Request the TIRZ No. 7 finance plan and confirm projected annual increment revenue is large enough to fund this 50% pledge plus the second TIRZ No. 7 development agreement council approved the same meeting — if both draw from the same pool, there's no buffer against a revenue shortfall.

Context: Council adopted the ordinance unanimously 9-0 on second reading 2026-05-05, one of two TIRZ No. 7 development agreements the council cleared that meeting.

Recommended: Pull the executed development agreement behind this ordinance — it commits 50% of annual tax increment revenue from TIRZ No. 7 to public infrastructure costs, a financing structure you can propose if you have a site inside the same zone.

Context: This ordinance passed 9-0 on both its 2026-04-28 first reading and 2026-05-05 second reading, alongside a second TIRZ No. 7 agreement carrying an identical 50% increment pledge on the same May 5 agenda.

Recommended: Request both TIRZ No. 7 development agreements approved this meeting — each pledges 50% of the zone's annual tax increment revenue, and the record doesn't say whether that's 50% of the same pool (leaving zero margin) or two distinct revenue streams tied to different tax years.

Context: Minutes describe the item as 'inadvertently pulled from the consent agenda' on April 28, then it passed 9-0 with zero Council or public comment on both the April 28 and May 5 readings — an unexplained anomaly in an otherwise routine budget item.

Recommended: Request the agenda-prep records showing why this ordinance was inadvertently pulled from the April 28 consent agenda, then check whether other items that night suffered the same clerical slip — a repeat points to a breakdown in how staff sorts routine business before it reaches Council.