People Management
Separate Performance Ratings, Promotion Readiness, and Pay Decisions
Map same-cycle performance, next-role readiness and compensation to different evidence, constraints, owners and approval statuses; explain a strong rating without promised promotion.
Treat a performance rating, promotion readiness, and pay decision as related decisions with different questions, evidence, constraints, and approvers. Assess current-role performance against the applicable expectations; evaluate next-role readiness against sustained scope and the organization's requirements; and confirm compensation through its own range, budget, and approval process. Do not translate a strong rating directly into a promised title or salary change, or downgrade an accurate rating to explain a constrained reward.
This LandOffer.ai guide includes a completed fictional three-decision record and employee conversation. All people, work examples, ratings, pay proposals, dates, and approvals are illustrative. No actual review, promotion process, compensation transaction, or employee outcome was tested.

Give each decision its own question
The performance question is: how did this person perform in the role and period being reviewed? Relevant evidence includes agreed responsibilities, delivered outcomes, quality, collaboration, and how the work was done. Use the employer's actual definitions rather than importing another company's rating labels.
MIT's ratings guidance describes performance levels through results and competencies relative to position expectations. Its higher ratings can recognize contribution beyond ordinary expectations. That illustrates why strong current-role performance can include valuable stretch contributions without, by itself, resolving a different employer's promotion process.
The promotion question asks whether the evidence meets the next role's expectations and whether the proposed role change can proceed. Depending on the employer, that may involve sustained scope, independent judgment, influence, business need, an available role, and formal review. Distinguish an evidence gap from a role-availability constraint; they require different explanations and actions.
The pay question concerns the actual compensation action available in the current cycle. Performance may be an input, but the result can also depend on position in a range, market and internal considerations, available funding, eligibility, and approval. Verify which factors apply at your employer. Keep a separate status, evidence basis, constraint, and owner for each decision even when the same cycle connects them.
Map evidence without moving it between questions
One work example can inform more than one decision, but it should answer the relevant question each time. Delivering a difficult component may strongly support the current-role rating. To support promotion, the same example would need to demonstrate the particular next-role scope or judgment being assessed.
Avoid counting hours or visibility as a substitute for impact. An employee's repeated rescue work may deserve recognition while also revealing a workload problem. Asking for still more unbounded work to “prove commitment” can obscure both the contribution and the conditions needed to evaluate it.
Identify the demonstrated scope, observation period, and remaining uncertainty against the applicable role framework. Do not turn one successful high-visibility assignment into assumed evidence of sustained responsibility across a broader role. Equally, do not erase the assignment's value because it does not establish every promotion criterion.
GitLab's engineering career-development page describes senior engineering as a destination role and says progression beyond it depends on different expectations, availability, and need. This is an employer-specific example of separating strong contribution from an automatic next step. It does not prescribe your organization's promotion criteria or authorize a manager to invent a hidden requirement.
Naming the missing evidence lets the employee supply a correction or discuss a supported opportunity. “Need more leadership” is too vague. “We have evidence from one cross-team decision, but not yet sustained ownership of the defined technical direction” gives the employee something they can inspect, question, and discuss within a supported workload.
Explain compensation through the actual approval route
Do not use the rating as a shorthand answer to every pay question. Confirm which compensation action is being considered: base-pay adjustment, one-time payment, variable award, equity, or no change. A salary range is not an approved personal amount, and a proposed award is not a received payment.
MIT's merit-increase guidance describes distributing a merit pool, considering salary position and other factors, and institutional recommendations reviewed in the context of available funds. These are MIT's arrangements. They illustrate that compensation involves resource and approval decisions alongside performance; they do not establish a universal merit formula or entitlement.
Ask the responsible HR or compensation contact what the manager can communicate and when. If an amount is awaiting approval, say so. If the process has not produced a date, do not fill the gap with a confident promise about the next payroll or cycle.
Budget limits also should not rewrite the performance evidence. If your review supports a strong rating under the actual framework, explain that assessment on its merits. A constrained pay pool may affect the compensation result, but “we could not fund a larger increase” is a different statement from “your work was only average.”
The opposite distinction matters too. A pay adjustment for market alignment or another permitted reason does not necessarily mean the employee received a higher performance rating or promotion. Record the actual reason and approval rather than inviting colleagues to infer one decision from another.
Completed three-decision record for one cycle
In this fictional case, Selene is a senior engineer on a transit timetable service. During the review period she delivered a revised route-conflict validator, improved the team's review examples, and coordinated one difficult interface decision with another team. Manager Anwar uses the fictional employer's current-role framework; the rating names and promotion criteria below are invented.
The record is prepared on October 19. It distinguishes a finalized rating, a readiness assessment, a role constraint, and a compensation proposal still awaiting approval.
| Decision | Evidence and constraint in the fictional case | Owner, status, and next action |
|---|---|---|
| Current-role performance | Selene's validator and review examples meet the agreed quality and delivery expectations; collaboration evidence supports the employer's “Exceeds Current-Role Expectations” definition. The cross-team decision is recognized as a valuable contribution. | Anwar and the designated review owner finalize that rating for this cycle. No rating reduction is made to fit the pay pool. |
| Promotion readiness and role | The next IC role requires sustained technical direction across several teams. One interface decision is promising evidence, but the review does not yet establish sustained scope. Separately, no additional next-level role scope is approved in the current plan. | Anwar records “readiness evidence incomplete; organizational opportunity not approved.” Director Helena owns the role-need question. No promotion date or future approval is promised. |
| Compensation | Anwar proposes a gross annual base adjustment from USD 125,000 to USD 128,000 within the existing role. HR must verify the applicable range and available cycle budget; compensation approval is still pending. No new equity or one-time award is proposed. | Compensation partner Ellis owns the pending approval route. October 26 is the planned status update, not an effective date or promise of payment. Current approved base remains USD 125,000. |
This is a three-decision record even though the promotion row contains two distinct issues. Readiness evidence and organizational opportunity are both visible; a missing role does not prove unreadiness, and incomplete evidence does not become complete because the business needs someone immediately.
The compensation proposal is not a reward formula derived from the rating. The illustrative USD 3,000 difference is a proposed annual base change, not an approved amount, one-time payout, market benchmark, or guarantee. Selene's existing role and approved compensation remain the baseline until the applicable process changes them.
Anwar also records what he can do now: preserve the contribution evidence, clarify the next-role scope, and bring a bounded opportunity proposal to Helena. He cannot create a role or approve compensation by encouraging Selene to keep working harder.
Completed conversation that corrects the conflation
Selene expected an excellent review to bring promotion and a larger increase. The fictional conversation below explains the three decisions without treating her disappointment as a misunderstanding she alone caused.

Selene: “If my work exceeds expectations, why am I not being promoted? Does the pay proposal mean the rating is less strong than it sounds?”
Anwar: “The rating recognizes your work in the senior engineer role this period. The validator, review examples, and interface work support that assessment. I am not revising it downward because of the compensation process. Promotion asks a different question about sustained scope in the next role, and the review has not yet established that evidence. Separately, Helena has not approved additional next-level scope in the current plan.”
Selene: “So should I take on every cross-team request until that changes?”
Anwar: “No. More requests do not automatically produce the evidence, and I cannot promise a role for doing them. I will ask Helena whether a defined technical-direction assignment is useful and supportable. If we agree to explore it, we will name the decision authority, reviewer support, time boundary, and current work that stops before you accept it.”
Selene: “Is USD 128,000 approved, and when would it start?”
Anwar: “It is my proposal, not approved compensation. Ellis is checking the range and budget through the compensation route. Your approved gross annual base is still USD 125,000. I will give you a status update on October 26, even if approval is still pending. I do not have an effective date or payment date to promise.”
Selene: “The cross-team decision also included follow-up that may not be in the review.”
Anwar: “Let's examine that evidence and correct the record if the review missed it. That can change our understanding of readiness; it would not itself create approved role scope or compensation.”
The fictional conversation produces a responsibility record, with follow-up still pending: Anwar will review the additional follow-up evidence with Selene by October 23; Anwar will bring the bounded scope question to Helena by October 23; Ellis retains the compensation approval route; Anwar will provide the October 26 status update. None of those actions is presented as an approved promotion or pay increase.
The conversation does not promise that disappointment will disappear. Its purpose is to explain the actual decisions, invite factual correction, and make the manager's next actions reviewable. An employee can understand the distinctions and still disagree with the outcome.
Turn an evidence gap into a supported next question
If promotion evidence is incomplete, say what the review did and did not establish. Invite missing examples through the permitted review process. Avoid defending an initial judgment simply because you have already communicated it, or implying that a current-role rating becomes invalid when the employee supplies additional scope evidence.
Then distinguish learning opportunity from promotion commitment. A bounded assignment can help develop or demonstrate a capability, but it should have a useful business purpose, clear authority, feedback, and a time limit. It should not become unpaid or invisible responsibility added indefinitely to the existing workload.
In Selene's case, a technical-direction assignment remains only a proposal. Helena must first determine whether the work is needed and can be supported. If that opportunity does not exist, Anwar should say so rather than asking Selene to manufacture an expanding role on her own. The next conversation might address current-role depth or another supported route without treating either as consolation for a promised promotion.
Keep this follow-up proportionate. The article's task is to map decisions, evidence, constraints, and owners; a complete development plan or promotion packet is a separate artifact. A long list of goals cannot repair an unclear explanation of what was actually decided this cycle.
Close each decision without inventing certainty
Before the conversation, check the status of every claim. Which rating is finalized? What readiness judgment has actually been reviewed? Is there a supported role opportunity? Which compensation action is proposed, approved, effective, or observed in payroll? Use those status words consistently.
Afterward, save corrections, unresolved questions, owners, and the next communication point in the approved private location. Do not share peers' confidential ratings or pay details to justify a decision. A clear explanation can use applicable criteria and the employee's own record without exposing someone else's information.
If the compensation outcome changes, update that record and explain its actual reason. If new readiness evidence changes the assessment, update that assessment separately. If an organizational role becomes available, use the required process. No single update silently settles the other decisions.
Save each decision status and the next communication owner and date, including an update when an approval is still pending. Return to LandOffer.ai for related management guidance after documenting the current-cycle decisions, evidence limits, and next owners. Keep recognition, readiness, organizational opportunity, and compensation explicit in the saved explanation.



