Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Engineering Retainer topic
No spam. Unsubscribe anytime.
Council adopts engineering retainer; members discuss maps, GIS and perceived conflict of interest
Summary
Council approved Ordinance 25‑04, renewing the retainer with Chagrin Valley Engineering; councilmembers requested more street-condition maps and GIS graphics and discussed the firm’s billing structure and perceived conflict of interest tied to consultant-led project work.
Pepper Pike City Council on Jan. 28 adopted Ordinance 25‑04 to renew the city’s retainer with Chagrin Valley Engineering. The retainer update includes a roughly 5.95–6% rate increase for the firm’s personnel, mirroring recent city employee adjustments, and was described as consistent with rates charged to other nearby municipalities.
During discussion, councilmembers asked whether the city’s pavement-condition inventories and street maps could be included under the retainer. Don, a representative of Chagrin Valley Engineering, said the firm maintains a spreadsheet and other data and can produce maps and GIS graphics, but those tasks would be extra work and likely increase the retainer if done routinely. He said the firm already maintains a database and does an annual condition rating and that generating higher-quality graphics would be an added fee.
Councilmember questions also touched on how the firm’s billing for capital-project work is routed through city funds, developer deposits or the capital projects fund. Councilmember Dr. Wang and others raised the sense that having the same engineering firm advise the city and then bill for project implementation “feels like a conflict” even if legal safeguards exist; the law director and administration replied that council must authorize projects before consultant work proceeds and that council approval provides the principal control.
Why it matters: The retainer governs engineering support on capital projects and recurring services; the discussion flagged resident-facing policy needs (pavement maps and condition inventories) and raised governance issues about consultant roles and municipal procurement and billing.
Council action and next steps: Ordinance 25‑04 was moved and adopted by roll call. Staff and the engineering firm will provide the committee with available pavement-condition spreadsheets and explore adding periodic map and GIS deliverables, with the understanding that extra work will likely increase retainer or be billed separately. Council also asked for a clearer breakdown of revenue that offsets engineering operating costs (e.g., deposits from developers) and the annual miscellaneous revenue related to engineering work.
Provenance: The engineering-retainer discussion and vote are recorded in the Jan. 28 meeting transcript.
