How-to: Build a One-Page Promotion Evidence Packet
Promotions stall when the case lives only in your head. A one-pager forces clarity: what level looks like, what you already operate at, and the evidence a manager can carry into a calibration room. This is not a threat letter. It is a decision aid.
Time box: 60 minutes for a solid first draft if you have kept light notes during the year. Add a second 30-minute pass after peer feedback.
Use with how promotions and leveling work, how to make a case for a raise, and the Individual Contributor hub. Managers advocating for someone should still insist on evidence; see New Manager and Director / VP.
When to use / when not
Use when:
– Leveling discussions are coming or you are mid-cycle and want a living doc
– Your scope already matches the next level more than your title
– You need your manager’s sponsorship, not just their encouragement
Do not use when:
– You have almost no evidence and hope adjectives will carry it (gather evidence first)
– You are using the packet to replace a hard conversation about performance gaps
– Company process forbids self-nominations in your cycle (adapt to the required form instead)
– You plan to invent metrics (never)
Prep
- Level rubric or job framework language (company doc)
- Outcomes from the last 2–4 quarters (quarterly priority reset agreements help)
- Artifacts: launches, docs, decision emails, incident write-ups, hiring scorecards you drove
- Feedback snippets you are allowed to share (from reviews, customers, partners)
- Business context: team goals, constraints you navigated
- Clear ask: promote now, promote next cycle with gaps listed, or expand scope as a bridge
Steps
- Paste the skeleton (5 min). One page max. If it spills, you are writing a memoir.
- Write scope vs. level language (10 min). Map 3–5 next-level behaviors you already show.
- Add 3–5 outcome bullets with evidence links (20 min). Results and your role. No borrowed glory without naming collaborators.
- Add collaboration and leadership proof (10 min). Cross-team work, mentoring, debriefs, escalation leadership.
- State gaps honestly (5 min). What you are still building; how you will close them.
- Draft the ask and send to your manager for a live review (10 min). Schedule time; do not only email into the void.
Complement with email that gets a decision when you need a clear yes/no on timing.
Script (what to say / send)
To your manager:
I’ve drafted a one-page promo evidence packet mapped to [level]. Can we spend 30 minutes on whether the case is strong enough for this cycle, what’s missing, and how you’d sponsor it? Doc here: [link]. I’m looking for a decision path, not only encouragement.
In the review meeting:
“I’ll walk the page in five minutes. I want your pushback on weakest evidence, then a call: nominate this cycle, nominate next with these gaps, or change scope first.”
If they say not yet:
“Thanks. Please list the concrete gaps and examples of ‘done’ for each. I’ll turn that into a quarterly plan and we can revisit on [date].”
Peer proof ask (optional):
I’m preparing a promo packet. If you’re comfortable, could you send two sentences on [project] about the outcome and how I contributed? I’ll only include what you approve.
Output artifact
Promo One-Pager:
Name / current level / target level / date
Role scope today (1–2 lines)
Business outcomes (3–5 bullets with links)
Next-level behaviors demonstrated (bullets mapped to rubric)
Leadership / cross-team impact
Feedback excerpts (attributed with permission)
Gaps + plan
Ask: nominate this cycle / next cycle / scope bridge
Manager notes (filled live)
Keep a private evidence folder throughout the year so the 60-minute build is assembly, not archaeology. Same-day feedback notes (feedback in the moment) and decision emails are excellent receipts.
Watch-outs
- Invented stats. If you do not have a number, describe the outcome qualitatively with a link to the artifact.
- Activity masquerading as impact. Hours worked and meeting count are not level evidence.
- Solo hero narrative. Credit collaborators. Calibration rooms smell exaggeration.
- Surprising your manager. The packet should refine an ongoing conversation, not ambush them a day before packets are due.
- Comparing pay gossip. Stick to scope and level; compensation follows process.
- Ignoring process. HR timelines and forms still rule; how HR works for the mechanics.
Sales roles should translate wins into retained revenue, expansion, and clean handoffs without confidential customer data dumped into the packet; see how sales works. Cross-functional leaders should show system fixes, not only personal heroics (how departments work together).
Done looks like: one page, rubric-mapped evidence, honest gaps, and a scheduled decision conversation with your manager.