Email Writing in Practice

The best way to learn email structure is to study real examples. This section presents side-by-side comparisons of poorly structured and well-structured emails for five common professional purposes: requests, follow-ups, introductions, complaints, and thank-yous. Each pair is analyzed so you can see exactly what makes the difference.

1. Request Emails

Request emails ask the reader to do something — provide information, approve a decision, schedule a meeting, or share a resource. They are the most common type of professional email, and they fail most often when the request is buried, vague, or missing a deadline.

Bad Example: Vague Request

Subject: Hey

Hi,

So I was wondering if you could maybe help me out with something. I've been working on this project and there are some things I need. It would be great if you could get back to me when you get a chance. There's no rush but it would be nice to have it soon.

Thanks! Alex

What went wrong:

• Subject line says nothing about the email's purpose
• No greeting with the recipient's name
• The actual request is never stated — "some things I need" is completely vague
• "No rush but... soon" is contradictory and gives no clear deadline
• The reader has no idea what to do or when to do it

Good Example: Clear Request

Subject: Request: Q3 Sales Data for Annual Report

Hello David,

I am preparing the annual report and need the Q3 sales data for the North American region. Specifically, I am looking for:

1. Monthly revenue totals (July, August, September)
2. Year-over-year comparison for each month
3. Top 10 accounts by revenue

Could you send this by Thursday, March 13 so I can include it in the draft before the review meeting on Monday?

If you have any questions about the format or scope, please let me know.

Best regards, Alex Martinez Financial Analyst, Reporting Team ext. 4521

What works:

• Subject line states the request and context
• Greeting includes the recipient's name
• Opening line explains why the data is needed (context)
• Numbered list makes the specific items easy to scan
• Deadline is bold and includes a reason for the timing
• Offers to clarify if needed
• Professional sign-off and signature

2. Follow-Up Emails

Follow-up emails check on something you previously requested, reference a past conversation, or gently remind someone of a commitment. The challenge is following up without sounding impatient or passive-aggressive.

Bad Example: Passive-Aggressive Follow-Up

Subject: STILL waiting

Hi,

I sent you an email last week about the budget report and I haven't heard back. I really need this ASAP. I don't understand why it's taking so long. This is the third time I've had to follow up. Can you PLEASE just send it?

Thanks.

What went wrong:

• Subject line is aggressive and unprofessional
• ALL CAPS conveys shouting ("STILL," "ASAP," "PLEASE")
• Accusatory tone ("I don't understand why it's taking so long")
• No specific reference to the original email (date, subject)
• No deadline — "ASAP" is vague and pressuring
• Damages the professional relationship

Good Example: Professional Follow-Up

Subject: Follow-Up: Budget Report Request (Sent March 5)

Hello Jennifer,

I hope you are doing well. I am following up on my email from March 5 regarding the Q3 budget report. I understand you may have a full workload, but I wanted to check whether you have had a chance to compile the figures.

The report is needed for the executive review meeting on Friday, March 21. If possible, could you send the data by Wednesday, March 19 to allow time for formatting?

If there are any obstacles or if you need additional information from me, please do not hesitate to let me know. I am happy to help however I can.

Thank you for your time, Alex Martinez Financial Analyst, Reporting Team ext. 4521

What works:

• Subject line references the original email with date
• Acknowledges the recipient may be busy (shows empathy)
• Restates the request without accusation
• Provides a clear deadline with context
• Offers help rather than placing blame
• Maintains a respectful, professional tone throughout

3. Introduction Emails

Introduction emails are your first impression. They are used when reaching out to someone you have not communicated with before — a potential client, a networking contact, a new colleague, or someone referred to you.

Bad Example: Unfocused Introduction

Subject: Hello!

Hey there!

My name is Alex and I work at a marketing company. I found your profile online and thought it would be cool to connect. I do a lot of different stuff — social media, content, SEO, analytics, branding, you name it. We should totally talk sometime. Let me know if you're interested!

Cheers, Alex

What went wrong:

• Subject line conveys zero information
• Overly casual greeting ("Hey there!") for a first contact
• No clear reason for reaching out
• "A lot of different stuff" is vague and unconvincing
• No specific value proposition for the reader
• No concrete next step
• No professional signature

Good Example: Focused Introduction

Subject: Introduction: Marketing Consultant Specializing in B2B Content

Dear Ms. Nakamura,

My name is Alex Martinez, and I am a content marketing consultant at BrightPath Consulting. I came across your recent article on B2B lead generation in Marketing Weekly, and I was impressed by your insights on content-driven customer acquisition.

I specialize in helping mid-size B2B companies develop content strategies that generate qualified leads. Over the past two years, I have helped clients increase their inbound lead volume by an average of 35%.

I would welcome the opportunity to discuss how our services might complement your team's efforts. Would you be available for a brief 15-minute call next week?

Thank you for your time and consideration.

Best regards, Alex Martinez Content Marketing Consultant BrightPath Consulting +1 (555) 234-5678 alex.martinez@brightpath.com

What works:

• Subject line identifies who and what
• Formal greeting appropriate for a first contact
• Opens with a specific reference showing genuine interest (not a generic template)
• States expertise concisely with a concrete result (35% increase)
• Makes a specific, low-commitment ask (15-minute call)
• Professional closing and complete signature

4. Complaint Emails

Complaint emails need to be firm without being aggressive, specific without being rambling, and solution-oriented rather than just venting. A well-written complaint is far more likely to get a positive response than an angry one.

Bad Example: Angry Complaint

Subject: TERRIBLE SERVICE!!!

This is absolutely unacceptable!!! I ordered a laptop from your website THREE WEEKS AGO and it STILL hasn't arrived. Your customer service is a joke. I called twice and both times I was put on hold for like 45 minutes before someone picked up, and they couldn't even tell me where my order was. This is the worst experience I've ever had with any company. I want a full refund RIGHT NOW or I'm going to tell everyone I know to never buy from you.

VERY unhappy customer

What went wrong:

• Subject line uses ALL CAPS and excessive punctuation
• Entire tone is hostile and emotional
• No order number or specific details that would help resolve the issue
• Threats reduce the recipient's willingness to help
• No professional greeting or closing
• No contact information

Good Example: Firm but Professional Complaint

Subject: Unresolved Delivery Issue — Order #LP-78432

Dear Customer Service Team,

I am writing regarding Order #LP-78432, a laptop computer placed on February 15, 2026, with an estimated delivery date of February 22. As of today, March 8, the order has not arrived, and the tracking information has not been updated since February 20.

I have contacted your support line twice (February 28 and March 4), but the representatives were unable to provide information on the shipment's status or an updated delivery estimate.

I would appreciate it if you could:

1. Investigate the status of my shipment and provide an updated delivery date
2. Arrange expedited shipping if the original package has been lost
3. Process a full refund if delivery cannot be confirmed within 5 business days

My account email is alex.martinez@email.com and my contact number is +1 (555) 234-5678. I am available during business hours and happy to provide any additional information needed to resolve this matter.

Thank you for your prompt attention to this issue.

Sincerely, Alex Martinez

What works:

• Subject line identifies the issue and includes the order number
• Opens with specific facts: order number, date, expected delivery
• Documents previous contact attempts with dates
• Numbered list presents clear, reasonable resolution options
• Includes contact information
• Professional tone throughout — firm but not hostile
• The reader knows exactly what happened and what is expected

5. Thank-You Emails

Thank-you emails strengthen professional relationships. They are sent after interviews, meetings, favors, collaborations, or any situation where someone helped you or gave you their time. The key to a good thank-you email is specificity — generic thanks feel hollow.

Bad Example: Generic Thank-You

Subject: Thanks

Hi,

Thanks for the meeting today. It was great. Let me know if you need anything.

Best, Alex

What went wrong:

• Subject line is vague
• No reference to what was discussed or decided
• "It was great" says nothing specific
• "Let me know if you need anything" is filler with no substance
• Feels like an obligation rather than genuine appreciation

Good Example: Specific Thank-You

Subject: Thank You — Productive Discussion on Q4 Marketing Strategy

Dear Rachel,

Thank you for taking the time to meet with me this afternoon. I found our discussion about the Q4 marketing strategy extremely valuable, particularly your insights on shifting budget allocation toward video content.

I have already started drafting the revised content calendar based on the priorities we discussed. I will send you a first draft by Friday for your review.

I also wanted to follow up on your suggestion to connect with James Park in the analytics team. I will reach out to him this week to set up a meeting.

Thank you again for your guidance and support. I look forward to continuing our collaboration.

Best regards, Alex Martinez Content Marketing Specialist ext. 4521

What works:

• Subject line references the specific meeting and topic
• Opens with genuine thanks and a specific detail from the meeting
• Demonstrates action — the writer has already started on next steps
• References a specific suggestion from the meeting, showing they were listening
• Commits to concrete follow-up actions with timelines
• Warm but professional closing

Patterns Across All Five Types

Looking at the good examples together, several patterns emerge:

And looking at the bad examples:

Key Takeaways

1. Structure is not optional. Every professional email needs a clear subject, greeting, organized body, closing, and signature.

2. Be specific. Vague emails create confusion and require follow-up emails to clarify, wasting everyone's time.

3. Tone shapes outcomes. The same request written aggressively and written professionally will get dramatically different responses.

4. Empathy improves results. Acknowledging the reader's perspective — their workload, their constraints, their expertise — makes them more willing to help.

5. Every email is a professional document. Treat emails with the same care you would give a report or presentation. They represent you in the recipient's inbox long after you send them.

Email Structure Reference

This section is a quick-reference guide for professional email writing. Bookmark it and return whenever you need a template, a checklist, or a reminder of best practices.

Email Templates

These templates provide a structural framework for common email types. Replace the bracketed placeholders with your specific details.

Template 1: Simple Request

Subject: Request: [What You Need] — [Context/Project Name]

Dear [Name],

[One sentence: why you are writing.]

[One to two sentences: context or background the reader needs.]

Specifically, I am requesting:
- [Item 1]
- [Item 2]
- [Item 3]

Could you please send this by [date]? [One sentence: why the deadline matters.]

Please let me know if you have any questions or need additional information.

Best regards,
[Your Name]
[Your Title]
[Contact Information]

Template 2: Follow-Up

Subject: Follow-Up: [Original Subject] (Sent [Date])

Hello [Name],

I am following up on my email from [date] regarding [brief description of the original request].

[One sentence acknowledging they may be busy or offering context.]

The [document/information/decision] is needed by [date] for [reason]. If possible, could you [specific action] by [date]?

If there is anything I can provide to help move this forward, please let me know.

Thank you,
[Your Name]
[Your Title]
[Contact Information]

Template 3: Introduction / Cold Outreach

Subject: Introduction: [Your Name], [Your Role/Company]

Dear [Name],

My name is [your name], and I am [your role] at [your company/organization]. [One sentence: how you found them or why you are reaching out.]

[Two to three sentences: what you do and why it is relevant to the recipient. Include one specific, concrete result if possible.]

I would welcome the opportunity to [specific, low-commitment ask — e.g., "schedule a brief 15-minute call" or "learn more about your team's approach"]. Would you be available [proposed timeframe]?

Thank you for your time.

Best regards,
[Your Name]
[Your Title]
[Your Company]
[Phone]
[Email]

Template 4: Professional Complaint

Subject: [Issue Type] — [Reference Number or Key Detail]

Dear [Name / Department],

I am writing regarding [order number / account / service], [purchased/initiated] on [date]. [One sentence describing the expected outcome.]

[One to two sentences describing what went wrong, with specific dates and details.]

[If applicable: One sentence noting previous attempts to resolve.]

I would appreciate it if you could:
1. [Resolution option 1]
2. [Resolution option 2]
3. [Resolution option 3 / fallback]

My contact details are [email] and [phone]. I am available [availability].

Thank you for your prompt attention to this matter.

Sincerely,
[Your Name]

Template 5: Thank-You (Post-Meeting or Post-Interview)

Subject: Thank You — [Meeting/Interview Topic or Position]

Dear [Name],

Thank you for [meeting with me / taking the time to interview me / your help with X] [today/yesterday/on date]. I particularly appreciated [one specific thing discussed or offered].

[One to two sentences about a follow-up action you are taking based on the meeting.]

[Optional: one sentence referencing a specific topic, showing you were engaged and attentive.]

Thank you again for your [time / guidance / support]. I look forward to [specific next step].

Best regards,
[Your Name]
[Your Title / Relevant Detail]
[Contact Information]

Template 6: Delivering Bad News

Subject: Update: [Project/Topic] — [Brief Indication of Change]

Dear [Name],

[One sentence of positive or neutral context, if available.]

Unfortunately, [state the bad news clearly and factually]. [One sentence explaining the reason, if appropriate.]

To address this, we are [taking specific action]. [One sentence about the revised plan, timeline, or alternative.]

I understand this may be inconvenient, and I apologize for any disruption. Please let me know if you would like to discuss this further.

Best regards,
[Your Name]
[Your Title]
[Contact Information]

Subject Line Formulas

Use these formulas to craft clear, effective subject lines for any situation:

Subject line rules:

• Under 60 characters (displays fully on mobile)
• Front-load the most important words
• Never leave the subject line blank
• Avoid ALL CAPS, excessive punctuation, and words like "URGENT" unless genuinely urgent
• Be specific enough that the email can be found through search months later

Dos and Don'ts Quick Guide

Do:

Don't:

Common Email Mistakes and Fixes

Mistake 1: The Buried Request

Problem: The email spends three paragraphs on background before stating what is needed.

Fix: Lead with the request. Provide context after.

Mistake 2: The Wall of Text

Problem: No paragraph breaks, no lists, no visual structure.

Fix: Break content into short paragraphs. Use lists for multiple items. Use bold for deadlines.

Mistake 3: The Ambiguous Closer

Problem: The email ends without a clear next step.

Mistake 4: Wrong Register

Problem: Using overly casual language with external contacts or overly formal language with close teammates.

Fix: Match your register to the relationship. First contact with an external stakeholder requires Level 3-4 formality. A quick message to your teammate can be Level 2.

Mistake 5: The Emotional Send

Problem: Writing and sending an email while frustrated or angry.

Fix: Use the "draft and wait" rule. Write the email, save it as a draft, wait at least one hour (preferably overnight for high-stakes messages), then revise with fresh eyes before sending.

Greeting and Closing Pairs

Match your greeting formality with your closing for a consistent tone:

Rule of thumb: When in doubt, go one level more formal than you think is necessary. It is easier to become more casual over time than to recover from being too informal on first contact.

Pre-Send Checklist

Before clicking send on any professional email, verify:

• Recipient: Is this going to the right person? (Check the To, CC, and BCC fields.)
• Subject line: Does it clearly describe the email's content?
• Greeting: Does it match the formality of the situation?
• Purpose: Is the reason for writing stated in the first one or two sentences?
• Details: Are all necessary dates, numbers, names, and references included?
• Request/Action: Is it clear what the reader should do and by when?
• Tone: Read the email from the recipient's perspective. Could anything be misinterpreted?
• Formatting: Are paragraphs short? Are lists used where appropriate?
• Attachments: If you mention an attachment, is it actually attached?
• Closing: Does the sign-off match the greeting in formality?
• Signature: Is your signature included with current contact information?
• Proofread: Have you checked for spelling, grammar, and punctuation errors?
• Reply vs. Reply All: Are you replying only to the people who need to see your response?

Quick Summary