Insight · HR Strategy

Building a Sustainable Classification Framework the City Can Maintain

By Tabitha McKenney Weinstein · 9 minute read

Most classification systems do not fail because the original study was bad. They fail because no one designed them to be operated by the people who would inherit them. Eighteen to twenty-four months after adoption, the structure that consultants left behind starts collecting one-off exceptions, hand-built side letters, undocumented promotions, and pay actions justified by recruitment urgency rather than the rules the system was built on. Three years in, the framework is no longer the system of record. It is a reference document that HR staff cite when convenient and route around when inconvenient. The replacement study gets commissioned, the cycle repeats, and the city has paid twice for a framework it should have been operating internally the entire time. Sustainability is a design specification, not a maintenance afterthought.

Why classification frameworks degrade

The degradation is predictable. A classification framework built by an external consultant typically arrives with three weaknesses that show up only after the consultant has demobilized. First, the documented decision rules are too sparse to cover the edge cases that arrive in month four. Second, the position description library reflects the work that existed during the study window, not the work that exists after a single round of reorganization. Third, the pay structure was set against a market reference point that begins drifting from real market the day the report was delivered.

None of those weaknesses are visible at adoption. They become visible when the first awkward question arrives: a department head requesting a new title that does not fit any existing classification series, a recruitment failure for a hard-to-fill position where the structure says one thing and the labor market says another, an internal employee promoted into a role whose duties have moved since the position description was last touched. The HR staff inheriting the system have no documented decision rule that fits, no comparator data refreshed since the study, and no authority to add a series. The path of least resistance is an exception. The first exception is harmless. The hundredth exception is the new system.

Sustainability has to be engineered into the framework before any of this happens. The objective is not a perfect system. It is a system that the city's existing HR staff can operate confidently for three to five years between full refreshes, with documented rules that survive personnel turnover and a maintenance cadence that prevents drift from compounding.

The four pillars of a sustainable framework

The framework that survives operationally rests on four design choices, each made deliberately at the design stage. Skip any one of them and the system will degrade on the timeline above. Apply all four and the city can run its classification function internally for years without external help, calling Pinnacle or any other consultant only for the periodic refresh.

Range architecture that holds up under pressure

Range width and midpoint progression are not aesthetic choices. They determine how much room the structure has to absorb market movement, internal promotions, and step progression without forcing a redesign. Pinnacle's house standard for public-sector pay structures is a range width of 35 to 50 percent from minimum to maximum, with midpoint progression of 8 to 12 percent between adjacent grades. Those ranges are not arbitrary. They are wide enough that a five percent market shift over two years does not collapse the structure, and tight enough that the midpoint of grade N+1 sits meaningfully above the midpoint of grade N rather than overlapping into noise.

Cities that adopt narrower ranges, typically in the 20 to 25 percent band that some private-sector consultants import without adaptation, run out of room within the first promotional cycle. An internal candidate promoted from grade 12 to grade 13 lands at the minimum of the new grade and earns less than a peer who never moved. The fix is either a structural exception or a redesign. Cities that adopt wider ranges than 50 percent run the opposite problem: the maximum of grade N exceeds the midpoint of grade N+2, and the structural distinction between grades collapses. The sustainable range sits in the middle and stays there.

Decision rules that HR staff can apply without an outside expert

The framework has to ship with written decision rules covering the recurring scenarios HR staff will face once the consultant leaves. At minimum: how a new position gets classified into an existing series, how a position with duties that have changed materially gets reviewed, how a reclassification request gets evaluated and documented, how a promotion through a grade affects pay placement, how a transfer between departments is handled when the receiving department uses a different working title for similar work, and how acting pay is administered when an employee performs higher-level duties on a temporary basis.

Each rule is written, dated, signed by the official with classification authority, and stored where any HR analyst can find it on day one of employment. The rule cites the federal authority where applicable, including OPM Position Classification Standards for federal-equivalent grade determination and 29 CFR Part 541 for FLSA exemption analysis. The rule states the decision criteria in language a non-specialist can apply. It includes worked examples. A new HR analyst inheriting the function should be able to handle ninety percent of incoming classification questions by reading the rules and applying them, escalating only the genuinely novel cases to the HR Director.

Documentation discipline that survives staff turnover

The classification framework's documentation is its institutional memory. Three documents per classification are non-negotiable. The first is a current position description reflecting actual duties as performed, not the duties that existed when the position was last allocated. The second is an FLSA determination memorandum citing the specific exemption claimed or confirming non-exempt status, with each element of the duties test addressed. The third is a classification rationale memorandum stating why the position sits at its assigned grade, what comparator positions were considered, and what factor evaluation produced the grade decision. Pinnacle's five-factor analysis is the house method for building that record.

Most public-sector employers I have audited have the first document, partially current. They have the second document for a minority of positions, often built years ago and never refreshed. They have the third document almost never. The absence of the third document is what makes a reclassification appeal or a grievance unwinnable. The hearing officer asks the employer to explain why the position is at grade 14 rather than grade 15. The employer cannot answer with anything but "that is how it has always been." That is not an answer that survives review.

Documentation discipline is a small recurring cost. Operating without it is a large episodic cost. Cities that build the discipline into the framework at design and assign a clear owner for keeping it current avoid the episodic cost entirely.

A classification framework without current rationale documentation is a system the city operates on faith. Faith does not survive a hearing.

A governance cadence that prevents drift

Frameworks drift because nothing forces a periodic look. The sustainable design specifies the cadence explicitly. Pinnacle's house standard for public-sector frameworks is a full structural refresh every five years, with a partial refresh at the midpoint that examines pay range competitiveness against market and refreshes the comparator peer set. Between refreshes, the HR Director conducts an annual internal review covering three questions: what positions were reclassified during the year and why, what positions failed to recruit and what does the failure imply about pay placement, and what new positions were created and whether they fit the existing series cleanly.

The annual review is not a study. It is a structured conversation between the HR Director and the chief administrative officer that produces a short written record. The record is the institutional memory of the framework's operation. After five years of records, the next full refresh starts with a documented history of where the framework held and where it strained, which makes the refresh faster, cheaper, and more focused than a refresh that begins with no operational record at all.

The political reality cities have to manage

A sustainable framework has to coexist with a political environment that produces continuous pressure to make exceptions. Council members hear from constituents about specific salaries. Department heads advocate for their staff in budget discussions. Bargaining units negotiate pay structures that may or may not align with the framework's logic. The framework cannot pretend the political environment does not exist. It has to be designed to absorb predictable pressure without breaking.

Three design choices help. First, the framework's logic is documented in language elected officials can read. A council member who understands why grade 16 sits where it sits is less likely to ask for a structural exception. Second, the framework includes a defined process for proposing changes that goes through HR review before reaching the executive or the council. The process is not adversarial. It channels pressure into a structured analysis that either confirms the proposed change is consistent with the framework or documents why it is not. Third, the framework explicitly identifies which decisions are HR's authority, which are the executive's authority, and which require legislative action. Most pay drift happens at the boundary, when no one is clear who owns the call.

The bargaining unit relationship deserves a separate note. Where a city has collective bargaining over wages, the framework has to be reconciled to the bargained pay structure rather than imposed on top of it. The reconciliation is straightforward when the framework is built with bargaining unit input early in the design. It is a litigated problem when the framework is built in isolation and the bargained structure is treated as a constraint to be worked around. Cities that approach the bargaining relationship as a co-design rather than a constraint produce frameworks that last.

Indicators your framework is sustainable

A sustainable framework produces observable signals. None of these are exotic, and any HR Director can check them annually without external help. If the signals are present, the framework is operating. If the signals are missing, the framework is degrading even if no one has yet acknowledged it.

The first signal is exception count. A sustainable framework produces a small number of documented exceptions per year, each with a written rationale tied to the framework's rules. The exceptions are concentrated in the hardest-to-recruit positions and in genuine edge cases. If exceptions exceed five percent of the position count in any year, the framework is drifting and the next refresh is overdue.

The second signal is recruitment yield. A sustainable framework produces yield rates within a defined band for similar positions. If recruitment for grade 11 positions consistently produces strong candidate pools and grade 12 positions consistently fail to recruit, the structure is mispriced at that boundary and the next refresh should focus there first.

The third signal is grievance and appeal pattern. A sustainable framework produces grievances clustered around specific issues that can be remediated. An unsustainable framework produces grievances spread across the entire structure, which means the rules themselves are no longer believed by the workforce. The pattern, not the count, is the signal.

The fourth signal is internal equity perception. A periodic short survey to managers and supervisors asking whether their direct reports are paid consistently with the work they perform produces a quick read on whether the structure still tracks reality. Sustained negative responses concentrated in specific departments point to where the next review should look first.

The cheapest classification refresh is the one that begins with five years of clean operational records. The most expensive is the one that begins with nothing.

How Pinnacle approaches sustainable framework design

Pinnacle designs classification frameworks for public-sector employers using a four-layer reference framework. Federal authority anchors the technical work: OPM Position Classification Standards for grade determination logic, 29 CFR Part 541 for FLSA exemption analysis, and Title 5 U.S.C. Chapter 51 for the statutory basis of position classification. Industry methodology adds rigor: the WorldatWork Total Rewards framework for compensation structure, IPMA-HR public-sector classification guidance for series design, and the discipline of factor-based internal equity analysis. Pinnacle's house standard governs the operational design through the four pillars above. EEOC and OFCCP statistical standards apply where pay equity analysis is part of scope.

The deliverables are designed to be operated by the city's existing HR staff. Every framework Pinnacle delivers includes a written operations manual covering the recurring decision scenarios, training for the HR Director and analyst staff on the framework's logic, and a year-one support agreement that allows the client to call with edge cases as they arrive. After year one, the framework should run internally. The annual review and the midpoint refresh are scoped, sequenced, and budgeted at delivery so the city is not caught flat-footed when the cadence comes due.

The objective is not to lock the city into perpetual consulting engagement. It is to deliver a framework the city owns and operates. The next refresh, when it comes, should be a focused update to a working system, not a rebuild of a broken one. That is the design specification. Everything else is implementation detail.

← All insights