“Does this sound rude?” is often a question about assertive communication at work: how to make a clear request, disagree or set a boundary while treating the other person respectfully. The SEND checklist helps you review emails and messages without weakening what you need to say.
You don’t need to turn every sentence into an apology. A clear deadline, a disagreement or a simple “no” can stay exactly that.
Before you hit send, check SEND.
The SEND checklist
| Check | Ask yourself | |
|---|---|---|
| S | State the need. | What do I want them to know or do? |
| E | Explain the context. | What do they need to know to understand this? |
| N | Name facts, not motives. | Am I saying what happened, or deciding why they did it? |
| D | Drop the digs. | Can I remove a jab without losing the point? |
Clear ask. Enough context. Facts. No digs. That’s the version to remember.
Use SEND when you’re unsure about a message or writing while frustrated. Keep the reader and the situation in mind.
S: State the need
“Any update??” leaves the other person to work out what kind of update you need and when.
Purdue University’s OWL’s email etiquette guidance recommends short, clear paragraphs that get directly to the point.
“Can you confirm the delivery date by 2 p.m.?” gives them a question they can answer.
A message can also state a decision: “I can’t take on another task this week.” You don’t have to turn a boundary into a request for permission.
E: Explain the context
“I need this today” may be enough when the reason is already clear. If it isn’t, add the missing piece:
“I need the figures today so I can submit the report tomorrow.”
Explain what matters; you don’t need a long introduction. For a personal boundary, context is optional. “I don’t want to discuss this” can stand on its own.
N: Name facts, not motives
“You ignored my email” makes a claim about intent. “I haven’t received a reply to Tuesday’s email” describes what you know.
You can still name the impact: “Without your approval, the release is blocked.” That explains the problem without guessing what someone was thinking.
The Center for Creative Leadership’s Situation-Behavior-Impact feedback model follows a similar principle: describe the situation, the behavior you observed and its impact. Ask about intent instead of assuming it.
D: Drop the digs
Look for words that add a jab but no useful information: “obviously,” “for once,” “as you should know,” or a sarcastic “great job.”
Try removing the jab and reading the message again. Keep the actual request, deadline and consequence. “Please” won’t do much for “Please try reading it properly this time.”
Try it on one tense message
“As I already told you, I need the numbers by 3. You clearly didn’t bother checking. Fix them or I’m escalating.”
If the problem is incorrect figures, be specific:
“The figures in rows 4 and 5 don’t match the source sheet. Please correct them by 3 p.m. so I can submit the report. If they aren’t corrected by then, I’ll escalate the issue.”
The request, deadline and consequence remain. The accusation about effort disappears, and the reader knows what to fix.
Use the actual facts. Don’t invent context to make an edit sound better.
12 messages and simple edits
These examples show how a small edit can change the tone. Choose wording that fits your situation.
| Message | Possible reading | Try this |
|---|---|---|
| “OK.” | Acknowledgment, or a curt end to the exchange | “OK, I’ll do that.” if you are agreeing to act |
| “FYI.” with a forwarded message | An unexplained task or implied correction | “FYI: no action needed; this affects Friday’s schedule.” |
| “Per my last email…” | A reminder with an implied “you didn’t read it” | “The details are in Tuesday’s email; the deadline is Friday.” |
| “As I already said…” | Impatience with having to repeat yourself | “To confirm, the deadline is Friday.” |
| “Any update??” | Frustration without a clear request | “Can you confirm the status by 2 p.m.?” |
| “You didn’t read the instructions.” | A judgment about effort or attention | “Step 3 is missing. Please add it.” |
| “You always leave this to me.” | A broad accusation that invites counterexamples | “I handled the last two reports. I need you to take this one.” |
| “Obviously, that won’t work.” | The other person should have known better | “That won’t work with the current budget.” |
| “Great job breaking the build again.” | Sarcasm aimed at a person | “The build is failing after this change. Please investigate.” |
| “Whatever.” | Genuine indifference, or withdrawal from the conversation | “Either option works for me.” if that’s what you mean |
| “I need this by Friday.” | A clear deadline; possibly abrupt without context | “I need this by Friday for Monday’s review.” |
| “No, I can’t take this on.” | A clear boundary; not inherently rude | Keep it. Add “I’m at capacity this week” only if you want to explain. |
The last two messages may be fine as written. A deadline or a boundary doesn’t need an apology.
Firm is not the same as rude
The University of Iowa describes assertive communication as stating your needs openly and respectfully while respecting the other person’s rights.
Before accepting any edit, check what survived:
- The request: does it still ask for the thing you need?
- The boundary: does “no” still mean no?
- The deadline: did a specific date become “when you have a chance”?
- The consequence: did an actual next step disappear?
For example, “Please send the signed form by Friday; otherwise we cannot start on Monday” is direct and specific. Changing it to “Send it whenever you can” changes the agreement.
The same applies to apologies and thanks. Include them when you mean them. You don’t need to add “Sorry!” to make a reasonable request acceptable.
When the wording isn’t the whole problem
If you’re talking past each other, ask a question or have a conversation. Confirm any agreement in writing.
People use punctuation, greetings and direct language differently. A brief message isn’t proof of hostility.
Can a tone checker help before you send?
A tone checker gives you another reading of your message. It may miss context, so use your judgment.
If you use a rewrite, check names, numbers, deadlines, negation and who is agreeing to do what. A smoother sentence can still change your meaning.
We’re building RiskCheck, a private message tone checker for iPhone. It checks tone as you type and offers an optional rewrite, all on your phone. You decide what to change.
RiskCheck is in development. Ask for early access or read our comparison of AI keyboards for iPhone.
Common questions
Does “OK” sound rude in a text?
Not necessarily. It can simply mean “understood.” If the other person needs to know whether you agree or will take action, say that: “OK, I’ll send it this afternoon.” Punctuation alone cannot tell you what someone meant.
Is “FYI” rude in an email?
Not by itself. The ambiguity is often what the reader should do next. “FYI: no action needed” and “Please review this before Friday” communicate different needs more clearly than a bare forward.
Is “per my last email” passive-aggressive?
Sometimes. Name the earlier email and repeat the key detail. If a request is still unanswered, say when you sent it and what you need.
How do I make a message less rude without sounding weak?
Keep the request, boundary, deadline and consequence. Remove unnecessary accusations and sarcasm, and add any context the reader is missing. Directness does not need an apology.
What’s the quickest check before sending?
SEND: State the need. Explain the context. Name facts, not motives. Drop the digs. Then make sure the message still says what you mean.
