City CouncilWednesday, July 22, 2026 · 9:00 AM

Context: City Council approved the Carolwood Drive at Kennedy Gully agreement on July 29 after it was not received or considered on July 22, and the supplied record verifies no implementation milestone.

Recommended: Request the executed Advance Funding Agreement and its attachments to identify the defined bridge scope, responsible agency, and any procurement path before committing estimating resources. The agreement was approved without a verified implementation milestone, so waiting could leave you behind once project documents emerge.

Context: The matter appeared twice: Item 21 was “Not Received - Not Considered” on July 22, while Item 45 became Ordinance 2026-0667 on July 29.

Recommended: Request the July 22 and July 29 agendas, minutes, routing records, and the executed Advance Funding Agreement to determine why the same bridge agreement was not considered one week before approval. Without those records, the public cannot tell whether the change involved document receipt, agreement terms, or another administrative issue.

Context: City Council approved the Texas Department of Transportation funding agreement for Emile Street at Japhet Creek on July 29, 2026, after the same item was not received on July 22, 2026.

Recommended: Obtain the signed funding agreement and its attachments to determine whether the project is defined as bridge replacement or rehabilitation and whether it assigns any notices, approvals, or other obligations. The supplied record verifies approval but no implementation milestone, so the agreement is the only identified source for those compliance questions.

Context: Ordinance 2026-0664 approved an advance funding agreement for bridge replacement or rehabilitation at Emile Street and Japhet Creek on July 29, 2026.

Recommended: Request the executed agreement and technical exhibits from the City and Texas Department of Transportation, then identify whether the work is replacement or rehabilitation and which agency is responsible for each component. That distinction will determine which future bridge-work opportunity to track; the current record does not verify a procurement or implementation schedule.

Context: The matter appeared twice: Item 18 was marked “Not Received - Not Considered” on July 22, 2026, while Item 42 became Ordinance 2026-0664 on July 29, 2026.

Recommended: Request the July 22 and July 29 agenda packets, staff transmittals, and meeting materials to establish why the bridge funding agreement was first not received and then approved one week later. Without those records, the public cannot tell whether the change reflected revised terms, missing documentation, or a scheduling issue before implementation records disperse.

Context: City Council approved the advance funding agreement for Furray Road at Kennedy Gully on July 29 after the item was not received on July 22.

Recommended: Obtain the executed City–Texas Department of Transportation advance funding agreement and determine whether it assigns any funding, scope, audit, indemnity, or notice duties before either party begins work; the approved record contains none of those terms.

Context: The matter appeared twice, with Item 20 marked Not Received - Not Considered on July 22 and Item 44 resulting in Ordinance 2026-0666 on July 29.

Recommended: Request the July 22 and July 29 agenda-routing records, staff transmittals, and correspondence for the bridge funding agreement, then compare what changed between the item being not received and its approval one week later; without those records, the public record does not explain the reversal.

Context: City Council approved the advance funding agreement for bridge replacement or rehabilitation at Laura Koppe Road at Ditch on July 29, while no implementation milestone is verified in the matter record.

Recommended: Obtain the executed City of Houston–Texas Department of Transportation funding agreement and its project exhibits to determine the bridge work scope, responsible procuring agency, and any consultant or construction procurement path. The agreement is now authorized, but the supplied record verifies no implementation milestone, so firms that wait may miss the first publicly documented opportunity to position for the work.

Context: The item appeared twice: it was “Not Received - Not Considered” on July 22 and approved by City Council on July 29.

Recommended: Request the July 22 and July 29 agenda backup, staff transmittals, and correspondence explaining why the same Laura Koppe Road bridge funding agreement was not considered and then approved one week later. Without those records, the reason for the reversal in this twice-appearing matter remains unresolved.

Context: City Council authorized the West 15th Street bridge agreement on July 29, 2026, after the same item was not received or considered on July 22, and no implementation milestone or agreement terms are verified in the record.

Recommended: Obtain the signed Advance Funding Agreement and City Council backup, then identify the City and Texas Department of Transportation duties, approvals, and reimbursement terms actually stated in those documents. The ordinance authorizes the agreement but the supplied record does not disclose its operative terms, so relying on the agenda description could miss binding project obligations.

Context: This agreement appeared twice: it was marked “Not Received - Not Considered” on July 22, 2026, then approved as Ordinance 2026-0678 on July 29, 2026, with no explanation supplied for the reversal.

Recommended: Request the July 22 and July 29 council backup, staff transmittals, and Texas Department of Transportation correspondence to determine what changed between the item being not received and its approval one week later. Publish the explanation before implementation records obscure whether the delay reflected missing funding, agreement revisions, or another unresolved issue.