Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Oversight topic
No spam. Unsubscribe anytime.
Council debates scope and timeline of a proposed forensic audit, expands items under consideration
Summary
Council members debated expanding a forensic audit to 15 items (originally four), discussed procurement and RFQ timing (minimum 30 days suggested), and tasked the finance committee and staff to finalize scope and qualifications for bidders before issuing requests.
Get email alerts on the Oversight topic
No spam. Unsubscribe anytime.
A broad forensic‑audit request was a focal point of the June 22 meeting. Councilmember Joseph Lowry urged a prompt, wide‑ranging audit covering potential waste, fraud and abuse dating to 2020. The finance committee had developed a prioritized list and initially recommended a narrower set of items; following public input the scope expanded to 15 items.
Staff and the finance committee explained the difference between a general request and a specific request for qualifications (RFQ): detailed scope reduces bidder uncertainty and produces more precise pricing. Staff said preparing 15 discrete audit items requires time to define the years, account sets, card types and records so vendors can bid accurately. Worth Ferguson recommended a minimum of 30 days for bid response on complex, multi‑topic RFQs; council members noted that adding items increases the time required to produce specifications and to evaluate bids.
Council discussed who should serve on the committee reviewing bids and whether volunteer expertise could be used; staff cautioned that procurement rules, nondisclosure/NDAs and vendor qualifications (municipal/Texas experience) matter. Several councilors pushed for speed and a hard deadline from council for completion. The finance committee will continue building the RFQ and return to council with a timeline and recommended qualifications; council members said they want transparent tracking and prioritized items to expedite work without sacrificing specificity.
No binding contract award was made during the meeting; the council directed staff to proceed with the RFQ development and to bring the packet back to committee and council for approval.

