📋 Contents
- What a promotion packet is actually for
- Start with the leveling guide, not your accomplishments
- A promo doc structure that works at most companies
- How to write a project write-up that shows next-level scope
- Mapping evidence to the next level: a worked table
- Getting peer and stakeholder feedback into the packet
- Mistakes that quietly sink strong cases
- Timeline: when to start and what to do each month
- A fill-in template you can copy
PART 1
What a promotion packet is actually for
At many US companies, especially in tech, promotions are not decided by your manager alone. Your manager nominates you, writes or co-writes a packet, and that packet goes to a promotion committee or a calibration session where managers and directors compare candidates across teams. Most of the people in that room have never seen your work firsthand. The document has to do the arguing for you.
That changes what "good" looks like. A packet is not a list of everything you did. It is a focused case that answers one question: is this person already doing the job of the next level, consistently, and with enough scope that the company is taking little risk by making it official? Everything in the document should serve that question. Anything that does not, including work you are proud of, can go.
Even if your company has no formal packet, the same document is useful. A clear one-to-three page case makes it easier for your manager to advocate for you in a meeting you will not attend, and it keeps the conversation anchored on evidence instead of impressions.
💡 Who usually writes it
Practice varies. At some companies the employee drafts most of it and the manager edits; at others the manager writes it from the employee’s self-review and brag document. Ask your manager early which model your company uses, and offer to write the first draft either way.
PART 2
Start with the leveling guide, not your accomplishments
Most mid-size and large companies publish a career ladder or leveling guide: a grid describing what each level looks like across a few dimensions such as scope, impact, technical or functional depth, collaboration and leadership. The committee will read your packet against that grid. So should you, before you write a word.
Find the exact rubric
Get the current leveling guide for your function and the next level up. If your company has none, ask your manager what the committee actually looks for and write it down in their words.
Highlight the differences
Compare your current level and the target level line by line. The promotion case lives in the gap: usually larger scope, more ambiguity, influence beyond your team, and multiplying others.
Turn each gap into a heading
Each dimension where the next level differs becomes a section of your packet, with two or three pieces of evidence under it.
Check for empty sections
If a dimension has no evidence, that is not a writing problem. It tells you what to work on, or that the timing may be one cycle early.
This approach also protects you from a common trap: a packet full of excellent work that is all at your current level. Shipping a lot of tickets well is valuable, but it proves you are a strong performer at your level, not that you have grown beyond it.
PART 3
A promo doc structure that works at most companies
If your company provides a template, use it exactly. If not, this structure fits most reviewers’ expectations and is easy to skim.
| Section | What goes in it | Length |
|---|---|---|
| Summary | Target level, the two or three strongest reasons, and the time period covered | 2–4 sentences |
| Scope and impact | Your largest pieces of work, what changed for the business or customers, and why it was hard | 2–4 project write-ups |
| Next-level behaviors | Evidence organized by leveling-guide dimension (for example, ambiguity, cross-team influence, mentoring) | 1 short paragraph per dimension |
| Feedback from others | Short quotes or summaries from peers, partners and stakeholders, ideally from other teams | 3–6 short excerpts |
| Growth areas | One or two honest gaps and what you are doing about them | 2–3 sentences |
| Appendix | Links to design docs, launch notes, dashboards and other artifacts | As needed |
Many committees read the summary and skim the rest. Write the summary last, after you know which evidence is strongest.
Keep the main body to what a reviewer can read in about ten minutes. Many committees review a stack of packets in one sitting; the one that is clear and short gets read carefully.
PART 4
How to write a project write-up that shows next-level scope
Each major project gets a short write-up. The pattern that works is context, your role, decisions, outcome. Reviewers want to see what you specifically did, especially the judgment calls, not what the team delivered in general.
✍️ Project write-up (illustrative)
Context: Our onboarding flow was the most common reason new customers contacted support, and three teams owned different pieces of it.
My role: I proposed consolidating it, wrote the plan, and led the work across product, support and engineering for two quarters. Nobody assigned this; I brought the proposal to my director.
Key decisions: I cut the scope of the first release to the three steps that drove most contacts, and negotiated a shared on-call rotation so no team carried the risk alone.
Outcome: Onboarding-related support contacts dropped noticeably after launch (the support team’s dashboard is linked in the appendix), and the shared process is now how the three teams run joint launches.
Notice what makes this read as a level up: the work crossed team boundaries, the person created the project rather than receiving it, and there were real trade-offs. Use "I" for what you did and "we" for what the team did. Reviewers are trained to look for that distinction, and blurring it costs credibility.
⚠️ Don’t inflate ownership
Committees often include people who know the project. Claiming you "led" something you contributed to can undo an otherwise strong packet. Precise language ("I owned the data migration within the larger launch") is more convincing than big verbs.
PART 5
Mapping evidence to the next level: a worked table
Before writing paragraphs, build a simple table. It shows you where your case is strong, where it is thin and what to cut.
| Leveling-guide dimension | Next-level expectation (example wording) | Your evidence |
|---|---|---|
| Scope | Owns problems that span multiple teams or quarters | Onboarding consolidation (two quarters, three teams) |
| Ambiguity | Defines the problem, not just the solution | Wrote the original proposal from support ticket analysis |
| Influence | Aligns stakeholders without formal authority | Negotiated shared on-call rotation; got sign-off from two directors |
| Multiplying others | Raises the output of people around them | Mentored two newer teammates who now run their own releases |
| Execution | Delivers reliably on commitments of growing size | All three planned launches shipped within the agreed window |
Use your company’s exact dimension names and wording. Example rows are illustrative.
Aim for at least two solid pieces of evidence for each dimension where the next level differs, sustained over time. Most committees want to see the behavior repeated across a period, often six months or more, rather than a single impressive moment.
PART 6
Getting peer and stakeholder feedback into the packet
Quotes from people outside your reporting line carry weight because they are harder to fake. Many companies collect formal peer feedback as part of the process; even where they do not, short endorsements strengthen the case.
- Ask the right people. Choose people who saw your next-level work directly: partner team leads, the PM or designer on your biggest project, someone you mentored.
- Make the ask specific. "Could you write two or three sentences about how the onboarding project went, especially the cross-team coordination?" gets better material than "Could you write something about me?"
- Give them context. Share the project summary and the dimension you hope they can speak to, so their memory matches the evidence.
- Let them say it their way. Do not draft quotes for others. Reviewers notice when every endorsement sounds like the same person.
💡 Ask early
People write better feedback when they are not rushed. Ask a few weeks before the deadline, and thank them whether or not the promotion goes through.
PART 7
Mistakes that quietly sink strong cases
- Listing everything. A long list of projects buries your best evidence. Pick the strongest few and go deeper.
- Describing activity instead of outcomes. "Attended planning meetings and wrote specs" says nothing about impact. What changed because of your work?
- Arguing for effort or tenure. Time in role and hard work matter to you, but committees promote on demonstrated scope. Leave out "I’ve been at this level for three years."
- Ignoring the rubric. If the guide emphasizes influence and your packet only talks about execution, reviewers will mark the gap for you.
- Surprising your manager. Your manager is your advocate in the room. If they have not read and agreed with the document, they cannot defend it.
- Hiding a known weakness. If everyone knows about a missed launch, address it briefly and show what you learned. Silence invites a skeptical reviewer to bring it up.
PART 8
Timeline: when to start and what to do each month
Promotion cycles at US companies typically run once or twice a year, often alongside the annual or mid-year review. Packets written in the final week are noticeably weaker than those built over months.
| When | What to do |
|---|---|
| 6+ months before | Agree with your manager that the next level is the goal. Ask what gaps they see against the leveling guide. |
| Ongoing | Keep a running log of work, decisions and feedback, tagged by leveling-guide dimension. |
| 8–10 weeks before | Build the evidence table. Identify thin dimensions and discuss them in a 1:1. |
| 4–6 weeks before | Draft the packet. Request peer feedback. |
| 2–3 weeks before | Review with your manager; edit for length and clarity. Have a trusted peer at the target level read it. |
| Deadline | Submit the final version and the appendix links. |
If the decision does not go your way, ask for the specific feedback from the committee and turn it into goals for the next cycle. The packet you wrote is not wasted; it becomes the starting draft for next time.
PART 9
A fill-in template you can copy
✍️ Promotion packet skeleton
Summary: I am proposing promotion from [current level] to [target level]. Over [period], I have [strongest next-level evidence #1] and [#2]. The work below maps to the [target level] expectations for [dimensions].
Project 1 — [name]: Context / My role / Key decisions / Outcome / Link.
Project 2 — [name]: Context / My role / Key decisions / Outcome / Link.
[Dimension A]: Two or three sentences of evidence, with dates.
[Dimension B]: Two or three sentences of evidence, with dates.
What others say: Short quotes from [peer], [partner team lead], [mentee].
Growth areas: [One gap] — what I am doing about it.
Appendix: Links to documents, dashboards, launch notes.
The hardest part of this template is not the writing. It is having dated, specific evidence on hand when the cycle opens. If you keep a habit of noting work as it happens, the packet becomes an editing job. The approach is described in detail in the guide to writing a brag document.
Frequently asked questions
Q. How long should a promotion packet be?
Follow your company’s template if there is one. Otherwise, one to three pages for the main body plus an appendix of links is typical. Reviewers often read many packets at once, so shorter and clearer usually beats longer.
Q. Who writes the promotion packet, me or my manager?
It depends on the company. In many cases the employee drafts and the manager edits and submits. Ask your manager how it works where you are, and offer a first draft either way.
Q. What should a promo doc include?
A short summary of the case, two to four major project write-ups, evidence organized by the leveling guide’s dimensions, feedback from peers and partners, an honest growth area, and links to supporting artifacts.
Q. How do I show I am already working at the next level?
Map your work to the next level’s description in the leveling guide and show repeated examples over several months, especially work with larger scope, more ambiguity, cross-team influence and mentoring.
Q. What if my company doesn’t have a leveling guide?
Ask your manager what the people who approve promotions look for and write it down. Then structure your document around those criteria, and confirm with your manager that the framing matches how decisions are made.
Q. Should I include work that failed?
If it is well known or shows next-level judgment, yes. Briefly explain what happened, what you decided and what you changed. Handling a setback well is often strong evidence.
Q. What happens if my promotion packet is rejected?
Ask your manager for the specific feedback from the committee, agree on the gaps to close, and set goals for the next cycle. Keep the packet; it becomes your starting draft next time.
This article is general guidance. Review formats, rating scales and expectations vary by company — check your own company’s guidelines alongside it.
PLAN2FOLIO
Evidence for reviews, raises and job moves — starting with one line today
Write what you did today in one line. PLAN2FOLIO sorts it into the outcomes of your role, drafts your weekly report on Fridays and gathers evidence by outcome at review time. Free to start.
Start free →📄 Career & Reviews
Keep reading