A brag document is exactly what it sounds like: a running, dated list of the things you did well. Not a resume, not a performance self-review - just an honest log you update as things happen, so that when you need to summarize your work for a review, an interview, or a job application, you're pulling from a real record instead of guessing what you did eight months ago.
Why waiting until review season fails
Most people try to write their self-review or update their resume from memory, in one sitting, right before it's due. The problem isn't effort, it's that memory is a bad archive. The project you're proudest of from March is a vague shape by November; the one specific metric that made a result impressive has usually blurred into "helped improve performance." A brag document fixes this by moving the recording closer to the moment the work happened, when the details are still sharp.
A simple structure that works
- Date. When it happened, even roughly.
- What you did. One or two sentences, specific: the project, the action, your actual role in it.
- The result. A number if you have one - time saved, revenue, users, error rate, whatever is real and relevant. If there's no clean metric, describe the outcome concretely instead of skipping it.
- Any feedback you received. A quote from a manager, client, or teammate, verbatim if you can capture it. This is gold for both reviews and reference conversations later.
Keep entries short. The goal is a complete, dated record you can scan quickly, not a polished narrative - you'll do the polishing later, once, when you actually need it for something specific.
What belongs in it (and what doesn't)
Include anything that shows you did something well: a project you shipped, a process you improved, a problem you caught before it became bigger, a piece of unsolicited positive feedback, a metric that moved because of something you did. You don't need every entry to be dramatic - a steady stream of smaller, real wins is more useful later than a handful of inflated ones. Leave out routine tasks with no notable outcome; a brag document that logs everything becomes as hard to scan as no document at all. The filter is simple: would this be worth mentioning in a review or an interview? If yes, it goes in.
What it feeds
A maintained brag document makes three different tasks dramatically easier: writing a self-review with real specifics instead of vague self-praise, building resume bullets that use the strong-verb-specific-action-measurable-result formula because the raw material is already there, and answering behavioral interview questions with the STAR method without scrambling to remember a good example under pressure. All three draw from the same well - the only real cost is keeping the well filled.
Making it a habit
The document only works if updating it is easier than not updating it. A recurring weekly reminder beats trying to remember on your own, and logging right after something notable happens - a shipped feature, a compliment from a client, a problem you solved under pressure - beats batching it up for later. The friction that kills most brag documents isn't the writing, it's forgetting the document exists in the middle of a busy week.
How Prefolio helps
Prefolio was built around this exact pattern for students and early-career applicants: log what you did and how it felt close to the moment, with recurring reminders so entries don't lapse, then let AI turn the accumulated record into polished material - resume bullets, activity descriptions, interview stories - when you actually need it. The same discipline that makes a strong AMCAS application or grad school statement also makes a strong brag document; it's the same habit applied to a different deadline.