A brag document is a running record of what you have actually achieved at work, written down as it happens so you never have to reconstruct it from memory under pressure. It solves a specific problem: managers forget, you forget, and performance reviews reward whoever shows up with evidence. Start one today with even three entries and you already have more to work with than most people bring to their next review.
TL;DR:
- A brag document should be updated regularly with specific, evidence-backed entries to provide reliable evidence during performance reviews and interviews.
- Using a simple, consistent template with fields like date, situation, actions, results, and evidence helps maintain clarity and ease of updates.
- Writing entries close to when achievements occur and reviewing them biweekly ensures information stays fresh and comprehensive.
- Turning raw entries into STAR stories or CV bullets involves selecting the most relevant accomplishments and practicing concise storytelling.
- Sharing should be limited to trusted individuals, and the document remains private unless explicitly requested for a specific purpose.
Table of Contents
- What is a brag document, and how is it different from a portfolio?
- A practical template you can copy: exact fields for every entry
- How to keep it up: cadence, tools and simple capture workflows
- Turning entries into STAR answers, CV bullets and promotion cases
- Sharing, privacy and when to supply a work sample instead
- Prompts and two ready-to-copy example entries
- Ruairi's coaching perspective: why this habit builds confidence
- What the research actually supports
- MT Coaching: turning your brag document into a promotion case
- Quick list of templates and guidance to consult
- Sources
- FAQ
What is a brag document, and how is it different from a portfolio?
A brag document (sometimes called a brag book, hype doc, or professional brag sheet) is simply a personal log where you record what you did, when, and what changed because of it. The idea has been floating around technology and recruitment circles for years, but it got a proper push into the mainstream when software engineer Julia Evans wrote about the habit, arguing that most good work goes unnoticed unless someone writes it down while it is fresh.
It is easy to confuse this with a portfolio or a set of work samples, but they serve different purposes. A portfolio or work sample is usually something an employer asks for, built or selected to demonstrate a specific skill under scrutiny. A brag document is yours alone. Nobody vets it, nobody grades it, and you control what goes in.
The real value sits in a problem every working professional runs into: your manager cannot remember what you did in March by the time your annual review comes round in November. Neither, honestly, can you. A brag document acts as both a memory aid and a source of evidence, and over time it starts revealing patterns in your own work that you would otherwise miss entirely, such as a tendency to be the person who unblocks stuck projects rather than the one who starts them.
A practical template you can copy: exact fields for every entry
You do not need anything fancy to start. A single document with consistent fields beats a beautifully designed system you abandon after two weeks. The format recommended by Volio's brag document guidance covers the essentials well, and it is the structure worth adopting:
- Date or period — when it happened, even roughly ("Q2" is fine if you can't recall the exact week)
- Situation or goal — what problem you were solving or what was expected of you
- What you did — your specific action, not the team's action
- Result or impact — what changed because of it, ideally with a number
- Evidence or link — a message, ticket, dashboard, or document that backs it up
- People affected — who noticed, benefited, or relied on the outcome
- Skills shown — what this entry demonstrates (negotiation, debugging, mentoring, whatever fits)
- What you learned — a line on what you'd do differently or what stuck with you
When you have a hard metric, use it. Write the qualitative version instead: "Talked a nervous junior colleague through their first client call, which went well and led to a repeat booking." That is still evidence.
For anything sensitive, a short entry works better than a detailed one. Write "Resolved a client escalation involving a data issue, avoided contract loss" rather than naming the client or repeating confidential details. You can always add colour later in a private conversation; you cannot un-write something that should never have been on paper.
How to keep it up: cadence, tools and simple capture workflows
The biggest reason brag documents fail is not lack of interest. It is that people set one up with enthusiasm, then let three months pass without a single entry. A workable cadence beats an ambitious one.
- Capture in the moment. When something noteworthy happens, jot one line into a notes app, a Slack message to yourself, or a sticky note. Do not wait for the "proper" write up.
- Tidy it fortnightly. Every two weeks, open the full document and turn those scraps into proper entries using your template. Volio's guidance suggests reviewing on this rhythm specifically because monthly gaps let too much detail evaporate.
- Roll up after big projects and annually. Once a project wraps, write a summary entry. Once a year, read the whole document and pull out the three or four entries that best represent your growth.
For the tool itself, a single running document (Google Docs, Word, or a plain notes app) works perfectly well for most people. If you want more structure, Notion's brag document template gives you a ready-made table with fields for accomplishments, dates, and evidence links, which suits anyone who finds a blank page intimidating. A slide deck is worth building only when you are actively preparing for interviews or a promotion panel and need a visual version to walk someone through.
Turning entries into STAR answers, CV bullets and promotion cases
Raw entries are useful, but they are not yet interview-ready or CV-ready. Turning one into something usable takes a few deliberate steps.
- Pick a strong entry that clearly shows a skill relevant to the conversation you're preparing for.
- Identify the STAR elements already sitting in your fields: your "situation or goal" becomes Situation and Task, "what you did" becomes Action, and "result" becomes Result.
- Draft a 30 to 60 second narrative by stringing those elements into two or three spoken sentences, then practise saying it aloud until it sounds natural rather than rehearsed.
- Write a CV bullet from the same entry by leading with the result: "Cut onboarding time for new starters from six weeks to three by rebuilding the training materials," rather than starting with the task.
- Choose deliberately for the audience. A promotion case wants entries that show scope and growth over time; an interview wants entries that map directly onto the job description in front of you.
Recruiter reporting backs this up directly: categorising your entries into groups like "what I'm good at," "what I deliver," and "what I'm most proud of" makes it far faster to pull the right story for the right question, and CNBC's coverage of brag doc practice notes it often produces sharper interview narratives than a cover letter ever does.
Pro Tip: Keep a "greatest hits" tab at the top of your document with your five strongest entries already converted into STAR format. When an interview lands with two days' notice, you're not starting from scratch.
If you want a deeper look at turning raw achievements into CV language without sounding boastful, Mtcoaching has covered the reframing process in more detail in a guide to promoting yourself on your résumé.
Sharing, privacy and when to supply a work sample instead
Your brag document is private by default, and it should stay that way unless you decide otherwise. Sharing it selectively is smart. Handing over the whole thing unfiltered rarely is.
- Share full entries only with people you trust completely, such as a mentor or coach helping you prepare.
- Share redacted excerpts (client names removed, figures rounded) when a manager or interviewer asks for specific examples.
- Say no, politely, if someone outside a legitimate hiring or review process asks to see the whole document.
A work sample is a different animal entirely and should never be confused with your personal log. The Management Center's guidance for employers is clear that work-sample requests should come with a stated time limit, ideally under two hours, and that employers should default to asking for something you have already produced rather than commissioning new unpaid work. If a request feels excessive, it is fair to ask for that time limit explicitly or offer an existing piece of work instead.
Prompts and two ready-to-copy example entries
Staring at a blank document is the fastest way to abandon this habit before it starts. Use these prompts to get moving:
- What did I fix this week that someone else would have struggled with?
- What number moved because of something I did?
- Who did I help, mentor, or unblock recently?
- What process did I improve, even slightly?
- What feedback did I get, good or hard to hear?
- What did I do that nobody asked me to do?
- What decision did I make that others relied on?
- What did I learn that changed how I work now?
- What did I do to make a colleague's job easier?
- What conflict did I help resolve?
- What did I build, write, or ship this month?
- What would I be proud to tell a future employer about?
Metric-driven example: March 2026 — Situation: Support tickets were taking an average of three days to resolve. Action: Rebuilt the triage process and wrote a new escalation guide. Result: Average resolution time dropped to one day. Evidence: Support dashboard export. Learned: Small process fixes often beat adding headcount.
Fuzzy-impact example: April 2026 — Situation: New team member was overwhelmed in her first month. Action: Set up weekly informal check-ins and answered her questions without judgement. Result: She told our manager directly that the check-ins helped her stay. Evidence: Manager mentioned it in my one-to-one. Learned: Mentoring rarely shows up in metrics, but it shows up in retention.
Keep entries short. One sentence per field is plenty; you can always expand later when you're preparing something specific.
Ruairi's coaching perspective: why this habit builds confidence
In coaching sessions, I often see the same pattern: talented people who genuinely cannot recall their own wins when asked directly. That is not modesty. It is memory, and it is fixable with a document rather than willpower.
When I work through a brag document with a client, we usually pick two entries and convert them into STAR answers together in the same session, then draft one CV bullet from a third. Doing it live, rather than as homework, tends to be where the confidence shift actually happens. Clients stop saying "I don't really have anything impressive" and start saying "actually, here's what I did." That shift matters more for interview and review performance than any amount of coached delivery technique.
If you want more on this, the career resources on Mtcoaching's site cover related exercises for building a stronger professional narrative.
What the research actually supports
The evidence here points to something fairly unglamorous: a brag document works because it is boring and consistent, not because it is clever. The template matters less than the habit of writing entries down close to when they happen, since memory decays fast and most of us underestimate how much we forget within a fortnight.
Where conventional advice tends to go wrong is treating this as an interview-prep exercise you do the week before a big conversation. That is too late. The document only earns its keep when it has months of unglamorous, regularly logged entries behind it, including the fuzzy ones like mentoring and culture-building that never show up in a KPI dashboard but shape how colleagues actually experience working with you.
If you take one thing from this, prioritise consistency over structure. A messy document updated fortnightly beats a beautifully designed one that gathers dust. Start today with three entries from the last month. You will have more evidence than you think.
— Ruairi
MT Coaching: turning your brag document into a promotion case
Mtcoaching helps you do the part most people struggle with alone: translating a private log into a confident, evidence-backed story you can actually say out loud in a review or interview. That is the gap between having a good document and having a good outcome, and it is exactly where our CV and LinkedIn optimisation and interview preparation services come in.
A one-to-one coaching session can take your rawest entries and turn them into STAR answers, sharpen a handful into standout CV bullets, and help you choose exactly which wins deserve airtime in a promotion conversation versus an interview. Ruairi's approach pairs that practical rewriting work with the emotional side too, so you walk in sounding like yourself, not a rehearsed script. If you have a document sitting half-finished on your laptop right now, that is the perfect starting point. Book a session with Mtcoaching and bring it along.
Quick list of templates and guidance to consult
If you want a ready-made structure rather than building your own, three sources are worth bookmarking. Notion's brag document template gives you a table-based layout ready to duplicate. Volio's brag document template offers the field structure and fortnightly review cadence covered above. For anyone on the hiring side, The Management Center's guidance on work samples sets out fair time limits and practice for requesting samples ethically.
Sources
- Notion: Brag document / highlight tracker template
- Volio: Brag document template
- The Management Center: How to ask candidates for work samples
- CNBC: How a 'brag doc' can help you ace interviews and land a job, says recruiter
FAQ
Is there a template for a brag document?
Yes. Notion offers a free downloadable template built specifically for tracking accomplishments, and Volio publishes a field-by-field template covering situation, action, result, evidence, and lessons learned. Either works as a starting point you can adapt to your own role.
What is a brag sheet example?
A typical entry records the date, the situation you faced, what you personally did, the measurable or observed result, and who noticed. For example: "March 2026, rebuilt the support triage process, cut resolution time from three days to one, confirmed via the support dashboard."
What is another name for a brag sheet?
It goes by several names depending on the context, including brag document, brag book, hype doc, or professional brag sheet. Some recruiters also call it a personal achievement document or career highlight document, though the core idea stays the same across all of them.
What does "brag book" mean?
A brag book traditionally refers to a physical or digital folder of supporting evidence, certificates, letters, and transcripts, often assembled for job hunting or sales roles. Military recommends organising it in reverse chronological order and rehearsing with it before interviews, which makes it closer to a portfolio than the ongoing personal log a brag document usually describes.