Brag Document Template You Can Copy

BRAG DOCUMENT

1. HEADER
Name:
Role:
Period covered:
Last updated:

2. TOP ACCOMPLISHMENTS
Repeat this block for each highlight.
Work or project:
My contribution:
Why it mattered:
Result or current status:
Evidence and date:
Collaborators and their contributions:
What needs a follow-up:

3. OTHER WINS
Include delivery, collaboration, mentoring, or useful work.
Contribution:
Context or effect:
Evidence and date:

4. GROWTH AND LEARNING
Skill, feedback, or lesson:
How I applied it:
Example or evidence:
What I want to work on next:

5. FEEDBACK AND PRAISE
Exact quote, or clearly labeled paraphrase:
Who gave the feedback:
Date and context:
Source or location:
Permission or sharing restrictions to check:

When I was a product manager, the worst part of every annual review was not having had enough time for myself to prepare a brag document. As a product manager working on a massive, cross-functional team, there's already so many documents and people to keep track of and follow up with that I didn't have much time to record my accomplishments, let alone refine them into a brag document. This was a double edged sword, because my reviews were with a more senior PM who experienced the things I did on a much higher level of intensity so he would have even less of a clue what was going on in my day to day.

What is a brag document?

A brag document is a running record of your professional accomplishments, organized so you can explain your contribution and find the supporting evidence. Julia Evans described this practice in her 2019 article linked in Sources below. The full record can be long; a summary for a particular review can be shorter. Follow the format your workplace requires.

Start with a private record of dates, links, and specific contributions. A career journal can provide that record, but you can also reconstruct it from permitted project files, messages, calendars, and other sources. Mark what you have verified and what still needs checking.

When to use a brag document

• Performance reviews — your self-review is just the brag document, expanded.
• Promotion packets — the brag doc is the evidence section.
• 1:1s with a new manager — the fastest way to onboard them on what you've shipped.
• Resume updates — every line in your resume should map to a line in the brag doc.
• Interview prep — 'tell me about a time' answers come from this list, not from memory.
• Layoff insurance — if you're suddenly job-hunting, you need this updated, not started.

Use that record to prepare for a review with a new manager, giving them the context and evidence behind work they did not see.

The five-section brag document template

The copyable outline at the start of this guide uses five sections. Adapt them to your Role and review requirements. Keep a fuller running record if useful, then select the most relevant items when you share a summary.

1. Header — name, role, period, link to current resume

Top of page: your name, current title, the period the document covers (e.g., 'Q1 2026' or 'last 12 months'), and a link to whatever your latest resume is. This sounds obvious; people skip it and then can't tell at a glance which version they handed someone.

2. Top three impact items

The three accomplishments you would want a stranger to remember if they read nothing else. Lead each with a one-line headline, then two or three lines of evidence: dates, metrics, the artifact. Example: 'Led migration to new auth provider — reduced login latency 40%, zero downtime cutover April 3, 2026, runbook here.'

3. Wins by category

Group your other accomplishments under whatever categories match your role. For an engineer: shipped, scaled, fixed, mentored. For a PM: shipped, researched, decided, aligned. For a designer: shipped, prototyped, taught, repaired. Keep each bullet to one line. The categories matter less than the consistency — pick four and stick with them.

4. Growth and learning

Two or three bullets on what you learned, what you got better at, what you changed your mind about. This is the section managers read most carefully because it tells them you are still growing — which is the implicit question behind every promotion conversation.

5. Quotes and praise

Save feedback from a manager, peer, customer, or stakeholder with its date, source, and context. Use quotation marks only for exact words. Label a paraphrase as a paraphrase, and check permission before sharing feedback outside its original audience.

An illustrative example: senior software engineer

The following example is illustrative, not a customer record. Names, dates, figures, and quotes are fictional and show the structure only. Replace them with your own supported contribution, results, and sources; do not reuse its metrics as your achievements.

• Header: Maya Patel · Senior Software Engineer · H1 2026 · resume link
• Top impact #1: Owned auth provider migration end-to-end — 40% login latency drop, zero downtime, runbook adopted by platform team.
• Top impact #2: Cut p99 checkout latency from 2.1s to 480ms — three commits, full writeup in eng wiki, presented at all-hands.
• Top impact #3: Designed and shipped feature flag service v2 — 11 teams onboarded, replaced 4 in-house systems.
• Wins / shipped: 27 PRs merged, 9 RFCs authored, 3 cross-team launches.
• Wins / scaled: on-call rotation runbook (12 pages), incident review process used in 4 incidents.
• Wins / fixed: 6 production bugs resolved with postmortems, 2 longstanding flaky tests stabilized.
• Wins / mentored: paired weekly with two new hires, both ramped to first solo PR within 3 weeks.
• Growth: started reviewing infra PRs (was strictly app-layer before), got better at writing RFCs that named tradeoffs early.
• Quotes: '[Maya's] runbook saved the on-call last weekend' — Sam, SRE, Mar 2026.

An illustrative example: senior product manager

This is also a fictional example. Its numbers and quotes demonstrate the format, not verified results or a promise about what a brag document will achieve.

• Header: Devon Liu · Senior PM, Growth · 2025 in review · resume link
• Top impact #1: Led onboarding redesign — activation rate from 38% to 51%, $1.4M annual revenue impact.
• Top impact #2: Shipped pricing experiment platform — 12 tests run by 4 teams in Q4, replaced 6-week vendor process.
• Top impact #3: Closed 3 strategic partnerships — added 2 distribution channels worth ~22% of new signups.
• Wins / shipped: 4 major launches, 11 PRDs, 2 strategy docs adopted by leadership.
• Wins / decided: killed the legacy referral program (saved 2 eng quarters), narrowed roadmap from 14 to 6 bets.
• Wins / aligned: facilitated 8 cross-functional planning sessions, got eng+design+marketing aligned on Q3 goals doc.
• Wins / researched: 41 user interviews, 3 quant studies, hypothesis log with 9 falsified bets and the lessons.
• Growth: stopped writing prescriptive specs, started writing problem statements — eng pushed back twice and was right both times.
• Quotes: 'This is the cleanest PRD I've reviewed all year' — VP Product, July 2025.

How to fill in your brag document

Block 30 minutes. Open your career journal. Skim every entry from the period the brag doc covers. Pull each candidate accomplishment into a working list — don't filter yet. When the list is done, sort by impact (not by chronology) and pick the top three. Everything else either fits a category bucket or gets cut. The hardest part is cutting; aim for one page at first, two pages only if every line earns it.

Common mistakes

• Writing it in one all-nighter from memory the day before review season — you will forget the most important wins.
• Including every PR you opened — the brag doc is curated, not exhaustive.
• Vague verbs like 'helped with' or 'contributed to' — name the artifact and the outcome instead.
• Numbers without baselines — '40% faster' is meaningless without 'from 2.1s to 1.3s'.
• Skipping the quotes section because it feels self-promotional — it is the section managers trust most.
• Using the same brag doc for an internal promotion and an external recruiter — the audiences need different framing.

How often to update it

Once a month is the right cadence. First Friday is a useful default — it's far enough from end-of-month chaos and close enough to remember the previous four weeks. Spend 15 minutes pulling the month's wins from your journal into the doc. Twice a year (before each review cycle), spend a longer block re-sorting and rewriting the top-three section.

Prefer to keep the running record in an app? You can keep your brag document in Bloomly while saving dated work entries. Typed journaling is free; generated reports require Pro.

Keep the record while the details are fresh. Before your review, choose the entries that best show your contribution and check each claim against its source. If you want an app for the running record, compare the work-accomplishment apps linked above and choose the workflow you will actually use.