A brag document is a running, personal record of work completed, problems solved, and feedback received over time. Many people keep one separately from any employer system, since performance platforms and file access typically end when employment does. This guide covers what usually goes into a brag document, how often people tend to update it, and how it can be organized so it is useful when a review or promotion case comes around. This guide is general information, not legal advice about your situation.
What is a brag document?
A brag document is a personal, ongoing log of work accomplishments, decisions, and feedback that an individual keeps outside of any formal employer review system. It typically exists as a simple file or note, organized by date, and many people share a version of it with their manager before a review, so the manager has specifics to work from. The purpose is usually to capture detail while it is fresh, since specifics that feel obvious in the moment often become hard to reconstruct months later during a formal review cycle. Because performance conversations often rely on memory and impression, a running record keeps the details from depending on what anyone happens to recall. Many people find it most useful when it stays factual and specific rather than evaluative, leaving judgments about significance to the review process itself.
- A dated log of tasks, projects, or problems handled
- Notes on measurable outcomes, when available
- Quotes or summaries of feedback received from managers, peers, or clients
What should go in a brag document?
A brag document generally mixes concrete outcomes with the context needed to understand them, since a bare list of tasks can be hard to interpret later without detail. Entries often include what the work was, why it mattered, what the result was, and who else was involved or affected. Numbers and measurable results are useful when they exist, but many roles do not produce clean metrics, so a plain description of the problem and the outcome can work just as well. Feedback, whether written in an email, said in a meeting, or given informally, is often worth recording close to when it happens, since exact wording tends to fade. Some people also note skills used or stretched, since this detail can matter later when discussing scope or readiness for a new role.
- Project or task name, date, and a short description of the work
- The outcome or result, described in plain terms
- Any direct feedback received, with rough wording and source
How often should someone update a brag document?
A brag document tends to be most useful when updated close to the event, generally on a weekly or biweekly basis rather than saved for a review period. Waiting until a review cycle to reconstruct months of work often means relying on memory, which can flatten detail and omit smaller contributions that add up over time. A short, regular habit, such as a few minutes at the end of each week, tends to produce a more complete and more accurate record than periodic catch-up sessions. Some people set a recurring reminder tied to a weekly planning routine or a Friday wrap-up, which can make the habit easier to sustain. The specific cadence matters less than consistency, since a document updated in small increments generally holds more useful detail than one filled in sporadically or all at once before a deadline.
How does a brag document help during a performance review?
A brag document generally gives a reviewer or a self-assessment writer specific, dated material to draw from instead of a general impression formed after the fact. Performance reviews often ask for examples of impact, initiative, or growth over a period of months, and a running log tends to make it easier to select relevant, well-documented instances rather than relying on whatever comes to mind first. It can also help correct gaps in a manager's memory, since managers who oversee several people at once often cannot recall every contribution in detail. Bringing specific dates, outcomes, and feedback into a self-review or a review conversation tends to ground the discussion in verifiable detail rather than general assertions. The guide on asking a manager for feedback covers how to get more of that input when it is not coming on its own.
How is a brag document different from a self-assessment?
A brag document is typically an ongoing, unfiltered personal record, while a self-assessment is a formal, curated document submitted as part of a review cycle. The brag document generally contains more raw material than any single self-assessment needs, since it accumulates detail continuously rather than being written for a specific audience or deadline. When review season arrives, the self-assessment often draws selectively from the brag document, choosing the examples that closely match whatever criteria or competencies the employer's review process uses. Keeping the two separate can help, since the brag document stays neutral and complete while the self-assessment can be shaped for tone, length, and relevance to a specific reviewer. Mapping brag document entries to a specific review rubric or competency framework is a distinct step, addressed separately from the recording habit itself.
Where should a brag document be kept?
A brag document is generally kept somewhere the individual controls directly, separate from employer systems, since access to internal tools, shared drives, and performance platforms typically ends when employment does. A personal file, a private note-taking application, or a dedicated record kept outside company infrastructure are common choices, and any of these can preserve access across a job change. Keeping copies of specific feedback, whether an email, a message, or a written comment, alongside the log entries can also help, since original wording sometimes matters more than a paraphrase written later. A service that lets someone keep their own career notes, feedback, and goals independent of any single employer can serve this purpose, since it keeps the record intact even after a role ends. More on keeping this kind of independent record is available through OffbookHR.
How does a brag document support a promotion case?
A brag document generally supplies most of the raw material for a promotion case, since many promotion processes ask for concrete examples of scope, impact, and consistency over time rather than general claims of readiness. A well-maintained log makes it easier to identify a pattern of growth, such as increasing project complexity or expanding responsibility, that might not be obvious from memory alone. It can also help identify gaps, since reviewing several months of entries sometimes reveals that a particular skill or type of work is underrepresented, which is useful to know before a promotion conversation rather than during it. Because promotion cases often need to persuade people who were not directly involved in the daily work, specific and dated examples tend to carry more weight than general descriptions. The guide on asking for a promotion covers how this kind of documented history is typically used in that conversation.
The specifics of what to record and how a brag document gets used can depend on an employer's review process and an individual's role, and the practices described here can vary by situation. This guide is general information, not legal advice about your situation.