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 records what you worked on, what changed, and how you contributed. Include enough detail for your manager to use it in your review: dates, results, feedback, and links to the work.
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 brings your achievements from a specific period into one place. It can cover projects, results, mentoring, feedback, and things you learned. Your manager can refer to it when writing your review or making a case for a raise or promotion.
If the word "brag" feels awkward, keep the writing factual. Describe your part in the work, give credit to collaborators, and include results you can support.
Why keep one throughout the year?
It’s easier to record an achievement soon after it happens. 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."
- Spend less time searching old messages before a review.
- Give your manager language and evidence they can reuse when advocating for you.
Try BragJournal
Give yourself less to remember at review time.
Save your achievements and useful emails in BragJournal. Add your review goals, then generate a Brag Document when you’re ready to write your review.
Sections to include in a brag document
Start with the sections below and adapt them to your role and review process.
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
Summarize your main responsibilities and two or three results. A reader should be able to understand the period without reading every project description.
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
Include decisions you helped the team make, disagreements you resolved, and work you coordinated across teams. Explain what happened as a result.
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
End with what you learned, what you’d do differently, and the responsibilities you want to take on next.
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 redesigned trial onboarding, fixed recurring reporting failures, and mentored two engineers as they led their first projects. The examples below cover the results and my role in each.
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 said the trial progress view helped them identify where customers were getting stuck. My manager highlighted the reporting fix because it removed a recurring problem before renewal discussions.
Growth and next scope
I got better at agreeing on requirements with other teams before starting implementation. Next half, I’d like to lead a project that connects product analytics with 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 main responsibilities, results, and what you learned.
## 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 to your work:
## Growth and next goals
- Skills developed:
- Lessons learned:
- Responsibilities you want to take on next: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 summarizes your career for potential employers. A brag document goes into more detail about a particular period: what you did, why it mattered, and what supports your account.
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.
Try BragJournal
Give yourself less to remember at review time.
Save your achievements and useful emails in BragJournal. Add your review goals, then generate a Brag Document when you’re ready to write your review.