How to keep a brag document
A template, real examples, and how to actually stick with it
Performance reviews reward the work someone can remember, and memory leans hard on the last few weeks. The project you finished in March, the problem you fixed in May, the new hire you got up to speed over the summer: by December most of it is gone, for your manager and for you.
A brag document is the fix. It's an ongoing record of what you did, why it mattered and what came of it, kept while it's fresh, so you're never reconstructing a year from calendars and old messages the night before your self-review.
What a brag document is
It's a private, running list of your work: the projects, the fixes, the people you helped and the results, written down as they happen. You'll also hear it called a brag sheet, a brag file, a hype doc, an accomplishments log or a work log. They're all the same idea. The name caught on after engineer Julia Evans wrote Get your work recognized: write a brag document, and it has since spread well beyond engineering.
It isn't a resume. A resume is a polished page for strangers. A brag document is the messy, complete record a resume, a self-review or a promotion case gets written from. Anyone whose work is reviewed by someone else should keep one: nurses, teachers, salespeople, analysts, designers, managers, engineers.
What goes in it
One formula works for every role: what you did → why it mattered → the result.
- Projects you shipped or finished, and the outcome (numbers if you have them)
- Times you unblocked or helped someone else
- Decisions you drove, and what happened because of them
- Skills you picked up, and where you used them
- Thanks and feedback people gave you, word for word
- The unglamorous work that kept things running
That last one matters more than it looks. The on-call nights, the onboarding docs, the meeting you ran so nobody else had to: it's the work that gets forgotten first, and often the work that shows you're ready for more.
A brag document template you can copy
Group by quarter, then by theme. Copy it into Google Docs, Notion, Apple Notes or a plain text file. If you'd rather keep it as a spreadsheet, the Excel and Google Sheets version below has one row per entry, with columns for what you did, why it mattered and the result:
Spreadsheet for Excel or Google Sheets Markdown
Two of those sections are easy to skip and worth keeping. What people said gives your manager quotes they can repeat in a calibration meeting. Numbers to fetch saves you hunting for metrics in December: note which number you'll want and where it lives, and fill it in later.
Example entries for any job
The same formula works everywhere. What you did, why it mattered, what came of it:
- A product manager: "Ran the pricing test we'd argued about for two quarters. Trial starts rose 9% in the first week, and the leadership debate ended with data instead of opinions."
- A nurse: "Caught a drug interaction on a new admission before the first dose. Flagged it with pharmacy, and we changed the order set so it gets checked automatically now."
- An engineer: "Rebuilt the nightly data job. It now finishes before standup instead of after lunch, so finance closed the quarter two days early."
- An account executive: "Saved the renewal everyone had written off by finding a new champion and rebuilding the business case with their finance team. Signed for two more years."
- A support lead: "Turned our ten most common tickets into help articles. Ticket volume on those topics dropped by a third in a month, and the team got its Fridays back."
- A teacher: "Started a weekly reading group for the six students furthest behind. Four of them moved up a full reading level by spring testing."
- A people manager: "Coached Priya through her first promotion packet. She was promoted this cycle, and she now runs the team's onboarding."
- An operations analyst: "Automated the monthly reporting pack. A day of copying numbers between spreadsheets is now an hour of checking them."
- A designer: "Ran five usability sessions on onboarding and redesigned the permissions step people kept stalling on. Activation went up, and the confused support emails stopped."
Notice none of them are long, and every one names the result. That's the part you won't remember in six months.
Turning a vague entry into a useful one
Most entries start vague. Ask "so what happened?" once, and they get useful:
| Vague | Useful |
|---|---|
| Worked on the API. | Cut API response times in half, so the mobile team could ship the new checkout on schedule. |
| Helped the new hire. | Paired with Sam through his first three releases. He shipped the fourth on his own. |
| Handled a difficult customer. | Talked an angry customer out of canceling by fixing their import that afternoon. They renewed and sent a thank you to my manager. |
Detail is what you'll need later. "Improved the API" won't mean much to anyone in December. "Cut response times in half so the mobile team could ship on time" can go straight into a self-review.
Common mistakes
- Listing tasks instead of results. "Attended the planning meeting" says you were there. "Got three teams to agree on one launch date" says why it mattered.
- Only writing it at review time. Then it's a memory exercise with all the same gaps. Write things down when they happen.
- Saving it for big wins. Big wins are rare and you'll remember them anyway. It's the small, steady work that disappears.
- Hiding behind "we". Credit the team, then say what you did. Your reviewer needs to know your part.
- Leaving out the numbers you had. If there was a number, write it down. If you'll need it later, note where to find it.
- Never showing it to anyone. A record nobody reads only helps your memory. See below.
How often to update it
A line a day beats a page a month. If daily feels like too much, set ten minutes at the end of each week, and add things the moment they happen: right after a launch, a hard conversation that went well, or someone thanking you. Nobody else reads the rough version, so don't polish it.
If you sit down on a Friday and can't think of anything, run through these:
- What did I finish this week, and who noticed?
- Who did I help, and what could they do afterwards?
- What did I decide, or push someone else to decide?
- What went wrong, and what did I do about it?
- Did anyone thank me? Copy their words while you still have them.
Starting late? Rebuild the year in an hour
If review season is already here and you have nothing written down, you can still recover most of it. Block an hour, go month by month, and write one line for each thing you find:
- Your calendar. Meetings you organized, launches, presentations, interviews you ran. Each one points at a piece of work.
- Your sent email and chat. Search for "thanks", "thank you" and "great job" to find praise. Search for "shipped", "launched" or "done" to find finished work.
- Wherever your work gets tracked. Closed tickets, closed deals, resolved cases, finished projects. Filter for your name and this year.
- Documents you wrote. Sort by date created. Proposals, plans and write-ups are usually the bigger pieces of the year.
- Last year's goals. Mark each one done, changed or dropped, and note why. A goal you dropped for a good reason is still worth a line.
It won't be as good as notes kept at the time, but it will be far better than memory. Then start the weekly habit, so next year takes ten minutes.
Share it with your manager
A brag document only you read helps your memory. Sent to your manager a week or two before they write your review, it helps your rating. Most managers write reviews from what they can recall, and they're glad to work from your record instead. It also gives them specifics to quote in calibration, the meeting where managers compare their people and settle ratings. Between reviews, skim it together in a 1:1 every month or so. When the evidence is on the table, the promotion conversation tends to start on its own.
Turning it into your self-review
When review time comes, your brag document is the raw material. Group the entries by whatever your company measures, often delivery, collaboration and growth, and pick the strongest two or three under each. If there's a leveling guide, use its words. Then write it up using these self-review examples, and turn the biggest wins into STAR stories for interviews and promotion packets. Our guide to preparing for a performance review walks through the rest.
Keeping it going
Every brag document guide says to update it on Fridays, and most people stop by the third week. The busy weeks, when the most is happening, are exactly the weeks nobody opens the doc. If that sounds familiar, make the habit smaller or hand it to something that doesn't forget.
Make it automatic
Nisshi is a work journal built for this. You jot a few lines about your day, or let completed tasks and meetings fill it in, and Nisshi does the rest. It turns your entries into weekly and sprint summaries on its own, shapes them into impact stories, and drafts a full self-review for any date range when you need it. You keep the habit small, and the brag document builds itself.
Or skip writing it altogether. If you already work with an assistant like ChatGPT or Claude, connect it to Nisshi and it can write the entries for you, filed under the right heading and tailored to your role. Add one line to its instructions, like "when we finish a piece of work, add a short entry to my Nisshi journal saying what we did and why it mattered", and your brag document keeps itself while you work.
And because your work record is nobody's business but yours, Nisshi keeps it on your Mac, with no account and no cloud. It's yours, not your employer's, and it comes with you when you change jobs.
Questions people ask
What's the difference between a brag document and a resume?
A resume is a short, polished summary written for people who don't know you. A brag document is the complete, private record you keep for yourself and your manager. Your resume, self-review and promotion case all get written from it.
How long should a brag document be?
As long as your year needs. Each entry should be a line or two, but there should be a lot of them. A couple of entries a week adds up to around a hundred by the end of the year, and that's the point: you'll pick the best ten when it's time to write.
How often should I update my brag document?
Ideally whenever something happens, and at least once a week. A line a day takes a minute. A page at the end of the quarter takes an evening and still misses things.
Should I share my brag document with my manager?
Yes, usually a week or two before they write your review. Take out anything private first. Most managers are glad to have it, because it saves them reconstructing your year from memory.
Doesn't keeping a brag document feel like bragging?
Only if you write it like an ad. Written plainly, with what you did and what came of it, it reads as a record, not a boast. Think of it as evidence your manager would otherwise have to go and find.
Is a brag sheet the same as a brag document?
Yes. Brag sheet, brag file, hype doc, accomplishments log and work log all describe the same thing: a running record of your work and its results.
What's the best tool for a brag document?
Whichever one you'll actually keep using. A Google Doc or a note works if you're disciplined about it. If you'd rather it kept itself, Nisshi turns a line a day, or entries your assistant writes for you, into recaps, stories and a review draft.