How do I keep an accomplishment log for performance reviews?

Record each accomplishment the week it happens with three parts: what you did, what measurably changed, and who noticed. At review time you filter the log to the entries that match what your organisation actually rewards, rather than reconstructing a year from memory under deadline.

The review problem this solves

Self-evaluations are usually written in a two-hour panic, covering twelve months, from memory. Memory is heavily weighted toward the last six weeks, so the strongest thing you did in March quietly does not make the document.

A log fixes the recall problem rather than the writing problem. If the entries exist, the review becomes an editing task — filter, order, cut — and editing under deadline is a far more reliable activity than remembering under deadline.

A format that stays useful a year later

Keep each entry short and make it answer the question a reviewer will actually ask, which is not "what were you busy with" but "what is different because you were here".

Date, so entries can be filtered to the review period without guesswork.
The work, in one line.
The change: the measure that moved, in its own units, with the before value as well as the after. "Cut deploy time" is unusable; "cut deploy time from 40 minutes to 6" survives scrutiny.
The evidence: link the ticket, the dashboard, the doc, the thread where somebody said it helped.
Scope, honestly stated. Say "led" when you led and "contributed to" when you contributed. An overstated entry is the one that gets challenged in the room.

Log everything; filter at review time

Do not pre-judge entries as you write them. The unglamorous work — the flaky test suite you fixed, the runbook you wrote, the person you unblocked twice a week — is exactly what gets forgotten and is often what a manager most wants evidence of.

Filtering happens once, at review time, against the criteria your organisation actually uses. Those criteria change; the underlying record does not, which is why the record is the thing worth keeping.

The same log is your resume source

A review document and a resume are two edits of one underlying record, which is why keeping a separate "resume file" is duplicated effort that goes stale.

CareerDiary is our product, and this is what it is for: entries in one place, and resume bullets generated from those entries rather than invented. The check that matters is that every bullet on the finished resume traces back to something you wrote at the time.

Frequently asked questions

What is the difference between an accomplishment log and a brag document?

Mostly the audience you have in mind. An accomplishment log is usually kept with performance reviews in view, so entries lean toward what the organisation measures; a brag document is broader and more personal. The format is close enough that one record can serve both.

How far back should I go if I am starting now?

Do not try to reconstruct a year. Spend twenty minutes on the highlights you genuinely remember, mark them as reconstructed so you do not later mistake them for contemporaneous notes, and start writing weekly from today.

What if my manager already tracks my work?

Their record is built for their purposes and you usually lose access to it when you leave. Keep your own regardless — and it should include the things a manager cannot see, like the help you gave people outside your team.

How do I write an entry for work that failed?

Record it with the same three parts, and add what you changed as a result. A project that was killed with a clear account of what you learned is legitimate review material, and it is far more credible than a log in which everything worked.