Build a promotion case that can move before the next review

You are told to wait for the annual review. Your work may already sit at the next level. The org chart may show a different option, and the question is whether the request can move without waiting for a calendar date.

A promotion case is a management decision, not a loyalty reward. It has to pass a budget conversation, a level definition, and a skeptical manager who can say no without hurting morale. The annual review makes that easier because everyone is already in the room. The Pave-Alpine Rewards 2027 budgeting survey included 251 companies, mainly from technology and life sciences. Among them, 57% make promotions outside the annual review cycle. In the same group, 61% of companies promoted more than 10% of their employees. Off-cycle promotion is common enough that a well-built case should not feel like a special favor.

The annual review is a deadline, not a requirement

Many employees treat the review as the only place where career evidence becomes real. That is a mistake when the job has already changed. When you have owned a project, led a meeting, made a decision, or carried a risk that belongs to the next level, the evidence exists now. Waiting can make it look like a claim instead of a record.

Merit budgets are usually the smaller part of the pay conversation. For 2027, U.S. companies planned a median merit budget of 3.5% of payroll. The survey identified 9% to 12% as the most common average promotion raise. A promotion changes level, scope, and accountability, not just pay. Ask only for money and you are asking for a merit decision. Ask for a level change and you are asking for a promotion case.

87% of surveyed companies set merit increases using individual performance ratings. Ratings are the minimum, not the full case. A strong rating says you did the job well. A promotion case says you are already doing the next job.

Build the file before the ask

The file should be short enough to read quickly and specific enough to defend in a meeting. Do not write a long narrative. Write a case. Each section should answer a question a manager will ask when deciding whether to move you.

• Define scope: List the work you own end to end, not the tasks you touch. Done means an outline of what you decide, what you escalate, what you no longer need approval for, and where your work connects to revenue, cost, risk, or customer outcomes.
• Quantify impact: Tie each scope item to a result. Use numbers when you have them, such as time saved, revenue protected, defects reduced, cycle time shortened, or churn lowered. If the result is qualitative, name the decision it changed. You are done when the table shows the outcome, your role, and the evidence.
• Document autonomy: Show where you acted without direction. Include examples where you set the approach, chose the tradeoff, or handled a problem before it became a manager issue. The finished version is a short list of decisions, not a list of responsibilities.
• Gather performance evidence: Collect ratings, written feedback, project notes, and stakeholder comments that show consistency. It should have dates, names, and links or excerpts, not a paragraph of praise.
• Set a quantified ask: Name the target level, the title if it exists, and the compensation range you expect. The ask should be a sentence: I am requesting a move to [level] with a target compensation of [range]. A vague ask is easy to defer; a specific ask is harder to ignore.
• Choose a submission trigger: Pick the moment when the case is strongest, such as after a shipped project, after a budget update, after a reorg, or after a clear gap in coverage. You are done when your manager has a dated note with the file attached and a request for a short decision meeting.

Make the ask specific enough to approve

A manager can approve a promotion faster when the next level is visible. Name the next role when the org chart has a clear one. For an ambiguous next role, describe the level in terms of scope, impact, and autonomy, and ask what evidence would close the gap. That keeps the conversation about the job, not about your patience.

Do not wait for permission to build the file. Build it, then ask for the meeting. A no should name the missing piece. A yes should make the paperwork easier, not harder.