The Brag Document: What It Is, Why You Need One, and How to Keep It
Your manager does not remember what you did in March. Neither do you. A brag document fixes that, and it takes less time than your morning coffee.
What is a brag document?
A brag document is a running record of your accomplishments at work: problems you solved, decisions you made, people you unblocked, projects you shipped. Not a diary and not a to-do list. It captures what moved forward because of you, written down while you still remember the details.
The name is a little misleading. Nothing in it is bragging. It is evidence, collected in advance, for the moments when you will need it: performance reviews, promotion cases, salary negotiations, and job interviews.
Why you need one
Performance reviews reward the people who can articulate their impact, not necessarily the people who had the most of it. Most of us walk into a review with two or three recent wins in mind and eleven months of fog behind them. The recency bias is brutal: the work you did in Q1 effectively did not happen unless it is written down somewhere.
A brag document flips that. When review season arrives, you are not reconstructing your year from calendar archaeology and old pull requests. You are choosing highlights from a complete record.
What a good entry looks like
The difference between a useful entry and a useless one is specificity. Compare:
Weak: "Fixed a bug"
Strong: "Resolved the payment timeout bug affecting 3% of checkout completions. Fix ships Monday."
The strong version has scope, impact, and a number. Six months later it still means something. Aim for one or two sentences with a concrete outcome. If you can attach a number, attach it. If you cannot, name who benefited.
What belongs in it
- Things you shipped, fixed, launched, or delivered
- Decisions you made and what they unblocked
- People you mentored, onboarded, or helped
- Fires you prevented, not just fires you put out
- Skills you used for the first time
How to actually keep the habit
This is where most brag documents die. Everyone agrees they are a good idea; almost nobody updates one weekly for a year. Three things make the habit stick:
Lower the bar. One line a day is enough. "What moved forward today, even if just a little?" is the whole prompt. An imperfect record beats a blank page by miles.
Attach it to a moment. Habits need triggers. End of the workday, right before you close the laptop, works for most people. A single quiet reminder at that hour beats any amount of willpower.
Get something back. A document you only give to never look at will not survive. The habit compounds when your record regularly turns into something useful: a standup update, a weekly summary, a review-ready narrative.
Template: the one-line format
[What moved forward] + [why it mattered or who it affected]
That is genuinely the whole template. "Led the architecture review for the payment migration; team aligned on the event-driven approach." Date it, tag the project, done. Thirty seconds.
Or let the document keep itself
ImpactTrack is a brag document with an engine: log one line a day, and it turns your entries into polished standups, sprint reports, and review-ready impact narratives. Free for macOS.
Get ImpactTrack free