Raise Case in a Flat Merit Year: Document a Paid Skill

You are preparing a raise or promotion case in a flat merit year. The case that survives is the one that points to a documented skill the org is already paying for, and asks for the move as a skills adjustment.

Tenure and effort help you belong in the room. They do not move the pay line.

The Conference Board's 41st annual US Salary Increase Budgets Survey forecast a 3.5% median 2027 total salary increase budget, the same level as its 2026 actual and planned figures. The 2027 median merit budget forecast is 3.1%, with the gap between total and merit budgets intended for other pay actions, including retention adjustments and promotions.

That gap is where a skills adjustment can live. When your manager is protecting a small merit pool, the ask can be placed outside the usual merit raise. The org chart still decides who can approve it, but the budget category can be different.

A flat year still allows pay movement when the movement is targeted, documented, and tied to a budget category that already exists.

The budget line is the constraint

2027 total salary budgets are projected at 3.8% for high tech, 3.7% for banking, 3.6% for non-financial services, 3.2% for healthcare services, 3.2% for retail and wholesale, and 3.1% for consumer goods. Your sector changes the number you should expect.

Do not assume the system will fix a vague case. 70% of surveyed organizations used some automation in compensation, but only 1% reported advanced transformation. Make the skill visible in the review file, not only in conversation.

The org's language tells you which skill to name

Choose a capability that is already visible in the org: a job description, a project mandate, a hiring request, or a manager priority. Do not invent a new label. Use the language the company already uses when it pays for something.

A promotion case that ignores the org chart tends to fail in review. A skill that is only valuable to you makes the case weak. A skill that is valuable to a team, a product, or a revenue stream gives the case a clear owner.

Start with the work that is already being paid for, even if it is not your title. A skill can be a technical capability, a coordination capability, or a decision-making capability. The test is simple: can a manager point to a budget category, a hiring need, or a performance risk that the skill addresses?

Look for the skill where money is already being discussed. Hiring requests make the need visible. Blocked projects do the same. A manager who keeps asking for help with the same problem makes it harder to ignore. You are asking the company to recognize a need it already has, not to create a new one.

Do not let the case become a personality argument. The org chart is the map. It tells you who owns the budget, who feels the risk, and who can say yes. Helping a manager solve a problem they are already paying to address gives the case a sponsor.

The ask needs a skill, proof, and a pay move

A strong case is short because it is specific. It does not ask for recognition of everything you have done. It asks for a pay move tied to one capability that the org can place in a budget category. The skill, the proof, and the request need to be in the same file.

Put the case in the review file before the conversation. The three-part ask is the rule you keep:

• Name the in-demand skill in the org's language. Match a current job description, budget note, or manager priority. A sentence that could apply to many roles is too broad.
• Show documented evidence of use or impact. Use a project record, a measurable outcome, and a confirmation from a stakeholder who can speak to the result. Hours, overtime, or personal commitment are not enough.
• Request the pay move as a skills adjustment, not a merit increase. State the skill, the evidence, and the pay move in a short paragraph.

The evidence should be easy to scan. A reviewer should be able to see the skill, the action, and the result without asking you to explain the org chart. If a document requires a long preamble, it is too long.

If your manager cannot place it in a budget category, ask what evidence would let it be placed in one. That keeps the conversation practical and gives you a next step.