How to Level Existing Employees When You Introduce a Career Framework

The meeting where the framework meets the people

The framework was approved on a Thursday. By Monday morning, a senior designer had walked into the HR manager's office with a printout of the new Level 4 description and one question: "Which of these am I?" Two desks away, a developer hired eighteen months ago had already asked the same thing of his manager, who had no answer. A third person, six years in and well liked, had quietly worked out that the framework described someone more junior than she believed she was.

Every company that introduces a career framework reaches this point. The document is finished, the titles are drafted, and 40 people are still in jobs that were never defined against it. How you place them decides whether the framework is read as a fair map or as a ranking handed down without explanation.

This article sets out how to level existing employees in a way you can defend to the employee, to their manager and to a skeptical executive: the evidence to gather, the sequence of passes, how to calibrate, how to handle the awkward cases, and how to communicate the result.

Separate leveling from performance, pay and title

Most leveling disputes start because three different questions get answered as one. Keep them apart before you start.

• Level answers: what scope, autonomy and impact does this person's work consistently demonstrate today, measured against the framework's level descriptions?
• Performance answers: how well did this person do the job they were given this cycle?
• Pay and title answer: what does the company decide to do about the level once it exists?

A person can perform strongly at Level 2 and still be a Level 2. Someone can be coasting at Level 4 and still be a Level 4 on the evidence of their scope. If your leveling exercise tries to reward effort or repair old pay disputes, it will produce inflated levels that the framework cannot sustain. Decide in advance that the exercise answers only the first question, and that pay review, if any, is a separate and later decision. Seek advice from your own counsel or compensation specialist on any change to pay or title that follows.

Fix the rule in writing for managers: "We level on demonstrated, repeatable work at the scope the level describes. We do not level on tenure, potential or likeability."

Prepare the level descriptions so they can be evidenced

A leveling exercise is only as good as the descriptions it uses, and how to level existing employees fairly starts with them. Before any person is placed, check that each level is written in observable terms. A description such as "shows strong ownership" cannot be evidenced. "Owns delivery of a project from scoping to handover with minimal supervision, and escalates risks before deadlines slip" can.

If you are still drafting the structure, our guide to how to build a career ladder covers level and track design, and how many career levels you need covers granularity. For the leveling exercise, the practical test is simple: take two real people you know well, one clearly more senior than the other, and ask whether the descriptions separate them. If a reasonable manager could read the Level 3 and Level 4 text and not tell which fits, rewrite before you place anyone.

A starting structure such as the Career Ladder Builder — Master Template, which provides six levels, real titles, and a computed promotion-readiness check, gives you descriptions to adapt rather than a blank page.

A three-pass method for how to level existing employees

The method that holds up best is three passes, each producing a written record. Run them in order and keep them independent until the last step.

Pass 1: Manager proposal with evidence. Each manager proposes a level for each direct report and attaches evidence. The evidence rule is strict: at least two concrete work examples from the last 12 months per person, each tied to a specific phrase in the level description. A proposal with no evidence is returned, not accepted.

A simple row looks like this:

Employee	Proposed level	Evidence against level description	Confidence
A. Rivera	L3	Led the billing migration end to end (scope); trained two new hires (influence)	High
J. Okafor	L3 or L4	Owns the client onboarding process; has not yet set direction beyond own team	Medium

Pass 2: Employee self-placement. Ask each employee to place themselves and supply their own examples, using the same format. This is not a vote. It surfaces work the manager has not seen, and it shows you where expectations differ before the announcement, not after it.

Pass 3: Reconcile and calibrate. Compare the two placements. Where manager and employee agree, the placement goes forward to calibration as a straightforward case. Where they differ by one level, the gap itself is the agenda: which example would change the answer? Where they differ by two or more levels, treat it as a signal that either the descriptions or the communication has failed, and resolve it before the case goes further.

Keep a scoring record for each case that sums up the placement, the evidence and the reason. That record is what you will point to when someone challenges the outcome.

Calibrate across managers before anyone is told

Individual manager proposals are not yet levels. They are opinions, and opinions vary by rater. In a widely cited study of performance ratings, Mount, Scullen and Goff (Journal of Applied Psychology, 2000) found that 62% of the variance in ratings was attributable to the individual rater's perceptions, while actual performance accounted for only 21%. Leveling is a different judgment from rating, but it is made by the same people and is exposed to the same effect.

Calibration is the structured response. Put the managers in one room, or one call, and work through the proposals:

1. Start with anchors. Agree on three or four people everyone knows well and settle their levels first. These become the reference points for the rest.
2. Review by level, not by manager. Look at everyone proposed for Level 3 together, then Level 4. Inconsistencies between teams become visible: the "Level 4" in one department who does less than the "Level 3" in another.
3. Look at the shape of the distribution. If nearly everyone is proposed at the top two levels, either the descriptions are too soft or the proposals are generous. Neither is necessarily wrong, but you should know which it is.
4. Challenge with the evidence rule. Ask the manager what a person did, not who they are. Record the decision and the reason for every change.

Our guide to calibrating performance reviews describes the mechanics of a session in more detail, and the same facilitation applies here.

Level on demonstrated, repeatable work at the scope the level describes — not on tenure, potential or likeability.

Handle the edge cases with a written rule

Most of the difficulty is concentrated in a handful of recurring situations. Decide the rule for each one before the first case arises, so that you are applying a policy rather than negotiating.

The long-tenured generalist. Someone with ten years of service whose work sits at Level 2 scope. Level on the work. Acknowledge the experience in the conversation, and build a development plan toward the next level.

The recent high performer. Someone who joined a year ago and operates well above their original level. Level on the scope demonstrated, not on time in role. Do not impose a waiting period unless the framework states one.

The person between two levels. Where evidence supports some but not all of a higher level's expectations, place at the lower level and state the specific gaps. The guide to evaluating career readiness shows how to score that distance so it can be turned into a plan.

The manager with no IC level. If your framework has separate individual-contributor and manager tracks, place people on the track that matches their current role, not the one they might want next.

The hybrid role that fits no description. Do not stretch a level to cover it. Flag it, log it, and use it as input to the next framework revision.

Cases where a decision may affect pay or employment terms. Route them to counsel or your compensation lead before anything is communicated.

Communicate the result so it reads as fair

Retention is at stake in how this conversation goes. Momentive Software's 2026 State of the Mission-Driven Workforce reports that 65% of employees with clear career paths say they are not considering leaving, compared with roughly a quarter of those who lack career-path clarity. Gallup's 2024 research found that only 29% of employees strongly agree the performance reviews they receive are fair. A leveling exercise that is opaque risks feeding the second figure rather than the first.

Sequence the communication in this order:

1. Manager briefing first. Give managers the framework, the calibrated placements for their team, and talking points. No manager should learn a level at the same time as the employee.
2. A short all-hands explanation. Describe the framework, what leveling is and is not, and the timeline. State plainly that it is not a performance rating.
3. Individual conversations, same day or within 48 hours. Each person hears their level, the evidence behind it, and what the next level would require. Hand over a one-page summary in writing.
4. An appeal route. Offer a defined way to ask for a second look, with a time limit, and make clear that new evidence, not disagreement alone, is what changes a level.

Expect to place some people lower than they expected. Say so in advance to managers. A level that is explained with evidence and paired with a development plan is easier to accept than a level that is simply announced. Our list of career framework mistakes includes several that show up at precisely this stage, such as announcing levels without explaining the criteria.

Keep the record, then run it again

Treat the first leveling as a baseline, not a verdict. Store each employee's level, the evidence, the date and the decision-makers. When the framework is revised, or when a promotion cycle opens, you will compare against this record rather than reconstruct it from memory.

A spreadsheet can carry this for a small group, but it has no version control for edits to the framework, no automated gap reporting and no audit trail for decisions. CareerEvaluations is built for this loop: a 1–5 score per competency with evidence notes, an approve/reject workflow, and auto-generated per-employee gap reports against the target level.

Whichever tool you use, the practice of how to level existing employees is the same. Define levels in observable terms, gather evidence, calibrate across managers, apply written rules to edge cases, and explain every outcome. To start from a working structure rather than a blank page, the Career Ladder Builder — Master Template is available as a template download.