Build a written next-level promotion file before the review window opens
Build a written next-level file before the review window: documented outcomes, named projects, manager support, and a fairness blocker check.

The market is tighter than the hallway talk
You are preparing a promotion case for the next review cycle. Start with the org chart: the number of upward moves is not growing with the number of candidates. In Workday's October 2026 Global Workforce Report, internal role changes declined at 57% of employers. Promotion rates worldwide were essentially unchanged. The median applicant count for filled jobs rose from 58 to 69 over one year.
Do not wait for a role to appear. Roughly 50% of employees made no internal move attempt in the prior year, and 27% of non-attempters said no appealing internal opportunity was visible. Waiting means relying on the part of the process you cannot see.
Build a written next-level file before the review window opens. A manager should be able to bring that file into a decision meeting without reconstructing your case from memory.
The file is the argument
The strongest promotion evidence is the set of outcomes that map to the next level's responsibilities. When the next level owns a budget, a cross-team program, a risk, or a new capability, your file should show that you already carried that weight. Without that, the case reads as current-level excellence, which is valuable but not the same thing.
Career advice often gets sloppy here. It tells you to own more or be visible without asking whether the org chart has a place for the next version of you. A manager who has to defend your promotion needs a position, a criteria match, and a record. The checklist below is the file you should be able to hand to your manager before the promotion review begins.
- Write the next-level title and a short mission. Name the role and the problem it owns; otherwise your evidence will blur into current-level work.
- List the outcomes that only the next level would be expected to own. Each outcome should have a quantified result, a date, and a stakeholder who can confirm it.
- Name cross-team projects where you were the person other teams had to route through. A project that stays inside your team proves current-level execution, not next-level reach.
- Draft the manager support line in writing. Ask your manager to state which next-level responsibility you already carry and when they will defend it.
- Check the org chart for the actual position. A promotion that requires a new role, a budget line, or a vacant position needs a named decision owner before the review.
- Run the fairness blocker check. Ask whether the selection criteria are written, whether the same criteria apply to external candidates, and whether the decision maker has seen your file.
- Write a dated skill-gap plan. For any capability the next level requires and you have not shown, attach a project, a deadline, and the evidence you will produce by the review.
The blockers are decision problems
An excellent file can still fail when the blocker is structural. In Workday's October 2026 Global Workforce Report, employees trying to move internally most frequently cited paused hiring, lack of manager support, and selection processes perceived as unfair. Those are decision problems.
Manager support is the human part, and it should be explicit. In Workday's September 2026 survey of 6,000 full-time employees, 79% identified the skills needed for success, but only 66% said their employer helped them develop those skills. That gap makes the development ask concrete: a project, a deadline, a named stakeholder, and a written line of support.
Demand signals can sharpen the case, but they should not replace the criteria. Workday recruiting job requisition data showed a 51% rise in demand for hands-on AI capabilities, including building AI tools, workflow automation, and AI engineering, from September 2025 to July 2026. Your next level may require that capability. Attach the work you did, the workflow you changed, and the result you can defend. Do not bolt it on when it is not part of the criteria.
Send the file to your manager with a question: which blocker, if any, would stop this case?