City CouncilWednesday, February 18, 2026 · 9:00 AM

Context: Ordinance 2026-0137 approving the Fifth Ward Zone budgets was adopted on February 18, 2026, following Council Member Ramirez's February 10 tag and dissenting vote at adoption.

Recommended: Pull the executed ordinance and every budget attachment, then identify whether the adopted Fiscal Year 2026 operating budget or 2026-2030 capital plan imposes approval, spending, or reporting requirements on the redevelopment authority. Do this now because the Council has resolved the matter and the supplied record names the budgets but does not provide their operative terms.

Context: City Council adopted the Fiscal Year 2026 operating budget and Fiscal Years 2026-2030 capital improvement plan budget for the Fifth Ward Zone on February 18, 2026, after the matter appeared twice, with no implementation milestone verified.

Recommended: Obtain the adopted Fiscal Years 2026-2030 Capital Improvement Plan budget and identify funded project scopes, delivery schedules, and procurement methods before pursuing work. The Council approval makes the plan operative, but the supplied record verifies no implementation milestone, so early review is the only way to distinguish actual upcoming packages from unfunded concepts.

Context: The matter was tagged by Council Member Ramirez on February 10 and, on its second appearance on February 18, Ordinance 2026-0137 was adopted with Ramirez voting no and the balance voting aye.

Recommended: Request Council Member Ramirez's tag explanation, any written concerns, and the February 11 agenda backup for the Fifth Ward Zone budget. Report whether the concern was addressed before adoption, because the item appeared twice and moved from a tag to adoption with Ramirez still voting no while the balance voted aye.

Applies if: You are preparing a competitive nine percent tax-credit application for a proposed Houston affordable rental development.

Context: Council adopted the affordable rental housing support resolution as amended on February 18, 2026, while four developments were separated and referred back by an adopted motion.

Recommended: Obtain the amended resolution, amendment text, and property list, then match your proposed development against the four projects that were separated and referred back. Do not assume City support covers your tax-credit application until that match is confirmed, because the final record does not identify which properties remained supported.

Context: The matter appeared twice: it was tagged on February 10, 2026, then adopted as amended on February 18, with four developments referred back despite the unanimous final vote.

Recommended: Request the amendment text, property list, and rationale for separating four developments, then report which projects retained Council support and which did not. Without those records, the public cannot tell why an all-aye final action still sent four developments back for further handling.

Context: The adopted February 18, 2026 resolution confirms support for the proposed affordable rental development, tax-credit application submission, and tax-credit allocation language, while the supplied record verifies no implementation milestone.

Recommended: Request the signed resolution and the City records documenting what was submitted with the competitive nine percent housing tax credit application, then determine whether Council authorized only support or any additional commitments tied to the property and One Mile Three Year Rule. This limits the risk of treating a support resolution as broader project approval without the governing documents.

Context: City Council unanimously adopted support on February 18, 2026, for Emancipation West at 2718 Emancipation and submission of a competitive nine percent housing tax credit application subject to the One Mile Three Year Rule.

Recommended: Pull the adopted City Council resolution and compare its property description, affordable-rental proposal, and One Mile Three Year Rule language against the submitted competitive nine percent housing tax credit application. The February approval supports this specific application path, so inconsistencies could weaken implementation even though Council support is already secured.

Context: This matter appeared twice: it was tagged by Council Members Thomas and Davis on February 10, 2026, then adopted with all votes aye and no nays on February 18, 2026.

Recommended: Request Council Member Thomas's and Council Member Davis's tagging communications and any revised backup material between the February 10 tag and the February 18 unanimous adoption. Establish whether a substantive project or tax-credit issue changed before the matter moved from a tag to unanimous approval.

Context: The record shows the matter was tagged by Council Members Thomas and Davis as Item 15, then adopted unanimously on February 18 as Item 36 after appearing on the February 11 agenda.

Recommended: Pull the February 11 agenda version and the final adopted resolution, including attachments, and compare the property descriptions and authorization language. The item was tagged before unanimous adoption, so reliance should be based on the final text rather than the earlier agenda version.

Context: On February 18, City Council unanimously adopted support for one or more proposed affordable rental housing properties subject to the Two Mile Same Year Rule and for Competitive 9% Housing Tax Credit applications.

Recommended: Obtain the adopted resolution’s property and development materials and match them to your tax-credit application. Council support is limited to proposed developments subject to the Two Mile Same Year Rule, so an unmatched property could lack the support reflected in this action.

Context: This matter appeared twice: it was tagged by Council Members Thomas and Davis and later adopted with all votes aye and no nays.

Recommended: Request the tag memo, council-office communications, and any revised resolution materials to explain why Thomas and Davis tagged the item before it later passed unanimously. Also ask why the record identifies it as Item 15 on the February 11 agenda but Item 36 at adoption.

Context: The February 18 resolution supports applications for “certain properties,” while the supplied record identifies neither the properties nor applicants and verifies no later implementation record.

Recommended: Pull the signed resolution, attachments, and submitted tax-credit application materials, then compare the named properties and applicant entities across them. This will establish whether each application is actually covered by the Council support resolution rather than relying on the broad public description.

Context: On February 18, City Council unanimously adopted Resolution 2026-0007 supporting applications for certain properties meeting those jurisdictional descriptions, but no site names or implementation milestone are verified.

Recommended: Obtain the adopted resolution and its property list before advancing tax-credit underwriting or site work. Council support applies only to certain developments in Houston’s extraterritorial jurisdiction or areas annexed for limited purposes, and the supplied record does not identify which properties qualify.

Context: The item was tagged by Council Members Thomas and Davis, then adopted with all votes aye as Item 34 after previously appearing as Item 13; the record provides no reason for the intervening tag.

Recommended: Request Council Members Thomas’s and Davis’s tagging rationale, communications, and any revised item materials, and ask why the item returned for unanimous adoption. The public record shows two appearances and the tag but gives no explanation of what changed before passage.