Plano, Texas

Context: Two appearances (05/26, 07/01) show no recorded vote while the same July 1 agenda logged $147.9M in other contract approvals.

Recommended: This item appeared on the agenda May 26 and again July 1 with no recorded outcome either time, while the July 1 meeting otherwise approved $147.9 million in contracts led by the $140 million Public Safety Campus deal — file a records request or ask the city clerk whether the repair item was approved, tabled, or simply re-listed, since neither published agenda documents a disposition.

Context: The item lacks any recorded outcome on either the 05/26 or 07/01 agenda despite the council taking recorded action on $147.9M in other contracts that same July 1 session.

Recommended: Pull the certified minutes from both the May 26 and July 1 meetings to confirm a vote was actually taken and documented on this item — under the Texas Open Meetings Act, agenda action items require a recorded outcome, and an undocumented disposition here could become a procedural defect if the eventual contract or funding action is ever challenged.

Context: 26-581 came before City Council twice, on 2026-05-26 and 2026-07-01, an unusual cadence for a routine contract renewal.

Recommended: Pull the staff reports and minutes from the May 26 and July 1 Plano City Council sessions to see what changed in the golf course management renewal between appearances — a five-week gap on a contract item, not an ordinance requiring two readings, suggests the vendor, term, or price was revised before final passage.

Context: 26-581 required votes on both 2026-05-26 and 2026-07-01, rather than passing on a single reading as a routine contract renewal normally would.

Recommended: Request the procurement file for the Pecan Hollow golf course management renewal to confirm whether it was competitively rebid or extended sole-source to the incumbent operator; Texas Local Government Code Chapter 252 requires competitive procurement for service contracts above $50,000, and this item needed two separate votes five weeks apart rather than the single reading typical of a straightforward renewal.

Applies if: If advising a client on Plano bid-protest rights tied to this item

Context: Item 26-580 reappeared on the July 1 agenda alongside a cooperative-purchase item covering public safety equipment, golf course, and roadway work, a procurement path Chapter 271 exempts from Chapter 252 bid-protest protections.

Recommended: Pull the July 1 agenda backup and check the procurement code on item 26-580 — if it's grouped under the cooperative-purchase line item spanning public safety equipment, golf course, and roadway spending, the deal proceeded under Local Government Code Chapter 271 interlocal purchasing rules, not the Chapter 252 competitive-bid process a rebid theory assumes.

Context: Item 26-580 appeared on the Plano Council agenda on both May 26 and July 1 without price or vendor disclosed, unlike the fully itemized $140 million contract on the same agenda.

Recommended: File for the staff report or contract backup on item 26-580 — Plano's public agenda detailed the $140 million Public Safety Campus contract in full but never disclosed this item's price or vendor, even though it has now surfaced twice without a recorded final vote.

Applies if: If pursuing public safety equipment contracts with Plano

Context: The July 1 agenda folds public safety equipment spending, including item 26-580, into a single cooperative-purchase line alongside golf course and roadway work rather than a standalone competitive-bid contract.

Recommended: Confirm whether item 26-580 falls under the July 1 cooperative-purchase line item — if so, only vendors already listed on that cooperative's approved roster, not general competitive bidders, can supply this and future Plano public safety equipment purchases.

Context: The matter appeared before City Council twice, five weeks apart (May 26 and July 1, 2026), with no stated reason in the available record.

Recommended: Pull and compare the City Council staff reports from the May 26 and July 1 meetings to see whether the erosion control contract was pulled, amended, or contested — the public record gives no explanation for why it came back five weeks later.

Context: The contract appeared before Council twice within five weeks (May 26, July 1, 2026), a pattern consistent with an unexplained post-award amendment rather than a routine award.

Recommended: Pull the dollar figures from the May 26 and July 1 staff reports and compare them — if the July 1 appearance reflects a change order that increased the original contract price by more than 25%, Texas Local Government Code §252.048 required new competitive bidding rather than a Council amendment vote.

Context: Texas Local Government Code Chapter 2269 requires a two-step qualifications-then-price process for CMAR contracts, and this item reached City Council twice — May 26 and July 1, 2026 — a sequence consistent with (but not confirmed as) that statutory process.

Recommended: Pull the procurement file to confirm the city first selected the construction manager based on qualifications, then separately negotiated a guaranteed maximum price, before awarding the $140 million contract; skipping either step exposes the award to a bid protest from a passed-over firm.

Context: The $140 million construction manager contract for the Public Safety Campus appeared before City Council twice within five weeks, and the public record does not explain why.

Recommended: Request the staff memos and agenda backup from both the May 26 and July 1, 2026 meetings to find out what changed in the $140 million construction manager award between the two hearings — dollar figure, scope, or negotiated terms the public agenda doesn't explain.

Context: Texas Government Code Chapter 2256 requires disclosure of investment policy deviations, and this routine report resurfaced twice (2026-05-26, 2026-07-01) with the $140M CMAR contract approved on that same July 1 agenda.

Recommended: Pull the itemized July 1 investment portfolio summary to confirm liquid, short-term holdings can cover progress payments on the $140 million Public Safety Campus construction contract approved the same day. If the numbers don't reconcile, the investment officer must disclose a Public Funds Investment Act policy deviation to Council.

Context: The matter shows two appearances (2026-05-26, 2026-07-01) with 'Next step: Unknown,' despite the July 1 agenda carrying a $140 million contract vote the same day.

Recommended: Pull the May 26 and July 1 meeting minutes to find out why this routine investment portfolio summary appeared on the agenda twice, five weeks apart, with no recorded next step. That gap is unusual for what should be a single-reading treasury report.