In an office, a manager absorbs a certain amount of context about your work just by being nearby — the late night before a launch, the meeting where you talked a client down from cancelling, the extra project you quietly picked up. Remotely, none of that reaches them unless you put it there yourself. This is the single biggest reason remote employees get passed over for raises they've earned: not because the work wasn't good, but because the case for it was never actually made.

Build the record before you need it

Waiting until review season to remember your wins is too late — by then, most of the detail is gone and what's left sounds vague. A running document, updated in a few minutes every couple of weeks, changes this. Keep it simple:

  • What you did, in one line.
  • What changed because of it — a number if you have one, a specific outcome if you don't.
  • Who else was affected or would remember it, in case you need to reference it later.

By the time a review comes around, you're pulling from a record instead of trying to reconstruct six months from memory.

Make the ask about value, not tenure

"I've been here two years and haven't gotten a raise" is a statement about time. It doesn't answer the question a manager actually has to justify upward, which is why the business should spend more on you now than it did before. The stronger version connects directly to impact: "Over the last six months I took on X, which resulted in Y, and I'd like to talk about adjusting my compensation to reflect that."

A manager can't advocate for a raise they don't have a specific reason to write down.

Time it around decisions, not calendars

Formal review cycles matter, but they're not the only moment that counts. A raise conversation lands better right after you've delivered something visible and successful than it does six months later when the memory of it has faded for everyone but you. If you shipped something significant, that's often a better moment to raise the conversation than waiting for the next scheduled review.

Know your market number before the conversation

Remote roles often draw from a wider, more competitive pool of comparable salaries than a single local office would, which is useful information going into a negotiation. A specific, sourced number — from a salary survey for your role and experience level, not a guess — gives the conversation something concrete to anchor to, rather than leaving both sides negotiating from a vague sense of what feels fair.

If the answer is no

Ask what specifically would need to be true for the answer to be yes next time, and write it down. A vague "keep doing great work" isn't useful. A concrete target — "own this initiative through launch," "hit this specific metric" — gives you something to point back to at the next conversation, and makes clear whether the door is actually open or just being kept politely shut.