· 7 min read
What Is a Brag Document? Template, Examples & How to Keep One
A brag document is a running log of your work wins — the highest-payoff career habit most people skip. What it is, a copy-paste template, what to put in it, and how to keep one without the cringe.
A brag document is a running list of what you've accomplished at work, kept as you go — dated entries noting what you shipped, what changed because of it, and any praise you got. It's also called a work log, hype doc, or "wins" doc. The point isn't a polished narrative; it's having the raw material ready when you write a résumé, a self-review, or a promotion case. It's the simplest career habit with the highest payoff, and almost nobody keeps one until they wish they had.
The term was popularized in tech by engineer Julia Evans, and it has since become standard advice for anyone who has to periodically prove their impact. Skip to the copy-paste template if you just want to start one now.
Why do you need a brag document?
- Memory is the enemy. By December, the project that mattered most in March is gone. You end up writing about last month because that's all you remember — recency bias, baked in.
- Good work doesn't speak for itself. Your manager is busy and tracking a whole team. At review and promotion time, the person who can show their impact wins over the one who merely had it.
- It turns activity into impact. A log of outcomes ("cut onboarding drop-off 18%") reads completely differently from a list of tasks ("worked on onboarding").
- It compounds. The same entries feed your self-review, your résumé bullets, your promotion packet, and your STAR interview stories. You capture once and reuse everywhere.
What goes in a brag document?
One line per entry is enough. Useful things to capture:
- Shipped work + result. "Launched X → Y outcome." Include the number while you still remember it.
- Problems solved. The fire you put out, the bug no one else would touch, the process you fixed.
- Scope signals (when there's no metric). "across 4 teams," "for 50+ stakeholders," "company's first." Not everything is quantifiable, and that's fine.
- Praise, verbatim. The Slack message, the kudos in a meeting, the customer email. Quotes are gold at review time.
- Decisions you drove. Not just what you did, but what you chose and why — that's what separates senior from junior.
Brag document template (copy-paste)
Paste this into a doc, a Notes app, or a spreadsheet and add one row whenever something happens. That's the whole system.
| Date | What I did | Result / impact | Proof (link, quote, number) |
|---|---|---|---|
| 2026-03-12 | Rebuilt onboarding email flow | Trial-to-paid 11% → 17% | Dashboard link |
| 2026-04-02 | Owned the on-call rotation no one wanted | Incident response time cut ~50% | PagerDuty report |
| 2026-04-18 | Ran first cross-team experiment review | Now weekly across 3 squads | "This is exactly what we needed" — PM, Slack |
If you prefer plain text, the same thing in one line per entry:
[Date] — [what I did] → [result/number]. Proof: [link or quote].
That's it. The format barely matters; the habit of capturing as you go is the whole value.
How do you keep a brag document without it becoming a chore?
The best brag document is the one you actually maintain, so optimize for friction, not format. The two rules that matter: capture as it happens (a weekly five-minute review is the realistic cadence), and write the outcome, not just the activity. If logging feels like work, you'll stop — keep each entry to one honest line. For a fuller system, see how to track accomplishments at work.
"Bragging" without the cringe
A lot of capable people find self-promotion uncomfortable — and the research shows it's unevenly hard: in a Harvard/NBER study, women rated their own equal-quality work about 25% lower than equally performing men did. The reframe that helps: a brag document isn't boasting, it's record-keeping. You're not inflating anything; you're writing down what happened, with the receipts attached. When review or negotiation time comes, the record makes the case so you don't have to oversell yourself.
From brag document to finished documents
Once you have a running log, the dreaded outputs get easy. Your performance self-review becomes an editing task instead of a blank page. Your résumé bullets write themselves from real results. Your STAR interview answers have specific stories ready to go. The hard part was never the formatting — it was having the raw material.
The one catch: AI can help turn a log into polished documents, but only if it's working from your actual entries. An AI that only knows your job title can only guess — and reviewers can tell. Grounded in your real log, the same AI becomes a genuine time-saver.
How Uptrack fits
Uptrack is built around exactly this habit: capture one line a day, and it turns your log into a self-review, résumé, portfolio, and interview prep — each grounded in what you actually recorded, not invented. If you've been meaning to start a brag document and never have, it makes the capture a 30-second habit and does the assembling for you.
Frequently asked questions
What is a brag document?
A brag document is a running, dated list of your work accomplishments — what you shipped, the result, and any praise — kept as you go so you have the raw material ready for résumés, self-reviews, and promotion cases.
What should I put in a brag document?
Shipped work with its result, problems you solved, scope signals when there's no metric, praise quoted verbatim, and decisions you drove. One line per entry is enough.
How often should I update it?
Capture wins as they happen, and do a five-minute review weekly. The habit of logging as you go — not the format — is what makes it valuable.