The Promotion Case Builder: Turn Scattered Wins Into a Quantified Case for Your Next Level
Why this prompt matters
Promotion committees reject packets for vague, unquantified claims far more often than for genuinely insufficient work. A packet written from memory the night before the deadline systematically underclaims impact, because people default to hedged language ("helped improve," "contributed to") instead of the specific before/after numbers that actually persuade a room of people who were not in the room when the work happened. Finding out your case was too vague only after the committee has already met costs you an entire additional cycle — six to twelve months, in most leveling systems — that a structured review the week before would have caught.
What we use it for
You are six weeks out from a promotion calibration cycle. You have a folder of self-review notes, a handful of Slack messages where a teammate said something nice, and a vague sense that this was a good year — but no structured case, and no idea which of it actually proves you are ready for the next level.
Prompt
Role: Act as a skeptical, senior member of a promotion calibration committee who has reviewed hundreds of packets and immediately spots padding, vague claims, and missing evidence. You are not here to make me feel good — you are here to tell me whether my case would survive a room full of people who do not already like me. Context: I am currently a [YOUR CURRENT TITLE AND LEVEL], aiming for [TARGET TITLE AND LEVEL] at [COMPANY NAME, OPTIONAL]. The calibration cycle is on [CYCLE DATE]. Below is my raw, unorganized material — self-review notes, praise from Slack or email, project retros, old performance review text, anything I have: [PASTE YOUR RAW NOTES, ACCOMPLISHMENTS, AND FEEDBACK HERE] Task: 1. Extract every distinct accomplishment from the raw material — do not merge two different pieces of work into one bullet. 2. For each one, force it into this structure: Action → Scope → Measurable Result → Who Else Benefited. 3. If an accomplishment has no measurable result, do not invent one. Instead, tell me exactly what number to go find and who would have it (e.g., "ask your manager for the before/after ticket backlog size" or "check the dashboard for the deploy frequency change"). 4. Group the accomplishments under the actual competencies required for [TARGET TITLE AND LEVEL]. If I have pasted a leveling rubric, use it. If not, use these four standard dimensions: Scope of Ownership, Technical Depth, Leadership and Influence, Cross-Team Impact. 5. Identify the single weakest competency in my case. If the case is not yet strong enough to make this cycle, say so directly — do not soften it into encouragement. Constraints: Never invent or round up a number I did not provide. Never use generic adjectives like "excellent," "strong," or "outstanding" unless they are someone else's direct quote. Every claim must trace back to the Action → Scope → Result structure or it gets flagged, not included. Name the weakest point explicitly even if it is discouraging to read. Output Format: - A table with four columns: Competency | Accomplishment | Measurable Result | Still Needs - A 150-word "Case Summary" paragraph written so a manager could paste it directly into a calibration document without editing - A short "Biggest Gap" section naming the weakest competency and one concrete action I can take before the cycle closes to address it
Result
Competency Table (excerpt)
| Competency | Accomplishment | Measurable Result | Still Needs |
|---|---|---|---|
| Scope of Ownership | Took over the payments reconciliation service after the previous owner left | Reduced monthly reconciliation discrepancies from 340 to 12 cases over two quarters | Confirm with finance whether the 12 remaining cases are a known acceptable floor |
| Technical Depth | Redesigned the retry logic for the billing webhook pipeline | Cut failed-webhook incident tickets from 18/month to 3/month; ask platform team for the exact latency delta | A specific p99 latency number — check the dashboard before the cycle |
| Leadership and Influence | Mentored two mid-level engineers through their first on-call rotation | Both passed their first solo on-call shift with zero escalations — confirmed by on-call logs | None — this is well-evidenced as is |
| Cross-Team Impact | Vague note: "worked closely with the data team on the migration" | Not provided — flagged, not included | Ask the data team lead for the specific deliverable and date it shipped |
Case Summary (150 words):
Over the past two quarters, [NAME] took ownership of the payments reconciliation service after its previous owner departed, reducing monthly discrepancies from 340 to 12 cases — a 96% reduction achieved through a redesigned retry architecture that also cut failed-webhook incidents from 18 to 3 per month. This work required independently diagnosing a cross-system race condition that had gone unaddressed for over a year. Beyond individual delivery, [NAME] mentored two mid-level engineers through their first on-call rotations, both of whom completed solo shifts with zero escalations, demonstrating leadership readiness beyond their current scope. The case for Staff Engineer is strong on Scope of Ownership and Technical Depth. Cross-Team Impact remains the open gap: the data team migration work needs a specific, dated deliverable before this packet goes to committee.
Biggest Gap: Cross-Team Impact is currently unevidenced. Before the cycle closes, get the data team lead to confirm in writing what specifically shipped, when, and what measurable effect it had — a vague "worked closely with" will not survive calibration.
Most promotion-prep advice tells you to “list your accomplishments.” That advice produces exactly the kind of packet calibration committees reject: a bullet list of activities — “led the migration,” “improved reliability” — with no evidence attached. The gap between an activity and an accomplishment is a measurable result, and almost nobody supplies one without being forced to.
This prompt forces that structure with a single rule: Action → Scope → Measurable Result → Who Else Benefited. Four slots, and if the third one is empty, the claim does not make it into the final case — it gets flagged with instructions on exactly what number to go find and who would have it. This matters because the natural failure mode isn’t lying, it’s rounding up. “Helped improve reliability” feels true and feels sufficient in the moment it’s written, but a committee member reading it has no way to tell whether that means a 2% improvement or a 200% one. Forcing the gap into the open — “ask your manager for the before/after ticket backlog size” — turns a vague memory into a research task you can actually complete before the deadline.
The second design choice is grouping accomplishments by competency rather than by project. Most people organize their self-review chronologically, which is the natural way memory works but the wrong way to make a case: a calibration rubric scores Scope of Ownership, Technical Depth, Leadership, and Cross-Team Impact as separate dimensions, and a chronological list hides which dimensions are thin. Sorting by competency surfaces the gap immediately — in the example output above, three competencies are well-evidenced and one is a single vague sentence with nothing behind it.
The last and most important instruction is the one most self-assessment tools skip entirely: naming the weakest competency and saying directly whether the case is strong enough yet. A prompt that only organizes material without ever saying “this isn’t ready” is just a formatting tool. The actual value here is catching a thin case six weeks before a committee does, when there is still time to go get the missing number — instead of six weeks after, when the only option left is to wait for the next cycle.
Use this the same way the example above does: paste in everything you have, even half-remembered Slack praise, and let the structure tell you what’s missing rather than trying to guess it yourself.