June 2026 / 12 min read
How to Write a Brag Document
A practical guide to writing a brag document, with examples, sections to include, common mistakes to avoid, and a downloadable template you can adapt for your next review or promotion conversation.
A brag document is not a list of compliments. It is a structured record of the work you did, the outcomes you influenced, and the proof that helps someone else understand your impact. The best ones are specific enough for a manager to reuse during a review and honest enough that they still sound like you.
People often start writing a brag doc the night before a performance review. That is when the hard part shows up: the work was real, but the details are gone. The launch numbers live in a dashboard, the praise is buried in email, and the leadership work felt too ordinary to write down at the time.
What is a brag document?
A Brag Document is a review-ready career artifact that explains your impact over a specific period. It usually includes projects, metrics, leadership, collaboration, mentoring, feedback, and growth. It gives your manager evidence they can use when they write a review, calibrate performance, or advocate for a raise or promotion.
The word "brag" can feel awkward, but the document is not about inflating your work. It is about making useful evidence visible. A strong brag document says: here is what I worked on, here is why it mattered, here is how we know, and here is what I am ready to do next.
Why high performers keep one year-round
High performers keep a brag document year-round because impact is easier to capture when it is fresh. A shipped project may feel obvious this week and impossible to reconstruct six months later. The same is true for customer praise, incidents handled quietly, mentoring conversations, and process improvements that prevent future problems.
A year-round habit helps you:
- Remember the work that did not turn into a launch announcement.
- Connect projects to metrics, company goals, and team outcomes.
- Notice leadership and mentoring contributions before they fade into "just helping."
- Prepare for reviews without a stressful archeology project.
- Give your manager language and evidence they can reuse when advocating for you.
Or automate it with BragJournal.ai
Keep the evidence all year, then generate a review-ready Brag Document.
BragJournal helps you capture achievements, connect work to KPIs, save proof from email, and turn the pattern into a polished draft when review season arrives.
Sections to include in a brag document
Your exact sections should match your role and review process, but most strong brag documents include the same core ingredients.
1. Review period and goal
Start with the timeframe, your role, and what the document is for. A self-review, promotion case, manager update, and skip-level packet may use the same evidence but different framing.
2. Executive summary
Write a short summary of your biggest themes. This should be scannable in under a minute: the scope you owned, the outcomes you created, the leadership you showed, and the next level of work you are ready for.
3. Projects and shipped work
For each project, explain the situation, your role, what changed, and what evidence shows it mattered. Do not stop at "built the new dashboard." Say who used it, what decision it enabled, what metric moved, or what risk it reduced.
4. Impact and metrics
Metrics make your document easier to trust. Use revenue, adoption, quality, latency, conversion, support volume, customer retention, cost savings, cycle time, or reliability measures when they are available. When exact metrics are not available, use credible evidence: customer quotes, stakeholder feedback, before-and-after examples, shipped artifacts, or decisions influenced.
5. Leadership and collaboration
Leadership is not limited to people management. Include decisions you clarified, cross-functional alignment you created, ambiguity you reduced, meetings you made unnecessary, and trade-offs you helped the team make.
6. Mentoring and team contribution
If you reviewed designs, onboarded teammates, improved docs, raised engineering standards, helped someone debug a hard problem, or created a repeatable process, include it. Mentoring is often invisible unless you name the outcome.
7. Growth and next goals
A brag document should not pretend everything was flawless. End with skills you developed, lessons learned, and the scope you want to take on next. This helps the document read as mature, not self-congratulatory.
Common brag document mistakes
- Writing only tasks. "Implemented API endpoint" is less useful than the customer, revenue, quality, or workflow outcome the work supported.
- Saving it for review week. Waiting until the end guarantees missing details and weaker evidence.
- Ignoring leadership work. Alignment, mentoring, quality improvements, and decision-making often explain why a person is ready for larger scope.
- Overclaiming. Be clear about your role and give credit to collaborators. Specific ownership is stronger than hero language.
- Forgetting the audience. Your manager needs a document they can scan, trust, and reuse. Structure matters.
Example brag document
Here is a fictional example for a senior product engineer. The shape matters more than the exact role: summary first, then specific evidence, then leadership and growth.
Example Brag Document
Senior Product Engineer / H1 2026
This half, I focused on improving enterprise activation, stabilizing customer-facing reporting, and raising the quality bar for project leadership on the team. My work combined product execution, reliability improvements, cross-functional coordination, and mentoring two engineers into larger ownership.
Reduced onboarding drop-off in the enterprise trial flow
Led the engineering work for a trial onboarding redesign across product, design, data, and customer success. I shipped the event model, rebuilt the checklist experience, and added account-level progress tracking so sales and success teams could intervene before a trial stalled.
Impact: Activation rose from 41% to 58% over two months, time to first successful workspace setup dropped from 3.8 days to 1.9 days, and the sales team reused the progress view in 37 expansion conversations.
Stabilized a noisy reporting workflow before renewal season
Owned a reliability push for the weekly executive reporting job after several large customers reported missing or delayed exports. I traced the failures to a queue retry edge case, added idempotency around report generation, and wrote the runbook used by support.
Impact: Reduced failed reports by 92%, cut support escalations from 14 per month to 2, and helped protect four at-risk enterprise renewals worth $420K in ARR.
Raised engineering quality through mentoring and review habits
Mentored two mid-level engineers through their first project leads, created review checklists for migrations and background jobs, and started a weekly architecture review for high-risk changes.
Impact: Both engineers led customer-facing releases by the end of the half, code review turnaround improved from 26 hours to 14 hours, and the migration checklist caught three launch-blocking issues before production.
Feedback and proof
Customer success shared that the trial progress view changed renewal-risk conversations from reactive to specific. My manager noted that the reporting reliability work was "quiet, high-leverage ownership at the exact right time."
Growth and next scope
I improved at creating alignment before implementation and want to take on a broader platform initiative next half, especially work that spans product analytics and customer operations.
Downloadable brag document template
Use this template as a starting structure. Keep the sections that match your role, remove the ones that do not, and add evidence as you go.
# Brag Document Template
## Review period
- Timeframe:
- Role:
- Manager:
- Promotion or review goal:
## Summary
Write 3-5 sentences about your biggest themes, scope, and impact.
## Projects and outcomes
### Project name
- Situation:
- Your role:
- What you shipped:
- Metrics or evidence:
- Business or team impact:
## Leadership and collaboration
- Decisions you influenced:
- Cross-functional work:
- Process improvements:
## Mentoring and team impact
- People you supported:
- Knowledge you shared:
- Hiring, onboarding, or review contributions:
## Feedback and proof
- Stakeholder praise:
- Customer quotes:
- Links or artifacts:
## Growth and next goals
- Skills developed:
- Lessons learned:
- Next scope you are ready for:FAQ
How long should a brag document be?
For most performance reviews, aim for two to four focused pages. A promotion packet may need more detail, but the strongest brag documents still lead with a concise summary and evidence-backed highlights.
What is the difference between a brag document and a resume?
A resume is a public career summary. A brag document is a private, review-ready artifact that explains what happened during a specific period, why it mattered, and what evidence supports it.
How often should I update my brag document?
Update your source notes year-round, ideally weekly or after meaningful milestones. Turn those notes into a polished brag document when a review, promotion, or manager conversation is coming up.
Can I use a brag document for promotion?
Yes. A promotion-focused brag document should show scope, judgment, leadership, repeatable impact, and evidence that you are already operating at the next level.
Or automate it with BragJournal.ai
Keep the evidence all year, then generate a review-ready Brag Document.
BragJournal helps you capture achievements, connect work to KPIs, save proof from email, and turn the pattern into a polished draft when review season arrives.