A completed example
This fictional example shows the level of detail to aim for. It is not a customer's work history.
Brag document Name: Priya N., Product Designer, Payments team Period: July 1 to September 30, 2026 Last updated: September 30, 2026 Shipped - Refund request flow redesign (August 12). Replaced a four-screen form with one page. Support reported far fewer "where do I start" tickets in the first two weeks. Evidence: launch note in the team channel, support lead's message. - Invoice settings audit (July 25). Found 31 inconsistent labels and fixed 22 with engineering. Evidence: audit doc, merged changes. In progress - Saved payment methods screen. Prototype tested with five merchants on September 18. Two open questions on card expiry warnings. Target: late October. - Error state tokens for the design system. About half migrated. Blocked on a contrast decision for dark mode. Helping others - Mentored Marco, our design intern, with weekly critiques from July to September. - Covered design review for the Billing team for two weeks in August. Feedback received - "The refund flow is the first launch we didn't need a workaround doc for." Support lead, August 28. - Manager 1:1, September 10: share design decisions with engineering earlier. Learning - Finished the internal accessibility course. Applied it to the error state work. For my review - Lead with the refund flow and the audit. - Ask about owning saved payments end to end next quarter.
Make it yours
Your draft
The example is fictional. Edits stay in this page and disappear when you leave. Copy or download your work to keep it.
How to fill it in
- Set the period to match your review cycle and add a dated entry within a day or two of finishing anything worth mentioning.
- For each shipped item, write one sentence on what you did and one on what changed, then name the doc, ticket or message that proves it.
- Keep unfinished work under In progress with its last milestone and blocker, so it does not get lost if it ships after the period ends.
- Copy feedback in the person's own words with a date, and include constructive feedback alongside the praise.
- Before your review, pick the two or three strongest entries for the For my review section and note any ask you want to make.
Start from your actual work
On a Mac, Dayflow can help you remember the work behind the update. It drafts a timeline from screen activity. Export a date range as Markdown from Settings → Export. Review that record alongside your calendar and task tracker, then fill in the template above.
For a guided walkthrough, see exporting your work history or drafting a report with Claude Code. Check the assistant's draft before sending it.
Local AI keeps screenshot analysis on-device. Your own cloud provider or Dayflow Pro processes selected screenshots off-device. An assistant can receive the Dayflow data it retrieves in your conversation. Local storage does not make a cloud assistant conversation local. Read the data-flow guide before choosing a workflow.
Questions about this template
What is a brag document?
A brag document is a running, private list of your work accomplishments, written as they happen. It records what you did, what changed because of it and where the evidence lives. It is your own record, not an official performance review, so your manager may weigh items differently, but it makes self-reviews and promotion cases much faster to write.
What should I put in a brag document?
Include shipped projects with dates and outcomes, work in progress, help you gave teammates, feedback you received, and things you learned. Add evidence for each item, such as a ticket, doc or message. Small wins count too, like fixing a recurring problem or covering for another team, because those are the items people forget by review time.
How often should I update my brag document?
Add entries as soon as something finishes or someone gives you feedback, ideally within a day or two. If that is hard to keep up, block fifteen minutes at the end of each week to review your calendar, sent messages and closed tickets. Waiting until review season usually means the details and evidence are gone.
Should I share my brag document with my manager?
Many people share it before a review or promotion discussion, since it helps a manager remember work they did not see directly. Trim it first: lead with the strongest outcomes, keep the evidence, and remove private notes. Treat it as input to the conversation rather than a final verdict on your performance.
How is a brag document different from a resume?
A resume is a polished summary for people outside your company, covering years of work in a few lines. A brag document is detailed, internal and dated, covering one review period with evidence for each item. Many people later pull their best resume bullets from a brag document because the specifics are already written down.
How can I remember what I worked on for my brag document?
Check your calendar, closed tickets, merged changes and sent messages for the period. On a Mac, Dayflow can draft a timeline from your screen activity, which helps jog your memory. Its summaries can miss or misread work, so check them against your own records and add meetings, calls and offline work it could not see.
Use the right format for the next step
- Weekly status report for a concise progress update.
- Daily work log for a record you can come back to.
- Daily standup template for yesterday, today, and blockers.
Download Dayflow