Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Governance Purchasing topic
No spam. Unsubscribe anytime.
Rathdrum council debates rewrite of purchasing policy and internal controls; asks staff for numeric thresholds and reporting plan
Summary
Council engaged in a lengthy debate over a proposed purchasing policy rewrite after auditor feedback that the budget functions as pre‑approval. Members split on fixed dollar thresholds versus percentage overruns and on how to balance day‑to‑day flexibility with transparency; staff will return with recommended thresholds and BSNA reporting options.
Rathdrum — The council devoted large portions of its meeting to a staff‑led discussion of proposed changes to the city’s purchasing and pre‑approval policy after an auditor advised clarifying that the adopted budget constitutes the city’s pre‑approval mechanism.
Staff told council the auditor’s concern was not the dollar amounts but that pre‑approval should be documented. The proposed rewrite would move from a patchwork of low fixed credit limits to a policy that treats the adopted budget as the pre‑approval and adds guardrails for transfers, emergency purchases and higher‑value procurements that state law requires to be competitively procured.
Council members debated two main approaches: (1) numeric thresholds tied to specific positions (for example, department head $10,000, mayor $50,000, council approval above that), and (2) a line‑item or percentage model allowing small overruns (5–10%) without council action but requiring notification for larger shifts or transfers across line items. Several members favored starting with tight percentages (5%) and relaxing them later if needed; others wanted clear fixed dollar limits to preserve public oversight.
Additional topics included: the treatment of emergency purchases (e.g., pumps or urgent repairs), credit‑card monthly limits and temporary increases, whether unused line‑item savings can be redeployed without council approval, and how BSNA accounting tools could automate flags when thresholds are reached. Staff committed to returning with: (a) recommended numeric thresholds or percentage rules, (b) sample BSNA trigger settings to automate alerts, and (c) reporting templates for quarterly transparency.
Outcome: No ordinance or final policy was adopted at the meeting. Council directed staff to refine the draft, add recommended numeric values and automation options, and return with a proposed ordinance or resolution for formal adoption.
