On this page
Readiness Is a Prediction, Not a RewardTwo Roles, Two Evidence SetsEvidence Sources That Actually PredictA Readiness Rubric on Verdict's Six DimensionsFailure Modes to Test ForStructuring the AssessmentFAQPromotion decisions are among the most consequential a manager makes — and among the least rigorously structured. The candidate is already known, which creates the illusion of sufficient evidence. In reality, past performance in one role answers a different question than readiness for the next one.
Readiness Is a Prediction, Not a Reward
The most common structural error in promotion decisions is confusing recognition with forecasting. A strong performer who has maximised their current role deserves recognition. That is not the same as evidence they will succeed in the role above it.
The target role typically demands a different distribution of skills: more ambiguity, broader stakeholder surface, larger scope with less direct oversight, and faster judgement under incomplete information. A candidate who excels at executing defined tasks may or may not have developed the capacity to define the tasks themselves. The question a readiness assessment must answer is: based on observable evidence, what is the probability this person succeeds in the specific demands of the target role?
That question is a prediction. It requires evidence about future-facing behaviours, not a ledger of past contributions.
Two Roles, Two Evidence Sets
Rigorous readiness assessment operates on two simultaneous lenses:
Lens 1 — Current role ceiling. Has the candidate genuinely saturated their current level? Evidence: they are consistently operating above their grade (taking on scope that belongs to the level above without being asked), their current output has compounding effects beyond their immediate team, and managers at the level above them are pulling them into decisions voluntarily. A candidate who is still developing in their current role is not ready to accelerate out of it.
Lens 2 — Target role demand. What does the target role actually require — and is there evidence the candidate has already demonstrated those behaviours, even at smaller scale? The job description is the starting document, not the full answer. Map each responsibility in the target JD to a behavioural dimension, then ask: where in this person's history do we see a scaled-down version of that behaviour?
These two lenses create a diagnostic matrix: high on current-role ceiling + high on target-role signal = strong case. High on current-role ceiling but weak on target-role signal = premature. Still developing in current role = not ready regardless of tenure or loyalty.
Evidence Sources That Actually Predict
Performance reviews are the most available source, but they require interpretation. A review that says "exceeds expectations consistently" is a current-role ceiling signal. The more useful question is: does the review contain examples where the person operated beyond their mandate? Phrases like "stepped in to resolve a cross-team dependency without being asked" or "rewrote the criteria the team had been using for a year" point toward target-role readiness. Generic praise does not.
The target job description is a structured checklist if used analytically. Take each accountability in the JD and find or fail to find evidence in the candidate's record. Do not fill gaps with inference. A candidate who has managed three people and is being considered for a role managing twelve has a gap in span-of-control evidence — that gap belongs in the assessment, not hidden behind "high potential."
Peer and stakeholder input carries weight specifically on Influence, which is the dimension most likely to differentiate a capable individual contributor from a capable manager. Ask: who came to this person voluntarily, and what happened as a result?
Stretch assignments — periods where the candidate held temporary responsibilities above their grade — are the closest available proxy for target-role evidence. If the organisation has run them, the output is high-value calibration data.
A Readiness Rubric on Verdict's Six Dimensions
Verdict's methodology uses six evidence-anchored dimensions for external candidates. The same framework applies to internal readiness assessments — with the dual-lens adjustment. Below is how each dimension functions in a Promote evaluation.
For a full breakdown of each dimension and what evidence anchors them, see the candidate evaluation dimensions guide.
Capability — At the target role level, not the current one. Evidence: can the candidate articulate how they would approach problems that sit above their current scope? In a stretch assignment or cross-functional project, did they demonstrate the technical or functional judgement the target role requires? Absence of evidence here is diagnostic: if no one has ever tested it, the organisation does not know.
Track Record — The pattern of outcomes, weighted toward recent and toward scope above current grade. A candidate with ten years of solid execution at the same functional level is demonstrating consistency, not readiness. What matters is whether the outcomes catalogue contains examples of expanded scope, not just extended tenure.
Trajectory — The rate of development over the past twelve to twenty-four months. Is the candidate's scope growing faster than their title? Are they pulling in more complex problems, or has their challenge set plateaued? Trajectory is the clearest signal of whether a candidate will continue to grow into the target role or will plateau again quickly after promotion.
Influence — Influence is where most internal readiness assessments fail to look hard enough. Individual contributors who become managers need the ability to move people who do not report to them — peers, senior stakeholders, other teams. Evidence: examples where the outcome required changing someone else's priorities or decisions, without authority. If all a candidate's wins are within their own direct control, the Influence dimension will be weak at the target level.
Domain Edge — The specific expertise that makes this candidate a credible authority to the people they will now need to lead or advise. At more senior levels, domain edge often shifts from technical execution to pattern recognition: the ability to read a situation quickly because they have seen the failure modes before. Evidence: moments where their perspective changed the direction of a decision, cited by others.
Risk Surface — Specific to internal promotions: does the candidate's track record contain unresolved signals? A pattern of delivering under low-conflict conditions but struggling when stakeholders disagree; a tendency to absorb scope without flagging capacity limits; a history of strong individual output but friction in collaborative ownership. These are not disqualifiers — they are development areas that belong in the assessment, because they are the most likely failure modes in the target role.
Failure Modes to Test For
Recency bias. A candidate who had an exceptional quarter is not necessarily ready for promotion. The assessment should look at the full evidence window — two to three years if the tenure supports it — and ask whether the recent strong signal is a pattern or a peak.
The Peter Principle as a predictive risk. Laurence Peter's observation — that people are promoted to their level of incompetence — describes an outcome, but the mechanism is predictable: organisations promote based on performance in the current role without testing the capabilities the next role actually demands. A readiness rubric is a structural defence against this. If the target role demands stakeholder management and the candidate has never been tested on it, that is a known gap — not a surprise to discover six months after promotion.
Advocacy confusion. A manager who lobbies hard for a candidate's promotion may be accurate, or may be confusing loyalty and cultural fit with target-role capability. The rubric's value is that it makes the evidence explicit: a manager who cannot point to target-role evidence is not making a readiness case, they are making a preference case. Those are different claims and deserve different scrutiny.
Compression error. When candidates are assessed only against their current peers rather than against the target role's demands, strong relative performers get promoted into roles they are not ready for. The rubric must be anchored to the target role's requirements, not the current team's distribution.
Structuring the Assessment
The practical sequence:
- Agree the target role's behavioural requirements before naming the candidate. The JD is the starting point; the hiring manager for that level should add what the JD does not say.
- Define what evidence at each readiness level looks like for each dimension — before reviewing the specific candidate. This is the rubric.
- Gather evidence: last two performance reviews, examples from stretch assignments, peer input on Influence, the candidate's own articulation of how they would approach the target role.
- Score each dimension against the rubric, with verbatim evidence cited for each score.
- Identify gaps explicitly: where is the evidence absent or thin? Name the specific gaps and decide — as an organisation — whether those gaps are acceptable given development support, or whether they indicate the candidate is not yet ready.
Verdict's Promote mode runs this process against a candidate's submitted materials and the target role description, scoring each of the six dimensions with verbatim evidence extraction and flagging where the record is thin. It does not make the promotion decision — that belongs to the people with organisational context. It makes the evidence legible, so the decision rests on what is actually documented rather than what feels true.
FAQ
Is readiness the same as potential? No. Potential is a prediction about long-run trajectory. Readiness is a prediction about the specific next role, now. A high-potential candidate may not be ready for this promotion in this cycle — and that is a legitimate, useful finding. Conflating the two inflates promotion rates into unprepared roles.
What if no one has given the candidate the opportunity to demonstrate target-role behaviours? That is a real constraint, and it belongs in the assessment as a gap with a cause. The question becomes: can the organisation create a structured test before formalising the promotion, or does it accept the uncertainty and build a development plan to close the gap within a defined window? Both are defensible. Ignoring the gap is not.
How do we handle high performers who are not ready? Separate the conversations. Recognition for strong current-role performance should not wait for promotion readiness. Delayed promotion is not a punishment — it is a data point. The communication should be: here is what the evidence shows for the target role; here are the specific gaps; here is what closing them would look like.