Professional Email Examples for Any Situation
Knowing the principles of professional email writing is useful. Having actual examples in front of you when you're staring at a blank compose window is more useful. This guide brings both together — real professional email examples across the most common workplace situations, with notes on why each element works.
For a full breakdown of the underlying principles behind all of these, see how to write a professional email. This guide is the practical companion: copy the structure, swap in your specifics, and send.
Why Examples Work Better Than Rules
The Gap Between Principle and Practice
Rules like "be concise" and "state your ask clearly" are easy to understand and surprisingly hard to execute under time pressure. When you're drafting a difficult email, abstract principles don't help as much as a concrete model that shows what "concise" and "clear" actually look like in that specific context.
Templates as Starting Points, Not Finished Products
Every template in this guide is a starting point. The goal is to give you a structure that's already calibrated — subject line format, opening, body flow, closing — so that you only need to fill in the specifics of your situation rather than building from scratch.
Adapt freely. The templates below reflect professional norms, but your relationship with the recipient, your industry, and your own voice should all influence the final version you send.
Introducing Yourself to a New Contact
Whether you're making a first connection through a mutual referral, reaching out to someone at an event, or introducing yourself as a new team member, the introduction email needs to establish who you are, why you're relevant, and what you're hoping for.
Example: Introduction via Mutual Contact
Subject: Introduction from [Mutual Contact's Name]
Hi [Name],
[Mutual contact] suggested I reach out — she thought our work might overlap in useful ways.
I'm [Your Name], [title] at [Company]. We [one sentence on what you do or what problem you solve]. I'd love to learn more about what you're working on and see if there's anything worth exploring together.
Would a 20-minute call next week work for you?
Best, [Your Name]
Why it works: The mutual contact is named upfront — it's the single most powerful opener in any introduction email. The ask is small and specific. The email is under 100 words.
Example: New Team Member Introduction
Subject: Quick intro — [Your Name], joining [Team Name] on [Date]
Hi [Name],
I'm [Your Name], joining the [team] on [start date] as [role]. I'll be working closely with your team on [area], so I wanted to introduce myself before we meet properly.
Looking forward to working together — feel free to reach out any time.
[Your Name]
Why it works: No fluff, no excessive enthusiasm. Clear context (who, when, why it's relevant to them), a warm close that doesn't demand a response.
Job Application Emails
A job application email serves as the cover note that sits above your attached CV or application materials. It needs to make a strong first impression while being short enough that a busy hiring manager will actually read it.
Example: Applying for an Advertised Role
Subject: Application for [Role Title] — [Your Name]
Dear [Hiring Manager's Name],
I'm applying for the [Role Title] position at [Company]. I've attached my CV and cover letter for your review.
In short: I have [X years] of experience in [relevant area], including [one specific achievement or credential]. I'm particularly drawn to [Company] because [genuine, specific reason — product, mission, team].
Thank you for your time — I look forward to hearing from you.
Best regards, [Your Name]
Why it works: Specific subject line, direct opening, one concrete differentiator, one genuine reason for interest. Doesn't try to fit the entire cover letter into the email body.
Example: Following Up on an Application
Subject: Following up — [Role Title] application, [Date]
Dear [Name],
I applied for the [Role Title] position on [date] and wanted to follow up to confirm receipt and reiterate my interest. I'm genuinely excited about this role and would welcome the chance to discuss it further.
Please let me know if you need anything additional from my end.
Best regards, [Your Name]
Why it works: Brief, non-pressurizing, signals genuine interest without desperation. Gives them an easy out if they need more information.
Requesting a Meeting
Meeting request emails are some of the most common professional emails — and some of the most frequently written badly. The most common error is under-specifying: "Let me know if you're free for a call" leaves all the work to the recipient.
Example: Requesting an Internal Meeting
Subject: 30-min sync on [topic] — this week?
Hi [Name],
I'd like to get 30 minutes with you to discuss [specific topic]. I want to [one sentence on what you're hoping to resolve or decide].
Would [Day] at [time] or [Day] at [time] work? Happy to adjust if neither suits.
Thanks, [Your Name]
Why it works: The subject line tells the reader exactly what to expect. The ask states the duration, the topic, and the purpose. Two time options reduce the back-and-forth of open-ended scheduling.
Example: Requesting an External Meeting
Subject: Meeting request — [Your Company] + [Their Company]
Hi [Name],
I'm [Your Name], [title] at [Company]. [One sentence on why you're reaching out — shared industry, specific interest in their work, referral].
I'd welcome 30 minutes to discuss [specific topic or potential area of collaboration]. Would you have time for a brief call in the next two weeks? I'm flexible on timing.
Best regards, [Your Name]
Why it works: Brief intro, specific reason for the meeting, open-ended on timing (appropriate for external, lower-pressure situations).
Follow-Up Emails
Follow-up emails need to do a specific job: re-engage without pressurizing. The full guide on this is how to write a polite follow-up email — these examples follow the same principles.
Example: Following Up on an Unanswered Email
Subject: Re: [Original subject]
Hi [Name],
Just following up on my email from [date] about [topic]. I know things get busy — I wanted to check if you'd had a chance to review it, or if you need any additional information from me.
[Single specific ask or yes/no question.]
Thanks, [Your Name]
Example: Following Up After a Meeting
Subject: Follow-up from our call on [date]
Hi [Name],
Thanks for taking the time to speak on [day]. As discussed:
- [Action item 1 — who, what, by when]
- [Action item 2 — who, what, by when]
I'll [your next action] by [date]. Please let me know if I've missed anything or if any of the above needs adjusting.
Best, [Your Name]
Why it works: The follow-up after a meeting confirms the shared understanding immediately while it's fresh. Named action items with owners and dates remove ambiguity and create accountability.
Declining a Request
Declining professionally is about being clear without being cold. The structure: acknowledge, brief reason, clear decline, offer an alternative where genuine.
Example: Declining a Meeting Request
Subject: Re: Meeting request
Hi [Name],
Thanks for reaching out. Unfortunately, I won't be able to meet this month — I have a full schedule through [date].
If this is still relevant in [timeframe], I'd be glad to reconnect then. Alternatively, if it's something I could help with over email, feel free to share the details.
Best, [Your Name]
Example: Declining a Project or Collaboration
Subject: Re: [Project name]
Hi [Name],
Thank you for thinking of me for this. After reviewing it, I don't think I'm the right fit at this stage — I don't have the bandwidth to do it justice.
I hope the project goes well. If it evolves into something that might be a better fit, I'd be happy to revisit.
Best, [Your Name]
Why it works: Clear, warm, specific reason, genuine offer to revisit. No excessive apologizing, no false promises.
Apology Emails
A professional apology email has three requirements: own the mistake specifically, keep it appropriately concise, and tell the reader what you're doing next. For the full breakdown, see how to apologize professionally in an email.
Example: Apologizing for a Missed Deadline
Subject: Apology — [Project name] delivery
Hi [Name],
I owe you an apology. I missed the agreed deadline for [deliverable] — this was my error, and I understand it created problems for your timeline.
I've completed [deliverable] and am sending it with this email. I've also flagged the delay to [relevant person] and adjusted the downstream schedule accordingly.
I'll make sure this doesn't happen again.
[Your Name]
Example: Apologizing for a Communication Error
Subject: Apology — incorrect information in my previous email
Hi [Name],
I need to correct something from my email on [date]. I stated [incorrect information] — that was wrong. The correct information is [correct detail].
I apologize for any confusion this caused. Please disregard the earlier version.
[Your Name]
Why it works: Direct, specific, corrective. No excessive hedging, no buried acknowledgment. The correction is the focus.
Delivering Difficult Feedback
Giving feedback by email is tricky because tone is easy to misjudge. The principles: be specific, focus on behavior and impact rather than character, and offer a path forward.
Example: Giving Constructive Feedback to a Direct Report
Subject: Feedback on [project/deliverable]
Hi [Name],
I wanted to share some feedback on [project] while it's fresh.
What worked well: [specific positive].
Where I'd like to see improvement: [specific behavior or output], because [impact it had]. Going forward, I'd like [specific change].
Happy to discuss any of this — let me know if it would help to talk it through.
[Your Name]
Example: Pushing Back on a Colleague's Work
Subject: Thoughts on [document/plan]
Hi [Name],
I've reviewed [document] and have a few concerns I wanted to flag before we move forward.
[Specific concern 1 — what and why] [Specific concern 2 — what and why]
I'm not suggesting we scrap the approach — I think [what works] is solid. But I'd like to discuss these points before we share this externally. Would you have 20 minutes this week?
[Your Name]
Sending a Professional Status Update
Status updates are often written hastily and end up being either too long or too vague. The goal: give the reader the three things they actually need — where things stand, what's next, and whether action is required from them.
Example: Project Status Update
Subject: [Project name] — status update, [date]
Hi [Name/Team],
Quick update on [project]:
Status: [On track / Delayed / At risk] — [one sentence]
Completed this week: [2–3 bullet points]
Next steps: [2–3 bullet points with owners and dates]
Action needed from you: [specific ask, or "No action needed at this time"]
Let me know if you have questions.
[Your Name]
Why it works: The structure is scannable. The "action needed" section means the reader immediately knows whether they need to do anything. The status flag at the top lets a busy manager understand the situation without reading the detail.
Frequently Asked Questions
How formal should a professional email be? It depends on the relationship and context. First contact with someone you don't know should be more formal. Ongoing communication with a familiar colleague can be semi-formal. Read the register of the emails you receive from each person and mirror it. When in doubt, err slightly more formal on first contact and let the relationship define the register over time. For more on this, see how to sound professional in emails.
Is it okay to use bullet points in professional emails? Yes — when you have three or more distinct items to communicate, bullet points make them easier to read and act on than dense paragraph text. Use them for action items, lists of questions, or multiple points that each need to be processed separately. Avoid them for flowing narrative or a single point that doesn't require separation.
Should professional emails always have a subject line? Yes, always. A blank subject line is one of the most reliable ways to ensure your email gets deprioritized. Even for short, informal internal emails, a clear subject line helps the reader triage and file your message. Keep it under 50 characters and make it descriptive.
How do I write a professional email when I'm frustrated or upset? Write it, then don't send it. Wait at least 15–30 minutes, re-read it with fresh eyes, and ask yourself whether you'd be comfortable if the recipient forwarded it to their manager. If the answer is no, rewrite it. Remove emotional language — "I'm frustrated," "this is unacceptable" — and replace it with factual description. If tone calibration is difficult, paste it into Polishit and use a professional or diplomatic tone to smooth the edges.
What's the best way to end a professional email? Use a sign-off that matches your register: "Best regards" for formal, "Best" or "Thanks" for semi-formal ongoing exchanges, "Kind regards" as a warmer formal alternative. Include your full name and a brief signature with your title and contact information. Avoid novelty sign-offs ("Cheers and best wishes!") in professional correspondence — simple and consistent is more credible.
Polish Any Email in Seconds with Polishit
Whatever the situation — introduction, application, apology, follow-up — the right tone makes the difference. Try Polishit free — paste your draft, pick the tone that fits, and get a polished version instantly.