Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Procurement Policy topic
No spam. Unsubscribe anytime.
Gahanna council pushes procurement redline back to committee over $250,000 threshold and reporting concerns
Summary
Finance staff reviewed procurement-policy revisions aligning local rules with federal guidance; councilmembers raised concerns that the $250,000 council-approval threshold is high compared with peers and asked for reporting and vendor‑diversity data. Staff will return to committee with requested information and may advance technical retainage changes separately.
The Committee of the Whole on Feb. 9 reviewed proposed updates to the city’s procurement policy, including adjustments to petty‑cash limits, micro‑purchase and small‑purchase thresholds, prequalification procedures for professional services, and sealed‑bid/competitive‑proposal rules to align with federal uniform guidance and Ohio law.
Finance staff explained that the city intentionally kept its micro‑purchase threshold at $10,000 and its small‑purchase threshold at $250,000 rather than adopting recent federal increases. Staff described a prequalification (RFQ/RFP) process used primarily by engineering for architecture and engineering services: respondents are scored and placed on a shortlist, and a later proposal phase remains competitive for specific scopes of work. The city also plans to use a roster of prequalified firms for categories such as flood‑plain management, traffic signal coordination, transportation, utilities and technology.
Several councilmembers questioned the $250,000 cutoff that triggers council approval and raised oversight and equity concerns: they asked whether the threshold is an outlier compared with peer communities, whether quarterly reporting of contracts below the threshold would improve transparency, and whether procurement could be better tied to community economic‑development goals and vendor diversity objectives. One speaker observed that the federal retainage change (from 8% to 4%) creates project‑protection gaps and asked that the city defer or separately advance particular code changes that preserve staggered retainage protections for construction contracts.
Councilmembers and staff agreed to continue the discussion publicly and requested that council submit questions to staff by the end of the week so that staff can prepare comparative data and suggestions for a return to committee. Staff suggested splitting the ordinance to take uncontroversial technical changes (for example, retainage language) forward while the larger policy and threshold debates proceed in committee.
