Brag Document for Performance Review: What to Include

Brag Document for Performance Review: What to Include

Many employees still receive formal feedback only once a year. A 2026 dataset covering more than 2,000 companies found that 68% rely on annual reviews alone, and nearly half of employees get just one formal review a year, according to OpsMatters' summary of PerformYard's 2026 study. That gap helps explain why career-document reviewer Volio recommends a brag document for performance review, a private, ongoing record of what actually happened at work, for anyone whose company runs on an infrequent review cycle.

Only 27.8% of employees get feedback more than twice a year, the same data shows (OpsMatters/PerformYard). Robert Half argues that once-a-year cycles were designed for a workplace that no longer exists, one where roles and priorities didn't shift as constantly as they do now. When a manager weighs in once a year and memory is the main evidence on the table, a written record gives a self-evaluation something sturdier to work from.

Why employees are keeping their own performance records

Part of the problem is infrastructure, not just review frequency. The same 2026 study found that 77.4% of companies manage reviews through spreadsheets, documents, or payroll platforms, compared with 22.6% using software built specifically for performance management (OpsMatters/PerformYard).

Companies using dedicated platforms reported feedback more than once a year at a 69% rate, versus 46% among spreadsheet-reliant companies (OpsMatters/PerformYard). The study doesn't prove software causes more frequent feedback, but the association is clear: employees at spreadsheet-dependent companies are far less likely to get regular check-ins than those at companies with purpose-built tools.

That leaves a lot of employees managing their own evidence trail by default. Volio, which reviewed more than 25 brag document formats, notes that most of the context around an accomplishment evaporates after about a month (Volio). Logging what happened close to when it happened, rather than reconstructing a year from memory during review season, is the practical case for starting now instead of waiting.

What to include in a brag document for performance review

The core of a useful entry, and the basic answer to how to write a brag document that still makes sense months later, is three parts: what you did, why it mattered, and what changed as a result. Volio puts the extra effort at around 30 seconds per entry, and calls that small addition the difference between a note you can actually use later and one that draws a blank at review time.

Wording matters too. Volio recommends writing entries with "I" and "my" rather than "we," so a manager reading the document later can see individual contribution clearly instead of a team credit that's hard to parse months afterward.

Some of the same logic that governs how managers should document employee conduct applies here, even though it wasn't written with self-tracking in mind. SHRM's guidance for workplace documentation calls for specific dates and details, and warns against vague or judgmental language, framed as "describe the conduct, not the individual." Applied to a brag document, that means describing the work itself rather than rating your own performance in the entry.

Together, these pieces form a simple brag document template for performance review use:

• the project or task, with enough context that it makes sense months later
• the specific problem or goal it addressed
• your individual role in it
• who else was involved, if anyone
• the outcome, whether that's a number, a result, or something a manager or client observed
• any feedback received on it at the time

A thin entry might read: "Worked on the onboarding project." A stronger one reads: "New hires were missing IT setup steps during their first week. I rebuilt the onboarding checklist and walked two new hires through it directly. The next four hires completed setup without missing a step, and my manager mentioned it in a team meeting." The second version survives a year of forgetting. The first one doesn't.

Performance review brag document examples: accomplishments to track

Project wins aren't the only employee accomplishments for performance review worth logging. Feedback received, progress toward stated goals, problems solved without being asked, and skills or leadership demonstrated all belong in the same document.

Goals in particular seem to matter for how reviews get structured. The 2026 study reports that completion reached 74.9% when employees and managers decided on goals together (OpsMatters/PerformYard). Whether organizing a personal brag document around the same goals produces similar results isn't something the study measured, but it offers a reasonable structure to borrow.

For anyone starting from zero, Volio suggests picking one section, "Projects and Accomplishments," and writing plain bullets with no metrics required (Volio). Three bullet points is a better starting point than an hour spent building a perfect template, and the habit matters more than the format. Volio recommends updating weekly while details are still fresh, though some people manage daily and others do it biweekly.

None of this is new. The brag document concept traces back to Julia Evans' 2019 framework, and the number of template variations has grown every year since, according to Volio's review of the space (Volio). The specifics differ across versions, but the underlying habit, writing things down close to when they happen, hasn't changed.

Turning brag document entries into a self-evaluation

A list of accomplishments doesn't automatically become a self-evaluation. Before submitting one, it helps to reshape entries around how the document will actually be read.

Group entries under the categories or goals the employer's review form already uses, rather than the order they happened in. A manager scanning for evidence tied to "collaboration" or "ownership" shouldn't have to hunt for it.

Keep individual contribution separate from team outcomes, even on group projects. If three people worked on a launch, note specifically what part was yours, not just the group's result.

Label outcomes honestly: some are measured (a number, a completion date), some are observed (a comment from a client or manager), and some are still in progress. Mixing these together without saying which is which makes a self-evaluation harder to trust.

Setbacks and changed priorities belong in the document too, not just wins. A project that got deprioritized, a deadline that slipped for reasons outside anyone's control, or a lesson learned from a mistake all show judgment, and they explain gaps a manager might otherwise read the wrong way.

One more thing worth checking before storing anything: whether client names, financial figures, or other confidential business details belong in a personal document at all. Company policy on that varies, and it's worth confirming with a manager or HR rather than assuming.

How a brag document supports, but doesn't replace, a fair review

A brag document is documentation, not insurance against a biased evaluation, and research on self-appraisals shows why that distinction matters. A study at a multinational financial-services company found that manager ratings closely tracked employee self-ratings when managers saw those self-ratings first, a pattern consistent with an anchoring effect (Harvard Gazette).

Women and workers of color tended to rate themselves lower in that study, with women of color giving themselves the least favorable ratings and receiving the lowest manager scores of any group (Harvard Gazette). The pattern held even during a year when a system glitch kept managers from seeing current self-ratings before submitting their own; researchers inferred that managers may have referenced prior-year self-evaluations instead, since the gender-race dynamics persisted anyway.

The company later stopped sharing self-evaluations with managers before their assessments and committed to auditing rating patterns on a regular basis (Harvard Gazette). That's a structural fix a company makes, not something an individual employee can replicate.

What a brag document can do is keep a self-review factual: grounded in dates, outcomes, and feedback actually received, rather than a number assigned to yourself or a tendency to undersell (or oversell) the work. A brag document cannot guarantee how a manager will interpret or weigh that information once it reaches them. That's a limit worth knowing before relying on one to change how a review turns out.

What to do next

Open a private note or document today. Add three entries from the past month, each following the same shape: what happened, why it mattered, and what changed as a result.

Set a recurring weekly or biweekly reminder to keep it current. Before the next formal cycle, check with a manager or HR about the categories or goals the company's self-evaluation actually asks for, then reorganize the document around those categories before submitting anything.