A brag document is a private, running list of your work wins, what you shipped, the impact it had, and the proof, kept up to date all year so you never have to reconstruct it from memory at review time. Build it once, add one line whenever something goes well, and when self-evaluation season arrives you copy-paste instead of staring at a blank form trying to remember what you did in March.
The hard part is the habit, not the template. Most brag-doc advice hands you a doc and a list of headers, then quietly assumes you'll remember to fill it in. You won't, and not because you're lazy. The win happens on a Tuesday afternoon mid-sprint, and by Friday it's gone. This page gives you the template and the one change that makes it actually stick: capture each win the day it happens, in one line, tagged by project.
The brag document template
Copy the template below and paste it wherever you keep private notes. The whole point is that it stays short: one line per win, with a format you can fill in without thinking. The "how to use this" header is part of the template on purpose, so future-you remembers the rules.
# Brag Document - [Your Name] - [Year] ## How to use this - Add ONE line whenever something goes well. Don't wait for it to feel "big enough." - Format: [Date] - [What I did] -> [Impact] -> [Proof] #project #competency - At review time: group by #competency, expand the strongest 8-12 into full bullets. ## Wins log (newest first) - 2026-06-18 - Cut onboarding email build time by automating the QA step -> saved ~3 hrs/week across the team -> [link to runbook] #onboarding #efficiency - 2026-05-30 - Led the incident retro after the payments outage; turned it into 3 shipped fixes -> zero repeat incidents since -> [retro doc] #payments #leadership - 2026-05-12 - Mentored new hire through their first solo release -> they shipped independently 2 weeks early -> [thank-you screenshot] #mentoring ## Kudos & recognition (paste it the moment you get it) - 2026-06-02 - "[paste exact quote]" - Priya, in #team-product - 2026-04-19 - Shout-out in all-hands for the migration -> [recording timestamp] ## Goals & focus areas (so you can show progress against them) - [Goal 1] - current status / evidence - [Goal 2] - current status / evidence ## Numbers worth remembering (your year in metrics) - [metric] from [X] to [Y] over [period]
Three tabs (Wins, Kudos, and Numbers), pre-filled with examples and a frozen header. Opens in Excel, Google Sheets, or Numbers. Nothing to sign up for.
That's it. No app to learn, no system to maintain. The only rule that matters is the first one: add the line the day it happens, before the detail fades.
Brag document vs brag sheet: is there a difference?
Strictly speaking, yes. A “brag sheet” is usually the high-school form a student fills out for a teacher or counselor before a recommendation letter, while a “brag document” is the work version: a running, personal list of your wins kept for review season, self-evaluations, and promotion cases. At work you’ll hear both, usually meaning a spreadsheet (one row per win, with columns for date, impact, and proof) versus a text file with the same content grouped under headings. Use whichever you’ll actually keep. The template above works as either. Copy it as text, or download the spreadsheet version with a tab per category.
Why maintaining a brag document matters
A brag document matters because memory is a bad filing system and review season is worse. Your strongest work (the quiet save, the incident you led, the mentoring that paid off months later) is exactly what fades first, while one recent stumble stays vivid. A maintained brag doc is what turns your self-review from a stressful reconstruction into a read-through, gives you concrete evidence for a raise or promotion, and protects you from recency bias in your own story. The value is entirely in the maintaining: one line the day it happens beats an hour of remembering in December.
Vague vs specific: rewrite each entry once
A brag document is only as useful as the lines in it. The most common mistake is logging the task ("helped with onboarding") instead of the impact ("cut setup from four days to same-day, activation up 12%"). The fix is one extra clause: what changed because you did it. Here is the same work, before and after.
| Vague (a task) | Specific (evidence) |
|---|---|
| Helped with onboarding. | Rebuilt the onboarding email flow; cut setup from four days to same-day, activation up 12% in the next cohort. |
| Worked on the payments outage. | Led the incident retro after the payments outage and turned it into three shipped fixes; zero repeat incidents since. |
| Mentored a new hire. | Mentored the new hire through their first solo release; they shipped independently two weeks ahead of plan. |
| Improved our docs. | Rewrote the API docs after new hires kept asking the same five questions; ramp time dropped from about three weeks to about ten days. |
| Did a lot of code reviews. | Reviewed 40+ PRs this half and introduced a self-review checklist; review cycles per PR dropped by roughly a third. |
You don't have to write it this way the moment it happens. Log the rough line in the moment, then sharpen the strongest ones at review time. The dated raw line is the part you can't recover later; the polish you can always add.
From logged lines to a competency paragraph
At review time, the magic is grouping. Pull every line tagged with one competency, and the paragraph almost writes itself. Here are three separate lines someone logged across the year, all tagged #leadership:
- 2026-05-30: Led the incident retro after the payments outage; turned it into 3 shipped fixes, zero repeat incidents since.
- 2026-03-14: Owned cross-team QA coordination for the launch when it was at risk; ran daily syncs and a shared tracker. Shipped on date, zero P1s.
- 2026-02-02: Volunteered to onboard two new hires; built the ramp checklist the team now reuses.
Grouped under Leadership & ownership, that becomes one strong self-review paragraph:
I stepped into ownership beyond my role this year. When the launch was at risk in March I ran cross-team QA coordination, daily syncs, and a shared tracker, and we shipped on date with zero P1 incidents. After the payments outage in May I led the retro and turned it into three shipped fixes, with no repeat incidents since. I also built the new-hire ramp checklist the team now reuses. Across all three, I owned the outcome, not just my piece.
Notice what made that possible: each fact had a date and a number already attached, because it was captured the week it happened. You aren't writing from memory. You're editing evidence.
Why you can't remember your year
When the self-review form lands, most people open it and go blank. That isn't a character flaw, it's how memory works. Two things are working against you at once.
Recency bias. Your brain offers up the last few weeks first, vivid and loud, and quietly drops the rest. The migration that ate three weeks in spring, the quiet save during a hire's first month, the workstream that simply fell below the waterline of recent attention: all gone. So your self-review becomes an account of the last sprint with the whole year compressed into a feeling. (More on that in our guide to recency bias in performance reviews.)
Wins don't announce themselves. The big, obvious launch you'll remember. But most of your real impact is small and undramatic in the moment: the bug you caught in staging, the teammate you unblocked, the doc you rewrote. None of it feels "big enough" to write down, so you don't, and then it's gone. By review season you're doing memory archaeology, digging through old tickets and your calendar trying to reconstruct a year you already lived. The problem was never your writing. It was that nothing got captured while it was still true.
Capture wins the day they happen
The single change that makes a brag document work is moving capture from review season to the moment the win lands. The day you ship something, the day a teammate thanks you, the day you catch a number move in the right direction, write one line. Not a paragraph. One line, dated, tagged.
This sounds almost too small to matter, and that's exactly why it works. A line takes ten seconds and survives. A "I'll write it up properly later" never gets written. The brag document isn't a writing project you do once a year. It's a tiny habit you do all year, so that the writing project never has to happen.
Set it up in five minutes
- Pick one capture spot. One private place you'll actually open. A second list you have to remember is a list you'll abandon.
- Set a Friday reminder. A recurring ten-minute slot to log anything from the week you didn't catch in the moment.
- Log the boring wins too. The unblock, the catch, the cleanup. The small stuff is what memory throws away, so it's exactly what you need on paper.
- Paste praise verbatim. The moment someone recognizes your work, paste their exact words and who said it. Real quotes beat your own summary.
- Tag everything with #project. Tagging as you go is what lets you group your year later without reorganizing anything by hand.
Make the habit effortless with Notivo
A brag document only works if you keep it up to date, and a doc you have to remember to open is exactly what gets abandoned by February. That's the whole problem Notivo is built to remove. The moment a win happens, type one private note and add a tag like #onboarding. The note files itself into an #onboarding timeline automatically. If you @mention a person, it also files into their timeline. No folders, no reorganizing, no remembering where things go.
Then at review time you open the tag, and your year is already grouped, dated, and searchable. The strongest eight to twelve lines are right there, ready to expand. The brag document stops being a thing you build in a panic and becomes a thing that quietly built itself.
One honest note on storage: your notes are private by default and stored on secured infrastructure. That's platform-level security, the protections that come with reputable cloud storage, plus account-level access controls that keep your notes visible only to you.
Frequently asked questions
What is a brag document?
A brag document is a private, running list of your work wins, what you did, the impact it had, and the proof, kept current all year so reviews and promotions are copy-paste instead of a memory test.
Is a brag document the same as a brag sheet?
No. A brag sheet is usually the high-school form you give a teacher or counselor for a recommendation letter. A brag document is the work version: a private log of your professional wins. Use the term brag document so you find the right templates and advice.
How often should I update it?
Update it the day a win happens, in one line, while you still remember the detail. If you prefer a routine, keep a recurring ten-minute slot once a week to log anything you missed.
Isn't keeping a brag document just bragging?
No. It is record-keeping, and it stays private. A brag document makes you more accurate, not more boastful. It gives you the dated facts so your self-review and your case for a raise rest on evidence instead of a vague feeling about the year.
What should I include in each entry?
Four things: what you did, the impact it had, the proof you can point to, and the competency it demonstrates. The impact and the proof are what turn a task list into evidence.
How do I turn it into a self-evaluation?
Group your entries by competency, pick the strongest eight to twelve, and expand each into a situation, action, and measurable result. Paste any kudos verbatim. Most of your self-evaluation is already written.
Can a brag document help me get promoted?
Yes. A promotion case is a year of evidence assembled into an argument. A brag document is that evidence, captured as it happened, so you can show you have been operating at the next level instead of trying to remember it the week before.
Keep going
Once your wins are logged, the rest gets easy. Turn them into a self-review, build the promotion case, or read why memory works against you at review time.
- Self-evaluation examples, with 30+ before/after lines by competency, plus how to stop writing from memory.
- Promotion packet template, for turning a year of wins into an argument that proves the next level.
- Recency bias in performance reviews, the reason your year collapses into the last six weeks.
- Notivo for employees, your private work memory, organized by project and person.