Professional Email

Professional Email Writing

When to Use

Use this skill when the user:

• Needs to draft a single professional email to a colleague, direct report, manager, skip-level, client, or vendor -- any one-to-one or one-to-many workplace communication
• Asks for help writing a request, status update, decision notification, follow-up, meeting request, introduction, or escalation within an existing professional relationship
• Has a draft they want reviewed, tightened, or rewritten before sending
• Is unsure how to phrase a sensitive but routine workplace message (asking for a raise, declining a project, pushing back on a deadline, flagging a problem)
• Needs to respond to a complex or charged email and wants to calibrate tone and content before hitting reply
• Is writing an internal announcement that will be sent as an email (not a newsletter or broadcast -- those are different)

Do NOT use this skill when the user wants:

• A cold outreach sequence to people they have no existing relationship with -- use cold-email-outreach
• A newsletter, digest, or email broadcast to a subscriber list -- use newsletter-writing
• A formal rejection letter (job applicant, vendor bid, proposal) -- use rejection-letter
• A conflict resolution or HR-adjacent email addressing interpersonal disputes, misconduct, or formal grievances -- use conflict-resolution-email
• A formal business letter requiring letterhead formatting, legal language, or notarized documentation accompaniment -- use business-letter
• A multi-email drip campaign or nurture sequence -- use cold-email-outreach
• A legal notice, cease-and-desist, or contract communication -- those require legal counsel, not this skill

Process

Step 1: Gather the Four Critical Inputs

Before writing a single word, collect -- or infer from context -- four pieces of information. If the user has not provided them, ask directly.

• Recipient identity: Who is this person relative to the sender? Peer, direct report, manager, skip-level, external client, vendor, or stranger? Seniority gap determines length, formality, and how much justification is required.
• Purpose category: Which of the six core email types applies? (Request, Update, Follow-up, Decision, Escalation, Introduction.) Each has a distinct structure. Misclassifying the purpose produces a structurally wrong email.
• The specific ask or action: What does the sender want the recipient to DO after reading? Approve something? Reply with information? Attend a meeting? Take no action but be informed? If there is no answer to this question, the email is probably not ready to be written.
• Deadline or urgency signal: Is there a hard date by which a response or action is needed? Without a specific date, urgency language is meaningless. "At your earliest convenience" is not a deadline.

If the user cannot answer what action they want from the recipient, pause. Help them clarify the ask before drafting. An email without a clear ask creates confusion and delays -- the most common cause of email threads that spiral past five replies.

Step 2: Classify the Email Type and Select Its Structure

Match the user's situation to one of six canonical structures. Each structure has a fixed sentence-level order that should not be violated -- the order exists because it mirrors how a busy professional reads email (first sentence for context, second for ask, skim to deadline).

Hybrid emails (a follow-up that is also a request escalation) should be categorized by their PRIMARY purpose. Lead with the most important element. If it feels like two emails, it probably is -- see Rule 12.

Step 3: Write the Subject Line

The subject line is the most under-engineered part of most professional emails. Treat it as a complete micro-sentence, not a label.

• Target 40-50 characters -- this is the threshold at which most email clients truncate on mobile. "Q3 forecast approval needed by Friday, Oct 18" is 46 characters and survives mobile truncation.
• Use an action verb when action is required: "Review," "Approve," "Confirm," "Decision needed on," "Update on," "Introduction:"
• Include a date when time-sensitive -- not "soon" but the actual day: "[Approve by Oct 18]"
• Avoid filler openers in subject lines: "Quick question about," "Following up on," "Re: checking in" -- these consume the visible character budget without informing
• For internal emails, include project or ticket identifiers when your organization uses them: "Budget approval -- Project Helix (#PX-4492)"
• For external emails to clients, lead with the client's frame of reference, not yours: "Your Q3 invoice -- action needed" not "Our billing process update"
• Never use all caps, excessive punctuation, or exclamation marks in professional subject lines -- these trigger spam filters and read as unprofessional

Step 4: Write the Opening -- No Throat-Clearing

The first three sentences of a professional email carry 80% of its communicative load. A recipient who reads only the first three sentences should know: (1) what this email is about, (2) what they need to do, and (3) when they need to do it.

The greeting:

• Use "Hi [First Name]," for colleagues, peers, and most professional relationships
• Use "Dear [Title Last Name]," for first contact with senior external parties, legal/formal contexts, or cultures where first-name usage is not assumed
• Use "Hello [First Name]," as a slightly warmer alternative to "Hi" -- acceptable in all professional contexts
• Never use "To Whom It May Concern" when the recipient is known; never use "Hey" in professional correspondence regardless of how friendly the relationship is

Sentence 1 -- The lead: State the purpose in active voice. Not "I wanted to reach out about the budget" but "I need your approval on the Q3 budget by Friday." The lead sentence must contain a verb that describes what you are doing (requesting, informing, escalating, following up) or what the recipient must do.

Sentence 2-3 -- The context filter: Provide only the minimum context the recipient needs to act. Ask yourself: "Would this sentence still be in the email if I removed it and the email still made sense?" If yes, remove it. Senior recipients need less context; external parties unfamiliar with your company need more.

Step 5: Write the Body -- Structure for Scannability

Professional email bodies fail when they are paragraphs of undifferentiated prose. Structure for a reader who will spend 15 seconds, not 2 minutes.

Word count thresholds:

• Routine request or update: under 150 words total
• Complex request requiring justification: 150-250 words -- if you need more, attach a document and summarize
• Escalation or sensitive message: 150-200 words -- more length does not add gravity; it dilutes it
• Emails over 300 words should almost always be restructured as a document with a short covering email

Formatting rules for the body:

• Use a bulleted list for any 3+ discrete items of information -- never embed them in a run-on sentence
• Bold key data points: deadlines, dollar amounts, names of people assigned to tasks, decision dates
• Use numbered lists only when sequence matters (step-by-step instructions, ranked priorities)
• Use a single blank line between paragraphs -- no indentation
• Tables are appropriate when comparing options or presenting multiple data points across categories -- do not use tables for simple lists

The context filter test: For every sentence in the body, ask: "Does the recipient need this to take the action I'm requesting?" If no, delete it. Justifying your request is not the same as providing context -- only include justification if it is necessary for the recipient to approve or decide.

Step 6: Write the Closing and Sign-Off

The closing of a professional email does three things: restates the ask (if the email is over 100 words), specifies what happens next, and ends cleanly.

Closing sentence patterns by email type:

• Request: "Can you [specific action] by [specific date]?"
• Update: "No action needed -- I will follow up with [next milestone] by [date]."
• Follow-up: "Please let me know by [date] so I can [consequence of their response]."
• Decision: "Please reach out if you have questions; otherwise, we will proceed on [date]."
• Escalation: "I need [specific action] by [date] to avoid [specific consequence]."

What never belongs in a closing:

• "Please feel free to reach out if you have any questions" -- this is filler; if a response is needed, the closing already requests it
• "Please do not hesitate to contact me" -- passive and redundant
• "I look forward to hearing from you" -- implies you are waiting helplessly; state a specific follow-up instead
• "Thanks in advance" -- presumptuous when used before a request has been agreed to; use after a favor has been done

Sign-offs by formality level:

• Informal / peer: "Thanks," / "Best," / "Cheers,"
• Standard professional: "Best regards," / "Regards," / "Thanks,"
• Formal / external: "Sincerely," / "Kind regards,"
• Avoid: "Warmly," (too intimate for most professional contexts), "Yours truly," (anachronistic), "Respectfully," (reserved for legal or government correspondence)

Signature block:

• Internal emails to colleagues you communicate with regularly: name only
• External emails or first contacts: name, title, company, phone number
• Never include inspirational quotes, excessive graphics, or legal disclaimers beyond what your organization mandates

Step 7: Apply the Anti-Slop Checklist

Before delivering the draft, run every item on this checklist. Each item catches a specific failure mode:

• Subject line is under 50 characters and contains a verb or action signal
• First sentence states the purpose -- no warm-up sentence precedes it
• The ask is visible within the first three sentences
• All deadlines are specific dates or times -- no "soon," "shortly," or "at your earliest convenience"
• No passive voice where active voice is possible
• All lists of 3+ items are bulleted, not embedded in sentences
• Total word count is under the threshold for this email type
• Closing sentence specifies exactly what happens next
• Sign-off matches the formality of the relationship
• The email contains exactly one primary ask -- not two or three requests bundled together

Step 8: Calibrate Tone and Sensitive Language

Tone is the most commonly misjudged element in professional email, especially in written form where vocal cues and facial expression are absent.

Tone calibration by relationship type:

Common tone failure modes:

• Over-apologizing: "I'm so sorry to bother you, but I just had a quick question..." -- weakens the ask and wastes the recipient's time
• Over-explaining: Providing justification for every decision signals insecurity; provide justification only when it materially affects the recipient's decision
• False urgency: Marking routine requests as "URGENT" destroys credibility; reserve urgency signals for genuinely time-critical messages
• Passive aggression via formality: Switching from "Hi Sarah" to "Dear Ms. Chen" when frustrated signals displeasure in writing -- avoid unintentional formality escalation
• Hedging language: "I was kind of thinking maybe we could possibly..." -- every hedge reduces confidence in the ask; be direct

Output Format

**Subject:** [Action verb + topic + deadline if needed -- under 50 characters]

[Greeting], [Recipient Name],

[Sentence 1: The ask or key information in active voice. No preamble.]
[Sentence 2-3: Minimum context needed to act. Deadline if applicable.]

[Body context -- only what is needed to act:]

- **[Key detail with label]:** [Specific information]
- **[Key detail with label]:** [Specific information]
- **[Key detail with label]:** [Specific information]

[Optional: One sentence of additional context or justification if genuinely necessary.]

[Closing sentence: restate ask + specific date OR confirm next step.]

[Sign-off],
[Sender Name]
[Title | Company | Phone -- for external emails only]

Annotation guide for the output:

• Subject line: flag if over 50 characters or missing an action word
• Opening: flag if purpose is not in sentence 1
• Body: flag if prose paragraphs contain 3+ items that should be bulleted
• Closing: flag if deadline is vague or missing
• Sign-off: flag if formality does not match relationship

Rules

1. The ask goes in sentence 1. If the recipient reads only the first sentence, they must know what you want from them or what you are telling them. No exceptions. Every sentence before the ask is a barrier between the reader and the information they need.

2. No throat-clearing openers. The following phrases are banned as opening sentences: "I hope this email finds you well," "I hope you're having a great week," "I wanted to reach out," "I just wanted to follow up," "I am writing to," "Per my last email," "As per our conversation." Start with the subject.

3. Deadlines must be specific. "At your earliest convenience," "soon," "ASAP," "when you get a chance," and "shortly" are not deadlines. A deadline is a day, date, or time. If you do not know the exact deadline, provide a relative reference: "by end of day this Friday" or "within the next 48 hours."

4. One email, one ask. Bundle multiple unrelated requests into a single email only when they share the same recipient action (e.g., "review these three documents" is one ask). A request for budget approval and a request for a 1:1 scheduling time are two separate emails. Bundled asks create tracking problems and reduce response rates.

5. Word count is a constraint, not a guideline. Routine requests: under 150 words. Complex requests: under 250 words. Escalations: under 200 words. If the email exceeds its threshold, attach a document and write a covering summary. Length is not proportional to importance -- a 50-word email can carry more authority than a 500-word one.

6. Never use passive voice when an agent is identifiable. "The deadline was missed" hides accountability. "The engineering team missed the Thursday deadline" does not. Passive voice in professional email creates ambiguity about who is responsible for what -- which is the most common cause of tasks falling through.

7. Do not bold entire sentences. Bold is for data points (dates, dollar amounts, names, decisions) within a sentence -- not for emphasis on your most important paragraph. Bolding everything means nothing is emphasized.

8. Formality must be consistent throughout the email. If you open with "Hi Sarah," do not close with "Sincerely." If you open with "Dear Mr. Kim," do not use contractions in the body. Inconsistent formality signals that the email was written carelessly or edited without reviewing the whole.

9. Negative news must come in sentence 1. Do not bury bad news under positive framing ("Great news -- the project is moving forward! Unfortunately, your timeline has been cut in half."). State the news directly, then provide context, then offer the path forward. Delayed bad news reads as manipulative.

10. Never imply urgency in the subject line that is not reflected in the body. "URGENT: Action needed" followed by a routine low-stakes request damages credibility. Reserve urgency signals for emails where failure to act by the deadline has a specific, named consequence.

11. Reply-all is an email structure decision, not a default. When instructing users on replies, consider whether all original recipients actually need the response. "Reply-all to a group thread with a one-sentence acknowledgment" is a structural error -- it creates noise for everyone on the thread.

12. The sign-off must match the ask. If you are asking the recipient to take action, do not sign off with "No rush." If the email is urgent, the sign-off and closing sentence must reinforce that -- the body, closing sentence, and sign-off should all point in the same direction.

Edge Cases

Recipient Is a C-Suite Executive or External Senior Leader

Executives process email differently from middle managers -- they skim, they delegate, and they move on. A 200-word email to a CEO is 150 words too long.

• Cap at 75-100 words total
• The first sentence must be the complete message: what decision is needed or what fact they should know
• Do not include background they did not ask for; assume they will ask if they want it
• Close with a single, binary ask: "Can you approve this by Thursday?" not "Let me know your thoughts"
• If supporting detail is necessary, attach a one-page brief and reference it: "Details in the attached one-pager."

Multiple Recipients With Different Action Items

When an email goes to 3+ recipients who each have distinct responsibilities, the body must assign tasks by name -- not by role, not by implication.

• Open with the overall purpose in sentence 1 as normal
• In the body, assign tasks using bold names: "Marcus -- please review the contract language by Wednesday. Priya -- please confirm the budget code before EOD today. Chen -- no action needed; this is for your awareness."
• Never assume recipients will self-assign from a general list -- they will each assume someone else is handling it
• If action items are complex, send individual emails to each person with the group email as a CC'd summary

Following Up on an Unanswered Email

The follow-up email is one of the most commonly botched email types. The instinct is to re-send the original; the correct move is to compress and clarify.

• Do not forward or re-send the original email -- this is passive-aggressive and creates inbox clutter
• Write a new email with the subject line "Following up: [original subject]"
• In the body, compress the original ask to one sentence: "Following up on the vendor contract approval I sent on Monday -- can you confirm by Thursday?"
• Do not apologize for following up; state that you are doing so neutrally
• On a third follow-up with no response, change the channel (call, Slack, mention in a meeting) -- repeated email follow-ups past two go-rounds rarely produce action
• Do not include language that implies frustration ("Per my last email" reads as passive-aggressive and is widely known to do so)

Delivering Bad News or Declining a Request

Declining a request or delivering unwelcome information via email requires structural discipline -- the impulse to soften bad news by delaying it produces emails that damage trust.

• State the news or decision in sentence 1: "We will not be able to extend the project deadline."
• State the reason in sentence 2 -- one sentence, factual, not apologetic: "The client presentation is fixed for October 30 and cannot move."
• Offer the path forward in sentence 3: "I want to discuss reprioritizing your backlog so the critical features are ready -- can we meet Thursday?"
• Do not over-apologize (one "I understand this is frustrating" is appropriate if the news is significant; more than one reads as performative)
• Do not use softening language that contradicts the message: "Unfortunately, we have made the difficult decision that..." -- the word "unfortunately" and the phrase "difficult decision" add length without adding empathy; state the fact and move to the solution

Email Thread Has Grown Too Long (The Thread Reset)

A thread that has passed 6-8 replies, spans multiple topics, or involves participants who joined mid-thread is no longer functional as a communication tool. Reset it.

• Start a new email -- do not reply to the chain
• Subject line: "Summary + next steps: [original topic]"
• Body sentence 1: the current state of the situation in one sentence
• Body: a brief summary of agreed decisions (bulleted) and open questions (bulleted separately)
• Close: a single specific next step with an owner and a date
• CC the original participants so they have the new thread
• The old thread can be archived; the new email is the single source of truth

Sensitive Requests (Raise, Promotion Consideration, Policy Exception)

Emails requesting something that benefits the sender and requires the recipient to grant an exception or make a favorable decision require a specific approach: lead with value delivered, not with the ask.

• Do not open with the ask: "I'd like to discuss my compensation" buries the recipient immediately in an awkward position
• Open with the context that frames why the ask is merited: "Over the past six months, I have led three product launches that generated $2.1M in new ARR and expanded the team from three to eight."
• Then state the ask directly in sentence 2: "I would like to request a compensation review reflecting this expanded scope."
• Provide specific data points -- percentages, dollar amounts, dates -- not qualitative self-assessments ("I've worked really hard")
• End with a specific next step: "Can we schedule 30 minutes this week to discuss?" -- not an open-ended "let me know your thoughts"
• Keep this email under 150 words; the conversation happens in the meeting the email is requesting

Cross-Cultural or International Recipients

Formality expectations, directness norms, and relationship-building conventions vary significantly across professional cultures. This is not about stereotyping -- it is about adjusting structure to match communication norms that affect how your email is received.

• High-context cultures (Japan, South Korea, China, many Middle Eastern countries): Relationship acknowledgment before the ask is appropriate; slightly more formal greeting; avoid blunt refusals -- frame as "this may be difficult" rather than "we cannot do this"
• Low-context cultures (US, Germany, Netherlands, Australia): Direct is expected and respected; get to the point in sentence 1; formality depends on seniority, not cultural default
• UK professional email: More formal than US norms by default; "Kind regards" rather than "Best,"; understatement is a deliberate rhetorical choice, not a sign of weakness
• When in doubt about formality, err toward slightly more formal on first contact -- it is easier to relax formality than to recover from a perceived lack of respect

Example

Input: "I need to email my manager's manager (VP of Engineering) to ask if we can delay the Q4 deadline for our authentication service rewrite by three weeks. My team of four has been pulled onto an emergency security patch for the past two weeks and we lost the time. The original deadline is November 15th. I'd like to push it to December 6th. We're about 60% done with the rewrite. I don't want to sound like I'm making excuses."

Output:

Subject: Authentication rewrite -- deadline extension request, Dec 6

Hi David,

I am requesting a three-week extension on the authentication service rewrite, from November 15 to December 6.

The team has been fully allocated to the emergency PCI security patch for the past two weeks -- this was a non-discretionary pull, but it has cost us 160 person-hours against the rewrite timeline. We are currently at 60% completion with the remaining work well-scoped; December 6 is achievable without scope reduction or weekend work.

To keep things on track:

• Weeks of Nov 11 and Nov 18 -- complete token refresh layer and session management modules (previously scheduled for Oct)
• Week of Nov 25 -- integration testing and staging deployment
• Dec 2-5 -- final QA pass and production readiness review
• Dec 6 -- production deployment

No other Q4 milestones are affected. The security patch ships this Friday, and the team returns to the rewrite full-time Monday.

Can you confirm the extension by end of this week so I can update the Q4 roadmap?

Thanks, Jordan Reyes Engineering Lead, Platform Services

Why this draft works:

• Subject line (46 characters): Includes the topic, the action type, and the target date -- the VP knows what this email is about before opening it
• Sentence 1: States the ask and both dates immediately -- no background before the request
• Sentence 2: Provides the reason (not an excuse -- a factual account of what happened and its quantified impact: 160 person-hours)
• Completion percentage and revised timeline: Answers the questions a VP will immediately have -- "how far along are they?" and "is December 6 realistic?"
• Bulleted timeline: Makes the plan scannable and concrete -- demonstrates the team has thought through the path, not just asking for more time
• "No other Q4 milestones are affected": Proactively addresses the concern a VP will have before they can raise it
• Closing sentence: Specific date, specific reason for that date (roadmap update), binary ask
• Tone: Confident and factual throughout -- no apologizing, no hedging, no "I know this is a lot to ask"
• Word count: 178 words -- within the complex-request threshold, appropriate for a skip-level communication