The professional achievement summary that gets you promoted. Free template plus real examples you can adapt.
What is a Brag Document?
A brag document (also called a "hype doc" or "achievement journal") is a running record of your work accomplishments. It's the single most underrated career tool.
Why you need one:
- Performance reviews become effortless
- Salary negotiations get stronger
- Job interviews improve dramatically
- Imposter syndrome fades (you have proof)
Most professionals forget 80% of their achievements within 3 months. A brag document captures everything before you forget.
π Brag Document Template
Copy everything below this line into a new Notion page:
[Your Name]'s Brag Document
Last Updated: [Date]
Period Covered: [Date Range]
π Quick Stats
| Metric | Value |
|---|---|
| Total Wins Logged | XX |
| Estimated Value Delivered | $XX,XXX |
| Period | Q1-Q4 2025 |
π Top Accomplishments
Your 3-5 biggest wins with full context and metrics.
1. [Achievement Title]
- What I did: [Specific action with details]
- Impact: [Quantified result]
- Skills demonstrated: [Relevant competencies]
- Recognition: [Any feedback or awards received]
2. [Achievement Title]
- What I did: [Specific action with details]
- Impact: [Quantified result]
- Skills demonstrated: [Relevant competencies]
- Recognition: [Any feedback or awards received]
3. [Achievement Title]
- What I did: [Specific action with details]
- Impact: [Quantified result]
- Skills demonstrated: [Relevant competencies]
- Recognition: [Any feedback or awards received]
π Projects Delivered
| Project | My Role | Outcome | Date |
|---|---|---|---|
| [Project Name] | [Your role] | [Impact/result] | [Month] |
| [Project Name] | [Your role] | [Impact/result] | [Month] |
| [Project Name] | [Your role] | [Impact/result] | [Month] |
π‘ Process Improvements
Ways you made work better for yourself or others.
-
-
-
π Learning & Growth
Skills developed, certifications earned, knowledge gained.
- [Skill/Certification]: [How you developed it]
- [Skill/Certification]: [How you developed it]
- [Skill/Certification]: [How you developed it]
π₯ Team Contributions
How you helped others succeed.
- Mentorship: [Who you helped, how they grew]
- Collaboration: [Cross-team work, partnerships built]
- Culture: [Ways you improved the team environment]
π¬ Feedback Received
Quotes and recognition from others.
"[Positive feedback quote]"
β [Person], [Role] "[Positive feedback quote]"
β [Person], [Role]
π― Goals Progress
| Goal | Status | Notes |
|---|---|---|
| [Goal 1] | β Complete | [Outcome] |
| [Goal 2] | π In Progress | [Status] |
| [Goal 3] | βΈοΈ Paused | [Reason] |
π Running Log
Quick capture of wins as they happen. Transfer to sections above periodically.
- [Date]: [Quick win note]
- [Date]: [Quick win note]
- [Date]: [Quick win note]
Real Example: Software Engineer
Sarah Chen's Brag Document
Last Updated: January 2025
Period Covered: 2024
π Quick Stats
| Metric | Value |
|---|---|
| Total Wins Logged | 47 |
| Estimated Value Delivered | $156,000 |
| Period | 2024 |
π Top Accomplishments
1. Led Payment System Migration
- What I did: Architected and led migration from legacy payment provider to Stripe, coordinating with 3 teams over 4 months
- Impact: Zero downtime during migration affecting $2M monthly transactions; reduced payment processing costs by 15% ($36K/year)
- Skills demonstrated: Technical leadership, cross-team coordination, system design
- Recognition: Shoutout in company all-hands; selected for Tech Lead track
2. Automated Deployment Pipeline
- What I did: Built CI/CD pipeline from scratch using GitHub Actions, including automated testing and staged rollouts
- Impact: Reduced deployment time from 2 hours to 15 minutes; enabled daily deployments (up from weekly)
- Skills demonstrated: DevOps, automation, process improvement
- Recognition: Pipeline adopted as template by 3 other teams
3. Resolved Critical Performance Issue
- What I did: Identified and fixed N+1 query problem causing 10-second page loads for enterprise customers
- Impact: Page load reduced to 800ms; prevented potential loss of $500K enterprise contract
- Skills demonstrated: Performance optimization, debugging, customer focus
- Recognition: VP Engineering mentioned in quarterly review
π Projects Delivered
| Project | My Role | Outcome | Date |
|---|---|---|---|
| Payment Migration | Tech Lead | $36K/year savings, zero downtime | Q2 |
| CI/CD Pipeline | Solo | 87% faster deployments | Q1 |
| Search Optimization | Primary IC | 3x faster search | Q3 |
| API Documentation | Contributor | 60% reduction in support tickets | Q4 |
π‘ Process Improvements
- Created PR template: Reduced review time by 30%, improved consistency
- Established on-call runbook: New engineers can handle incidents independently
- Introduced feature flags: Enabled safer deployments, 5 incidents prevented
π Learning & Growth
- AWS Solutions Architect certification: January 2024
- Internal Tech Lead development program: Completed Q3
- Self-taught Rust: Built high-performance data processing module
π₯ Team Contributions
- Mentorship: Guided 2 junior developers; Jake promoted to mid-level, Sarah leading her first project
- Collaboration: Partnered with Security team on SOC 2 compliance
- Culture: Started "Debugging Lunch" series (8 sessions, avg 15 attendees)
π¬ Feedback Received
"The payment migration was the smoothest major change we've had. Your documentation and communication were exceptional."
β Dana, Engineering Manager "Thanks for taking time to explain the caching architecture. That session unblocked me for the whole quarter."
β Jake, Junior Developer
How to Use Your Brag Document
For Performance Reviews
- Filter entries by review period
- Select top 5-10 accomplishments
- Group by competency (delivery, leadership, growth)
- Calculate total value delivered
- Write narrative connecting achievements to goals
For Salary Negotiations
- Calculate total dollar value created
- Compare to your salary (show ROI)
- Highlight accomplishments above your level
- Prepare specific examples for each skill area
- Bring printed one-pager to the meeting
For Job Interviews
- Select 8-10 stories covering different competencies
- Practice STAR format for each
- Have metrics ready for all achievements
- Prepare failure stories too (shows growth)
- Customize emphasis based on job requirements
For Fighting Imposter Syndrome
- Read through when confidence is low
- Add small wins too (they compound)
- Review monthly to see growth patterns
- Share with trusted mentor for perspective
- Remember: you have PROOF
When to Update
Real-Time (Best)
- Log wins immediately
- Takes 30 seconds
- Nothing forgotten
Weekly Review (Good)
- Set Friday reminder
- Review the week's work
- Log anything significant
Monthly Review (Minimum)
- Better than nothing
- Risk of forgetting details
Quarterly Review
- Consolidate and organize
- Calculate value delivered
- Identify gaps and growth areas
Tips for Writing Strong Entries
Use Action Verbs
β "Was responsible for the project"
β "Led the project"
Add Numbers
β "Improved performance"
β "Improved response time from 4s to 400ms"
Include Impact
β "Built new feature"
β "Built recommendation engine that increased user engagement by 40%"
Be Specific
β "Helped with hiring"
β "Conducted 15 technical interviews, with 5 candidates receiving offers"
Common Mistakes to Avoid
Mistake 1: Only Logging Big Wins
Small wins add up. "Fixed a bug" becomes "Resolved 50 customer-impacting bugs this quarter."
Mistake 2: Being Too Vague
"Improved the product" is useless. What specifically? How much? For whom?
Mistake 3: Waiting Too Long
Memory fades fast. Don't try to reconstruct 6 months of work during review season.
Mistake 4: Forgetting Soft Skills
Leadership, mentorship, collaboration matter. Document them.
Mistake 5: Not Tracking Feedback
Positive feedback fades from memory. Screenshot it, save it, add it.
Brag Document vs. Resume
| Brag Document | Resume |
|---|---|
| Comprehensive (everything) | Curated (best achievements) |
| For your use | For employers |
| Running document | Snapshot in time |
| Includes context and process | Just results |
| Raw material | Polished output |
Your brag document feeds your resume.
FAQ
Q: Isn't this arrogant?
Documenting your work isn't arrogantβit's responsible. Your manager can't remember everything you did.
Q: Where should I store this?
Personal document, not company systems. Use Notion, Google Docs, or a dedicated app. Keep it when you change jobs.
Q: How detailed should entries be?
Detailed enough to jog your memory 6 months later. A few sentences per entry.
Q: Should I share this with my manager?
Some people do! A well-maintained brag document makes your manager's job easier at review time.
Q: What if I'm new and don't have accomplishments yet?
Start now. Log your onboarding, first contributions, things you learned. The entries will grow.
Your Next Step
- Copy the template above into Notion
- Spend 15 minutes filling in what you remember from the past month
- Set a weekly reminder to update it
Your future self will thank you.
Related Articles:
- How to Track Work Accomplishments
- How to Calculate the Dollar Value of Your Work
- STAR Method Examples
- Performance Review Self-Assessment Guide
<!-- FAQ Section -->
<!-- Related Articles -->
<section class="related-section">
<h2>Related Articles</h2>
<div class="related-grid">
<a href="/blog/templates/one-on-one-meeting-template/" class="related-card">
<div class="related-category">Templates</div>
<h3>1:1 Meeting Template for Employees: How to Prepare and Get What You Need</h3>
</a>
<a href="/blog/templates/salary-negotiation-scripts/" class="related-card">
<div class="related-category">Templates</div>
<h3>Salary Negotiation Scripts: 15 Email Templates That Actually Work</h3>
</a>
<a href="/blog/templates/weekly-win-tracker/" class="related-card">
<div class="related-category">Templates</div>
<h3>Weekly Win Tracker: The Simple System to Never Forget Your Accomplishments</h3>
</a>
</div>
</section>
<!-- CTA -->
Ready to Track Your Wins?
Free, no account, no sign-up. Available on the App Store now.
Download on iOS Free, no account needed