Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Mosquito Spraying topic

No spam. Unsubscribe anytime.

Pryor Creek council rejects draft citywide mosquito‑spraying contract, orders bids and tighter terms

Pryor Creek City Council · July 2, 2024
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

After hours of public comment and council debate over environmental and cost concerns, the Pryor Creek council rejected a proposed citywide mosquito‑spraying renewal and directed staff to solicit competitive bids with clearer specifications and spot‑treatment options.

The Pryor Creek City Council on July 16 rejected a proposed contract to renew citywide mosquito spraying and directed staff to solicit competitive bids, tighten contract language and specify treatment areas and chemicals.

Council members and several public commenters questioned the proposed approach after residents and advocates said broad fogging could harm pollinators and that more targeted, larval and spot treatments can be effective. The contract included in the meeting packet listed treatment at “$5,000 per month,” and an internal line in the draft referenced a per‑treatment figure shown as “25100” in the packet; council asked staff to clarify billing and unit pricing before any agreement is signed.

“The decades of spraying has created super mosquitoes with an immunity… There are alternatives to citywide spraying,” public commenter Nina Roberts told the council, urging spot sprays and larval control rather than blanket fogging. Council members said they wanted written specifications from the contractor, including chemical names, application frequency and a clear billing formula.

Mayor (role) said the city would not pay unless treatments were needed and described how staff could ask the contractor to identify and treat only verified problem areas. Still, several council members said the packet language was too vague for a binding contract and moved to reject the draft and reopen the work to competitive bidding.

Councilmember discussion also acknowledged operational needs for large public events and the possibility of an interim, narrowly scoped treatment for an imminent event while the formal bid process proceeds.

Outcome: Council voted to reject the draft contract as presented and directed staff to prepare formal bid specifications (including spot‑treatment options, chemical disclosures and maps of service areas) and to invite bidders to address the council. The council asked staff to return with specific language and pricing options before approving any renewed multi‑month agreement.

What’s next: Staff will draft bid specifications and return with legal and procurement language. The council asked that the contractor who has historically provided services be invited to the next meeting to explain practices and pricing while the city prepares a competitive solicitation.