How do you ask for something at work without over-apologizing?

State the ask plainly and add a specific deadline. 'Can you send the Q3 numbers by Thursday? I need them for the board deck' is a complete, confident request. Drop 'so sorry to bother you' and 'silly question' entirely. A single 'thanks' at the end is enough courtesy. You are asking a colleague to do their job, not asking a stranger for a kidney.

Why does over-apologizing in emails make you look less confident?

Every apology and hedge tells the reader the request is an imposition and maybe not worth doing. 'Maybe possibly, whenever you get a chance, no rush' signals the ask is optional, so it gets deprioritized. It also makes you the smallest person in the exchange. Confident is not rude. It is simply asking clearly for something you have a legitimate reason to need.

Is it bad to say sorry in a work email?

One genuine sorry for an actual mistake is fine. The problem is reflexive apology for existing, for asking, for taking up space. 'So sorry to bother you' before a normal request trains people to see your asks as low priority. Replace the apology with a reason, a clear request, and a by-when, and you sound like a peer instead of a supplicant.

All practice questions

How to Rewrite an Over-Apologetic Email

Free practice. No signup.

Try it: Rewrite an over-apologetic ask

Rewrite this message so the ask is clear and confident, without the pile of apologies that buries it.

There is a real, reasonable request buried in here: send the Q3 numbers. But it is wrapped in six apologies and three hedges that make you sound like you are asking for a kidney, not a spreadsheet. Rewrite it so Marcus reads it in five seconds and knows exactly what you need and by when.

The message to rewrite

Hi Marcus, So sorry to bother you again, I know you are incredibly busy and this is probably a silly question! I hate to be a pain, but I was just wondering if maybe, whenever you get a chance (no rush at all!!), you might possibly be able to send over the Q3 numbers? So sorry again, thank you so much!!

Rewrite it here. Keep the point, lose whatever made it land badly.

Say your answer out loud first if you can, then type what you said. Most strong answers are about 80 to 150 words (3 to 4 sentences).

0 words

There is a real, reasonable request buried in the message you just wrote: send the Q3 numbers. The trouble is that it is wrapped in six apologies and three hedges that make you sound like you are asking Marcus for a kidney, not a spreadsheet he already has open.

Cut the apologies and hedges, then state the ask plainly with a deadline. That is how to rewrite an over-apologetic message so it reads as a confident request instead of a nervous one. The politeness is not the problem. The self-erasing is.

Look at what the original actually does. 'So sorry to bother you again' apologizes for existing. 'I know you are incredibly busy' pre-agrees that your request is a burden. 'This is probably a silly question' tells Marcus not to take it seriously before he has read it. 'Maybe, whenever you get a chance, no rush at all' quietly informs him the ask is optional. By the time you get to the actual request, you have spent five sentences teaching Marcus that it does not matter. So he files it under later. And later becomes never.

Here is the cost. Reflexive apology does not read as polite. It reads as uncertain, and uncertainty is contagious. If you are not sure your own request is worth Marcus's time, he will take your word for it. He believes you. The people who get fast responses are not ruder. They are clearer.

Try the rewrite below. The sim gives you the original and a blank field.

What the message is really trying to say

Strip it down and there are three things. You need the Q3 numbers. You need them for a reason. You need them by a time. That is a normal, legitimate ask between colleagues, and it deserves to be stated like one.

A financial analyst at a bank in Charlotte told me she used to open every request with 'so sorry to bother you' out of habit. Her manager finally pointed out that she apologized more than anyone on the team and got slower replies than anyone on the team. She ran an experiment for two weeks: no opening apology, just the ask and a deadline. Her response times roughly halved. Nobody found her rude. They found her easy to help.

A version that sounds like a peer

Here is the same request, dug out. 'Hi Marcus, can you send me the Q3 numbers by Thursday at noon? I need them to finish the board deck for Friday. Thanks.' That is it. One reason, one deadline, one thanks.

Notice the request is now the first thing, not the last. There is a specific by-when, so 'no rush' does not quietly become never. And the single 'thanks' carries all the courtesy the six apologies were failing to carry. It is warm. It is also confident, because it treats the ask as normal, which it is.

The overcorrection to avoid

Cutting the apologies does not mean going cold. 'Send Q3 numbers by Thursday.' with no greeting and no thanks swings too far and reads as a command. The target is warm and clear at once. Keep the greeting, keep one thanks, keep a friendly reason. Drop the flinching. 'Can you' is a request. 'So sorry to bother you, this is probably silly, but maybe' is a flinch.

Confidence in a message is not volume or bluntness. It is the quiet assumption that your reasonable ask is, in fact, reasonable. When you rewrite an over-apologetic message, you are not adding ego. You are removing the six little signals that told the reader to ignore you, and letting the real request stand on its own.