Email etiquette lists tend to mix two very different kinds of rule: the ones that are manners, and the ones where breaking them makes a reader draw a conclusion about your judgement. Only the second kind is worth memorising.
Etiquette Is Not Politeness
The word makes it sound like a question of courtesy, and that framing is why so much of the advice is unhelpful. Etiquette in a professional inbox is closer to a shared protocol: a set of conventions that let people process a hundred messages a day without reading each one closely.
When you break a convention, the reader does not think "how rude". They think "this person does not know how this works" — and that judgement transfers to everything else you send. That is the actual cost, and it is why some of these rules matter far more than their tone suggests.
The Four That Are Load-Bearing
- The subject line describes the contents. "Question", "Hello" and "Following up" describe nothing. "Budget sheet — need your sign-off by Thu" tells the reader what it is, what is wanted and when, before they open it. This is the single highest-leverage line in the whole message, and it is the one most people write last and fastest.
- The ask appears in the first two sentences. Context after the ask, not before it. Readers scan the top of a message and decide whether to deal with it now; an ask buried under three paragraphs of background gets deferred, and deferred usually means forgotten.
- Direct messages get a reply within a working day. Even when the real answer is days away. "Got this — I will come back to you Thursday" costs eight seconds and removes the sender’s uncertainty entirely. Silence is read as either disorganisation or disregard, and you do not get to choose which.
- Reply-all is for messages everyone needs. The test is whether every person on the thread would act differently for having read it. If the answer is no, reply to the sender. A thread of nine people watching two of them arrange a meeting is the most common avoidable irritation in professional email.
CC, BCC and the One Real Breach
The address fields carry meaning that people rarely state out loud, and getting them wrong causes disproportionate damage.
- To — you are expected to act or answer.
- CC — you do not need to act, but you should know this happened. Anyone in CC who is expected to do something has been put in the wrong field, and they will reasonably assume it is not their job.
- BCC, honest use one — a large list where recipients should not see each other’s addresses.
- BCC, honest use two — dropping people off a long thread, with a visible note: "moving everyone else to BCC".
- BCC, the breach — silently letting a third party read someone’s reply. This is the one item on any etiquette list that reliably ends working relationships when it surfaces, and it surfaces more often than the people doing it expect.
Timing, Follow-Ups and Silence
Time is where etiquette does the most work, because the sender cannot see what is happening on your end and will fill the gap with a story.
Two to three working days on something with a deadline, longer on something without. The framing matters more than the interval: "do you need anything from me to move this?" gives the other person a graceful way back into a thread they have dropped. "As per my previous email" does the opposite, and is read as an accusation no matter how it was meant.
Writing at 11pm is your business; landing in someone’s inbox at 11pm is a message about expectations that you probably did not intend to send. Schedule it for the morning if your client supports it. This matters more when you are senior than when you are not.
If something you own is going to slip, the message goes out before the deadline, not after. A short warning with a new date is a normal professional event. The same information arriving a day late is a different event entirely, and it is the version people remember.
The Rules That Are Only Calibration
Everything below is real, and none of it is fixed. These vary by industry, country, seniority and the individual thread, and treating them as absolutes is how people end up writing stiff, mismatched messages.
- Greeting formality. "Dear", "Hi" and no greeting at all are each correct somewhere. Read the thread you are in.
- Exclamation marks. Fine in most internal email, out of place in a formal complaint, and read as unserious in some conservative professions. One is emphasis; three is a tone.
- Sign-offs. "Thanks" and "Best" are invisible almost everywhere, which is what you want from a sign-off.
- Message length. Norms differ enormously between organisations. Match what you are shown.
- Emoji. Ordinary in internal chat at many companies, still unusual in external email, and close to unheard-of in formal correspondence. Follow, do not lead.
Why Two People Follow the Same List and Get Different Results
Etiquette is a set of conventions, and conventions are only half the skill. The other half is judging which room you are in — because the same message that is exactly right for a colleague you have known for years is wrong for a first email to someone senior in another organisation, and no list can tell you which one you are writing.
Those two are genuinely separable. People who know every convention and apply the same register to every recipient run into trouble as often as people who read the room perfectly and do not know the conventions.
The Communication Adaptability test scores medium conventions and audience judgement as separate results across 24 short situations, in about five minutes, so you can see which of the two is the one costing you.