What is a brag document, and how do I keep one?

A brag document is a running private record of what you did at work: the project, what changed because of it, and the numbers. You keep it so that review season, a resume rewrite, or an interview draws on evidence instead of memory. It takes about ten minutes a week.

What actually goes in one

The useful unit is not "worked on the billing migration". It is one entry that answers three questions while you still know the answers: what was the situation, what did you do, and what changed as a result.

Write the entry the week it happens. Six months later you will remember that the migration went well; you will not remember that it cut invoice errors from roughly forty a month to under five, and that number is the entire value of the entry.

The situation — what was broken, blocked, or newly asked for.
What you specifically did, as opposed to what the team did.
What changed, in whatever units the work is measured in: time, money, errors, headcount, latency, retention.
Who noticed. A name, a thread, a quote from a review. This is what makes the entry credible later.
Anything you would otherwise lose: the doc link, the ticket number, the before-and-after screenshot.

Why this matters more now than it did two years ago

When you ask an assistant to write your resume, it has your old resume and the job posting. It does not have the billing migration, the error rate, or the fact that your manager quoted you in a review. So it does the only thing it can: it writes plausible sentences in the shape of achievements.

That is where invented numbers come from. Not malice — an absence. The brag document is what closes the gap, because a model working from a real record does not have to guess, and you can check every line against something you wrote at the time.

Keeping it is a ten-minute habit, not a project

The version that survives is boring: one recurring slot a week, one heading per entry, no formatting. Every system that asks you to categorise, tag, or rate entries is a system you will abandon by the second month.

Two rules that keep it honest. Write only what happened — a brag document you have padded is worse than none, because you will eventually quote it in an interview. And keep it somewhere personal rather than in a company doc you lose access to on your last day.

Where CareerDiary fits

CareerDiary is our product, so read this with that in mind: the free diary is a place to keep those entries, and the reason to keep them with us rather than in a text file is what happens next. When you tailor a resume, the bullets are generated from your entries rather than invented, so every line traces back to something you wrote.

A plain text file works. Use one if you prefer — the habit is what matters, not where it lives.

Frequently asked questions

What is the difference between a brag document and a resume?

A resume is an edited argument aimed at one job and kept to a page or two. A brag document is the unedited source it is drawn from: everything, in whatever detail you captured, with no audience. You write the brag document for yourself and cut a resume out of it later.

How often should I write in it?

Weekly is the cadence that survives contact with a real job. Monthly works if the week is genuinely too fine-grained for your role, but by the quarter you are reconstructing from memory, which is the failure this is meant to prevent.

Should my brag document be private?

The default should be private, because the entries are most useful when you have written them without an audience. A curated subset — the version you bring to a review or a promotion case — is worth assembling separately when you need it.

What if I cannot measure my work in numbers?

Plenty of real work has no clean metric. Record the change in qualitative terms instead: what became possible that was not before, what stopped breaking, who said so. "The on-call rotation stopped paging at 3am" is evidence even without a percentage attached.

Can I use a brag document to fix a resume an AI wrote?

That is one of its best uses. Read the generated resume line by line against your entries: every claim that maps to an entry stays, and every claim that does not is either rewritten from a real entry or deleted. See our page on what to do after ChatGPT writes your resume.