Guide

How to keep a brag document without it becoming a chore

Updated November 2026 · by Jerry Liu, Dayflow's founder

Keep it in a plain document or notebook and add one line every Friday, ten minutes, with links as proof. When you skip weeks, rebuild them from your calendar, sent mail and chat history. If you are on a Mac and remembering is the real bottleneck, Dayflow can record your screen and draft a timeline, but the plain doc is the core tool.

Review season shows up, and the form asks you to list your accomplishments from the past six or twelve months. You know you worked hard. You remember being busy, and you remember a few late nights. But when you try to name what you actually did in March, you get a blank, or one project that ran long. You end up writing about the last six weeks because that is all you can recall, and the rest of the year quietly disappears.

Maybe you have tried a brag document before. You set it up with good intentions, wrote three long entries in January, felt guilty about not updating it in February, and never opened it again. The document turned into one more thing you were failing at.

This guide covers how to keep a brag document that survives an ordinary busy year: what to write, when to write it, how to recover the weeks you missed, and how to turn a pile of fragments into something you can hand to a manager. Most of it needs nothing more than a text file and a calendar. Dayflow, the Mac app that publishes this blog, comes up once near the end, along with where it is the wrong choice.

The short version

Why does a brag document keep turning into a chore?

The idea behind a brag document is simple, which is part of why it feels bad when it does not stick. A few things tend to go wrong.

The bar is set too high. Many people picture a brag document as a polished record, so each entry feels like a small essay. Writing a good paragraph about your impact takes real effort. Doing that weekly, on top of the actual work, is a lot to ask, so it slides.

Memory fades fast. On Friday you remember Tuesday in detail. By the end of the month, Tuesday has blurred into “that busy week.” By review time, it is gone. Most of what you did in a year is not memorable, even when it mattered, because it was spread across small decisions and messages rather than one big moment.

Your own work stops looking impressive. The tenth time you fix a broken release or calm down an unhappy client, it feels like part of the job, not an accomplishment. People are often the worst judges of their own work because they see the effort and the mess, not the result.

Bragging feels awkward. A lot of people were taught not to talk themselves up. Writing “I led” or “I saved” can feel uncomfortable even in a private document, so they write nothing, or they write so modestly that the entry is useless later.

Missed weeks create guilt. Once you skip a few entries, opening the document reminds you of the gap. Avoiding the document becomes easier than facing it.

None of this is a character flaw. It is how memory and habits work for most people. The fixes below are mostly about making each step smaller and leaning on records instead of recall.

Make the smallest possible entry count

Decide that a single fragment is a complete entry. No full sentences required, no impact statement, no formatting. A date, a few words and a link if you have one.

What to do: Open a plain document, the notes app you already use, or a paper notebook. Write the date as a heading. Under it, list whatever you can remember from the week in short fragments. Stop when you run out. If you only write one line, that counts.

Illustration:

Week of Oct 6

  • Fixed the export bug support kept escalating (ticket link)
  • Ran onboarding for the two new hires
  • Client thanked us for the faster turnaround (email saved)

That took about two minutes. None of it is polished, and it does not need to be yet.

How to tell after a week: You wrote at least one entry and it did not feel like a burden. If you still put it off, the bar is too high. Try writing only one line, or try speaking a voice memo and transcribing it later.

Attach it to a ritual you already have

A new habit that floats free in the week tends to get skipped. One that rides on an existing routine has a better chance.

What to do: Pick something you already do at the same time every week. Maybe Friday afternoon coffee, the last thirty minutes before you log off, or the commute home. Put a recurring ten minute calendar block right after it, labeled “brag doc.” When the block starts, set a kitchen timer for ten minutes. When it rings, you are done, even mid-sentence.

If you like a structure to fill in, a weekly work log template gives you prompts so you are not staring at an empty page.

Illustration: Someone who already writes a short status update on Friday adds one step: after sending the update, they copy two or three lines from it into their brag document, with the date. The update did most of the remembering already. If you write those updates, our guide on how to write a weekly status report pairs well with this.

How to tell after a week: The block arrived and you did something with it, even if it was one line. If you keep dismissing the reminder, move it to a time when you are less drained, or attach it to a different ritual.

Save proof as you go, write later

Collecting evidence is much easier than writing about it. A link or a screenshot takes seconds and does most of the persuasive work later.

What to do: Create one place for proof. An email folder called “wins,” a pinned chat channel with only yourself in it, a folder of screenshots, or a section at the bottom of your brag document. Whenever something lands, drop it there. Good candidates:

Do not stop to describe it. Just save it.

Illustration: A designer gets a message in chat saying the new checkout flow cut a lot of confused support tickets. She right-clicks, forwards it to her “wins” email folder, and goes back to work. Eight months later that message becomes one of the strongest lines in her review.

How to tell after a week: Your proof folder has at least one or two items in it. If it is empty, you may be filtering too hard. Save anything that made you or someone else a little happier, and sort it out later.

What if you have already forgotten the last three months?

This is the most common situation, and it is recoverable. You do not need memory. You need records you already have.

What to do: Set aside an hour. Work through one month at a time, oldest first. For each month, go through these in order:

  1. Your calendar. Meetings point to projects, decisions and people you helped.
  2. Sent email and chat messages. What you sent tells you what you were working on and who you were working with.
  3. Tickets, tasks or cards you closed.
  4. Documents, files or designs you created or edited, sorted by date.
  5. Any commit, version or revision history your tools keep.

Write a fragment for anything you recognize. Do not worry about completeness. If you want a more structured walk through this, our page on where did my day go covers reconstructing time from the traces you leave behind, and how to remember what you worked on has more prompts.

Illustration: Someone scrolling back to July sees a recurring meeting called “migration sync” that ran for five weeks and then stopped. They had forgotten it entirely. Opening the meeting notes, they find they owned the cutover plan. That becomes an entry: “Planned and ran the July data migration cutover, no downtime (meeting notes link).”

How to tell after a week: You have recovered entries for the months you thought were lost, and opening the document feels less like facing a gap. If the backfill feels overwhelming, cap it at one month per sitting.

Add the “so what” once a month

Weekly entries capture what you did. A brag document becomes useful when it also says why it mattered. That second step is harder, so do it less often and in one batch.

What to do: Once a month, block twenty minutes. Read through the last four or five weeks of fragments. Pick the three to five that matter most and add one line under each answering a question like:

Leave the rest of the fragments alone. Not everything needs an impact statement. A monthly status report template can double as the structure for this pass if you like headings.

Illustration:

  • Ran onboarding for the two new hires
    • So what: both were shipping on their own within their first few weeks; wrote up the checklist so the next person does not start from scratch

How to tell after a week: Since this is monthly, check after the first pass instead. Your top items should now read like something you could say out loud in a review without having to explain the background. If they still sound vague, ask “and then what happened?” one more time.

Find a brag buddy

Other people notice your accomplishments more easily than you do, and a little accountability helps the habit survive.

What to do: Ask a friend or trusted colleague, ideally someone outside your reporting line, to swap brag documents once a month or before review season. Each of you reads the other’s list and does two things: points out anything that undersells itself, and asks about anything missing that they know you did.

Illustration: Two friends at different companies meet for lunch at the end of each quarter. One mentions she spent weeks covering for a teammate on leave. The other says, “That is not in your document.” It goes in: “Covered a second workload for six weeks while maintaining my own deadlines.”

How to tell after a week: You have a date set and someone who expects to see your document. After the first swap, check whether you added at least one item you had overlooked. Most people do.

Count the work nobody sees

Some of the most valuable work never shows up in a ticket or a launch announcement. It is easy to leave out, and it is often what separates a solid review from a strong one.

What to do: Add a standing heading to your brag document called “invisible work.” Under it, keep a running list of things like reviewing other people’s work, interviewing candidates, answering the same question for new people, mentoring, writing documentation, handling incidents at awkward hours, and smoothing out conflicts between teams.

Illustration: An engineer realizes every Tuesday afternoon is eaten by pull request reviews. Over a quarter that adds up to a substantial chunk of his time, and nobody tracks it. He writes: “Primary reviewer for the payments team’s changes this quarter; caught two issues before release (links).”

If you are not sure how much time goes to this kind of work, the where does my week go calculator is a quick way to sketch it out.

How to tell after a week: The invisible work section has a few entries. If it is empty, look at your calendar for recurring blocks that are not tied to a project. Those are often where this work hides.

When review time arrives, these steps together give you a document you can pull from. Our guide on how to prepare for a performance review picks up from there.

Where seeing your actual day helps

Every step above has the same weak point: it depends on you remembering, either during the week or months later. Records like your calendar and sent mail help, but they miss the hours you spent heads-down in a document, debugging, or designing.

Dayflow is a free, open-source Mac app (MIT licensed, macOS 14 or later) that records your screen at one frame every 10 seconds and has AI write the day into a readable timeline. Recordings and the timeline are stored on your Mac. You choose how screenshots are analyzed: a local model through Ollama or LM Studio keeps analysis on-device, your own cloud provider processes selected screenshots under its own terms, or the optional Pro plan at $20 a month handles cloud analysis.

For a brag document, the useful part is that you do not have to start a timer or reconstruct the week. On Friday you can skim the timeline, or export a date range as Markdown from Settings → Export (see exporting your work history), and lift the lines worth keeping. Treat it as raw material. AI summaries can miss or misinterpret work, so check anything before it goes into a document your manager reads, and write the impact yourself.

Dayflow publishes this blog. The product details here come from Dayflow’s published documentation and its 2.2.0 release, reviewed in September 2026.

Where Dayflow is the wrong pick

For most people, a plain document or a paper notebook is the right core tool, and nothing else is required. Dayflow is a poor fit in several cases:

The bottom line

A brag document does not fail because you lack discipline. It fails when each entry feels like an essay and when you rely on memory for months at a time. Make the entry tiny, attach it to a ritual you already have, save proof instead of prose, and add the impact in a monthly batch. When you miss weeks, rebuild them from your calendar and sent messages rather than guilt. A friend who reads your list will catch what you overlooked. If remembering is still the bottleneck and you work on a Mac, an automatic record of your day can fill in the gaps, but the habit and the plain document are what carry you to review season.

Frequently asked questions

What is a brag document?

A brag document is a running private list of what you did at work and why it mattered: projects shipped, problems solved, people helped, praise received. You keep it for yourself and draw on it for performance reviews, promotion cases, salary talks and resume updates. It is not a polished essay. Most of the time it is short dated lines with links to the proof.

How often should I update my brag document?

Once a week works for most people. It is frequent enough that you still remember the details, and rare enough that it does not feel like homework. A ten minute slot on Friday afternoon, tied to something you already do, tends to stick better than a daily habit. If you miss a week, skip the guilt and fill it in from your calendar and sent messages the next time.

What should I put in a brag document?

Put in outcomes, evidence and invisible work. Outcomes are things that shipped, got fixed or got decided. Evidence is a link, a screenshot, a number you already know or a thank-you message. Invisible work is mentoring, code or design reviews, interviews, onboarding help and incidents you handled. Leave out routine tasks unless they add up to something worth naming.

Should I share my brag document with my manager?

Keep the raw document private so you can write freely and include half-finished thoughts. Before a review or a one-on-one about growth, make a short edited version that groups the strongest items by theme and shows impact. Many managers appreciate getting this, because it saves them from reconstructing your year from memory. You decide what goes in the shared version.

How do I write a brag document if I have forgotten most of the year?

Work backward from records instead of memory. Scroll your calendar month by month, then your sent email, chat history, tickets you closed, documents you created and any commit or version history. Write one fragment per thing you recognize. You will not recover everything, and you do not need to. A dozen solid items with links beats a long list you cannot back up.

Is a brag document the same as a work journal?

They overlap but have different jobs. A work journal records what you did and thought each day, including dead ends and notes to yourself. A brag document is a filtered list of the things worth telling someone else about. Many people keep a light journal or log and pull the best items into the brag document once a week or once a month.

Is Dayflow better than a plain document for keeping a brag doc?

No. A plain document or notebook is the better core tool, and it works on any computer or none at all. Dayflow is a Mac app that records your screen and drafts a timeline, which can jog your memory when you write entries. It cannot judge what mattered, it misses meetings and conversations off screen, and its AI summaries can be wrong, so the writing stays your job.

Can I keep a brag document on Windows or a work laptop that blocks screen recording?

Yes, and here a plain text file, shared doc or paper notebook wins outright. Dayflow runs only on macOS 14 or later and needs screen recording permission, so it is not an option on Windows, Linux or managed machines where recording is restricted. The weekly one-line habit, your calendar and your sent messages cover most of what you need anyway.

How long should a brag document be?

There is no target length. The raw document can grow as long as it needs to, since only you read it. What matters is that each entry is short enough to write in under a minute and specific enough to understand months later. The version you share with a manager should fit on a page or two, grouped by theme rather than by date.

See where your day actually went

Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.

Download for MacOS macOS 14+ · MIT licensed · no account required