Productivity
The Brag Document: Track Your Wins So You Never Forget Them
A brag document is a running record of your accomplishments at work. Learn what to track, how to keep it, and how to use it for reviews, raises and confidence.
Key takeaways
- A brag document is a running record of your wins. It captures what you did, the impact, and the evidence, as it happens.
- Memory is unreliable. By review season you will have forgotten most of your early-year work, and so will your manager.
- Track impact, not activity. Record outcomes and numbers, not just tasks, so the entries make a case on their own.
- Update it little and often. A two-minute entry every Friday beats a frantic rebuild once a year.
- It pays off everywhere. Reviews, raises, interviews and bad days of self-doubt all draw on the same log.
A brag document is a running, private record of your work accomplishments: what you did, the impact it had, and the evidence to back it up, captured as it happens rather than remembered at the end of the year. It exists because memory is unreliable — by review season you and your manager will have forgotten most of what you did in the first half of the year. Keep it short and current, track impact rather than activity, and you will have a ready-made case for every review, raise, promotion and interview, plus a factual antidote to self-doubt on the hard days.
Why you need a brag document
The term was popularised by software engineer Julia Evans, but the problem it solves is universal: good work is invisible unless someone records it, and memory is a terrible record-keeper. Ask yourself what you delivered in March. Most people cannot answer, and neither can their manager, who is tracking their own year and a whole team besides.
That gap has real consequences. Come performance-review time, the work that gets rewarded is the work that gets remembered, which tends to mean the last two months and whatever was loudest, not what mattered most. A brag document fixes this by capturing your contributions while they are fresh, so your case is complete rather than recency-biased.
It also protects you against a quieter risk: managers move on. A boss who saw your best work leaves, a reorganisation drops you under someone new, and suddenly the person deciding your raise has no memory of your first nine months. A record you control survives all of that, because it does not depend on anyone else having paid attention.
What to put in it
The single biggest mistake is logging activity instead of impact. "Attended the planning meetings" is activity. "Reshaped the roadmap in planning, cutting the launch timeline by three weeks" is impact. Always push past what you did to what changed because you did it, with a number attached wherever you can find one.
Capture entries across these categories:
- Projects and deliverables you led or meaningfully contributed to, and the outcome.
- Problems you solved, especially ones that were costing time, money or morale.
- Metrics you moved: revenue, costs, speed, quality, retention, anything measurable.
- People you helped: mentoring, onboarding, unblocking colleagues.
- Skills you learned and how you applied them.
- Feedback and recognition, quoted directly where possible.
How to keep it current
A brag document only works if it is alive, and the enemy of that is trying to do it all at once. The trick is a tiny, regular ritual rather than an annual archaeology project. Add one or two entries every Friday as part of your shutdown routine, while the week is still clear in your mind. Two minutes a week beats two frantic hours the night before your review.
Keep the format simple so there is no friction. For each entry, note the date, what you did and its impact, and a link to the evidence — the document, the dashboard, the thank-you email. A loose structure like this is enough:
| Field | Example entry |
|---|---|
| Date | 2026-10-20 |
| What I did | Rebuilt the onboarding flow for new customers |
| Impact | Cut drop-off at sign-up from 22% to 9% |
| Evidence | Link to the analytics dashboard and launch doc |
| Feedback | "Biggest conversion win this quarter" — Head of Product |
How to use it when it counts
The log is the raw material; its value comes out when you shape it for a specific purpose.
- Performance reviews: group your entries into the themes your organisation rewards and pull the strongest, most quantified examples into your self-assessment. This is the backbone of good review preparation.
- Asking for a raise: your documented impact is the evidence that turns a request into a business case.
- Interviews: your entries convert cleanly into the specific, results-driven stories that strong answers are made of.
- Updating your manager: a glance at recent entries gives you a ready summary for a one-on-one or a status update.
The key move in every case is translation. A raw log entry is for you; a review bullet or interview story is for someone else, so you reshape it for the audience. "Cut sign-up drop-off from 22 to 9 percent" becomes, in a review, evidence of commercial impact, and in an interview, a story about spotting a problem and owning the fix. Because the facts and numbers are already captured, that translation takes minutes instead of a painful afternoon of trying to remember whether the figure was 9 percent or something you half-invented under pressure.
The hidden benefit: confidence
There is a payoff that has nothing to do with reviews. On the days when you feel like you have achieved nothing — a near-universal experience, and the heart of imposter syndrome — a brag document is a factual rebuttal. You can open it and see, in black and white, a year of real contribution. Feelings lie about your track record; a written log does not.
Nobody is going to track your impact for you. Spend two minutes a week doing it yourself, and you will never again have to reconstruct a year of work from memory, or wonder whether you actually accomplished anything.
Start today, even if it feels like starting late. Open a note, write down three things you did this week and what came of them, and put a recurring reminder on Friday afternoons. By the time your next review, raise conversation or job search arrives, you will have exactly what everyone else wishes they had kept: the receipts.
Frequently asked questions
What is a brag document?
A brag document is a running, private record of your professional accomplishments: the projects you delivered, the problems you solved, the impact you had, and the positive feedback you received. The term was popularised by software engineer Julia Evans. Its purpose is to replace unreliable memory with a concrete, evidence-based record that you can draw on for performance reviews, raise conversations, promotions and job interviews, so your work is never quietly forgotten.
What should I include in a brag document?
Record what you did and, more importantly, the impact it had, with numbers wherever possible: time or money saved, metrics moved, problems resolved. Include projects led or contributed to, skills learned, people helped or mentored, process improvements, and any positive feedback or recognition you received. For each entry note the date and a link to the evidence, so you can expand it into a full case later without having to reconstruct the details.
How often should I update my brag document?
A short, regular cadence works far better than an occasional overhaul. Many people add entries weekly, for example as part of a Friday wind-down, which takes only a minute or two while the details are fresh. At minimum, update it monthly. The point is to capture work as it happens rather than trying to remember a whole year at review time, when most of it will have faded.
How do I use a brag document for a performance review?
Before the review, read through your log and group the entries into themes that match what your organisation values, such as impact, leadership or teamwork. Pull out the strongest, most quantified examples and turn them into clear statements of contribution. Because you captured the evidence as you went, you can write a precise, confident self-assessment instead of vaguely half-remembering the year.
Is keeping a brag document bragging?
No. It is a private record for your own use, not a public performance. Accurately documenting what you did and the impact it had is simply good professional hygiene, and it makes you more honest, not less, because you argue from evidence rather than impression. Many people find it also quietens self-doubt, since it gives them a factual answer to the feeling that they have not achieved anything.
Sources
- Julia Evans. Get your work recognized: write a brag document. jvns.ca/blog/brag-documents/
- Harvard Business Review. How to Write a Self-Evaluation. hbr.org/topic/subject/managing-yourself
- American Psychological Association. How to overcome impostor phenomenon. www.apa.org/monitor/2021/06/cover-impostor-phenomenon
- MindTools. Keeping a Work Journal. www.mindtools.com/pages/article/newHTE_85.htm
- U.S. Office of Personnel Management. Performance Management. www.opm.gov/policy-data-oversight/performance-management/
This article is for general information and does not replace advice from a doctor. If you have persistent sleep or health problems, consult a qualified professional.