Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Parks Recreation topic
No spam. Unsubscribe anytime.
Council debates fast‑track for Fireman's Field warning track; asks staff for three material options
Summary
Councilors split over whether to appropriate $189,000 now to replace a deteriorated warning track before next season or to run market research; mayor directed staff to return Dec. 9 with three candidate materials, square footage and budgetary cost estimates.
Councilors on Nov. 19 considered a budget amendment to replace the warning track at Fireman's Field after staff described the current surface as a safety hazard and proposed a $189,000 amendment for the warning track alone (the earlier CIP request had been $234,000 including fencing).
Daria Thompson, parks and recreation staff, said the track "represents a clear and documented hazard" and recommended replacement; she told council the larger CIP number would include fencing but the budget amendment before council would be for the warning track only. Thompson said the estimate was recent and that a specialist contractor provided the budgetary input.
Some council members pressed to appropriate now and proceed to an RFP so work could be completed before the 2026 season; others urged procurement caution and an RFI market check so the town does not signal a fixed budget to bidders. The mayor read correspondence from the local team owner noting the current track is an asphalt base with a deteriorated rubberized coating and called it a health hazard for players.
After extended discussion the mayor directed staff to return to the Dec. 9 council meeting with: (1) budgetary cost ranges for removal and replacement (ballpark figures based on 7,150 square feet), (2) at least three candidate materials vetted with the league owner and staff, and (3) a recommended procurement path (RFI vs RFQ/RFP) that complies with state procurement code and public‑hearing/appropriation timing. Staff agreed to solicit input with the team owner and prepare an RFQ scope if council so directs.
The council did not adopt the amendment at this meeting; the item was tabled for Dec. 9 to allow staff to provide the requested information.
