Back to blog

What Is a Brag Document (And Why You Need One Before Your Next Review)

Career Growth

A brag document (or achievement log) is a running log of your wins, regular tasks, feedback and metrics. Here's why keeping one all year makes review season painless.

What Is a Brag Document (And Why You Need One Before Your Next Review)

Quick question. What did you actually accomplish in March? Not the vague "it was busy" answer. The specific stuff. The project you saved, the process you fixed, the compliment your manager gave you in passing that you never wrote down.

If you're struggling to answer that, you're not alone, and you're also exactly why brag documents (also know as an achievement log) exist.

So What Is a Brag Document, Really

A brag document is a living record you keep for yourself, updated throughout the year, that tracks your wins, your projects, your metrics and any good feedback that comes your way. Some people call it a hype document. Some call it a brag sheet. Whatever the name, the idea is the same: instead of trying to remember a year of work in the ten minutes before your review is due, you've already got it written down.

It's not a CV. It's messier than that, and that's the point. A CV is polished and public facing. A brag document is the backstage notebook, full of half finished experiments, small wins nobody clapped for, and the kind of detail that never makes it onto LinkedIn.

The term got popular through Software Engineer Julia Evans, who wrote about keeping one document a year to track contributions and impact. It stuck, and now it's spread well beyond engineering into pretty much every corner of knowledge work.

Why Your Memory Cannot Be Trusted Here

Here's the uncomfortable bit. Research into performance management keeps landing on the same finding: managers generally can't recall specific things you did more than 60 to 90 days ago. Not because they don't care, but because nobody's memory works like that when they're managing five, ten, fifteen people at once.

Which means if you shipped something brilliant in Q1 and your review happens in Q4, there's a real chance it's just... gone. Not forgotten on purpose. Just naturally faded, the way most of what we do fades.

A brag document is your insurance against that. It's evidence gathered while it still exists, rather than reconstructed from memory under pressure months later.

What Actually Goes In One

There's no single required format, but most good brag documents end up with a similar shape:

The basics Your name, role, team and the period you're covering. Simple, but it anchors everything else.

Goals for the period A short list of what you were aiming for. This gives later entries something to be measured against.

Major projects and outcomes The meat of the document. What you delivered, why it mattered, and what changed because of it. Numbers help a lot here.

Quantifiable metrics Percentage improvements, time saved, cost reduced. Anything measurable. These are what turn "I worked hard" into "I cut deployment time from 40 minutes to 9."

Collaboration and leadership Mentoring, cross team work, running that onboarding revamp nobody asked for but everyone benefited from. Easy to forget, important to promotion cases.

Skills and learning Courses, certifications, new tools you picked up. Proof you're growing, not just grinding.

Feedback and recognition Quotes from managers, peers, customers. Save them the moment you get them. Screenshot the Slack message. You will not remember the exact wording six months from now.

A running log A simple, chronological diary of what happened when. This is often the most underrated section, because it's the one that stops smaller wins blurring together into nothing.

I'll be honest, I think this last one is the most important part and the one people skip most often. Big projects tend to stick in your memory anyway. It's the quiet, one line wins that vanish, and those are often exactly what a manager needs to hear about.

The Real Benefits (Beyond Just "Looking Good")

Fairer, more accurate reviews When you walk into a review with specifics instead of vague impressions, the conversation changes. You're not debating whether something happened, you're discussing what it meant and where to go next.

Stronger promotion and pay cases Promotion decisions run on evidence of sustained impact. A brag document gives you a ready made pattern of achievement to point to, rather than trying to build a case from scratch during promotion season.

Visibility for the invisible work Mentoring, stabilising a shaky system, quietly unblocking a colleague. None of that shows up on a dashboard. A brag document gives it somewhere to live.

A genuine confidence boost This one surprised me a bit, but it's backed up repeatedly: scrolling through a long list of things you've actually done is a decent cure for imposter syndrome. Turns out seeing the evidence helps more than just telling yourself you're doing fine.

Easier CV updates and job moves When you're job hunting and trying to remember what you did eighteen months ago at a different company, a brag document is the difference between staring at a blank page and copy pasting strong bullet points straight in.

How to Actually Start One

Don't overthink the format. A Notion page, a Google Doc, a plain text file, whatever you'll actually open again. The best brag document is the one that survives past week two.

Start with the last month. List three to five things you did, why they mattered, and any numbers attached. Then work backwards through your calendar, tickets and emails to fill in earlier wins. Don't aim for completeness, aim for the stuff that mattered.

Use a consistent structure for each entry: what the situation was, what you did, what changed, and what proves it. Keep entries short. You can always expand them later when you need a fuller story for a review or a promotion packet.

And the habit matters more than the format. Five minutes on a Friday, logging what happened that week, beats a beautifully structured document you update twice a year.

The Biggest Mistake People Make

Treating it as a one off task the week before their review. At that point you're back to reconstructing from memory, which defeats the entire purpose. The value comes from the habit, not the document itself.

The second biggest mistake is logging activities instead of outcomes. "Attended the planning meeting" tells nobody anything. "Proposed the change that cut planning time in half" does. Whenever you can, upgrade your entries from what you did to what changed because you did it.

Where the Real Work Still Waits

Here's the thing about a brag document, even a perfect one. Having a year of well logged wins doesn't automatically turn into a polished self assessment or a strong case for promotion. You still have to sit down, read through months of one liners and half formed notes, and shape them into something a manager or a promotion committee will actually read.

That's the part I think gets overlooked. The logging is the easy bit once you've got the habit. The harder bit is turning "fixed the flaky deploy pipeline, saved everyone about 20 minutes a day" plus many other entries into three tight themes with a clear narrative. That's genuinely where I think AI assisted tools earn their keep, not by inventing achievements for you, but by helping structure the raw material you've already honestly logged into something coherent.

How Perform Review Can Help

If you like the idea of a brag document but know yourself well enough to admit you won't keep opening a spreadsheet every Friday, Perform Review's Achievement Log is built for exactly this. It's a simple tool for logging one liner tasks, wins and feedback as they happen throughout the year, and it integrates directly with Slack. Add an entry on the fly through the Perform Review Slack bot or with a quick /log command, no context switching, no forgotten tab.

Beyond the Achievement Log, Perform Review helps you turn that running record into high quality, professional self, peer and manager reviews with AI assistance, so when review season arrives, you're editing a strong draft instead of starting from a blank page.