Career·Updated January 27, 2026

Promotion Case Builder

Draft a promotion packet that maps your work to the leveling rubric, with evidence, gaps, and a 30/60/90 plan.

Use Case

Preparing a promotion case, structuring evidence against a rubric, and creating a clear growth plan with your manager.

Prompt

Help me write a promotion case to move from [current level] to [target level].

Inputs:
- Company / team: [describe]
- Role: [your title]
- Leveling rubric (paste if you have it): [paste rubric]
- My strongest projects (3–6): [list projects]
- Evidence per project: [impact metrics, decisions, scope, constraints, collaboration, leadership, research findings]
- Feedback quotes (optional): [paste]
- What I’ve been doing beyond scope (optional): [mentoring, process improvements, cross-team leadership]

Output a promotion packet with:
1) Executive summary (3–5 bullets)
2) “Why now” narrative (1–2 short paragraphs)
3) Evidence mapped to rubric (table: rubric area → evidence → links/projects → confidence)
4) Impact section (what changed for users/business/team)
5) Scope & leadership (examples of ownership, alignment, influence)
6) Gaps & risks (what’s missing for next level)
7) 30/60/90 plan to close gaps (specific actions + measurable signals)
8) Manager 1:1 script (how to ask, what to propose, how to handle pushback)

Style constraints:
- Specific, evidence-based, not inflated
- Prefer measurable outcomes; when not available, use strong qualitative signals
- Keep it concise and scannable

How to use

1Paste your company leveling rubric if available; if not, describe expectations for the target level.
2List 3–6 projects with concrete evidence (metrics, decisions, scope, stakeholder quotes).
3Include at least one example of cross-functional influence (alignment, tradeoffs, decision-making).
4Ask the model to “tighten to 1 page” after the first draft if it’s too long.
5Use the 1:1 script to frame the conversation as collaborative: “here’s the evidence + plan.”

Pro Tips

• Promotion cases are stronger when you map evidence to the rubric explicitly.
• Include tradeoffs and constraints, senior work is decision-making under constraint.
• If metrics are missing, use credible proxies (support tickets, usability findings, stakeholder alignment, shipped learnings).