What a brag document is
A brag document is a private, running list of what you have done at work: projects you finished, problems you solved, feedback you received, things you learned and people you helped. The name is a bit tongue-in-cheek. It is not meant to be shown off, and it does not need to sound boastful. It is a factual record that you keep for yourself, and from which you can later pull material for performance reviews, promotion discussions, resume updates or conversations about your role.
The idea is simple: your memory is not a reliable archive. By review time, most people recall the last month or two clearly and forget the early part of the year, including work they were proud of at the time.
Why keep one
- Reviews become easier. Instead of staring at a blank form, you start with a list.
- You notice progress. Seeing a year of notes can be encouraging, especially when daily work feels routine.
- You can describe impact accurately. Writing details while fresh preserves numbers, dates and names.
- It helps your manager. Many managers supervise several people and cannot track every contribution. A clear summary gives them accurate material to work from, and it supports workplace visibility without any need for self-promotion.
- It supports other documents. The same notes can feed a resume, a professional bio or the details in your resume bullets.
Keep expectations realistic. A good record helps you communicate your work, but it does not guarantee a particular rating, raise or promotion, which depend on many things outside your control.
What to record
Aim for items that were meaningful, not a log of every task. Useful categories include:
- Projects and deliverables. What you worked on, your role, and what came of it.
- Results. Anything measurable, such as time saved, errors reduced, customers served or deadlines met. Use only numbers you can support.
- Problems solved. Situations where you fixed something, improved a process or prevented a problem.
- Feedback. Positive comments from colleagues, customers or managers, ideally with the date and who gave it. Notes of constructive feedback and what you changed are valuable too.
- Skills learned. Courses, new tools, certifications and stretch assignments.
- Collaboration and support. Mentoring someone, helping a team, or sharing knowledge.
- Leadership and initiative. Things you started, organized or volunteered for.
- Setbacks and lessons. Honest notes on what did not go well and what you learned. These show growth and help you prepare for questions.
How to write each entry
A short, consistent format keeps entries useful. For each item, try to note:
- What happened, in a sentence.
- Your part, stated plainly.
- The result or impact, with evidence where you have it.
- Who else was involved, so you can give credit accurately.
- The date, so you can place it in the review period.
Example, hypothetical:
March: Rewrote the onboarding checklist for new support staff after noticing repeated questions. Worked with two senior team members on content. New hires reported in their first-week check-ins that they had fewer questions about tools. Manager mentioned it in the team meeting.
Notice that the entry gives credit to others, avoids inflated claims and sticks to what happened. It leaves out phrases like “revolutionized” or “single-handedly.” Staying accurate protects you if someone asks follow-up questions, and it avoids overstated claims.
Where to keep it
The best format is the one you will actually use. Options include a simple text file, a note in your phone, a spreadsheet, a page in a notebook or a private document with a heading for each month. Whatever you choose, keep it somewhere easy to open in under a minute.
Two cautions about privacy and confidentiality:
- Store it personally and securely. A document on a work system may belong to your employer or be accessible to others. Consider what you would be comfortable having someone read.
- Avoid sensitive details. Do not copy confidential customer information, internal financial data or private messages. Describe the work in general terms. This matters especially if you later reuse material in a portfolio, where respecting portfolio confidentiality is part of professional conduct.
Make it a habit
The trick is to make updates quick and regular.
- Set a recurring reminder. Ten minutes at the end of each week, or fifteen at the end of each month, is enough.
- Capture things as they happen. When you get a nice email or finish something notable, paste a line into the document immediately.
- Save evidence. Keep screenshots or copies of positive feedback where company policy permits.
- Review it quarterly. A short look every few months shows patterns and helps you plan.
Missing a week is no problem. Add what you remember and carry on.
Turning it into a review
When review time arrives, the document becomes raw material, not a final submission.
- Read through the whole period. Mark the most significant items.
- Group them by theme, such as delivery, collaboration and growth, or whichever categories your employer uses.
- Select the strongest examples. Quality matters more than quantity.
- Write concisely. Use plain language and aim for brief, clear sentences, following the same principles as concise writing.
- Match the employer’s criteria. If your company has competencies or goals, link examples to them.
- Be balanced. Mention areas where you want to improve. This tends to read as self-aware, not weak.
- Check facts. Confirm numbers and dates before submitting.
You can also use the document to prepare for the conversation itself. Practicing a few short stories with a clear situation, action and result makes you more comfortable talking about your work. The STAR method is a common structure for this.