Consider a senior analyst whose work has grown from producing a report to defining the metrics other teams use to make decisions. Their next scheduled review is still some time away. How often should you get a raise in a situation like that? There is no universal interval: the useful decision is when to raise the question, based on changed responsibilities, evidence of impact, and how pay decisions are made where you work.
A raise conversation can happen without a promotion, and a promotion case may involve expectations beyond your current work. Before choosing a date, work through the questions below. Each points to a different next action.
Has your work changed materially since your pay was last discussed?
Look for a sustained change in what you own, not just a demanding week. The analyst might now define metrics, resolve disagreements about them, and be the person other teams consult when a number looks wrong. Those responsibilities describe a different scope from producing the original report.
If your scope has expanded and stayed expanded, ask your manager for a dedicated conversation about responsibilities and compensation. Bring a short account of what changed and when. If the work was temporary coverage or a one-off assignment, document it and ask what sustained scope would justify revisiting pay.
Can you show what your expanded work changed?
Effort deserves recognition, but a pay discussion is clearer when someone else can see the contribution. Keep examples of decisions you made, problems you resolved, and the effect on the work. The analyst could point to clearer metric definitions and explain how colleagues used them, without claiming a business result they cannot verify.
If you can support your case, summarize two or three examples before the conversation. If the evidence is thin, start a lightweight record now. After meaningful work, note the problem, your decision, who used the result, and where you could later verify it. Ask your manager which outcomes would make the case stronger while you build that record.
Do you know when compensation decisions are made?
Your employer may have a regular review process, but its timing and flexibility are specific to your workplace. Ask your manager when recommendations are prepared and whether a change in responsibilities can be discussed outside that cycle. This gives you a practical deadline for presenting evidence rather than assuming the review meeting is when the decision begins.
If an earlier request is possible, this checklist for an out-of-cycle raise explains how to prepare your case.
If the window is approaching, share your case early enough for your manager to examine it. If it has passed, ask when the next decision can be considered and what information they need beforehand. Record the answer so the follow-up has a date and a clear purpose.
Has your manager told you what is missing?
A response such as “keep doing what you’re doing” does not tell you whether the obstacle is timing, scope, evidence, or something else. Ask what would need to be true for a pay change to be supported, and request examples of the standard being applied to your role. You can also ask who makes the decision and when your manager expects to revisit it.
If the answer identifies a gap you can influence, agree on the work or evidence to review next. If no criteria or timing are available, document the conversation and decide what other information you need about your options. Repeatedly asking the same question without learning what blocks the decision gives you little to act on.
What should you bring to the next conversation?
Prepare a brief record of your original scope, what you own now, and examples that show the change. Include dates for major shifts and separate observed outcomes from goals. Do not put confidential company documents or private customer information into a personal tool; record your contribution in your own words.
A small, current record makes the discussion more specific whenever the right time arrives. Build your work evidence in ImpactLogr before you need to assemble a raise case from memory.