Most promotions are decided in a room the candidate never enters. A manager makes a case, a skip-level asks whether the person is "operating at the next level," someone mentions budget, and someone else mentions the person promoted last cycle with a thinner case. The decision that comes out is defensible the way a jury verdict is defensible: people who were there can explain it. Nobody who was not there can check it.
That is advocacy, and advocacy is the default whenever promotion criteria are not written as skills and levels. The best-argued case wins, and it is usually made by the most senior manager in the room, for the person most visible to them, in the function with the most headroom that quarter. None of those are measures of capability.
A promotion workflow is the fix. Not a form: a sequence, with criteria that can be checked against a record, evidence that accumulates before the meeting, approvals that are named steps, and a level change recorded with a date. This guide covers how to build one, what to automate, what to keep human, and how to know it is working. The short version is the promotion workflow reference entry; this is the long one.
What a Promotion Workflow Is
A promotion workflow is the defined sequence an organization follows from evidence that a person meets the next level's requirements, through the approvals that confirm it, to the recorded change of role or level. It has four parts: criteria (the benchmark proficiency each skill requires at the target level, the training the target role requires, the certifications that must be current), evidence (assessed grades against those benchmarks, approved training records, and current certifications, each with a date and a source), approvals (named people who confirm the decision as recorded steps rather than an email thread), and the change itself (a new level or career assignment, saved with the prior level retained). A workflow with all four can answer the question that follows every contested promotion: on what basis, approved by whom, and when. A workflow missing any one of them cannot.
Why Promotions Run on Advocacy
Advocacy fills the space left by undefined criteria. Ask a manager what "senior" means for a field service technician and you get a paragraph: handles escalations alone, mentors the new hires, customers ask for them by name. Ask a second manager in the same function and you get a different paragraph, equally sincere. Neither can be checked against a record, so every promotion decision reopens the definition.
Three things follow. Calibration meetings become negotiation, because there is nothing to calibrate against. Employees cannot see what advancement requires, so the ambitious guess, the cautious wait, and the ones with less visible managers leave. When a promotion is challenged, HR has meeting notes and nothing else.
The pattern is the same in a hospital as in a software team. A nurse moving from Clinical Nurse II to III, an engineer moving from L3 to L4, a plant operator moving from Level 2 to Lead: in every case the organization has an intuition about the difference and no written test for it. Career ladders describe the levels; they do not tell you whether a specific person has reached one. The career pathway makes the route visible, and the workflow is what moves someone along it.
Write the Criteria as Levels, Not Adjectives
The first job is to turn every adjective in the career ladder into a number a record can hold. Three kinds of criteria do this.
Benchmark proficiency per skill, per level
A career already lists the skills a role requires. Give each skill a required proficiency at each level: fault diagnosis at Level 2 means a 3 on your scale, performing independently on known faults, and at Level 3 a 4, handling novel faults and teaching others. Do this for every skill in the career and "senior" becomes a row of numbers instead of a feeling. The benchmarks must sit on the same scale your assessments use, or the comparison is meaningless.
Required training for the target role
Some criteria are binary. The target role requires the high-voltage safety course, the advanced clinical module, the on-call rotation induction. List them on the role. Approved training for the target role is the cleanest trigger a workflow can have, because it is either complete or it is not.
Certifications that must be current
For regulated functions, add the credentials the level requires and require them to be unexpired on the date of the decision. A promotion into a role that carries a lapsed certification is a compliance finding waiting to be written.
The test for a criterion is simple. If it cannot be checked against a record, it is an opinion, and opinions belong in the manager's approval step, not in the criteria.
The Evidence Chain
Criteria without evidence are a job description. The workflow's second job is to make sure evidence accumulates against the criteria long before anyone convenes a meeting. Four records do the work, and each one has an owner and a date.
| Record | What it proves | Where it comes from | Who is accountable |
|---|---|---|---|
| Assessed proficiency | The person performs each skill at or above the next level's benchmark | Manager assessment, with self-assessment as a second signal | Direct manager |
| Approved training | Every course the target role requires is complete and signed off | Training records, approved by the designated expert or approver | Training approver |
| Current certification | Required credentials are valid on the decision date | Certification record with issue and expiry dates and attached evidence | The holder, verified by an approver |
| Recorded approval | A named person confirmed readiness on a date | The workflow's approval step | Direct manager, then any second approver |
Completeness matters more than order. When a manager opens the case, the readiness question should already be answered by data with dates on it: the skills matrix, filtered to the next level's benchmarks, shows which of a Level 2 technician's grades already meet Level 3 and which do not. The gaps are the development plan. The manager's judgment is still required, but it is now a judgment about a person whose record is in front of everyone, not a story told from memory.
The Steps and Who Owns Each
A promotion workflow is not a single button. It is a sequence of steps, each with an owner. Written down, it looks like this.
Eligibility. All required training for the target role is approved. The system can detect this; nobody has to remember to check.
Readiness. The manager reads the person's assessed grades against the next level's benchmarks. Where grades fall short, the manager assigns learning and schedules a reassessment; where they meet, the case moves to approval. A "high potential" label keeps the pipeline visible between cycles.
Manager approval. The direct manager confirms readiness and records the decision. This is where observed performance, the part no record captures, enters the workflow, as a recorded step rather than a hallway conversation.
Second approval. Where policy requires it, a named approver signs off: a skip-level leader, a functional head, or HR. Naming the approver in the workflow turns "get sign-off" into a step with a date.
Assignment. The new level or career is added to the person. The prior level is retained in history. Anyone who needs to know receives the activity log.
For a software engineering organization the second approver is usually a calibration committee chair; for a nursing unit, the clinical educator; for a plant, the operations manager. The roles differ. The shape does not.
Where Automation Belongs, and Where It Does Not
Everything mechanical in the sequence should be automated: detecting that required training is complete, routing the approval to the right person, adding the new level, notifying stakeholders, writing the log. These are hand-offs, and hand-offs are where promotions stall. The training record sits in one system, the manager conversation happens in another, and the level change waits for someone in HR to see the email.
SkillsDB takes a different approach to that problem. The criteria live on the career: levels, a benchmark grade per skill per level, required training, and linked certifications. Readiness shows in the Skills Matrix by filtering to the next level's benchmarks, and a promotion is recorded by changing the person's level, with their level history kept.
Journeys automate the sequence around that change. An activated journey enrolls anyone whose required training for the target career is fully approved, routes Manager Approval and Custom Approval steps by email and Inbox to the named approver, assigns the new career or level once approvals are in, notifies the people who need to know, and logs every step on an Activity Page. Steps run strictly in order, and a withheld approval stalls the journey without rolling anything back. The pieces are described on the career frameworks page.
Two things are not automated, and should not be. The first is the judgment that a person performs at the next level: a human decision, which the workflow routes to a named human with the evidence attached rather than replacing with a threshold. The second is the criteria themselves, because automation adds nothing while "senior" is still an adjective. Write the benchmarks first, prove the manual sequence on one career, then let the system take over the hand-offs.
The Fairness and Audit Dividend
The obvious benefit is speed: fewer promotions that slip a quarter because a form sat in someone's inbox. The larger benefit is what the record makes possible.
Every promotion now carries the same answer to the same questions: which benchmarks the person met and as of which assessment, which training was approved and by whom, who approved the move and on what date. Two candidates in different teams under different managers are measured against the same numbers, and the difference in their outcomes is visible in their records rather than in the persuasiveness of their advocates. That is fairness in practice: not identical outcomes, but identical criteria and an inspectable trail. It is also what an employment lawyer, a union representative, or a regulator asks for when a decision is challenged.
The employee side matters as much. When the next level is a set of benchmarks a person can see, "what do I need to do to get promoted" has an answer that does not depend on who their manager is. That is the difference between a career ladder people believe in and one they route around by leaving.
A Rollout Plan
Promotion workflows fail in rollout for the same reason competency frameworks do: organizations try to define every level for every role before anything runs. Start narrow.
Weeks one to four: one career, all its levels. Pick a career with a real promotion backlog and a manager who wants this to work. Write the benchmark per skill per level with the people who hold the roles today, list the required training and certifications, and agree who approves in what order.
Weeks five to eight: run it by hand. Assess everyone in the career, read the matrix at the next level's benchmarks, and take the first two or three cases through the full sequence manually, recording each step. Expect the benchmarks to need adjustment; that is the point of running by hand first.
Weeks nine to twelve: automate the hand-offs. Once the sequence has held for real cases, build the journey: training completion as the trigger, the approvals in order, the level assignment, the notifications. Activate it for the one career, then take the pattern to the next.
Organizations that skip the manual phase automate their ambiguity. Those that skip automation end up back in the meeting room within two cycles.
What to Measure
Four numbers tell you whether the workflow is doing its job, and all of them fall out of its own log.
Time from eligibility to decision. The gap between the date required training was approved and the date the level changed. If it is not shrinking, a hand-off is still manual somewhere.
Share of promotions with complete evidence. Promotions where every criterion was met by a dated record at decision time. The target is all of them; anything less is advocacy with a form attached.
Distribution across managers. Promotion rates per manager, adjusted for eligibility. Wide variance against identical criteria is a manager problem the workflow has made visible.
Stalled approvals. Cases sitting at an approval step past a set number of days. Each is a person waiting on a decision that has already been evidenced.
A Promotion Is a Claim About Capability
Every level change is a statement that a person can do something they could not do before, or could not be trusted to do alone. Organizations have always made that claim. Most have never been able to show their work.
A promotion workflow is how the claim becomes provable: criteria written as levels, evidence gathered before the meeting, approvals recorded as steps, the change saved with its history. Advocacy does not disappear. It is confined to the one step where it belongs, the manager's judgment, and it arrives with the record attached.