Panda's Recap

The Brag Document: A Template, Real Examples, and How to Keep Yours Alive

Updated July 25, 2026 · by the Panda's Recap team

A brag document is a running record of your accomplishments at work — what you shipped, fixed, improved, and made possible — kept all year, so that when review season arrives the evidence is already written down instead of half-forgotten.

The name is a joke at its own expense. It isn't bragging; it's record-keeping for the one subject nobody else is keeping records on: your work.

Why you need one

Two facts collide every review season. First, you genuinely cannot remember your own year. What you did in February is gone by November, and what survives is whatever happened recently — which is why year-end reviews quietly become reviews of the last quarter. Second, your manager remembers even less. They're reconstructing five to ten people's years from the same failing memory, between meetings.

A brag document fixes both. You stop depending on memory, and you can hand your manager the evidence instead of hoping they recall it. People who do this consistently get reviews that reflect their actual year. People who don't get reviews that reflect their actual November.

What goes in it

• Things you shipped or finished — projects, launches, migrations, documents, decisions that stuck.
• Problems you solved — the outage handled, the process unstuck, the fix nobody else could find.
• People you helped — mentoring, unblocking, onboarding, the questions that keep coming to you because you're the one who knows.
• Numbers, when they exist — time saved, errors reduced, revenue touched, tickets closed. Don't invent them; do capture them while they're fresh.
• What you learned — new skills and new territory. This is the growth story your next review or résumé is built from.

The bar for an entry is low on purpose. One honest sentence written the week it happened is worth more than a polished paragraph reconstructed months later.

The template

Copy this into whatever you'll actually keep open. The structure matters less than the habit, but this shape has a reason: entries grouped under goals turn straight into a self-review, and the "boring but real" section exists because invisible maintenance work disappears first from memory.

# Brag document — [Your name], [Year]

## Goals this year
(What you and your manager agreed matters. Entries below tie back here.)
- Goal 1 …
- Goal 2 …

## Projects and wins
(One entry per thing, dated, written the week it happened.)
- [Mar 4] Shipped …  — what it was, why it mattered, my part in it.
- [Apr 22] Led …  — outcome, who benefited, anything measurable.

## Fires put out
- [Feb 11] Diagnosed and fixed …  — impact if it had stayed broken.

## People I helped
- [May, ongoing] Onboarded …  — what they can now do without me.

## The boring but real
(Maintenance, cleanup, meetings run, documentation. It counts. Write it down.)
- …

## What I learned
- …

## For next review
(Things to raise: scope grown, responsibilities added, the case for what's next.)
- …

What a good entry looks like

The difference between a brag document that writes your review for you and one that doesn't is specificity. Same events, written two ways:

Notice what the strong versions have: a date, a specific thing, your specific part in it, and what changed because of it. None of them required a metric that doesn't exist.

Why most brag documents die by February

Here's the part the advice usually skips. Almost everyone who starts a brag document stops updating it within weeks, for a predictable reason: it's a second, parallel record of your work that only pays off in November. Nothing reminds you. Nothing depends on it. The doc just sits there, and skipping a week is free — until you've skipped forty of them and it's review season and the document holds three entries from January.

The fix isn't discipline; it's making the record a by-product of something you already do. If your task list, your time tracking, and your brag document are the same thing, then working keeps the record, and there's nothing separate to abandon.

Common questions

How often should I update it?

Weekly is the honest minimum. Fifteen minutes on Friday beats an hour at month-end, because the value is in details you'd otherwise forget, and detail fades in days, not weeks.

What if my work doesn't produce numbers?

Most work doesn't. Write what changed because you did the thing: who was unblocked, what stopped breaking, what a decision made possible. A specific sentence about a real outcome beats an invented percentage.

Is a brag document the same as a self-review?

No — it's the raw material. The brag document is what you collect all year; the self-review is the story you write from it at review time. Writing a self-review without one means reconstructing a year from memory, which is exactly what goes wrong.

Should I share it with my manager?

A tidied version, before your review: yes. Your manager writes their review of you from memory too. Handing them your evidence makes their job easier and your review more accurate.

How is it different from a résumé?

A résumé is the highlight reel for strangers, compressed to two pages. The brag document is the uncompressed archive for yourself. When you need a résumé, you write it from the brag document — or let it write itself.