The Brag Document: How to Track Your Work for Performance Reviews

When review season opens, most people sit down and try to remember a whole year of work in one afternoon. That never goes well. Your strongest project from February has evaporated, the cross-team save you pulled off in spring is gone, and what survives is whatever happened in the last few weeks. A brag document fixes that. It is a running, private log of what you did, captured while it is still fresh, so that writing your review becomes retrieval instead of invention.

This guide works for anyone who gets reviewed: a customer success rep, a salesperson, an operations lead, a product manager, a marketer, an engineer. The principle is the same on every team. You do the work; you also have to remember it; the brag doc is how you remember it without relying on memory.

The honest trade-off: a brag document costs you about ten minutes a week, every week, even the weeks when nothing feels worth logging. Most people who quit do so in the quiet stretches. The payoff is real but deferred: it only shows up months later when you write a review in twenty minutes instead of two stressful days. If you will not commit to the small recurring habit, skip the manual doc and automate the capture instead (more on that below).

By Samira Bahmanyar · HR Manager

Key Takeaways

• Your manager mostly remembers your recent work, not your whole cycle. A brag document is how you put the earlier wins back on the table.
• Capture weekly in artifact-linked bullets, not prose: what you shipped, who you helped, what you influenced, and how you grew.
• The format is identical across roles. Only the artifacts differ: a CS rep links tickets and renewals; a salesperson links closed deals; an engineer links pull requests.
• Turning a brag doc into a self-review is a filtering job: pick the strongest items, group them by your rubric, and write each as situation, action, result, evidence.

Try it on your own data: PerfCopilot turns real work into a cited, bias-checked review draft — generate a performance review, run the bias checker, or see it for GitHub activity. Free for up to 5 seats.

What is a brag document?

A brag document is a private, running list of your accomplishments that you add to throughout the year, so you have real evidence ready at review time instead of relying on memory. The term was popularized by software developer Julia Evans in her 2019 post "Get your work recognized: write a brag document" (jvns.ca, 2019), though the underlying habit (a work journal or accomplishment log) is much older.

Evans described the exact problem most people hit: at review time she could not remember what she had done all year and had to dig through old tickets and pull requests to reconstruct it. The brag doc removes that scramble. It is not a public brag and it is not a status report for your manager. It is a personal evidence file that you keep for yourself and draw from when you need it: reviews, promotion cases, one-on-ones, and the awkward "what have you been up to?" moment with a new skip-level.

Why a brag doc beats end-of-cycle memory

A brag document beats memory because it captures work at the moment it happens, when you still recall the specifics: the numbers, the names, the link to the deal or ticket. Human memory naturally favors recent events, and so do the people writing about you, which means the work you did early in a cycle is the first to fade.

This is not a story about bad managers. Anyone reviewing several people at once, in a compressed window, is working largely from what they can recall, and what they recall best is the last month or two. That tendency to over-weight recent events is well documented as recency bias in performance reviews, and it works against you specifically when your biggest contribution landed in Q1.

You cannot fix someone else's memory. You can hand them better evidence. A brag doc turns your review from an act of creative writing under deadline into a calm filtering exercise: the work is already written down, dated, and linked. For a deeper look at how this plays out for one role, see the engineer-specific walkthrough on self-review examples for software engineers.

How to keep a brag document

Keep a brag document by opening it once a week, on a fixed day, and adding a few artifact-linked bullets under the current date. The cadence matters more than the format. Ten minutes every Friday beats a heroic two-hour session once a quarter, because the weekly version captures detail you would otherwise lose.

Cadence: weekly capture, quarterly review

Pick one recurring slot and protect it. Friday afternoon works for many people because the week is fresh. Add bullets for what you did, then close the file. Once a quarter, spend twenty minutes reading back through and tidying: merge duplicates, add any numbers that have since landed, and flag the two or three items you would lead with if a review opened tomorrow. That quarterly pass is also a useful gut-check on where your time actually went.

What to capture (four buckets)

You do not need a complicated system. Four buckets cover almost everything, on any team:

• Shipped or delivered: the concrete output. A closed deal, a resolved escalation, a launched campaign, a published feature, a process you fixed. Link the artifact.
• Helped or unblocked: the work that does not show up in your own output. Covering for a teammate, onboarding a new hire, answering the question that saved someone a day.
• Influence: decisions you shaped, proposals you wrote, a recurring problem you named and got the team to address.
• Growth: a skill you built, a course you finished, a stretch you took on, feedback you acted on.

Write artifact-linked bullets, not paragraphs. "Resolved escalation for Acme (ticket 8841), saved the renewal, customer upgraded a tier" is enough. Future-you will fill in the prose.

Quantify when you can, estimate when you cannot

Numbers make a brag bullet credible, and almost every role has them once you look. If you genuinely cannot pull an exact figure, estimate it and say so plainly: "handled roughly 40 tickets a week at a sub-4-hour median response" is stronger than "improved support quality." A labeled estimate reads as honest; a vague adjective reads as filler.

Brag document examples by role

The format does not change across roles. What changes is the kind of evidence you link. Here is what a single week's capture looks like for five different people, all using the same four buckets.

Notice that none of these are prose, and each one links or names a real artifact. That is the whole discipline: capture the evidence now so you are not reconstructing it later.

A simple, reusable brag document template

You do not need a tool. A single text file or doc, append-only, with a section per week, is enough. Copy this and start adding to it today:

# Brag Document: [Your Name]

## Week of [date]
### Shipped / delivered
- [What you produced + link or ID + result if known]

### Helped / unblocked
- [Who you helped + what it freed up]

### Influence
- [Decision you shaped / proposal you wrote]

### Growth
- [Skill, course, feedback acted on, stretch you took]

## Week of [previous date]
...

Keep it boring on purpose. Resist the urge to design a fancy system: the only feature that matters is that you actually open it every week. If you want to back-fill, spend one session pulling the last quarter from your inbox, your CRM or ticket tool, and your calendar, then keep it current from there.

How to turn a brag doc into a self-review

Turning a brag document into a self-review is a filtering exercise, not a writing-from-scratch one. Read through the year, pick the items with the most impact, group them under whatever categories your review rubric uses, and rewrite each strong bullet into a short, evidence-led statement.

A reliable shape for each statement: situation, action, result, evidence. For example, a raw bullet like "saved the Acme renewal (ticket 8841), customer upgraded" becomes: "When Acme showed churn signals mid-cycle, I led the recovery (ticket 8841), resolved the underlying integration issue, and turned the account around: they renewed and upgraded a tier." Same facts, framed for a reviewer.

End your self-review with an honest growth area that names a specific next step rather than a fake weakness. If your team writes a lot of these, a bank of performance review phrases can help you find sharper wording, and managers writing the other side of the document can see the matching process in how to write performance reviews for engineers, which generalizes well to any role.

If you would rather not keep a manual doc

The honest weakness of the brag document is the one named at the top: it depends on a weekly habit, and habits lapse. If you know you will not keep one up, the alternative is to let your tools do the capturing. This is exactly the gap PerfCopilot fills for managers: it is a review-writing layer that connects to the systems where work already happens (Slack, Jira, Salesforce, HubSpot, Gmail, GitHub, and more), then pulls the real signals (closed deals, resolved tickets, shipped work, threads, goals) into a cited, bias-checked draft. It does not run OKRs, surveys, or compensation, and it is not a full performance platform, but for the specific job of gathering evidence so the whole cycle is represented and not just the last sprint, it removes the discipline tax. (Disclosure: PerfCopilot is our product.) If you want the broader landscape first, start with our overview of performance review software.

Frequently asked questions

What is a brag document?

A brag document is a private, running list of your accomplishments that you add to throughout the year. The term was popularized by Julia Evans in 2019. It is for your own use at review time, promotion cases, and one-on-ones, so you have dated, linked evidence ready instead of trying to remember a full cycle of work from memory.

How often should I update my brag document?

Update it weekly, on a fixed day, in about ten minutes. Weekly capture catches detail you would otherwise lose, like exact numbers and the names of people you helped. Then do a longer quarterly pass to tidy entries, add results that have since landed, and flag the items you would lead with in a review.

What should I put in a brag doc if my work is not measurable?

Use proxy evidence and honest estimates. Link the artifact even without a clean metric: the ticket you resolved, the doc you wrote, the deal you reopened, the teammate you onboarded. If you cannot pull an exact number, estimate and label it as an estimate. A labeled estimate is more credible to a reviewer than a vague adjective.

Is a brag document the same as a work journal?

They overlap. A work journal can be a freeform daily log; a brag document is focused specifically on accomplishments and evidence you will reuse at review time. You can keep one file that serves both purposes. The key difference is intent: a brag doc is curated for later retrieval, so artifact-linked bullets beat long narrative entries.

How do I turn a brag document into a self-review?

Filter, group, and rewrite. Pick your highest-impact entries, sort them under your review rubric's categories, and turn each into a short statement using situation, action, result, and evidence. Close with a specific growth area. Because every claim traces back to a dated bullet, the self-review reads as evidence rather than recollection.

Conclusion

The people who write the strongest reviews are rarely the ones with the best memory. They are the ones who kept a simple file open and spent ten minutes a week adding to it. A brag document turns review season from a stressful reconstruction into a quick filtering job, and it does the same work for a CS rep, a salesperson, an ops lead, a PM, and an engineer alike.

Two things to do this week: create the file with the four buckets above, and back-fill the last quarter from your inbox, your CRM or ticket tool, and your calendar. From there, keep it current. And if a weekly habit is not realistic for you, that is a fair reason to let your tools capture the evidence instead.

Start your next review from real work, not a blank page. PerfCopilot pulls the signals you already generate into a cited, bias-checked draft. Free for teams up to 5; Pro $4.99/seat/mo billed annually. Get started.

Related

• Self-review examples for software engineers
• How to write performance reviews for engineers
• Performance review phrases
• Performance review software

Affiliation: PerfCopilot is our product. We have tried to keep the comparisons fair and the trade-offs honest. Spot an error or an out-of-date detail? Email corrections to hello@perfcopilot.com.

Sources

• Julia Evans, "Get your work recognized: write a brag document," published 2019-06-28, retrieved 2026-06-04, https://jvns.ca/blog/brag-documents/