A review asks what you contributed over the past few months. You remember being busy, but the useful examples have blurred together. A small work log can preserve the evidence while it is still easy to find.
This is a record for reflection and discussion, not permission to copy confidential material into a personal account.
Record the problem and your contribution
For each entry, write what the team was trying to achieve and what you actually did. Distinguish your contribution from the group’s overall result. “Prepared the comparison used in the venue decision” is more precise than claiming sole responsibility for a successful event.
Use ordinary language. You can refine the wording later when you know the audience and purpose.
Link to evidence you are allowed to retain
Note the location of an approved document, a delivered output or a piece of feedback. Follow workplace rules for access, retention and confidentiality. If you cannot keep a document, a permitted high-level description may be sufficient.
Do not invent metrics because a numerical result sounds stronger. If an outcome was not measured, say what was completed and what evidence exists.
Include what changed your approach
A useful log also records a mistake corrected, a new skill practised or a question you learned to ask earlier. This helps a development conversation move beyond a list of wins.
Keep the entry brief enough that you will maintain it. A few minutes after a milestone can be more effective than reconstructing an entire quarter.
Use the log to choose examples
Before a review or career conversation, select entries relevant to the discussion. Explain the context, action and observed outcome without presenting a team achievement as an individual feat.
Our career-conversation guide can help turn the record into questions about the work you want to do next. The log’s value comes from accuracy and continuity, not from making every week sound exceptional.

