Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Personnel Salaries topic
No spam. Unsubscribe anytime.
Council holds first reading on ordinance to set new employee salary bands; council asks for comparative data
Summary
At first reading, council discussed a proposal to set salary bands for city positions (Ordinance 25‑03). Administration said bands are intended to reduce annual ordinance updates; council asked for comparative charts, redlines and benchmarking to peer cities before final action.
Get email alerts on the Personnel Salaries topic
No spam. Unsubscribe anytime.
Pepper Pike City Council took up Ordinance 25‑03 on Jan. 28 for first reading, a measure that would codify salary bandwidths for city employees and clarify pay ranges for seasonal and part‑time roles.
Administration explained the ordinance does not authorize specific salary payments but aims to create broader bands that reduce the need to return to council regularly for band adjustments. Joe, the administration representative, told council the bands were sized to avoid yearly changes and that the ordinance cleans up language around seasonal positions, part-time slots and classifications.
Councilmembers pressed for benchmarking data and a redline comparison to prior ordinances. Several asked for charts showing how Pepper Pike’s proposed bands compare with similar municipalities such as Chagrin Falls, Highland Heights and Moreland Hills. Joe said staff would prepare comparable data and a red line between the current and proposed order and return the materials for council review ahead of further readings.
Why it matters: Salary bands frame hiring decisions and retention; council members said they want to maintain competitive pay while ensuring consistency across similar positions.
Next steps: The ordinance remains at first reading. Staff will prepare a red‑line document, comparative data against peer cities and a proposed timeline for final readings and adoption.
Provenance: Discussion is recorded in the Jan. 28 meeting transcript; no final vote occurred on Ordinance 25‑03 at that meeting.

