Building a promotion case from scratch

You know you had a good year. You can feel it. But when your manager asks you to "put together something for the promo committee," you open a blank doc and stare at it for twenty minutes before writing "Led several key initiatives" and wanting to delete your laptop.

This is the single most common failure point in the promotion process, and it has nothing to do with whether you did the work. It's a translation problem: you have a year of scattered accomplishments, and the committee needs evidence mapped cleanly to a level's actual criteria. Those are two different documents, and most people try to write the second one straight out of memory instead of building it deliberately.

Here's the walkthrough for doing it properly.

Start with the criteria, not your memory

Before you write a single bullet, go find your actual leveling rubric — the competency matrix, the ladder doc, whatever your company calls it. Not the vibes version you remember from a Slack thread eighteen months ago. The real one, with the real language.

Committees don't grade on "did great work." They grade against specific competencies: technical depth, scope of ownership, cross-functional influence, mentorship, ambiguity handling, whatever your ladder defines for the level you're going for. If you write your case before you have this in front of you, you'll end up with a narrative that sounds impressive to you and says nothing measurable to a committee member who's never worked with you.

Action step: Copy every competency for your target level into a doc, word for word. This becomes your skeleton.

Audit a year of work systematically, not from memory

This is where most cases actually fall apart, and it's not a writing problem, it's a recall problem. Memory is bad at this by design. You remember what was recent and what was emotionally salient, so a promotion case written from memory alone is really just a case built on the last six weeks plus whatever went wrong badly enough to stick.

Go source by source instead of relying on recall:

• Calendar. Scan meeting titles month by month. Projects you led, reviews you ran, cross-team syncs you were pulled into.
• Git history / ticket system. Pull your closed PRs, shipped tickets, and merged work for the period. This alone usually surfaces three or four things you'd completely forgotten.
• Slack and email search. Search your own name plus words like "thanks," "great work," or "appreciate." People say nice things about your work far more often than you remember them saying it.
• 1:1 notes. If you or your manager kept running notes, they're a goldmine of context you've since lost. Write every single win down at this stage, no matter how small it seems. You're not curating yet, you're just recovering the raw material. Most people skip straight to writing the polished version and lose 70% of their actual year in the process.

Map evidence to competencies, not the other way around

Once you have a raw list, go back to your competency skeleton and sort each win under the criterion it actually demonstrates. Some wins will map cleanly. Others won't map to anything on the ladder, which is useful information too, it tells you what you spent time on that the committee won't credit.

A few things tend to surface once you do this sorting honestly:

• You'll have five strong examples piled under one competency and nothing under another. That's your gap, not your strength.
• Some of your "biggest" projects by effort turn out to be weak evidence for the level you're going for, because they were execution-heavy but didn't demonstrate the scope or ambiguity the next level requires.
• Small things — a design review you influenced, a junior engineer you unblocked — often map better to leadership or mentorship criteria than the big flashy project does. This is the step that turns a list of accomplishments into an actual case.

Fill the gaps deliberately, if there's still time

If your audit turns up a competency with thin or no evidence, and you're not submitting for another few weeks, that's still fixable. Look for a review, a design doc, or a piece of mentorship you can proactively take on that speaks directly to the gap. This only works if you catch it early, which is the real argument for doing this audit well before the deadline rather than the week of.

If there's no time left, don't try to stretch a mediocre example to cover a gap. Committees can tell. It's better to have four strong competencies and one honestly thin one than five that all feel forced.

Assemble the narrative last

Only once every competency has its strongest one or two pieces of evidence do you start writing prose. Each entry should follow roughly the same shape: what the situation was, what you specifically did, and what the measurable or observed outcome was. Specificity is what separates a promo-ready bullet from a resume bullet — "improved reliability" is a resume bullet, "cut on-call pages by 40% by rewriting the retry logic in the ingestion pipeline" is a promo bullet.

Resist the urge to include everything. A packet with eighteen bullets under one competency reads as padding, not strength. Two or three of your best, clearly written, will always beat a wall of minor ones.

The mistake almost everyone makes

The single biggest failure mode isn't a lack of accomplishments, it's building the case in the two weeks before the deadline entirely from memory, which means the case is really a summary of Q4 wearing a full-year costume. The fix isn't better writing. It's not relying on memory in the first place — capturing wins as they happen, so that by the time the committee asks for a packet, the raw material already exists and the only work left is the mapping and the writing.

That's the whole premise behind LogPact's packet builder: it keeps the running list so you're never doing the archaeology dig in week one, and its gap analysis flags exactly which competencies are thin while there's still time to do something about it, not after you've already submitted.

---

Building your own case right now? Start with the audit step above even if you're not using a tool for it — a spreadsheet with "competency" and "evidence" as your two columns will get you 80% of the value. But if you'd rather not rebuild that spreadsheet every review cycle, that's exactly what LogPact does automatically.