How to Build a Brag Document That Actually Gets You Promoted

Most Brag Documents Fail Before the Meeting Even Happens

The advice to "keep a brag document" is everywhere, and most people who follow it end up with a running list: shipped the Q2 report, ran the onboarding project, covered for a teammate on leave, presented to leadership twice. It's accurate. It's also almost useless in a promotion conversation, because a list of tasks doesn't answer the question your manager actually has to answer to their own boss: why does this person deserve the next level, specifically?

Start From the Level, Not From Your Calendar

Before you write a single entry, find your company's leveling guide or competency matrix for the role above you — most companies have one, even if nobody hands it to you unprompted. If yours truly doesn't exist, ask your manager directly what separates someone at your level from someone at the next one. Then organize your brag document around those criteria instead of around your calendar.

• Task-based (weak): "Led the migration to the new CRM system."
• Level-mapped (better): "Ownership at scope beyond current role — led the CRM migration across three teams with no direct authority over two of them, which is a Senior-level expectation on our ladder."

Log Entries While They're Fresh

The biggest reason brag documents fail isn't laziness — it's timing. Nobody remembers the exact impact of something they did eight months ago with enough precision to make it a compelling data point. The habit that actually works is logging an entry within a day or two of it happening, while you still remember the before-and-after, the stakeholders involved, and the specific obstacle you solved. A rushed reconstruction the week before calibration reads exactly like what it is.

Every Entry Needs Three Things

A strong brag document entry isn't just what happened. It's three parts: the situation, what you specifically did (not your team — you), and the measurable or observable result. If you can't fill in the third part with something concrete, that's a sign the entry needs another week to develop before it's ready to include, not that you should pad it with adjectives.

Use It Before the Meeting, Not Just During It

The most common mistake is treating the brag document as ammunition you save for the promotion conversation itself. By then it's often too late — your manager should already know most of what's in it, because you've been sharing highlights in 1:1s throughout the cycle. The document's real job is to make sure nothing you mentioned in passing six months ago gets lost by the time calibration happens, and to give your manager a ready reference when they're building your case with their own leadership, often without you in the room.

Review It Against the Ladder Quarterly

Once a quarter, sit down with your brag document and your leveling criteria side by side. If there's a competency with no entries under it, that's not a writing problem — it's a signal about where to focus your actual work for the next few months, before the next review cycle makes it a harder conversation.

The habit underneath all of this is capturing wins the moment they happen instead of trying to remember them later, which is the exact gap Strivo is built to close — you talk through what you did while it's fresh, and it's there, tagged and ready, when it's time to build the case.