How to write what you did before a performance review

The meeting is too late to remember the year

Most people open a review and can name the last three weeks. The quarter before that is a blur. Your manager is in the same position, with more people to recall. Whoever brings a dated list sets the map.

The list is not a speech and not a demand for a raise. It is evidence: what changed, for whom, and how you know. Pay talks later can use the same page. A review with no page becomes a conversation about personality.

Start even if the review is months away. Ten minutes on Friday beats a Sunday night reconstruction. Reconstruction invents credit and forgets the work that actually moved a number.

Write results, not tasks

“Attended stand-up” and “answered email” are tasks. A result names a change: the queue dropped, the error rate fell, a deadline moved in, a customer stopped escalating. If you cannot say what changed, it may still have been necessary work — put it in a second list, not the first.

Use a scale when you have one. People, tickets, dollars, days, or error counts. “Helped the team” does not survive a follow-up. “Closed 40 billing tickets in March that had been open more than two weeks” does.

Name your part. “We launched” hides whether you wrote the plan, ran the rollout, or sat in the room. Managers cannot promote a “we.” They can discuss a person who owned a piece.

• What changed
• The scale, if you have one
• Your part, not the whole team’s
• The month it happened

Keep a weekly note, not a diary

One file is enough. Each Friday, three lines: finished, stuck, next. Finished is a result. Stuck is a fact with a date, not a complaint about a person. Next is what you will do if nobody changes the priority.

Link the proof while you remember where it lives: a ticket, a doc, a dashboard, a sent email. Do not paste secrets, customer names, or pay data into a personal note if your company forbids it. A ticket id and a one-line outcome are usually enough.

If a week has no finished line, write that. Empty weeks are information. They show a stretch of support work, waiting, or a priority that kept moving. You will need that context when someone asks why the year looks thin.

Sort the page the week before

Pull six to ten items, not forty. Lead with the ones that match the goals you were given, not the ones you enjoyed. If the written goals and the real work diverged, say so with dates: the goal was X, the work that arrived was Y, here is what you did with Y.

Put one line under each item: the before and the after. “Invoice errors were about 6% in January; after the checklist, March was about 2% on the same report.” If you do not have a before, do not invent one. Say “we did not have a baseline.”

Mark anything you want as a next-cycle goal, separate from credit for the past. Mixing “please notice me” with “please change my job” makes both weaker. The review can record the past. A later meeting can talk about level and pay.

Work that does not have a clean number

Coordination, training, and cleanup often have no dashboard. Describe the load and the substitute. “New hires used to wait on me for account access. I wrote the steps; the last four people finished it without a same-day ping.” That is a result.

If the work prevented a failure, say what would have broken and how you know it was close. A single anecdote is weak. Two dated saves, or a drop in repeat questions, is stronger. Do not claim a disaster you cannot point at.

Shared credit is still credit. Write “with A, I owned the customer list; A owned the mail merge.” Hiding partners looks like inflation when the manager asks them. Naming partners makes the story easier to check.

If the form only wants a rating

Many forms ask you to pick “meets” or “exceeds” and leave a small box. Put three results in the box, each one sentence, with the month. Do not fill the box with adjectives. Adjectives cannot be checked.

If you disagree with a rating, ask what evidence would have made it different, and by when that evidence is reviewed. “I feel undervalued” does not create a next step. “The March error drop was not in the packet; can we add it before calibration?” does.

A rating is not a promise of a raise. Some companies split the performance meeting and the pay meeting. Ask which meeting decides pay, and what date that is. Bring the same page to both.

What this page is not

This is a way to remember work. It is not a script that forces a promotion, and it is not legal advice about a disputed review. Your company’s form and calendar still rule.

Do not store other people’s performance notes, medical details, or anything you were told not to copy. If a review involves harassment or safety, use the company’s reporting path. A brag list is the wrong tool for that.

After the meeting, add one line: what was agreed, and the date of the next check. A review that ends only in a feeling will be just as blurry next year.