Professional Email Rules

Every recipient decides whether to open, skim, or ignore an email within seconds, mostly from the subject line alone — write every part of a professional email as if it might only get that much attention, because it often does.

Subject line = the ask

• State the specific action or content in the subject line, not just the topic — "Approve Q3 budget by Friday" beats "Q3 budget," because the recipient can triage and prioritize without opening the email at all.
• Put a deadline in the subject line when one exists ("Feedback needed by EOD Thursday") — a deadline buried in paragraph three of the body routinely gets missed by recipients who only skim subject lines in a crowded inbox.
• Update the subject line when the topic of a long reply thread has drifted from the original — a thread still titled "Quick question" after 15 replies about a contract negotiation actively misleads anyone triaging by subject.

One email, one topic

• Cover a single topic or decision per email. Bundling three unrelated asks into one message means the recipient can act on the easy one and silently drop the other two, or none.
• If a second topic comes up while drafting, send a separate email rather than appending it — this also makes both threads independently searchable and referenceable later, which a merged thread isn't.
• Exception: a genuine batch update (e.g., a weekly status covering several small items) is fine as one email, but structure it with clear headers per item so it doesn't read as a single dense request.

Front-load the request

• State the ask or the key information in the first sentence or two, before any pleasantries, context, or backstory — a recipient scanning an inbox on their phone should see what's needed without scrolling.
• Move necessary context after the ask, not before it. If the recipient needs background to act, provide it, but don't make them read three paragraphs of setup to discover there's a request at all.
• End with a clear, specific next step: what you need, from whom, and by when. "Let me know your thoughts" is weaker than "Can you confirm by Wednesday whether option A works for your team?"

Formatting for skimming

• Use short paragraphs (2-4 sentences), line breaks between distinct points, and bullets or numbered lists for anything with more than two items — a wall of unbroken text is the fastest way to get an email skimmed past rather than read.
• Bold the specific action or deadline if the email is more than a few sentences long, so it's visible even to a reader who only scans rather than reads word-for-word.
• Keep the email as short as the content genuinely allows. Length should be driven by what the recipient needs to act, not by a habit of restating context they already have.

Reply, CC, and forward discipline

• Reply-all only when every recipient genuinely needs the reply to act or stay informed — defaulting to reply-all on a thread with a dozen people creates noise that trains people to skim your emails, including the important ones.
• CC people who need visibility but no action; put people who need to act in the To line. Mixing this up means an action item addressed to "everyone" effectively belongs to no one.
• When forwarding, add a one-line note explaining why you're forwarding and what, if anything, you need from the recipient — a bare forward with no context forces the recipient to reconstruct your intent from a thread they weren't part of.
• Trim the quoted history when a thread gets long, keeping only what's needed for context — an email that opens with 40 lines of quoted replies before the new content buries the actual message.

Tone calibration

• Match formality to the relationship and the organization's norms, not to a generic "professional" template — an email to a close daily collaborator can be terser than one to a new external partner, and over-formality with a familiar colleague can read as cold or passive-aggressive.
• Write requests as requests, not disguised demands — "Could you send this by Friday?" lands better than "This needs to be done by Friday," even when the underlying expectation is the same.
• Read time-sensitive or corrective emails once before sending with an eye specifically for tone — text strips vocal tone entirely, and a line meant as neutral often reads as curt or annoyed without it.

What to avoid

• Don't mark routine requests "urgent" or use ALL CAPS for emphasis — both lose their signaling power the first time they're used for something that wasn't actually urgent, and erode how seriously your genuinely urgent emails get taken afterward.
• Don't send an email as a substitute for a conversation that actually needs real-time back-and-forth (a sensitive disagreement, a fast-moving decision) — email is the wrong medium when the exchange will take five long back-and-forth replies to resolve what a five-minute call would.
• Don't leave the ask implicit and expect the recipient to infer it from context — state it explicitly even when it feels obvious to you; it usually isn't equally obvious to someone with a different inbox's worth of context.