How to Track Accomplishments for a Raise

By Peter Miller · Published August 31, 2026 · Last updated: September 20, 2026

10 min read

What did you accomplish last March? If you're like most people, you'll pause, say "a lot, actually," and then name one thing. That's the gap raise conversations fall into. 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.

How to track accomplishments for a raise isn't about being organized for its own sake. It's about giving whoever argues for you quotable proof: outcomes with numbers attached, stored somewhere you'll still have access if accounts get cut on a Friday afternoon.

Before you start a log, check your resume for free and see how much of last year actually made it onto the page. For most people the answer is a fraction. That gap is money, whether the raise lands or you search later.

Below: why memory loses calibration fights, five ordered steps to build the habit tonight, before-and-after log entries, a copy-paste template, and mistakes that turn a brag doc into a diary nobody forwards.

The log is for whoever argues on your behalf

Calibration rewards specifics, not vibes. Compensation decisions usually happen in a meeting where your manager sits with other managers and argues for a fixed pool. Whoever makes the clearest case wins the bigger share. Your manager is tracking eight people on memory. If you hand them nothing, they argue with whatever happened 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 drifts toward effort. "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.

A brag document isn't arrogant when it's outcomes, not hours. It's the same material your manager needs and can't reconstruct from scratch. Write every entry for that person, not for your future self on a nostalgic Sunday.

When you're ready to use the one-pager, pair it with how to request a raise for scheduling scripts and recap emails. The log is proof. The conversation is where you spend it.

How to track accomplishments for a raise: six steps

The system fails on effort, not design. Anything that takes fifteen minutes gets skipped by week three. These steps stay small enough that skipping feels sillier than doing them.

Step 1: Book four minutes every Friday

Put a recurring calendar block at the end of the week. Friday 4:45pm works for most desk jobs. The day matters less than the consistency. Treat that block as the only time you write entries. No "I'll catch up Sunday" spiral.

Before: "I'll remember the important stuff when review season comes."
After: A recurring "Wins log" event every Friday with a note in the description: open sent mail, write two or three entries, stop at four minutes.

Step 2: Open sent mail as your memory prompt

Your outbound email from the week is the best prompt there is. Approvals you unblocked, dashboards you shipped, threads where someone thanked you by name. Skim sent items before you write a single line from scratch.

If your role is mostly meetings, check calendar titles and Slack threads you started. The goal is external evidence, not introspection.

Step 3: Record five fields per entry

Same shape every time. Date (week ending). What changed (outcome, not activity). The number (money, time, volume, rate, headcount, or scale). Who noticed (name or team). Where proof lives (dashboard, ticket, doc, thread).

Before: "Worked on month-end close."
After: "Week ending Mar 14: closed month-end two days early by automating intercompany reconciliation; finance lead flagged it in stand-up. Proof: Feb close checklist."

Before: "Helped the new starter."
After: "Week ending Mar 14: onboarded new analyst onto reporting stack; first solo close in week three instead of usual six. Proof: onboarding doc."

Same week. Same person. The right column takes ninety extra seconds and is worth several thousand dollars in a calibration room.

Step 4: Store it outside company systems

Keep the log in a personal document, notes app, or email-to-self thread. Accounts get disabled the same day you leave. A two-year log locked on a company drive is a log you no longer own.

Don't store client names where policy restricts them, customer data, confidential financials, or screenshots of internal systems. Describe outcomes instead: "a mid-size regional insurer" carries the weight without the risk.

Step 5: Compress quarterly into a one-pager

Nobody reads a fifty-entry log. Every quarter, spend twenty minutes grouping wins into three or four themes. Lead each theme with its strongest number in the first eight words. Three bullets per theme maximum. Add one line on scope change: what you do now that wasn't in the job when you started.

Send the one-pager twenty-four hours before a compensation meeting, not during it. A manager who has read it arrives ready to agree. For timing inside a review cycle, see how to bring up a raise in a performance review .

Step 6: Convert the same entries into resume bullets

Outcome verb first, number early, tool named, scope at the end. Log entry: "Built self-serve variance dashboard; ad hoc requests 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."

I've seen the same weekly habit turn a thin resume into a raise file and an interview file without rewriting from memory. The log is the single source of truth.

WINS LOG - week ending [date]

Entry 1
- What changed: [outcome, not activity]
- Number: [metric or scale/frequency]
- Who noticed: [name or team]
- Proof: [dashboard / ticket / doc / thread]

Entry 2
- What changed:
- Number:
- Who noticed:
- Proof:

Entry 3 (optional)
- What changed:
- Number:
- Who noticed:
- Proof:

QUARTERLY ONE-PAGER (copy themes from above)
Theme 1 - [strongest number first]: [3 bullets max]
Theme 2 - [number]: [3 bullets max]
Scope change: [duty not in original JD]
              

Edge case: you already lost the year

Before: Trying to reconstruct twelve months from a blank page in December.
After: Rebuild one quarter from sent mail, calendar, tickets, and closed pull requests in an hour. Then start the Friday habit so you never do that again.

Edge case: team win, not solo win

Before: "Led the entire ERP rollout."
After: "Owned the data migration workstream of the five-person ERP rollout; cut manual entry from 40 hours to 6 per close cycle." Honest scope beats over-claiming.

Habits that make a log useless

Logging effort instead of outcomes. "Spent three weeks on the migration" tells your manager nothing they can quote.

Keeping it only on company systems. One access revocation and the whole record is gone on the day you most need it.

Writing monthly instead of weekly. By week four you've lost the numbers and you're summarizing a summary.

Sending a fifty-line document to your manager. Rewriting is friction. Friction kills advocacy. Compress before you share.

Only logging wins. A note on what you learned from something that went badly makes the whole document more credible.

Before: Vague weekly notes, company drive only, never converted to a one-pager.
After: Five-field Friday entries, personal storage, quarterly compression, resume bullets from the same source.

The log pays even if the raise doesn't

Your entries are already ninety percent of resume bullets. Upload the updated file to HireFlow's free ATS resume checker and confirm parsers extract the tools and metrics you logged. Naming the actual system matters because recruiters and parsers both search for them.

When you're applying as well as asking internally, generate a cover letter that pulls one theme from your one-pager. Don't paste the raise doc verbatim. External applications need a different frame.

Create the Friday block now

How to track accomplishments for a raise comes down to four minutes every Friday, five fields per entry, personal storage, quarterly compression, and the same lines on your resume. Memory keeps six weeks. The log keeps the year.

• Create the recurring calendar block before you close this tab.
• Write three entries from this week using the copy-paste template.
• Calendar twenty minutes at quarter-end to build the one-pager.

Then see what's already on your resume. Run a free ATS check and compare it to your log. The gap is what you fix next.