Employee promotion process flowchart (nomination to effective date)
Employee promotion process flowchart: nomination or application, eligibility, the evidence pack, calibration across the peer group, funding, senior approval, pay within the band, the letter, effective date and handover.
How it works
Rename the lanes to your own structure
Replace Employee, Line manager, HR business partner, Calibration panel, Finance and reward, and Senior leader with the roles you actually have. Keep reward separate from the line if pay ranges are owned by somebody other than the budget holder; merge the two lanes if they are the same person. If there is no panel, rename that lane to whichever group compares cases — a heads-of-department meeting, a grading committee — and if nobody compares them at all, that is the first gap the chart has found.
Write the eligibility rule as figures
"Eligible and time in role met?" is inert until it carries numbers. Most policies set months at the current level, a minimum rating in the last completed review, and no live formal improvement plan, plus a line on people who changed role or returned from leave during the year. Publish it before the window opens. An unwritten eligibility rule is argued case by case, and those arguments are won by the most persistent manager rather than the strongest case.
Say what calibration is allowed to do
Record whether the panel's view is advisory or binding, whether any distribution or quota applies, who breaks a tie, and what a manager may do with a decision they disagree with. Then define the middle branch properly: More evidence needed should come back with a written list of what is missing and a date, otherwise it becomes a polite way of declining. Keep the reason for every outcome with the case; it is what you will be asked for next year.
Put the money questions in the right order
Ask finance two separate questions at "Budget and headcount available?": whether the establishment carries a post at the higher grade, and whether the in-year cost of the increase and its on-costs is funded. Then hold the pay decision until after the approval. Set the figure against both the band for the new level and the people already in it, and route anything outside the range back to be priced again: above the band, because exceptions signed once reappear as a pay-equity problem two years later, and below its floor, because an uplift that stops short of the minimum is a pay rise, not a promotion.
Fix the three dates and what the letter says
The effective date, the payroll cut-off and the announcement date are not the same date. Decide the order they happen in, write down whether a missed cut-off means back pay in the next run, and list what the letter must state: new title and level, salary and effective date, any change to bonus, notice or probation terms, and who the person now reports to. Then check the announcement does not go out before the letter is signed.
Walk it through, then publish a version
Take the finished chart to a line manager who has run a case, the HR business partner, somebody who has sat on the panel, whoever holds the budget, and if you can, an employee who was turned down last cycle — they will tell you what the process felt like from the outside, which is the part nobody documents. Correct it to what actually happens, then publish that revision and keep the earlier ones, so anyone opening it later can tell which version was in force.
Frequently asked questions
What are the steps in an employee promotion process?
A case is raised, either as a manager nomination or as an application from the employee. HR checks eligibility and time in role. The manager builds an evidence pack against the level or competency framework and writes a recommendation. A panel compares the case with others at the same level and supports it, asks for more evidence, or does not support it. Finance confirms budget and headcount. HR and a senior leader approve. Pay is set within the band for the new level and checked against the people already in it. A promotion letter is issued and accepted. The effective date is fixed against the payroll cut-off, the promotion is announced, and the responsibilities the person has vacated are handed over or backfilled. The names differ between organisations, but the order matters more than the vocabulary: the two failures that cause the most damage are pricing the job before it has been approved, and announcing it before payroll can pay it.
How is a promotion process different from a performance review process?
They answer different questions, and running them as one thing is why promotion decisions are hard to defend. A performance review process, drawn at /templates/performance-review-process, asks how well somebody did the job they hold: it launches a cycle, collects a self-assessment and feedback, produces a rating, calibrates ratings across teams and hears appeals. A promotion process asks whether somebody should hold a different, larger job. Its evidence is behaviour already visible at the next level, not a score for the current one; its calibration compares promotion cases against a level definition rather than people against a distribution; and its gates are budget, headcount and delegated authority, which have no place in an appraisal. The review cycle feeds this one — a rating is usually part of the eligibility test — but a strong rating is not a promotion, and treating it as one is how organisations end up promoting their best individual contributors into jobs nobody assessed them for.
Should employees be able to apply for a promotion, or only be nominated?
Both, and the chart keeps both routes visible with a "Nominated or self-applied?" decision. Nomination alone is the more common design and the more quietly unfair one: it makes the process depend on whether a particular manager notices, advocates well and remembers before the deadline, which reliably disadvantages people who are less senior-facing, part-time, recently returned from leave, or working for a manager who is new or overloaded. An application route on its own is not a fix either, because the people most likely to use it are the people most confident that they will be supported. The practical answer is to run both, brief managers that the deadline applies to nominations as well as applications, and record which route each case arrived by so that the split can be looked at by team, grade, gender and working pattern once the cycle has closed. That number is usually the most useful thing the process produces.
How should an off-cycle or retention counter-offer promotion be handled?
As a labelled exception with a named approver, never as a shortcut through the ordinary route. In this chart, an employee who is not eligible in the current cycle reaches "Off-cycle retention case?", and a yes goes through "Evidence the retention risk and market rate" to a senior "Off-cycle exception approved?" gate before the case may rejoin the normal evidence and calibration route. That order matters, because a counter-offer under notice is decided under time pressure by the person with the most to lose from the resignation. Give the approver the market data, an internal comparator, the pay position of the rest of the peer group, and an answer to the plain question: would this promotion have been made had nobody resigned? If not, it is a retention payment with a job title attached, and the rest of the team will work that out. Whatever is decided, record the reason and count how many off-cycle cases the year produced; a rising count usually means the bands or the cycle timing are wrong, not that people are exceptional.
What should happen when someone is not promoted this cycle?
The route needs an ending with a date on it, which is why "Agree a development plan and re-review date" leads to "Not this cycle, re-review date set" rather than to silence. Everybody who reaches it should get the same three things: the reason, expressed as the gap between the evidence presented and the level definition rather than as a general remark about readiness; a small number of specific things that would change the answer, with who is responsible for creating the opportunity to do them; and a date when the case will be looked at again. Distinguish the causes, too. A case that was not supported at calibration is a different conversation from one that was supported but not funded, and telling somebody they were not good enough when the real answer was that the post did not exist is both untrue and easy to disprove. Note that this is a development plan, not a formal improvement plan; the latter addresses performance below the level somebody already holds and is a different process entirely.