Keep a Brag Document: The Habit That Pays Every Year

The problem it solves

Every year, at review time, people sit down to remember what they did and cannot. March is gone entirely. The project that consumed six weeks in the spring surfaces as a name with no details attached.

What disappears first is exactly what makes an accomplishment persuasive. The number of customers affected. How long the thing took before you changed it. What the original problem actually was. Who asked for it and why it mattered to them. Those details are obvious the week it happens and unrecoverable four months later.

The habit that fixes this is small enough to be worth describing precisely, because most advice about it is vague enough that nobody starts.

Two minutes, once a week, in one file. That is the entire practice.

What an entry looks like

Each entry needs a date, what happened, and the detail you will not remember.

The detail is the part people skip and the only part that is expensive to reconstruct. Write the number. Write what it was before. Write who noticed.

Compare two versions of the same week. "Finished the reporting automation" is a note that will mean nothing in November. "Finished the reporting automation. Monthly close reports used to take about 11 hours of manual work across two people; now it runs unattended. Priya asked for it after the August close overran." The second is a review entry, a resume bullet and a raise argument, already written.

Keep it rough. This is not a document anyone else reads, and polishing it is what turns a two-minute habit into one that gets skipped.

Where a project runs for months, add an entry when something concrete happens rather than waiting for the end. Long projects produce their best details in the middle and their vaguest summary at the finish.

One clear takeaway: write the number down now, because it will be gone by November.

What to record beyond projects

Project outcomes are the obvious material and they are maybe half of what belongs in the file.

• Praise, verbatim. Copy the message. A quoted line from a customer or a colleague is verifiable in a way your summary of it is not.
• Problems you prevented. The bug caught before release, the contract clause spotted, the hire you argued against. These produce no metric and disappear completely unless written down.
• Help you gave other teams. Invisible in your own team's records and consistently under-credited.
• Things you learned. A tool, a system, a domain. Useful for both reviews and the next resume.
• Interviews, mentoring and onboarding. Real hours that get treated as background noise unless counted.
• Decisions you made and why. Especially the reasoning, which is what a promotion case is built from.
• Things that went badly and what you changed. These become the credible weakness answer in a review and in an interview.

That last category is the one people resist and it is worth including. A failure recorded with what you did about it is a stronger story than any success, and it is the only version of that story that survives with the details intact.

Making the habit stick

Three things determine whether this survives past a month.

One file, easy to open. A plain document, a note, whatever you already have open. If capturing a thought requires opening a tool you do not otherwise use, it will not happen.

A fixed trigger. Friday afternoon works for most people because the week is fresh and nothing else is competing for the slot. Attaching it to something that already happens weekly is more reliable than a reminder.

Permission to skip. Some weeks contain nothing worth recording and forcing an entry makes the file useless. Missing three weeks in a row is not a failure of the system; the file with nine months in it is still worth more than nothing.

One extra habit pays for itself: when a message arrives that says something good about your work, paste it in immediately. That is the single highest-value item in the whole file and the one most reliably lost when an inbox is cleared or a job ends.

Using it

The file has four uses and none of them require rewriting it.

The self review. Read the year, pick six entries, write them properly. What normally takes an evening of reconstruction takes an hour of editing. Our post on self review examples covers the shape each entry should take.

A promotion or raise conversation. The argument for both is a list of specific things with scope attached, which is precisely what the file already contains.

Resume writing. The reason most resume bullets are vague is that they are written from memory years after the fact. Written from a contemporaneous record, they carry numbers. Our resume builder works directly from this kind of material.

Interviews. Behavioural questions ask for specific examples, and the file is a list of them. Reading it before an interview is better preparation than trying to think of stories on demand.

A few practicalities

Keep a copy somewhere that is not your employer's systems, where your local law and contract permit it. People lose years of this the day their access is revoked, and the record of your own work is worth more to you than to anyone else.

Do not copy in anything confidential. The point is your contribution and its scale, not the customer's data or the company's internal figures. Write "a seven-figure account in the healthcare sector" rather than the name and the number.

Review it twice a year rather than only at review time. Reading six months of your own entries is the clearest available picture of whether your work is trending towards the things you want to be doing, and it is a much better prompt for a career decision than a general feeling.

Start with the last three months rather than from today. An hour spent going back through your calendar, sent mail and finished work gives the file enough content to feel worth maintaining, which is the difference between a habit that starts and one that is planned.

Finding the numbers

The most common objection to this habit is that the work does not produce numbers. Usually it does, and they sit in systems nobody thinks to look at while the memory is still fresh.

Your own tools hold most of them. Tickets closed, cases handled, deals worked, documents produced, code merged, campaigns run. None of these are impressive on their own and all of them supply the scale that makes a claim specific.

Time is the most underused measure. How long something took before you changed it, and how long it takes now. Almost every improvement can be stated this way, and it is the version non-specialists understand fastest.

Scope works when volume does not. How many people, teams, sites, systems, customers or countries. A process improvement affecting three people and one affecting three hundred read identically without this.

Where you truly cannot measure something, record the consequence instead. What would have happened without the work. A prevented outage, an avoided compliance breach, a bad hire not made. State it plainly rather than inventing a figure, since a made-up number fails the first follow-up question and takes the rest of your credibility with it.

A monthly version for people who will not do weekly

Weekly is the recommendation and it is not the only workable cadence.

A monthly pass takes fifteen minutes and recovers most of the value. Open your calendar for the month, scroll your sent mail, look at whatever tracks your work, and write down four or five things with their details attached. A month is short enough that the numbers are still available and the context is still clear.

What does not work is quarterly, and the reason is specific. Three months back, you remember the projects and none of the surrounding detail, which means you end up writing exactly the vague entries the file exists to prevent.

Questions people ask

How often should I add to it?

Once a week, or at the end of each piece of work. Reconstructing at review time is what the habit exists to avoid.

What should each entry contain?

The date, what happened, and the details you will forget: the numbers, what the situation was before, and who asked for it.

Should I include things that went badly?

Yes, with what you changed afterwards. They become the credible weakness answer in reviews and interviews, and the details vanish otherwise.

Where should I keep it?

Somewhere you already open daily, with a copy outside your employer's systems where your contract and local law allow it.

What if I have not kept one?

Reconstruct the last three months from your calendar, sent mail and finished work. An hour recovers enough to make the file worth continuing.

Related reading

• Is a Professional Resume Writer Worth Paying For?
• How to Make Your Resume Stand Out When Everyone Uses AI