To write a promotion case for your employee (the business case for promotion a committee will actually scrutinize), gather dated and specific evidence of work already operating at the next level, quantify the impact where you can, and map each example to a line in your level rubric. The strongest cases are not arguments that someone deserves a promotion; they are demonstrations that the person is already doing the job, written with enough detail that a skeptical committee can verify it. Your job here is different from the person writing their own packet: you are the advocate, the one who saw the work happen and can vouch for the scope behind each line.
The hard part is almost never the writing. It is the evidence. A promotion case needs a year of specific, dated wins, and most of those wins are invisible by the time the cycle opens. The quiet cross-team save your engineer made on a Thursday in March is gone by October, while the one rough launch in September is still vivid because it just happened. That is recency bias, and it does more than dull a review. It can quietly sink a promotion the person had earned. The fix is not a better memory. It is a running log you add to as the work happens, so when the window opens the case is already mostly written.
Start the case months before the cycle
The most common reason a deserving report does not get promoted is not that the work wasn’t there. It is that the manager started assembling the case the week the form was due and could only remember the last six weeks. By then the evidence is cold. You are reconstructing a year from chat history and a fuzzy sense that “they’ve been great,” which is exactly the kind of vague advocacy a committee discounts.
So start the moment you think someone might be approaching the next level, ideally a cycle or two out. Open a private log for that person and drop in evidence as it happens. You are not committing to anything by doing this; you are just making sure that if the case is real, you’ll be able to prove it. The same habit also tells you early where the gaps are, which gives you time to coach toward them instead of discovering the hole in front of the committee.
Write one line, tag the person, and it files into their timeline for review season.
Gather dated, specific evidence
A committee can only act on what it can picture. “Consistently delivers high-quality work” tells them nothing they can verify. A dated, concrete example tells them everything. The unit of a strong case is one line: a date, what the person did, and the scope or outcome behind it. Copy the layout below and keep one of these per report you’re advocating for.
PROMOTION CASE - @[Name] Target level: [____] THE ONE-LINE THESIS - Already operating at [level] by [doing X at Y scope]. EVIDENCE, MAPPED TO THE RUBRIC (dated + specific + quantified) Rubric line: [e.g. "Drives projects across teams"] - [Date] - [what they did] - [the number / scope / outcome] - [Date] - ... Rubric line: [e.g. "Raises the bar technically"] - [Date] - ... Rubric line: [e.g. "Grows others"] - [Date] - ... SCOPE & CONSISTENCY (not a one-off) - [Pattern over the period, with 2-3 dated points] KNOWN GAPS + HOW WE'RE CLOSING THEM - [Gap] - [the plan / the recent progress] WHO CAN CORROBORATE - [Peer / partner team / stakeholder] - [what they witnessed]
Here is the difference a single rewrite makes. The vague version is a feeling; the specific version is something a committee can act on.
- Vague: “Sam is a strong technical leader.”
Specific: “Mar 9: Sam led the billing migration across three teams, zero downtime, and wrote the runbook the on-call team still uses. Owned the rollback plan end to end.” - Vague: “Priya is great with people.”
Specific: “Apr-Jun: Priya mentored two new hires through their first ships and rewrote the onboarding doc; both reached independent delivery a month ahead of the usual ramp.” - Vague: “Handles ambiguity well.”
Specific: “Feb 14: took an under-scoped reliability project, broke it into a three-quarter plan, got buy-in from two partner teams, and cut p95 latency by a third.”
Notice that none of the specific versions are longer arguments; they are just anchored in fact. The date makes it checkable. The scope (“three teams,” “two partner teams”) shows the person operating above their current level. That is the whole game.
Quantify the impact
Wherever you can, attach a number, a scope, or a concrete outcome to each win. Numbers travel through a committee in a way that adjectives never do. Reach for one of these:
- People affected: teams unblocked, engineers onboarded, customers served.
- Money moved: revenue influenced, cost reduced, spend avoided.
- Time saved: a manual process automated, a build pipeline cut from hours to minutes.
- Risk prevented: incidents avoided, a migration with zero downtime, a security gap closed.
- Scope owned: the size of the decision the person made on their own, the blast radius of the project.
When a clean number genuinely isn’t available, and for a lot of good work it isn’t, don’t invent one. Name the concrete consequence instead: the team that got unblocked, the launch that shipped on time because they caught the problem, the practice the rest of the group adopted. A real consequence beats a fabricated metric every time, and a committee can smell a number that was made up to sound impressive.
Walk into the calibration meeting with the whole record, not the last six weeks.
Map every win to the rubric
A pile of good examples is not a promotion case. A pile of good examples mapped to the next level’s expectations is. Pull up your level definition or competency rubric, list each expectation for the target level, and place at least one dated example under each line. This does two things at once. It turns your case into the exact shape the committee is going to evaluate, and it makes the gaps impossible to miss.
That second part is the quiet superpower of mapping early. If the rubric says “drives cross-team initiatives” and you have three strong examples, good; that line is covered. If it says “raises the technical bar across the org” and your evidence is all within one team, you’ve just found the gap while there’s still time to do something about it. Now you can coach toward it: point the person at the project that would stretch their scope, and log it when they land it. A case built this way is honest, because you’re not papering over a missing competency; you’re showing the work that fills it.
One discipline keeps the mapping fair: distinguish a one-off from a pattern. A committee wants to see the next level operating consistently, not a single heroic quarter. For each rubric line, aim for two or three dated points spread across the period. That is also where the early-start habit pays off: consistency is only provable if you were capturing all along.
Notes inform the case; they don’t make the decision
Keep one line clear in your head while you do this. The log you build, and any AI help you use to organize it, gives you accurate input. The promotion decision, and the accountability for it, stays with you, your calibration process, and your organization under its own policies. A well-evidenced case makes a fairer decision more likely; it does not replace the people and the process that make the call. Keep the evidence factual and behavior-based, written the way you’d be comfortable having a committee read it, and the case stays a tool for fairness rather than a sales pitch.
Where Notivo fits: the evidence ledger
This is exactly the problem Notivo is built to remove. The reason promotion cases are hard is that the evidence is scattered across a year and most of it evaporates before you need it. Notivo is a private manager’s notebook: you jot a quick note about your team (one line is enough) and tag the person with @ and their name and the topic with #, and it files into that person’s dated timeline. Type @Sam later and the whole year is there, dated and searchable: the cross-team save in March, the mentoring in spring, the reliability project in February.
When the cycle opens, you read the timeline top to bottom instead of reconstructing it. Notivo’s AI assistant can then help you draft a recap or pull the relevant wins, but it works only from your own notes (it retrieves from what you wrote; it never trains on your data and never invents events), so what comes out is your evidence, organized, not a model’s guess. You capture from wherever the work happens: the web app, WhatsApp on your phone right after a standup, or the ChatGPT and Claude connectors. For the most sensitive material, a PIN-locked Black Box vault (triggered with @bb or #bb) is end-to-end encrypted.
On storage, the honest answer: your notes are private by default and scoped to your own account, and they are stored on secured infrastructure. That is platform-level security, the protections that come with reputable cloud storage. It is not a claim that your note content is encrypted end-to-end (only the Black Box is) and we are not going to pretend otherwise. So use the same judgment you would use with any cloud notes app: this is the right home for your working memory of who did what, and the Black Box is there for anything more sensitive.
Give your strongest people the case they earned, built from a year of dated wins.