How to Document Promotion Criteria and Review Weights
Turn promotion decisions into a transparent scorecard: define eligibility gates, evidence standards, weighted criteria, and a review cadence you can defend.
How to Document Promotion Criteria and Review Weights
Promotions get messy when the rules live in someone's head. One manager remembers the last big project. Another weighs tenure. A third trusts a gut feeling. You need a scorecard people can inspect before the decision, not a rationale written after it.
Documented criteria help reviewers compare evidence consistently and show employees what the next level requires. Here is a practical way to build that document and review the weights behind it.
1. Define the decision and its gates
Write one sentence that names the role, level and review window: “This process decides whether a senior engineer is ready for staff engineer based on evidence from the last 12 months.”
Separate eligibility gates from weighted criteria. Gates are pass/fail requirements, such as required training or minimum time in role. Criteria measure the strength of evidence. A candidate can meet every gate and still not be ready. A high score should never erase a failed gate.
Name the decision options too: ready now, ready with a defined support plan, or not yet. Clear options make the review less political.
2. Choose a small set of criteria
Pick four to six criteria. More than that and reviewers start scoring noise. Group them into pillars if it helps: execution, influence, culture and role-specific capability.
Wudd's Promotion Engine uses three pillars — Execution, Network Influence and Cultural Adherence — and combines them into a Promotion Value Score. The lesson is not to copy those weights. It is to define each pillar, state where evidence comes from and make the combination visible.
Write a definition for each criterion at the target level. “Strong communicator” is not a criterion. “Writes decision records that other teams use without follow-up” is.
3. Write evidence standards
For each criterion, document six things: evidence source, collection method, time window, owner, rating scale and minimum data needed. This is where promotion documents often fail. They list qualities but do not say what counts as proof.
Use outcomes and behaviors. Outcomes include KPI results, delivered projects and quality measures. Behaviors include peer input, values-tagged recognition and examples of cross-team work. Do not rely on a single manager's memory.
A sample scorecard for one role family might look like this:
| Criterion | Evidence | Window | Weight |
|---|---|---|---|
| Execution | Delivered outcomes, quality, KPI results | 12 months | 40% |
| Network influence | Cross-team peer input and collaboration examples | 6 months | 25% |
| Cultural adherence | Values-tagged recognition and specific examples | 12 months | 20% |
| Role capability | Skills assessment and project evidence | Current cycle | 15% |
This is an example, not a universal formula. Every weight should have a named evidence source.
4. Set weights with a reason
Weights express strategy. If execution matters most in the next role, give it more weight. If the role depends on cross-team influence, do not leave influence at 5% and hope reviewers notice it.
Use a simple scale, such as 1 to 5, with written anchors for each number. A 4 should mean the same thing to every reviewer. Then calculate a weighted score: rating multiplied by weight, summed across criteria.
For example: 4 × 0.40 + 3 × 0.25 + 4 × 0.20 + 3 × 0.15 = 3.60. Set a threshold, such as 3.50, plus at least one strong example for each core criterion. A total score alone can hide a serious gap.
Decide how to handle missing data. Do not turn a blank into a zero or an average without saying so. Mark confidence. Wudd's Promotion Value Score includes a data confidence level on every score. Apply the same principle to a spreadsheet: missing evidence should prompt a conversation, not a silent penalty.
5. Freeze the rubric and govern exceptions
Version the document. Date it. Record the weights, thresholds, evidence rules and rating anchors. Freeze them before nominations open or calibration begins. This makes it harder for reviewers to move the goalposts for a favorite candidate.
Wudd's Promotion Engine locks scoring requirements when a promotion cycle begins. It also requires written justification for any manual override and records the override in an audit log. Apply the same discipline with a shared document and a change log.
Define the approval path. A direct manager can recommend, but should not be the only approver. Use a skip-level, a calibration panel or a cross-functional group. Wudd's Promotion Engine separates recommendation from approval: direct managers recommend, while approvals follow a stricter path.
For people-leader promotions, consider a succession gate. Wudd pauses the paperwork when a manager is nominated until they prove they have trained someone on their team to take over. Whether or not you adopt that rule, the principle is sound: a promotion should not leave a critical role with no bench.
6. Collect two perspectives
Manager memory and employee self-review rarely match. That gap is useful. Ask the manager and the candidate the same questions independently, then compare both views with performance data.
Wudd calls this a blind cross-check: managers document what the employee accomplished, the employee answers the same questions independently, and Wudd compares both perspectives against actual performance data. A manual version works too. Use separate forms, collect them before calibration and discuss gaps openly.
Calibrate on evidence, not personality. Reviewers should point to the same source material and apply the same anchors. If a criterion cannot be scored consistently, revise its definition before the next cycle.
7. Review the weights and publish the standard
Reviewing weights means two things: applying them to criteria, and checking whether they still fit the strategy. Do the second on a schedule, not in the middle of a decision.
After each cycle, ask: did the criteria predict who succeeded? Did one criterion dominate? Were some teams penalized by missing data? Were overrides concentrated in one department? Use pass rates, score distributions, override rates and dispute data to find weak spots.
Review annually for stable roles and more often for fast-changing ones. Change the document before the next cycle opens. Do not rewrite the rubric while decisions are underway. Communicate what changed and why.
Give employees a one-page standard for each role family. Show the eligibility gates, weighted criteria, evidence sources, review dates, approval path and appeal route. Make it a first-class document, not a buried paragraph in a policy portal. Then train reviewers on the anchors.
You do not need a perfect formula. You need a transparent one. Start with one role family, write the gates and criteria, set defensible weights, freeze the rubric before review, and revisit it on a fixed schedule. That gives managers a fairer way to compare evidence — and gives employees a clearer path to earn the next role.