A short email is not automatically rude. People use direct wording to save time, communicate accessibly or avoid leaving instructions ambiguous. The useful question is whether the reader can understand the action, the timing and any choice they have. Warmth can help, but adding several apologies or exclamation marks will not repair a request that leaves out the information another person needs.
If you are hesitating over a draft, read it as someone who has not been following your thoughts. What do they need to do? Why does it matter? When do you need it, and is that deadline agreed or proposed? You can keep a direct style while making those details visible. The examples below are starting points for everyday work, not a requirement to disguise how you naturally communicate.
What you know
You can check the words you wrote, the facts included, the people addressed and whether you have stated a deadline. You can compare these with any agreed communication preferences.
What you don’t know
You cannot guarantee how the recipient will feel, infer their mood from a slow reply, or predict every cultural or personal interpretation. An editing tool cannot supply the missing relationship context.
Read the situation before guessing the tone.
Bluntness often comes from an unexplained command, an assumption that someone has failed, or a deadline that appears without context. “Send this today” might be efficient between colleagues who already agreed the task, but surprising to someone seeing it for the first time. “Could you send the signed copy by 3 pm? Finance needs it for today’s run” makes the action and reason clear without a long introduction.
Extra politeness is not always extra clarity. “Sorry to bother you, but I was just wondering if maybe you might possibly…” can make a straightforward request harder to find. A brief greeting, a specific action and a realistic date are often enough. If the answer can be no, say what flexibility exists. If the action is a genuine requirement of the role, explain it accurately rather than presenting it as an optional favour.
Three ways the conversation could unfold.
Constructed examples. Change the facts, dates and commitments to match your situation.
01 / Your manager
Your manager
You need a decision to finish a piece of work. Your first draft says “You haven’t approved this. I can’t do anything until you reply.” The dependency is real, but the wording may sound like a judgement about effort.
Their messageYou haven’t approved this. I can’t do anything until you reply.
A possible replyCould you approve option A or B by Wednesday morning? I need the decision before I can finalise the schedule. If that timing is difficult, I can prepare a provisional version.
This version keeps the dependency and asks for a specific decision. It does not pretend you can complete work without approval. If the manager has already missed an agreed date, name that fact neutrally: “We planned to confirm on Monday.” You can then explain the effect on delivery. Avoid adding an alternative you do not actually have time to produce; a useful option must also be a realistic one.
02 / A colleague
A colleague
A peer sent a file with a missing section. You want the correction quickly, but do not know whether the omission was an oversight, a version problem or a request that never reached them.
Their messageThis is wrong. Fix it before the meeting.
A possible replyThe version I opened is missing the cost breakdown. Could you add it before the 2 pm meeting, or point me to the latest file if it is already there?
The revised message describes an observable issue and leaves room for missing context. It still asks for an action and time. If you need to correct a repeated error, you can explain the standard separately: “For future reviews, please include the breakdown in the first tab.” Avoid turning one missing section into a statement about the colleague’s competence. Check the file version yourself before asking someone else to redo work.
03 / A client
A client
A client asks for an extra revision outside the agreed scope. Your draft says “That isn’t included. You’ll need to pay more.” The boundary may be correct, but the client also needs to understand the available choices.
Their messageThat isn’t included. You’ll need to pay more.
A possible replyThe agreed scope includes two revisions, which we have completed. We can quote for this additional change, or proceed with the current version. Would you like me to send an estimate?
This response explains the basis of the boundary and offers a next step. Check the actual agreement before relying on a revision limit. If the client’s request concerns an error your team should correct, do not present a charge as automatic. Keep commercial promises within your authority, and involve the appropriate colleague when you cannot approve a change yourself. The tone should make a legitimate choice understandable, rather than soften a decision by obscuring it.
Choose one useful next step.
Replace judgement with an observation
Look for words such as “obviously”, “again”, “wrong” and “you never”. They can make a specific problem sound like a wider accusation. Describe what you can observe instead: a date, missing item, version number or unanswered question. You can still say that a result is unacceptable when that is necessary; explain the concrete reason.
Check the request and deadline
Make the requested action easy to find. Distinguish an agreed deadline from a preferred one: “Could you send this by Friday?” and “The submission deadline is Friday” mean different things. If you are escalating a genuine dependency, identify its effect on the work rather than using urgency alone.
Read once, then stop polishing
Try one final read for action, context and choice. Remove details that do not help the recipient respond. Repeatedly rewriting a harmless greeting may not improve the message. If you are still unsure, ask a trusted colleague a concrete question such as “Is the deadline clear?” instead of asking them to predict how everyone might react.
You are aiming for a message that another person can act on, not a perfect emotional performance. Keep any helpful greeting or acknowledgement that sounds like you. Remove claims you cannot support, make room for a reasonable clarification, and keep the boundary where it belongs. If you later learn that a message landed badly, you can acknowledge the effect and clarify what you meant without abandoning a legitimate request. Communication can be repaired through another exchange; the first draft does not have to carry every possible nuance.