Keep a Work Accomplishment Log You Can Actually Use

When a performance review or interview arrives, recent work is usually easier to remember than something valuable you did several months earlier. You may recall being busy while struggling to explain what improved because of your contribution.

A short accomplishment log gives you a place to keep those examples. It can also help you notice work you want to do more often and skills you need to develop.

Capture the problem and your contribution

For each entry, write down the date, the situation, what you did, and the result you can support. Add a link or reference to evidence when appropriate.

An entry might read: "The monthly handoff often arrived with missing fields. I created a checklist with the receiving team and tested it on the next two handoffs. Both arrived with the required fields completed. Revisit after another month."

That example is more useful than "Improved team communication." It identifies a problem, describes your action, and keeps the result within what you observed.

Separate activity from outcomes

Attending a meeting or writing a document may be necessary work, but it does not automatically explain the value of that work. Ask what the activity enabled: a decision, a clearer process, a resolved issue, or a deliverable someone used.

When an outcome is still unknown, say so. "Draft submitted; awaiting customer feedback" is an accurate entry. You can add the result later.

Use numbers when you have a reliable basis for them. If you estimate time saved, record how you estimated it and the period involved. Avoid converting a single promising example into a broad claim about ongoing performance.

Include collaboration and less visible work

Useful contributions are not always dramatic launches. You may have helped a new colleague become independent, documented an awkward process, or spotted an error before it reached a customer.

Record what you contributed and who else was involved. If a team delivered the result, explain your role without claiming the entire outcome. "I prepared the analysis used in the team's proposal" is both specific and fair.

Also note lessons from work that did not go as planned. A failed approach can provide a strong example of how you gathered feedback and changed your decision.

Keep the log brief and safe to use

Choose a location permitted by your workplace and set aside five minutes at the end of the week. One or two useful entries are enough. A system that requires extensive writing after every task may be difficult to maintain.

Do not copy confidential material into a personal account. Keep sensitive details in approved systems, and use general descriptions when preparing examples for external applications. A reference to a document can be sufficient when you are authorized to access it.

If you leave a role, follow the organization's rules about information you may retain. The purpose is to describe your experience accurately, not to build an archive of company files.

Turn entries into a useful conversation

Before a review, choose a few examples that relate to your responsibilities and goals. For each, explain the situation, your action, the observed result, and what you learned.

Use the log to ask better questions too: "I have taken on more analysis work this quarter. Which capability would help me contribute at the next level?" This connects past work to a concrete development discussion.

Start with one recent contribution while the details are fresh. Keep it short, attach the evidence where permitted, and add a reminder to revisit any result that is still unfolding.

Put this into practice

Three things to keep

• Record your specific contribution and the result you can support.
• Credit collaborators and distinguish observed results from estimates.
• Store work information only where your organization permits it.

Try a five-minute log entry

Choose one recent piece of work and fill in these lines in an approved location:

• Situation: What needed attention?
• My action: What did I personally do, and with whom?
• Observed result: What changed? If it is too soon to tell, say so.
• Evidence and follow-up: Where can the result be checked, and when should I revisit it?

Example: "Two colleagues were using different versions of an instruction sheet. I checked the process with them and consolidated their corrections into one shared document. Both confirmed which version to use. The revised sheet and their feedback are in the team folder; I will ask next month whether anything is still unclear."

Reflect: What does this example show about how I contribute or learn, beyond simply staying busy?

Keep exploring: Career Capital: How to Build Skills That Create More Opportunity connects these examples to longer-term skill development.