City CouncilWednesday, June 17, 2026 · 9:00 AM

Context: City Council adopted the $26,437,655 appropriation and contract authorization after the matter appeared three times, and the ordinance includes a bidder-default condition tied to post-bid documents.

Recommended: Pull the executed contract and adopted ordinance to identify the exact post-bid-document deadline, required submissions, and default procedure; those terms now control a material risk under the authorized construction-manager-at-risk arrangement.

Context: The adopted East Water Purification Plant Enhancement ordinance authorizes Kiewit’s construction-manager-at-risk contract and expressly sets a post-bid-document deadline with default for noncompliance.

Recommended: If you are Kiewit Water Facilities South Co, obtain the contract’s exact post-bid-document deadline and submit every required item with proof of delivery; failure to meet that deadline can place the bidder in default.

Context: The same $26,437,655 East Water Purification Plant item appeared three times: it was tagged by Council Member Castex-Tatum, adopted by a 16-0 motion, then adopted as an ordinance after being delayed by that motion.

Recommended: Request the council backup, motion text, and staff correspondence explaining why an item tagged in June became a unanimous motion in July and then an ordinance a week later; without those records, the reason for the repeated delay and final sequencing remains unanswered.

Context: The July 15 adoption authorized $93,771,329 for the project, professional engineering services with CDM Smith, and capital-improvement-program cost recovery, but the supplied record gives no implementation milestone or contract terms.

Recommended: Obtain the final adopted ordinance and executed CDM Smith contract, then compare the authorized engineering scope and cost-recovery language with the appropriation language. This establishes whether the signed documents contain limits, approvals, or cost-recovery obligations not visible in the meeting record before implementation advances.

Context: On July 15, City Council adopted the appropriation and authorized professional engineering services with CDM Smith after the item appeared three times in the record.

Recommended: Request the executed CDM Smith engineering-services contract and its scope, schedule, and subcontracting provisions before pursuing work tied to the East Water Purification Plant enhancement. The City Council has already authorized the engineering contract within a $93,771,329 appropriation, so waiting may mean missing any consultant-led specialty work or learning too late that the scope is closed.

Context: The item was not received on June 17, was tagged by Council Member Pollard on July 8, and was adopted on July 15.

Recommended: Request the June 17 receipt log, the reason the item was tagged on July 8, and any staff or council communications explaining its return for adoption on July 15. The public record shows three appearances—first not received, then tagged, then adopted—but does not explain what changed before $93,771,329 was authorized.

Context: Council authorized the interlocal agreement and specified three dedicated funding sources for twenty-five neighborhood park improvements on July 15, 2026.

Recommended: Obtain the executed agreement with Houston Parks Board LGC and compare its project scope and fund uses against the authorization for improvements at twenty-five neighborhood parks. Do this now so any mismatch is identified before implementation records become harder to reconcile.

Context: The item was previously tagged by Council Member Castex-Tatum and then tagged by Council Member Martinez before Ordinance 2026-0610 was resolved on July 15, 2026.

Recommended: Request the executed interlocal agreement, the list of all twenty-five parks, and records explaining the funding allocation for each project. The matter appeared twice and was tagged before resolution, but the supplied record does not identify which neighborhoods receive improvements or why the item was delayed.

Context: On July 8, City Council adopted Ordinance 2026-0601, which set a post-bid document deadline and provided for bidder default if it was not met.

Recommended: Obtain the adopted ordinance and executed construction contract to identify the post-bid document deadline and required submissions, then determine whether the selected bidder met them. A missed requirement could trigger the default consequence expressly included in the adopted action.

Context: City Council adopted the Chateau Forest Area Drainage and Paving construction contract with Total Contracting Limited on July 8, after the matter appeared twice and was not considered on June 17.

Recommended: Contact Total Contracting Limited now to ask which construction, testing, or construction-management work and supplier scopes may be released. The City Council authorization is already adopted, so waiting may mean missing early procurement decisions.

Context: The same matter appeared twice: Item 34 was not received or considered, while Item 35 was adopted 16-0 as Ordinance 2026-0601.

Recommended: Request the records explaining why the Chateau Forest item was not received or considered on June 17 but was adopted unanimously on July 8. Establish whether the two appearances reflected missing bidder documents, revised materials, or another unresolved issue before implementation advances.

Context: City Council adopted the $10,500 Union Pacific preliminary-engineering reimbursement ordinance 16-0 on July 8, 2026, after the matter appeared twice; the supplied record does not include agreement terms or milestones.

Recommended: Obtain the adopted ordinance and executed Union Pacific reimbursement agreement to identify the preliminary-engineering scope, payment obligations, and any City review or cost-recovery triggers. The record verifies a $10,500 appropriation but no implementation milestone, so unresolved agreement terms may become harder to shape once work begins.

Context: The July 8, 2026 adoption appropriated $10,500 for a Union Pacific preliminary-engineering reimbursement agreement and CIP cost recovery, while the matter record verifies no implementation milestone.

Recommended: Request the executed reimbursement agreement and determine whether Union Pacific performs all preliminary engineering or whether any City-managed consultant work is identified. Do not spend resources pursuing a construction opportunity unless the agreement or later records identify one, because the adopted action funds only preliminary engineering and cost recovery.

Context: The matter appeared twice: Item 35 was not received or considered on June 17, 2026, then Item 36 was adopted 16-0 as Ordinance 2026-0606 on July 8, 2026.

Recommended: Request the June 17 and July 8 agenda backups, staff correspondence, and executed agreement to explain why the same $10,500 Union Pacific reimbursement item was not considered before being adopted three weeks later. Reporting now can establish whether the delay reflected a missing agreement, changed scope, or another unrecorded issue before implementation records obscure the sequence.