9 min read
Ask anyone what they achieved last March and watch what happens. They'll pause, say "a lot, actually," and then name one thing.
That's the whole problem. Knowing how to track accomplishments for a raise isn't about being organised for its own sake. It's that pay decisions get made on whatever your manager can remember and defend in a room you're not in, and memory reliably keeps the last six weeks and drops the rest. Four minutes a week fixes it.
The same log does double duty. Before you start one, run your current resume through the free ATS resume checker and see how much of last year actually made it onto the page. For most people the answer is a fraction, and that gap is money.
Quick Wins
- Put a 4-minute recurring block in your calendar for Friday afternoon. Do it now.
- Write this week's three entries before you close the laptop today.
- Go back through your sent mail for one month and mine it for what you already forgot.
Why memory loses you money
Compensation decisions usually happen in a calibration meeting. Your manager sits in a room with other managers and argues for their people against a fixed pool. Whoever makes the clearest case wins the bigger share.
Your manager is running on memory too, and theirs is worse than yours, because they're tracking eight people. If you hand them nothing, they argue for you with whatever happened in the last month and a general sense that you're solid. Solid loses to specific every time.
There's a second cost. When you're asked in a review what you achieved, an unprepared answer tends toward effort rather than outcome. "I've been really focused on the migration" is what people say when they can't remember the number. It sounds like less than it was.
The log isn't for you. It's for whoever has to argue on your behalf. Write everything with that person in mind.
How to track accomplishments for a raise: the four-minute Friday
The system fails on effort, not on design. Anything that takes fifteen minutes gets skipped by week three. So keep it small enough that skipping feels sillier than doing it.
- Fixed slot, every week. Friday, 4:45pm, recurring calendar block. The consistency matters more than the day.
- Open two windows: your log, and your sent mail for the week. Sent mail is the best memory prompt there is.
- Write two or three entries. Not ten. If nothing notable happened, write "maintenance week" and close it. Some weeks genuinely are.
- Stop at four minutes. Seriously. The value is in fifty weeks of entries, not in one beautiful one.
Once a quarter, spend twenty minutes compressing. That's where the log becomes the one-pager, and it's much easier than trying to write one from a blank page in December.
Do this now: create the calendar block before you read the next section. It takes eleven seconds and it's the only step people skip.
The five fields to record
Every entry, same shape. It keeps the writing fast and it forces the detail that matters later.
| Field | What goes in it | Why it matters later |
|---|---|---|
| Date | Week ending | Proves the work sits inside the review period |
| What changed | The outcome, not the activity | Becomes the verb in your resume bullet |
| The number | Money, time, volume, rate, or headcount | The thing your manager quotes in calibration |
| Who noticed | Name of the person or team who said so | Gives your manager a corroborating source |
| Where the proof is | Dashboard, ticket number, thread | Lets you rebuild the detail six months on |
The same week, logged two ways
Take a mid-level financial analyst. Here's a real week written badly and written usefully.
| Useless entry | Useful entry |
|---|---|
| Worked on month-end close. | Closed month-end two days early by automating the intercompany reconciliation; Priya flagged it in the finance stand-up. Proof: the Feb close checklist. |
| Helped the new starter. | Onboarded Kwame onto the reporting stack; he ran his first close solo in week three instead of the usual six. Proof: my onboarding doc. |
| Lots of ad hoc requests. | Built a self-serve variance dashboard; ad hoc requests from the commercial team dropped from about 12 a week to 3. Proof: the Looker board. |
Same week. Same person. The right column takes ninety extra seconds to write and is worth several thousand dollars in a calibration room.
Where to keep the log
One rule above all: keep it somewhere you'll still have access to if you leave at short notice. Accounts get disabled the same day, and a two-year log locked inside a company drive is a two-year log you no longer own.
- A personal document in your own cloud account. Simplest, works everywhere.
- A note in your phone's notes app. Best if you write entries in odd moments rather than at a desk.
- An email to yourself each Friday. Searchable, dated automatically, hard to lose.
What not to put in it: client names where policy restricts them, customer data, confidential financials, screenshots of internal systems, anything covered by an NDA. Describe the outcome instead. "A Fortune 500 retail client" carries the same weight as the name and creates none of the risk.
You want the log to be entirely about your own contributions and results. Kept that way, it's yours to take with you, and nobody can reasonably object to it.
Turning it into a one-page case
Nobody reads a fifty-entry log. Your manager needs something they can forward without rewriting, because rewriting is the friction that kills advocacy.
Compress it like this:
- Group into three or four themes. Ownership, delivery, efficiency, people. Whatever fits your role.
- Lead each theme with its strongest number. The number goes in the first eight words, not the last.
- Keep three bullets per theme, maximum. Everything else stays in the log as backup.
- Add one line on scope change. What you do now that wasn't in the job when you started. This is the line that justifies a raise rather than a good review.
- Close with the ask. One sentence, a specific number or range.
Send it 24 hours before the meeting, not during it. A manager who has read it arrives ready to agree; a manager handed paper across a table skims the first bullet and nods. For the conversation itself, the raise conversation guide has the scripts, and bringing it up in a performance review covers the timing.
Turning it into resume bullets
This is the part that pays whether or not the raise lands. Your log entries are already 90% of a resume bullet; they just need reordering.
The conversion is mechanical: outcome verb first, number early, tool or system named, scope at the end.
Log entry: Built a self-serve variance dashboard; ad hoc requests from the commercial team dropped from about 12 a week to 3.
Resume bullet: Cut ad hoc reporting requests 75% by building a self-serve variance dashboard in Looker for a 40-person commercial team.
Naming the actual tool matters more than people expect, because parsers and recruiters both search for them. Keep the phrasing plain and the file single-column so nothing gets scrambled on the way in.
Once you've moved a quarter's worth across, upload the file to the free ATS resume checker and check what a parser extracts. If you're applying as well as asking, the cover letter generator will pull the same themes into an application, and the job match score shows which of your logged wins a specific posting actually cares about.
Edge cases
Your work genuinely has no metrics
Plenty of jobs don't generate numbers. Use scale, frequency, and consequence instead: how many people or accounts, how often, and what breaks without you. A school administrator who cut enrolment processing from three weeks to five days has a number, even though nobody tracks revenue.
It was a team win
Log your specific part and say so. "Owned the data migration workstream of the five-person ERP rollout" is honest and stronger than claiming the whole project. Overclaiming is the fastest way to lose a manager's trust in the rest of the document.
You're new in the job
Start on day one, and log the baseline as well as the wins. Recording what the process looked like when you arrived is how you prove improvement six months later, and it's the one thing you can never reconstruct afterwards.
Client work under strict confidentiality
Anonymise by sector and scale. "A mid-size regional insurer" and "a nine-figure retail account" both convey what matters without naming anyone. Keep it that way in the log itself, not just in the version you share.
You already lost the year
Reconstruct one quarter, not twelve months. Sent mail, calendar, ticket history, and closed pull requests will give you most of it in an hour. Then start the weekly habit so you never do that again.
Mistakes that make a log useless
- Logging effort instead of outcomes. "Spent three weeks on the migration" tells your manager nothing they can use.
- Keeping it only on company systems. One access revocation and the whole record is gone on the day you most need it.
- Writing it monthly. By week four you've lost the numbers and you're writing a summary of a summary.
- Making it too long to read. A fifty-line document sent to a manager is a document nobody forwards.
- Only logging the wins. A note on what you learned from something that went badly makes the whole document more credible, and managers notice that.
- Never converting it. A log that never becomes a one-pager or a resume bullet is a diary. Schedule the quarterly compression.
The short version
- How to track accomplishments for a raise comes down to four minutes every Friday, forever.
- Five fields per entry: date, what changed, the number, who noticed, where the proof is.
- Compress quarterly into a one-pager your manager can forward without editing.
Do this today: create the recurring calendar block, then write three entries from this week before you log off.
Then put the same material where it also earns. Check your resume for free and see how much of your last year is actually on the page.
Read more
- How to ask for a raise — where the one-pager gets used.
- Asking for a raise after being denied — what the log gives you for round two.
- How to show career growth without promotions — when the scope grew but the title didn't.
Frequently asked questions
Weekly, at a fixed time, in about four minutes. Monthly logging loses the detail that makes an entry persuasive, and quarterly logging turns into an hour of reconstruction where you quietly drop half of what you did.
Record scale, frequency, and consequence instead. How many people or accounts were affected, how often the thing happens, and what would have gone wrong without you. A support lead who cut a recurring escalation from weekly to monthly has a number even if nobody measures revenue.
Somewhere you will still have access if you leave suddenly, such as a personal document or a note in a personal account. Keep it to your own contributions and outcomes, and leave out client data, confidential documents, and anything covered by an NDA.
Cut it to one page with three or four themes, put the strongest number in the first line of each theme, and write it so your manager can forward it without editing. The test is whether it could be pasted into a justification form as it stands.
It is only arrogant if it reads like a diary of effort. A log of outcomes with numbers attached is the same material your manager needs to argue for you in a calibration meeting, and they cannot produce it from memory any better than you can.