Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Procurement topic
No spam. Unsubscribe anytime.
Hooper council debates procurement rules after legal fees exceed $25,000 threshold
Summary
Council members discussed whether to issue requests for proposals after city legal and engineering bills exceeded the council's $25,000 procurement threshold; no formal vote was taken, but members weighed keeping long-term providers versus running RFPs to meet state guidance.
Get email alerts on the Procurement topic
No spam. Unsubscribe anytime.
Council members and staff spent an extended portion of the meeting discussing whether Hooper should issue requests for proposals for legal and engineering services after the city's bills exceeded the $25,000 threshold in the current fiscal year.
The discussion began as the council reviewed line-item spending and procurement rules. Debbie, a council member, said the city has already exceeded $25,000 for legal services this year and that an RFP appears necessary: "I don't see how we get away from not doing an RFP because we are making..." she said. Tammy, a city staff member, described how attorney fees and engineering costs had been recorded under multiple budget categories so the total exceeded the $25,000 limit used by the city.
Council members raised competing concerns. Several members noted institutional knowledge and continuity: Debbie and others said the city's existing legal counsel and its long-standing engineering partner know Hooper's ordinances and sewer system and that replacing them could cost institutional expertise. "Our legal is so well versed in Hooper, you could not replace their knowledge," Debbie said, noting the firm had worked on many of the city's ordinances.
Staff and some council members countered that the state auditor had recommended the city put procurement documents in order and that the city procurement code requires procedures when contracts exceed the threshold. One council member said the state auditor described the RFP requirement as mandatory and recommended doing RFPs on a periodic (roughly five-year) basis; another reported the auditor characterized the step as a strong recommendation but not always legally binding depending on the contract form.
Council members discussed options: (1) issue RFPs for legal services, engineering (JUB/JV), and the city treasurer/accounting functions; (2) adjust the city's procurement threshold in its own code to a higher dollar amount and remain in compliance with state statute; or (3) limit spending to stay under the current threshold in future budgets. No formal motion or vote on changing the procurement code was taken at the meeting.
Council members repeatedly emphasized transparency and budget limits. Tammy said staff would circulate account details and copies of prior invoices so the council could see where attorney and engineering costs were posted. The council asked staff to re-send the draft RFP the state had provided and to bring a revised procurement-code proposal or a clearer accounting summary to a future meeting.
The discussion closed without a binding decision; council members recorded preferences and asked staff for follow-up material and suggested timeline options for issuing RFPs or amending the city procurement code.
The matter remains at the discussion stage; council members asked staff to return with a clearer accounting of the prior years' attorney and engineering expenditures and a draft RFP for review.

