Review season usually starts the same way: you open a blank self-evaluation form and realize you can't remember what you did in March. Calendar invites only show meeting titles. Chat history is too noisy to search. So you spend a Sunday night writing vague lines like "kept things running smoothly" and undersell a full year of work.
A brag sheet (also called a brag document or work accomplishments log) fixes this. It's a single running page where you jot down a couple of lines each week about what you finished, what you fixed, and what changed.
Below is a copy-and-paste brag sheet template for any role, examples of what to put in it, and how to keep the habit alive without it feeling like a second job.
The copy-and-paste brag sheet template
Keep this in a single document with the newest week at the top, so you never have to scroll to the bottom to add a line.
# Work Brag Sheet — [Your Name]
Role: [Your Title] | Year: [Year]
## Goals & priorities for this half
- [Goal 1 your manager cares about]
- [Goal 2 your manager cares about]
- [Skill or habit you're working on]
---
## Weekly log (newest on top)
### Week of [Month Day]
- [What finished / changed]: [Problem or before state] -> [what I did] -> [outcome or after state]. ([Link or number if any])
- [Unblocked / helped]: [Who or what was stuck] -> [how I helped].
### Week of [Month Day]
- ...
---
## Invisible wins & prevention (things that stopped breaking)
- [Checklist, doc, or fix you put in place] -> [what failure or delay it prevented]
## Feedback & kudos received
- [Date] — From [Name/Role]: "[Exact quote from Slack, email or 1:1]" (Context: [project])
## Ideas & lessons for next review
- [One thing that went sideways, what I learned, and what I changed]
(If you work in software engineering and want a technical version organized around systems, PRs and incident postmortems, see our software engineer brag doc template.)
What actually goes into a brag sheet?
The biggest mistake people make is waiting for a huge, company-wide launch before writing anything down. Most careers are built out of dozens of smaller fixes that look ordinary in the moment and impressive when collected over six months.
Here are five categories worth logging, with examples across non-technical and technical roles. The examples are illustrative: swap in your own work and only keep a number you can point to.
1. Projects and deliverables shipped
Don't just write the project name. Write the constraint you navigated or the specific decision you drove.
- Too vague: "Shipped Q3 pricing page."
- Useful in November: "Shipped Q3 pricing page on the planned date after legal requested late copy changes; re-sequenced design work and ran daily 15-minute check-ins for the final two weeks."
2. Process fixes and time saved
Whenever you turn a messy manual task into a repeatable checklist, form, or template, write down how it worked before and how it works now.
- Too vague: "Improved vendor onboarding."
- Useful in November: "Moved vendor approval requests from three email inboxes into one intake sheet with weekly finance triage; approval time dropped from ~6 days to ~2 days."
3. Problems prevented ("invisible work")
If you caught a mistake before a customer saw it, or built a checklist that stopped a recurring error, log it the day it happens. Prevention leaves no trace once the crisis is avoided.
- Too vague: "Helped with month-end close."
- Useful in November: "Created a month-end close checklist in April; we went from 3 late closes last year to 0 this year."
4. Helping teammates and unblocking other teams
Cross-team help is the first thing you forget and the easiest way to show leadership in a review.
- "Wrote a first-week onboarding guide and paired with two new hires in June; the team now uses the guide for every new joiner."
- "Ran a weekly 20-minute sync between finance, procurement and legal that cleared 40 stuck requests in six weeks."
5. Exact quotes from teammates or customers
When someone thanks you in Slack or email—especially for something specific—copy the exact sentence and the date into the bottom of your brag sheet. Quoting a stakeholder ("Thanks for catching the billing mismatch before renewal") is far more persuasive than praising yourself.
How to turn rough weekly notes into review answers
Your weekly log doesn't need to be polished prose. Write messy notes on Friday, and polish only the best ones when review season arrives.
| Friday note in your brag sheet | Self-evaluation line at review time |
|---|---|
| Oct 10: finally got finance + legal on one sheet for vendor approvals, down from ~6 days to 2 | Cut vendor approval turnaround from ~6 days to ~2 days by consolidating three email threads into a single shared approval sheet with finance and legal. |
| Aug 22: caught missing compliance step on ERP rollout, would've pushed launch 2 months | Identified a compliance gap during ERP planning and worked with legal to close it early, preventing a two-month delay to go-live. |
| Jun 14: onboarding doc for Sam and Priya done, they took tickets in wk 2 | Created our team's first written onboarding checklist and paired with two new hires, who both started handling their own queue in week two. |
Why most brag docs get abandoned by Week 3
Almost everyone agrees a brag sheet is a good idea. Almost everyone stops updating their Notion page or Google Doc after three weeks.
Three things usually kill the habit:
- Too much structure. If your template has twelve columns and dropdown tags for every entry, you won't open it on a tired Friday afternoon.
- It's buried in a tab. Out of sight means out of mind until November.
- You still have to rewrite everything at the end. A 10-page dump of raw bullet points still takes hours to turn into a weekly update, a categorized brag sheet, and STAR method stories at review time.
A simpler way to keep the habit
If you like keeping a manual doc, copy the template above, bookmark it in your browser bar, and set a recurring 5-minute calendar reminder for Friday at 4:00 PM. Pair it with a weekly status update to your manager so one note does two jobs.
If you'd rather not maintain and rewrite a document by hand:
- Paste any single rough note into our free STAR method generator (no sign-up) to turn it into a clean review story right now.
- Or start free on WinStash to log your week in a minute from your browser and automatically synthesize your real notes into weekly updates, a categorized brag sheet, and STAR stories when review season arrives—with nothing made up.