How to Write a Brag Document (2026 Guide)

Keep one document with dated entries, capture raw notes daily, and spend 15 minutes each week turning them into impact statements with evidence. A tracker makes capture easier. Dayflow fits if you want an AI-written timeline of your whole Mac day at $0. Timing fits if you also bill hours. WakaTime fits if your work is mostly code, and ActivityWatch if you're on Windows or Linux.

A brag document is a running list of what you did at work and why it mattered. You keep it so that review season, a promotion case or a job search starts from evidence instead of memory. The goal is simple. When someone asks what you accomplished this year, you open one file and the answer is already there.

The usual failure is just as simple. You start the doc in January, add three entries, and reopen it the week your self-review is due. By then you still remember the big launch. But the incident you defused in March, the hiring loop you ran and the design doc that saved another team weeks of rework are gone.

This guide gives you a method that works with nothing more than a text file. Some steps get easier with a tracker. One of the trackers covered here, Dayflow, is our product. We say where it helps, where it doesn’t, and which tool wins instead.

The short version

1. Create one document with fixed sections and a date on every entry.
2. Capture raw notes daily, by hand or with a tracker that records for you.
3. Review once a week and promote the few notes worth keeping.
4. Rewrite each kept item as an impact entry with evidence.
5. Add the work nobody sees: reviews, mentoring, incidents, glue work.
6. Before each review, cut the document into a one-page summary mapped to your role’s expectations.

What you need before you start

• One place to write. A doc, a notes app or a Markdown file all work. Pick something searchable that you open often. Keep confidential details in a company-approved location. If you keep a personal copy for job searches, write it at a level of detail your employer would be comfortable with.
• Your role’s expectations. Find your company’s career ladder, leveling guide or review rubric. If none exists, ask your manager what “doing well” looks like at your level. You will map entries to this later.
• Your existing trails. Your calendar, ticket tracker, pull request history, sent email and chat threads already hold evidence. You don’t need to copy them. You need to link to them.
• A recurring 15-minute slot. Put it on your calendar for the same day every week. Friday afternoon or Monday morning both work.
• Optionally, a tracker. If you plan to run one on a work machine, check your employer’s policy on screen recording and activity tracking first.

Step 1: What should a brag document include?

Set up a fixed skeleton so you never have to decide where something goes. Use themed sections, and give each entry four parts: a date, a one-line summary, the impact, and a link to evidence.

Sections that cover most roles:

• Projects and outcomes: what shipped or moved, and what changed because of it
• Problems solved: bugs, incidents, blockers, decisions that unstuck something
• Collaboration and mentoring: reviews, pairing, onboarding, interviews
• Writing and influence: design docs, proposals, talks, internal posts
• Process improvements: anything that made the team faster or less error-prone
• Learning: new skills or domains that changed what you can take on
• Praise received: paste the message and link to it

Illustration: an empty skeleton might look like this.

## Projects and outcomes
- 2026-03-14 | Migrated billing exports to the new queue | Export failures stopped paging on-call | [ticket]

## Problems solved
## Collaboration and mentoring
## Writing and influence
## Process improvements
## Learning
## Praise received

Mistake to avoid: building something so elaborate that adding an entry feels like work. If your template needs scrolling to find the right section, cut sections. A short document you update beats a perfect one you abandon.

Step 2: How do you capture work without a daily chore?

Separate capture from writing. The brag document is the curated output. Underneath it sits a raw log that is cheap, messy and complete enough to review once a week.

The manual version takes two minutes at the end of the day. Write three lines: what you worked on, what you finished, and anything that surprised you. The daily work log template gives you a ready format.

If end-of-day notes never stick, let software keep the raw record. There are several kinds, and our roundup of Mac time trackers covers the wider field. For a brag document, four tools are relevant:

• Dayflow records the screen at one frame every 10 seconds, and AI writes your day into a readable timeline. Recordings and the timeline are stored on your Mac. With local AI through Ollama or LM Studio, screenshot analysis stays on-device. If you use your own cloud provider or Dayflow Pro, selected screenshots are processed off-device. The app is $0 and MIT licensed, with an optional Pro plan at $20 a month. It needs macOS 14 or later.
• Timing (how it compares) records time automatically across apps, websites and documents on the Mac, down to specific URLs and Mail threads. It lists AI activity summaries on all plans. It has no free tier. Professional costs $9 per month billed annually, or $11 per month billed monthly, and there is a 30-day trial with no credit card required.
• ActivityWatch (how it compares) is free and open source under MPL-2.0. It records the active app, the window title and away-from-keyboard time, and browser extensions add the tab title and URL. Data stays on your device. It lists no AI summaries, so you read the raw data yourself.
• WakaTime uses editor plugins to record coding time per project, language and editor, and sends it to a hosted web dashboard. The free plan keeps 1 week of dashboard history. That still works for a brag document if you do your weekly review before the data rolls off.

For more ways to rebuild a day after the fact, see how to remember what you worked on.

Illustration: a raw Tuesday entry, whether typed or read off a timeline, might be “Reviewed two PRs for the payments team. Hour in the incident channel on the export bug. Started the queue migration doc.” It isn’t polished, and it doesn’t need to be.

Mistake to avoid: treating tracker output as the brag document. “Three hours in a design tool” is a fact about time, not an accomplishment. Trackers tell you where to look. They don’t tell you what mattered.

Step 3: How often should you update a brag document?

Weekly. Daily is too often to judge what mattered, and monthly is long enough for details to fade.

In your 15-minute slot, open the week’s raw log or timeline next to your calendar and your merged or closed work. Ask three questions:

1. What shipped, moved forward or got decided?
2. Who did I unblock, and what would have stalled without me?
3. What would I be annoyed to forget by December?

Promote one to three items into the brag document and leave the rest in the log. If you already send a weekly update, the weekly status report template can do double duty. Write the status first, then copy the items that show impact.

With Dayflow, you can export the week as Markdown from Settings → Export and ask an AI assistant for a first-pass list of candidates. The export guide and the Claude weekly report workflow walk through this. Two cautions apply. A cloud assistant receives whatever data you paste into the conversation, even though Dayflow stores it locally. The local vs cloud processing page explains that boundary. Also, AI summaries can miss or misinterpret work, so check every candidate against what actually happened.

Illustration: a week’s review might turn ten raw lines into two entries. One is the export bug fix. The other is the migration doc that two other teams commented on.

Mistake to avoid: skipping weeks and planning to “catch up at the end of the quarter.” Catch-up sessions produce vague entries, because the specifics are what you lose first.

Step 4: How do you write an entry that shows impact?

Each entry should answer four questions: what you did, what changed, how someone could verify it, and who else was involved. A useful pattern is action + result + evidence + collaborators.

Use numbers only when you can point to their source, such as a dashboard, a ticket or a report. If there is no number, describe the change concretely: “on-call stopped getting paged for this,” or “the onboarding doc is now the first link new hires get.”

Illustration:

• Weak: “Worked on the billing export issue.”
• Stronger: “Found and fixed the retry loop behind recurring billing export failures, so the alert stopped firing on-call. Paired with Sam from payments on the fix. [incident ticket] [PR]”

The stronger version takes thirty seconds longer to write. It is also the version a manager can copy into a review.

Mistake to avoid: soft verbs like “helped with,” “was involved in” and “supported.” They hide your actual contribution. The opposite mistake is just as costly. Claiming shared work as solo work damages credibility, and naming collaborators makes the entry easier to believe.

Step 5: Record the work nobody sees

The work that gets forgotten is the work that never had a ticket. That includes code reviews, interviews, onboarding a new hire, answering the same question in chat for three teams, coordinating a cross-team launch, and covering on-call for someone on leave.

This is also where capture tools help most, because the work is fragmented. You won’t write “answered questions in the data channel” in a daily log. A timeline that shows a recurring block in that channel reminds you it happened. If you want a rough sense of how your week splits between project work and everything else, the where does my week go calculator is a quick way to estimate it.

Group these into patterns instead of listing every instance.

Illustration: “Q2: ran 9 interview loops for the platform team and wrote the take-home rubric now used for all backend candidates. [rubric doc]” counts as one entry. The number here should come from your own calendar, not a guess.

Mistake to avoid: leaving this work out because each piece feels small. At more senior levels, rubrics often weigh this kind of influence heavily. Check yours.

Step 6: How do you turn it into a review self-assessment?

A week or two before reviews, read the whole document from the top. Then:

1. Open your role’s expectations and label each entry with the area it shows, such as technical depth, ownership, collaboration or communication.
2. Pick the three to five strongest outcomes across the whole period.
3. Write a one-page summary that leads with those outcomes. Each one gets a sentence or two and a link to the full entry.
4. Note any expectation area with no entries. That gap is worth raising with your manager, either as context or as a goal for next cycle.
5. Send the summary to your manager ahead of their writing deadline.

Illustration: a summary line might read “Ownership: led the billing queue migration end to end, from design doc to cutover, with zero rollback (see entries Mar 14, Apr 2, May 20).”

Mistake to avoid: recency bias. If your summary only covers the last six weeks, you are making the same mistake the brag document exists to prevent. Make sure the first quarter of the period is represented.

Doing it by hand vs with a tool

Approach	Effort	What you get	Cost
Manual daily log + weekly review	Two minutes a day plus 15 minutes a week	Exactly what you chose to write, nothing more	$0
WakaTime (editor-only tracker)	Install plugins, then review weekly	Coding time per project, language and editor, plus AI coding usage	Free plan with 1 week of history. Full history requires Premium at $14/mo billed monthly, or $12.83/mo billed $153.96 yearly
Timing (automatic tracker)	Install, then review weekly	App, website and document time on the Mac, with AI activity summaries	Professional at $9/month billed annually or $11/month billed monthly. No free tier, 30-day trial
ActivityWatch (automatic tracker)	Install plus browser extensions, then read the raw data weekly	App, window title, URL and away-from-keyboard data, stored locally	Free
Dayflow	Install, choose local or cloud AI, then review weekly	An AI-written timeline of your screen day, exportable as Markdown	$0, optional Pro at $20 a month

None of these is a start/stop timer app. If you prefer that style, the time tracker for Mac roundup covers it.

Disclosure: Dayflow is our product. The comparison above uses each vendor’s own documentation as checked on October 4, 2026, with Dayflow facts reviewed against version 2.2.0. Current Dayflow plans are on the pricing page.

Common mistakes

• Starting at review time. A brag document written in one sitting is a self-review draft, not a brag document. The value comes from the dates.
• Logging hours instead of outcomes. Time data is input. “Spent a lot of time on X” is not an entry.
• Pasting AI summaries unchecked. Any AI-written summary can misread what was on screen. Read it as a prompt for your memory, not as a record.
• Writing in private shorthand. “Fixed the thing with the cron” means something to you today and nothing to a promotion committee next year. Write for a reader who wasn’t there.
• No evidence links. An entry without a link is a claim. An entry with a link is evidence.
• Never sharing it. A document only you read helps your memory. It does not help your manager argue your case.

Where Dayflow is the wrong pick

Dayflow fits one specific job: a broad, readable record of your whole Mac day. It is not the best choice in several situations.

• You’re not on a Mac, or you’re on macOS older than 14. Dayflow won’t run. ActivityWatch is free and runs on Windows, Linux, Mac and Android.
• Your evidence is mostly code. If your brag document is about projects shipped in an editor, WakaTime gives you per-project, per-language numbers and AI coding usage data. Dayflow doesn’t produce those.
• You bill hours as well. Freelancers who need billing status, rounded reports and invoicing through GrandTotal should use Timing. Dayflow has no invoicing or payroll features.
• Your team wants shared reporting. Dayflow has no team reports. Timing’s Connect plan has shared projects, at $16 per user per month billed annually or $20 billed monthly.
• Screen recording isn’t allowed on your machine. Keep a manual log. If activity trackers are permitted, ActivityWatch records app and window titles instead of an AI-written screen timeline.
• You want website blocking to protect focus time. Dayflow doesn’t block anything. Use a dedicated blocker.

The bottom line

A brag document is a habit, not a tool. Keep one file with fixed sections and capture rough notes daily. Spend 15 minutes each week turning the few that matter into dated entries with evidence and collaborators. Before each review, cut it down to one page mapped to your role’s expectations.

A tracker only makes the capture step easier. Dayflow, Timing, ActivityWatch and WakaTime each record a different slice of your day. None of them can tell you what mattered, and that judgment is the part of the document that gets you recognized.

Frequently asked questions

What is a brag document?

A brag document is a private, running record of your work accomplishments and why they mattered. You write it as you go instead of reconstructing it later. It usually covers shipped projects, problems you solved, people you helped, writing you produced and praise you received, each with a date and a link to evidence. You use it for self-reviews, promotion cases, resumes and updates for a new manager.

How long should a brag document be?

The working document can be long. It is your raw archive, so it can run to many pages over a year. The version you hand to a manager or review committee should be short, ideally a one-page summary of your top outcomes, each linking back to the detailed entry. Length matters less than every entry having a date and a piece of evidence behind it.

Should I share my brag document with my manager?

Usually yes, in curated form. A manager writing reviews for several people works partly from memory. A summary you send before review season gives them specific outcomes and links to cite. Share the one-page version, not the raw file, and remove anything personal. If your company uses a self-assessment form, draw on the document to fill it in instead of attaching the whole thing.

Can AI write my brag document for me?

AI can draft, but it cannot judge impact. Tools such as Dayflow and Timing produce AI summaries of your activity, which are useful raw material for a weekly review. Those summaries describe what you did, not why it mattered. Dayflow's own documentation notes that AI summaries can miss or misinterpret work. Use the summary to jog your memory, then write the outcome, evidence and collaborators yourself.

Is WakaTime better than Dayflow for a developer's brag document?

For code-specific evidence, yes. WakaTime's editor plugins record coding time per project, language and editor across 100+ editors and terminals. It also tracks AI coding tool usage, and it works beyond the Mac. Dayflow writes a general timeline of your whole screen day, including meetings, docs and reviews in the browser. WakaTime's free plan keeps only 1 week of dashboard history, so review weekly.

How do I remember what I worked on months ago?

Memory alone is unreliable, which is why the brag document exists. For past months, rebuild from trails such as your calendar, merged pull requests, closed tickets, sent email, docs you authored and chat threads. Going forward, keep a daily log by hand or run an automatic tracker, so there is a record to review each week. Dayflow can export a recorded date range as Markdown from Settings → Export.

Is it okay to run a screen-recording tracker on a work laptop?

Check your employer's policy first, because some companies restrict screen recording or third-party software on managed machines. If it is allowed, check where the data goes. Dayflow stores recordings and the timeline on your Mac and can analyze screenshots with local AI. Its Pro plan, or a cloud provider you configure, sends selected screenshots off-device. If recording is not allowed, keep a manual daily log instead.

What is the difference between a brag document and a work log?

A work log records what you did, usually daily and in rough form. A brag document records what mattered. It is curated weekly and written for someone else to read. The log is the input and the brag document is the output. A practical setup keeps both, a quick end-of-day log or tracker timeline, then a weekly pass that promotes the few items worth keeping.

Can I keep a brag document on Windows or Linux?

Yes. The document itself is just a file, so any editor works. For automatic capture, Dayflow is Mac only, so it is not an option there. ActivityWatch is free, open source under MPL-2.0 and runs on Windows, Linux, Mac and Android. It records active apps, window titles and away-from-keyboard time. It lists no AI summaries, so you read the raw data during your weekly review.