How to keep a work record you can use in reviews and interviews

Record a change, not everything you did

“Attended the planning meeting” tells you where you were. It does not tell you whether your involvement helped. “Spotted that the launch plan had no owner for the customer handover, then agreed an owner and a check-in date” gives you something you can return to.

A useful entry answers: what was different because you did this work? The answer might be a decision clarified, an error caught, a customer question resolved or a process made easier to use. It need not be a dramatic business result.

Routine work counts too. If you kept an essential service running, describe what you maintained and how you know it was maintained. Do not turn reliable delivery into a fictional transformation just because “changed the business” sounds more impressive.

Choose moments you would otherwise struggle to explain later. A handful of specific examples will usually serve you better than a diary of every task. Your task tracker can remain a task tracker.

Use four lines and a date

For each entry, note the date and use these four prompts. This is a practical editorial template, not a validated assessment tool or a promise of a better rating.

Situation: What problem, responsibility or constraint were you dealing with? Keep enough context that your future self can understand it without reopening the whole project.

My contribution: What did you personally do? Be precise about the action, judgement or coordination. Name shared work as shared work rather than claiming the team's whole result.

Observed result: What happened, and what remains unknown? Include a number only if it has a reliable source and a meaningful comparison. “Not yet checked” is an acceptable answer.

Evidence and next check: Where can you verify the account within an approved work system? What would you check later to find out whether the change lasted? A pointer is often enough; you do not need a copied file.

Keep entries short enough that you will actually make them. You can expand a strong example when you need it. Writing a polished case study every Friday is an easy way to abandon the habit by the second week.

A worked example: improving a request handover

Imagine Alex works in a service team. Requests sometimes reach the next person without the information needed to act. Alex creates a short handover checklist with two colleagues and tries it on a small batch. This is a fictional example, not a reported customer result.

Their first note reads: “Improved the handover process.” That sounds useful, but leaves almost everything unexplained. Here is a more usable entry.

Situation: The receiving colleague had to ask for missing information before starting some requests. We did not yet have a consistent way to check the handover.

My contribution: I reviewed recent requests, drafted a checklist and revised it with two colleagues who receive the work. The team lead chose the trial scope; I did not lead the whole project.

Observed result: In the six trial handovers I checked, the receiving colleague could start five without another information request. One still needed clarification. We have not established whether this saves time across the team.

Evidence and next check: Trial notes and checklist version in the approved team workspace. Ask the receiving colleagues after another week whether the checklist remains useful and whether any missing fields recur.

This entry does not invent a percentage improvement, revenue saving or company-wide result. It gives Alex a credible account of their contribution and a clear boundary around the evidence. If the trial later fails, the same record helps explain what they learned and changed.

Do not force a number into every example

“Reduced processing time by 30%” needs a defensible before-and-after comparison. A feeling that things moved faster is not that comparison. Neither is one quick case compared with the slowest case you remember.

When reliable measures exist, record their source, period and limits. When they do not, describe an observable outcome: a decision made, a document accepted, a problem identified before release, or feedback from the person using the work. Separate their feedback from your interpretation.

You can also record an intermediate result. “The proposal was accepted for a trial; the trial has not started” is honest and useful. A pending result does not erase the work that got the proposal to that point.

For help turning evidence into readable application language, use our guide to CV mistakes that hide good experience. The record gives you material; it does not require every entry to become a CV bullet.

Keep the credit accurate

A team result and your contribution are related, but they are not interchangeable. “We delivered the rollout” can be true while telling a reviewer very little about your role.

Try: “The team delivered the rollout. I mapped the handover dependencies and coordinated checks with the two receiving teams.” If someone else designed the solution or held the final decision, retain that distinction.

Record useful collaboration as work in its own right. Helping a colleague spot a risk, making an ambiguous request answerable or arranging a missing decision can matter. Describe what you did and why it helped rather than borrowing somebody else's outcome.

UC Davis's self-evaluation guidance^[1] recommends specific, honest accounts of contributions and keeping records through the year. Treat that as support for accurate preparation, not permission to present every shared success as your own.

Keep a pointer, not a private archive of work files

Use a place approved by your employer for this information. Work records can contain confidential business details, customer information or personal data about colleagues. A personal note-taking app, private email account or new AI service is not automatically an appropriate destination.

Where possible, write a short, non-sensitive description and point to the original in the approved system. Do not copy customer messages, employee assessments, screenshots or internal datasets simply to make the entry feel well supported.

Before moving to another employer, check what you are allowed to retain. The ability to access a file today does not establish permission to keep it after leaving. You may be able to write a general account of your skills without retaining the underlying material; follow the relevant workplace rules.

If you cannot record an example safely, leave out the sensitive detail or ask which approved method to use. A career record is not worth creating a second, uncontrolled store of other people's information.

Review the record before you need to perform from it

Choose a brief review point that fits your week. Look for an entry worth adding, an unfinished result worth checking and an example whose meaning has changed. The aim is a usable record, not a streak you must protect.

Before a performance review, select a few examples relevant to your actual responsibilities and agreed expectations. Grouping them by those expectations is usually clearer than handing over a long chronological list.

Bring uncertainty and development needs too. “This trial did not work; here is what I changed afterwards” can be a useful discussion. The record should help you understand your work, not conceal everything that did not succeed.

If you are preparing a progression conversation, our guide to what to bring when asking for a promotion helps you connect examples to the scope of the next role. Doing good work and meeting a particular promotion standard are not necessarily the same thing.

Adapt an example to the question you are answering

For a review, explain the contribution in relation to your current role. For a CV, choose the details relevant to the job you want. For an interview, give the listener enough context to understand your choices, then explain the action and outcome.

The National Careers Service's STAR guidance^[2] uses situation, task, action and result to structure examples. Your work record can supply the raw material without becoming a script you repeat regardless of the question.

Practise explaining one example aloud and notice where you become vague. If “I supported the team” hides your actual action, clarify it. If the result is not known, say what you observed and what you would still need to check. Our guide to interview preparation without memorising a script takes that approach further.

Start with one entry, not a perfect system

Think of something useful you worked on this week. Write the situation, your part, the observed result and an approved evidence pointer. If the result is still pending, add the next check instead of filling the gap with optimism.

A record cannot make an unfair review fair or guarantee recognition. It can make your own account less dependent on last-minute memory. That is enough reason to keep it small, accurate and ready to use.