What is a “brag document” or accomplishment log?

It is a running, private record of what you actually did at work — the projects, the decisions, the problems you solved, and the impact each had. It is not a résumé and not for your manager’s eyes; it is raw material you keep for yourself, so that when you need to write a review, make a case for a raise, or answer an interview question, the specifics are already there.

What should I write down?

Anything that took judgment or made a difference: an accomplishment, a hard project, a decision you owned, a stakeholder you brought along, something that went wrong and what you learned, a measurable result. For each, capture the situation, what you did, and what changed — and any concrete detail (a number, a quote, a before-and-after) while you still remember it exactly.

When should I record an accomplishment?

As close to when it happens as you can — ideally within a week. The specifics that make a story convincing fade fast; a month later you remember that a project went well but not the number that proved it. Capturing it while it is fresh means you are saving a real story, not reconstructing a vague one later.

How is this different from just updating my résumé?

A résumé is compressed, outward-facing, and heavily edited for a specific role. An accomplishment record is the opposite: raw, complete, and kept for yourself. The résumé is what you distill from it. Keeping the full record means every future résumé, review, and interview answer is drawn from real detail instead of half-memory.

How to Keep a Record of Your Work Accomplishments (Brag Document)

The short answer

Keep a private, running record of what you actually did at work — the situation, your action, and the result — written down while it is fresh. It is not a résumé and not for your manager; it is raw material for yourself. Capture within a week of anything meaningful, keep the specific numbers and details, and you will never again reconstruct your career from half-memory.

Why your memory is not enough

Ask anyone to list their accomplishments from two years ago and you will watch the same thing happen: they remember that a project went well, but not the number that proved it; that a launch was hard, but not the specific thing they did that saved it. The impact is real. The evidence has evaporated.

This matters because interviews, performance reviews, and cases for a raise are all won on specifics. “I improved the process” persuades no one; “I cut the close from nine days to four” is undeniable. The difference between them is not that you did better work — it is that you wrote one of them down while you still remembered it.

What to capture

Not everything. Capture anything that took judgment or made a difference:

Accomplishments — something you shipped, fixed, grew, or turned around.
Hard problems — a difficult project and the specific thing you did about it.
Decisions you owned — a call you made under uncertainty, and how it turned out.
People moments — a stakeholder you brought along, someone you led, a conflict you resolved.
Failures and lessons — something that went wrong and what you took from it. These make some of the strongest interview answers.
Hard evidence — the number, the before-and-after, the exact thing a customer or leader said.

How to keep the record

1
Capture within a week.
The specifics fade fast. As close to the moment as you can, jot down what happened while the details are still exact — especially any number.
2
Write it in situation → action → result.
Three lines is enough: what the situation was, what you did, what changed. This is the same shape interviews want, so you are pre-building your answers. See the STAR method.
3
Keep it private and raw.
This is for you, not your manager. Because no one else reads it, you can be honest and complete — the editing happens later, when you distill it into a résumé or an answer.
4
Reread it before reviews and interviews.
When you need to make a case, the material is already there. You are selecting from a real record instead of staring at a blank page trying to remember your own year.

What a good entry looks like

One entry in a record

Q3 renewal risk. Our biggest account (~18% of revenue) flagged they were evaluating a competitor after two outages. I owned the recovery: ran the root-cause review, built a 30-day reliability plan, and presented it to their VP myself. They renewed for two years and referred us to a sister team. Detail worth keeping: their VP said the plan was “the most straight-talking thing a vendor had shown them.”

Months later, that single entry answers questions about ownership, handling pressure, stakeholder management, and communication — because the specifics were saved while they were still exact.

Common mistakes

Waiting until you need it.
Instead: By the time you are updating your résumé, the details are gone. Capture as you go — the whole value is in the freshness.
Recording vague impressions.
Instead: Keep the concrete number, quote, or before-and-after. Specificity is exactly what makes it usable later.
Only logging wins.
Instead: Save the hard projects and the failures too. What you did when something went wrong is often your most convincing material.
Treating it like a résumé.
Instead: Keep it raw and complete. The résumé is what you distill from the record — not the record itself.

From record to ready

A record of your work is the foundation everything else in career readiness stands on. It feeds your résumé, your reviews, and — turned into a small set of rehearsed stories — your interview story bank. Keep the record, and you are never starting from a blank page again.

How to Keep a Record of Your Work Accomplishments