How to Ask for a Raise: Write It Before You Say It

The request that lands is rarely improvised. Most people who successfully learn how to ask for a raise arrive at the conversation having already written most of it down. The achievement document, the meeting request email, the three sentences you refine before the room: what you write in the weeks before the meeting carries more weight than anything you say in it.

That is the argument of this guide, and it is also the practical method. A well-structured written case does most of the persuasion work. The conversation becomes, in most situations, a formality.

The achievement document: what to track and why

Most people sit down to ask for a raise with a vague sense that they deserve one. Some of them do. The problem is that "I've been working hard" is not a document. Your manager may know this, feel good about your contribution, and still have nothing to take to their own conversation with HR or with whoever controls the budget.

What they need is a list they can lift from. Specific results. Dates. Numbers where numbers exist, plain English where they do not. "Led the onboarding project that cut client setup time from six weeks to nine days" is a sentence. "Worked on onboarding" is a mood.

Start building this ninety days before you plan to ask. Add to it weekly. Track projects you closed, problems you solved, decisions you made that others did not have to. Note the things nobody asked you to do but you did anyway: the process you improved without being prompted, the person you helped, the meeting you ran when your manager was away.

By the time you send the meeting request, this document should be three to five bullet points of substance, not a list of duties. Keep it as a working file you own. This is not a formal document you hand over. It is the source material for your conversation. You will not read from it in the room. You will have absorbed it, and that will show.

How to request the meeting without flagging it as awkward

The email requesting the meeting is the first piece of writing your manager will see on this subject. It should do one thing: make it easy to say yes to a time slot without making the topic feel loaded.

Most people either say nothing specific or over-explain before the meeting happens. Neither approach is useful. The vague request gets deprioritised. The over-explained one gives your manager two weeks to form a reaction before the conversation happens, which is not in your interest.

The better approach is one sentence on the subject, framed around the relationship rather than the transaction:

"I'd like to set up 30 minutes to talk through my role and how I'm thinking about my next twelve months here. Would Thursday afternoon or Friday morning work?"

That is the whole email. It names the scope (your role, your plans), signals this is a serious conversation without sounding adversarial, and asks a closed question about timing. Your manager will say yes or suggest a different slot. The topic is declared. The pressure is off.

One timing note: do not send this on a Monday morning or the week before a major deadline. Thursday afternoon is a reliable default. The week after a visible win is better.

Writing the case itself: three sentences that carry it

When the meeting comes, you do not want to be constructing your case in real time. The case needs to be written first and then translated into the conversation. This is where the ninety days of tracking pays off.

The verbal version of a raise request has three components, and each of them is easier to deliver if you have already written it down.

What you have done. One or two concrete results from the achievement document. Not the full list. The ones that are hardest to argue with. Revenue generated, cost reduced, scope expanded. The metric, the date, the outcome.

What the market says. A specific data point from salary benchmarks for your role and location. This is not a threat and it should not feel like one. It is a reference point that removes the conversation from the territory of opinion. LinkedIn Salary and Glassdoor both let you filter by city, role, and years of experience. Use one source and name it. "Based on current data from LinkedIn Salary for this role in London, the median sits about 12 percent above my current base" is the kind of sentence that ends a subjective argument.

What you are asking. A specific number or percentage, not a range with a soft lower bound. "I'd like to discuss a move to X" or "I'm looking at an adjustment to bring my base to Y" is the format. Ranges signal negotiating flexibility; you can add that later in the conversation if needed.

Most of the phrasing that works in this room is simple and close to these three components. The places where people lose ground are not in the argument but in the language around it: apologising for asking, underselling results, framing a significant number as a small request. Write the version of the conversation you would be comfortable sending as an email. Then deliver it at approximately that level of directness.

After the meeting: what to write in each scenario

The meeting ends. You leave with one of three outcomes: a yes, a no, or a request for more time to consider. Each of these has a follow-up email, and the difference between them matters.

When the answer is yes: Thank your manager and confirm the agreed figure in writing. One sentence is enough. "Thank you for today's conversation. As agreed, my base salary will move to X from [date]" followed by a request for written confirmation. This is not bureaucratic caution. It is the record that protects both parties if there is a payroll delay or a management change later.

When the answer is to look into it further: This is the most common outcome, and it is usually genuine. Wait five to seven business days, then follow up with a single-sentence email: "I wanted to follow up on our conversation from last week. I am happy to talk more if that would be useful." Do not restate your case. The meeting happened. You are keeping the matter alive without applying pressure.

When the answer is no: Ask one question before you leave the room, or in the follow-up email: "What would I need to demonstrate or achieve for this to be the right time?" A specific roadmap is worth more than a vague reassurance. Write down what your manager says. That becomes your plan.

When the timing is wrong and you can read the room

There are periods when asking for a raise will not land regardless of how well you write the request. A company in a hiring freeze, a manager under pressure to cut costs, a quarter following a missed target. These signals are usually visible if you are paying attention.

In these situations, the useful move is not to wait indefinitely. It is to ask a different question earlier: "I want to have a conversation about my compensation at the right time. When do you think that window is likely to open?" Most managers will tell you honestly. If they say six months, you have a date. If they are evasive, you have information about whether the path forward exists in this organisation.

This conversation also takes written form. A note sent after a one-to-one where you raised the timing question can be one or two sentences: "Thanks for your honesty about the timing. I will plan to come back to this in Q1 and am happy to discuss sooner if the picture changes."

You are not being passive. You are building a paper record that shows you raised the question and were given a timeline. That record matters if the timeline slips, or if you ever need to make the case to someone else in the organisation.

Three writing habits that sink otherwise solid requests

The preparation can be thorough and the case can be sound, and the raise still gets delayed because of how it is written or spoken in the room.

Vague numbers. "Something more in line with the market" is not a request anyone can action. It is an expression of discomfort. Name a number or a specific percentage. The specificity signals that you have done the work; the vagueness signals that you have not.

The personal reason. "I need more money because my rent has gone up" is not a market argument. It is a personal circumstance. The cost of your housing is not a data point anyone can take to HR or to finance. Leave personal finances entirely out of it. The case is about what you have delivered and what the market pays for that delivery.

The long preamble. Raise requests that build through multiple paragraphs of context before arriving at the ask read as anxious. The ask should come in the first third of the email or the first minute of the conversation. Everything after the ask is supporting evidence. The preamble is not preparation; it is delay.

The written record adds up

The people who get what they ask for in these conversations are not the most confident speakers in the room. They are the most prepared writers. Their case was assembled before the meeting. Their numbers were precise. Their email after the meeting confirmed what was agreed, and their follow-up when nothing happened kept the matter on record without turning it into a confrontation.

At the second send, you stop rewriting. At the tenth, you start refining. The achievement document is the discipline. The email is the form. The boilerplate disappears. The personal part stays yours.