A strong salary-raise email is direct but cooperative: state that you want to discuss compensation, connect the request to role scope, achievements, market context or changed responsibilities, and make the next step easy. Personal financial pressure is not a substitute for a work-based rationale.
ReviewedEvidence2 sourcesSectionWriting & Style
Quick answer
A raise-request email should make the request clear, give concise evidence of your contributions, and invite a professional discussion rather than demand an immediate answer.
Key details
Core Issuehow to make a written salary-increase request that is evidence-based, professional, and easy for a manager to act on
Registerprofessional workplace email
Rule Familysalary-request wording
Important caveats
Tone Boundary
Be assertive, cooperative, and positive. Avoid threats, comparisons with coworkers, or a claim that personal expenses alone justify a raise.
Further guidance
Evidence To Include
Use specific achievements, measurable results, expanded responsibilities, relevant market information, or another job-related basis. Keep the strongest evidence in the message and save supporting detail for the discussion.
Reader Check
Can the manager tell what you are asking for, why the request is timely, and what you want them to do next?
Recommended Structure
Open with the purpose of the message, briefly summarize the value or responsibilities supporting the request, state the compensation discussion you are seeking, and close by asking for a meeting or next step.
Worked Example
Example: “I’d like to schedule time to discuss my compensation. Over the past year I have taken ownership of X and Y, and the changes have produced Z result. Could we review whether my salary can be adjusted to reflect the role as it now stands?”
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
Negotiate↗ (opens in a new tab)UC Berkeley Career Engagement · Supports salary-negotiation preparation: research market value, make a supported request, and use an assertive but cooperative approach.
A job-offer acceptance email should clearly communicate the decision to accept, identify the position, and confirm agreed logistics such as a start date when useful. It is different from an invitation acceptance because it responds to an employment offer with contractual and onboarding context.
A complaint acknowledgment is the short first response that confirms the issue has been received and is being handled. It should not pretend the investigation is complete or promise a remedy before the facts are known.
An apology-for-delay email should acknowledge the missed timing and give the recipient a reliable next step. This intent is broader than apologizing for a late email reply: it can cover delayed work, files, decisions, or delivery.
An approval-response email should make the yes decision unmistakable and state any conditions, limits, or next steps. It is the response counterpart to a request-for-approval email.
A professional cancellation email should identify the meeting being cancelled, state the change clearly, and give any next step that matters. A brief reason can help when appropriate, but clarity about the cancellation is more important than a long explanation.
A demo-confirmation email should give the recipient a reliable calendar-ready record of when the demo happens, how to join, what will be covered, and whether any preparation is needed.
A meeting confirmation should restate the essential details that both sides need to verify: date, time, location or link, and any key preparation item. The goal is to remove ambiguity, not merely say “confirmed.”
A replacement-confirmation email tells the recipient what substitute will be provided, its current status, and any return or next-step requirements. It is distinct from delivery confirmation, which reports that an item has already reached its destination.
