Document recent scope and contributions, connect them to your role, and request a discussion about compensation and the process for a decision.
Choose examples showing sustained responsibility, not only a busy week. For each, note the task, your action, the result or standard met, and evidence you can share. Consult the performance cycle and compensation policy if available. If the organization uses salary bands, ask how your role is positioned and which outcomes matter at the next level. A manager may not control the budget, so ask who makes the decision and what documentation they need. If a change is not possible now, request criteria and a review date rather than relying on a vague promise.
Preparing a raise request: what to compare
A practical sequence
- Choose a review date and collect your role description, recent feedback, and work records from the period being discussed.
- Select two or three contributions that changed scope, quality, cost, risk, revenue, or service; separate your part from team results.
- Compare the role and location with current wage evidence, noting that group data do not set an individual raise.
- Ask for a compensation review, name the evidence and researched range, and agree on criteria/date if the answer is no.
Worked example
Task: Request a review after an office coordinator’s duties expand to include weekly staffing schedules and a monthly service report. The worker’s records show the report turnaround falling from 18 to 12 business days over six months after they built a shared checklist. This fictional outcome is illustrative and should be replaced with verified records.
First output / attempt: “I’ve been here three years and took on more work, so I deserve a 15% raise.”
Mistake / weakness: Tenure and a percentage do not establish the scope, quality, or level of the work; the candidate has not asked how the company evaluates compensation changes.
Human correction: The coordinator checks the written internal band for Senior Coordinator ($62,000–$70,000 in this fictional company) and current feedback. Their current salary is $60,000. They ask to discuss $66,000, a $6,000 (10%) increase, and say: “My recurring scope now includes schedule coordination and the monthly report. The documented turnaround moved from 18 to 12 business days after I introduced the checklist. Could we review whether the role is now aligned with the Senior Coordinator band, and what evidence you need to decide on $66,000?” The band and amounts are invented for this example, not BLS data.
Quality check: The employee verifies the six-month comparison and confirms the checklist was their contribution, not a team-wide claim. They separate the internal band from BLS occupation estimates, which are broad group context, and bring only work records they are permitted to share. The 10% request is not a rule or a guaranteed raise.
Final usable result: The manager cannot approve a change that quarter but agrees the role may fit the higher band and names a review date six weeks later. The employee requests the required evidence and decision owner in writing, then prepares those records. The usable outcome is a dated process—not an assumed approval or an open-ended promise.
A beginner exercise
Input: One review period, your role description, two feedback records, and three verifiable contributions. Steps: For each contribution record task, your action, evidence, outcome, and scope; compare the role to current wage data; choose a researched ask and private minimum; rehearse the request and a “not now” response. Expected output: A one-page evidence dossier with a filled row (date, recurring task, your action, verifiable source, result, and context) plus a 3-sentence meeting opener. After the meeting, draft a recap naming the agreed owner, criterion, and date; use only commitments the manager confirmed. Retain: The records you are allowed to keep, official wage source/date, meeting notes, and agreed criteria/follow-up date. Never copy confidential company data to personal storage.
Measure the result, not just the effort
Before the meeting, count how many claims have a source, how many show your own contribution, and which scope changes are ongoing. Track research and preparation time separately. Score evidence, role match, and request clarity 0–2; no score predicts approval. Afterward record whether you received a decision, criterion, owner, and date.
Continue with a related example
accounting coordinator salary negotiation provides a related example; 3d designer negotiation scripts is useful for the next decision. Adapt only what matches your context.
Frequently asked questions
When is the best time to ask for a raise?
Use a scheduled review or a moment when your evidence is current, but first learn the organization’s budget and approval cycle. Timing improves preparation; it does not guarantee a decision.
How much should I request?
Use the role’s responsibilities and comparable current data to define a range. BLS occupational estimates describe groups, not one person’s value; keep your private minimum separate from the opening request.
What if my manager says no?
Ask whether the issue is readiness, budget, timing, or role classification. Request one measurable criterion and a date to revisit it. If the answer stays vague, decide how long you are willing to wait and compare other options.
Collect evidence before the meeting
Review your current job description, the last performance review, and any written goals. Create a short contribution log with date, task, your role, result, and source. Sources might be a project record, quality report, customer feedback, or a manager-approved milestone. Protect confidential information and avoid using client data in a personal file. Distinguish work you led from work the team delivered; a raise case becomes stronger when ownership is precise.
Look for changes in scope, not just busyness. Did you take responsibility for a process, train colleagues, handle a new customer segment, or perform duties associated with a higher level? Explain why the change matters to the role. If you use a wage benchmark, align occupation, geography, level, and date; BLS OEWS estimates are useful context but cannot establish what your employer must pay. The central question is whether your current compensation and title reflect the role you are actually doing.
Request a decision process, not a vague promise
Ask for a meeting with your manager using a direct note: “I’d like to review how my current responsibilities align with my compensation and understand the process for an adjustment.” Bring one page of examples and your supported target. If the employer cannot decide in the meeting, ask who decides, what evidence is needed, and when you can revisit it. If the answer is a timing constraint, make the next date explicit. A verbal “we’ll see” should not become a commitment in your notes.
Prepare for different answers
If the answer is yes, confirm amount, effective date, and whether other terms change. If the answer is partial, compare it with your stated goal and ask if the gap is reviewable later. If the answer is no, ask whether the issue is budget, performance evidence, level, or policy. You are not required to accept a new responsibility in exchange for a future possibility; clarify scope and compensation before agreeing. Leave the meeting with a summary of what was decided and what remains open.
Send a useful follow-up after the meeting
Turn the conversation into a dated record without implying that a discussion is approval. For the fictional coordinator, a neutral recap could read: “Thanks for reviewing the expanded scheduling and reporting work with me today. I understand we will revisit role alignment on [date]. I will bring the six-month turnaround log and the current task list; you will confirm who makes the band decision and whether the Senior Coordinator range applies. Please let me know if I have misunderstood.” Only include commitments both people actually agreed to.
For your own practice artifact, fill one row before the meeting: Date: [month]; recurring task: weekly staffing schedule; my action: built and maintained the shared schedule; evidence: manager-approved schedule history; result: [verified outcome, if available]; context: [team or seasonal factors]. Do not invent a metric to make the row stronger. Keep confidential material with the employer, and use the meeting to ask what can be discussed.
If the next review date passes without a decision, follow up once with the agreed evidence and ask whether the owner, criteria, or timing changed. If the answer remains indefinite, decide how long you are willing to wait and whether the added duties still fit your role. A promised review is a process checkpoint, not a promised raise.
Sources
- BLS Occupational Employment and Wage Statistics tables — At the October 17, 2026 check, the latest standard tables were May 2025 OEWS, released May 15, 2026; group estimates do not prescribe an individual raise. Checked October 17, 2026.
- New York State DOL Salary Negotiation Guide — New York State DOL gives practical guidance on negotiating offers and raises; it is not a rule governing every employer. Checked October 17, 2026.