How to Write a Professional Email: 7 Templates

The average office worker sends and receives over 120 emails per day, according to data from the Radicati Group. With that volume, the emails that get read and acted on are the ones that are clear, concise, and respectful of the reader's time.

Good email writing isn't about sounding formal — it's about being easy to help. Research from the Nielsen Norman Group found that users read email in an "F-pattern," scanning the first line and left edge before deciding whether to continue. That means your first sentence, your subject line, and your formatting all carry disproportionate weight.

Here are 7 templates for the most common workplace email situations, with notes on why each one works.

1. The Follow-Up Email

Subject: Quick follow-up: [project or topic]

Hi [Name],

Following up on my note from [date] about [topic]. I know things get busy — just wanted to make sure this doesn't fall off your radar.

[If action is needed from them:] Could you let me know if you need anything from me to move this forward?

[If you're providing something:] I've attached [document] — let me know if you have questions.

Thanks, [Your name]

Why it works: It acknowledges that they're busy (removes defensiveness), is short, and makes the next step clear.

When to use it

Send a follow-up 48–72 hours after your original email if you haven't received a response. If the topic is time-sensitive, note that explicitly.

Scenario: You submitted a contract for signature two days ago and need it returned before a client call. What to say:

Hi Marcus,

Following up on the NDA I sent over Tuesday — I have a client call Friday morning and would love to have this signed before then. Let me know if anything needs adjusting on your end.

Thanks, [Your name]

2. The Meeting Request

Subject: Meeting request: [topic] — [date/time options]

Hi [Name],

I'd like to schedule [length] to discuss [topic]. The goal of the meeting is to [specific outcome — e.g., align on the Q3 roadmap, review the draft proposal, make a decision on vendor selection].

A few times that work on my end:

[Day, date, time]

[Day, date, time]

[Day, date, time]

If none of these work, feel free to suggest alternatives. I'll send a calendar invite once we land on a time.

Best, [Your name]

Why it works: It states the purpose and desired outcome upfront, and gives concrete options instead of asking the other person to propose times. Research from Harvard Business School on decision fatigue shows that forcing someone to generate options from scratch creates friction. Remove that friction and you get faster responses.

Scenario: You need to align with a senior stakeholder before presenting to the executive team. What to say:

Hi Priya,

I'd like to schedule 30 minutes before the Thursday board presentation to align on our recommendations. Specifically, I want to confirm we're on the same page about the budget ask before we're in the room.

I have openings Tuesday at 2pm, Wednesday at 10am, or Wednesday at 3pm. Let me know what works.

Best, [Your name]

3. The Project Update

Subject: [Project name] update — [date]

Hi everyone,

Quick update on [project]:

Status: On track / At risk / Blocked Completed since last update: [1-2 bullets] Next steps: [1-2 bullets] Risks or blockers: [If any, with what you need from the team]

Let me know if you have questions.

[Your name]

Why it works: Scannable format. Busy stakeholders can get the key information in 10 seconds. The explicit "Status" label forces you to be honest about where the project actually stands — a practice the Project Management Institute identifies as critical to early risk identification.

For escalations, adjust the subject line

When status shifts from "on track" to "at risk," change your subject to: [Action Required] [Project name] — Decision needed by [date]. This signals urgency without panic and is consistent with the SBI (Situation-Behavior-Impact) communication model — you're naming the situation clearly before asking for action.

4. The Apology Email

Subject: Following up on [what happened]

Hi [Name],

I wanted to follow up on [what happened — be specific]. I realize that [impact on them or the project]. That was on me — I should have [what you should have done].

Going forward, I'll [specific change].

I appreciate your patience, and I'll make sure this doesn't happen again.

[Your name]

Why it works: Takes specific responsibility, acknowledges impact, and states a concrete plan to change. No "I'm sorry if" or "I'm sorry but."

The research behind effective apologies

Roy Lewicki's apology research, published in Negotiation and Conflict Management Research, identifies six components that make apologies credible: expression of regret, explanation of what went wrong, acknowledgment of responsibility, declaration of repentance, offer of repair, and request for forgiveness. You don't need all six in a professional email, but the three most essential are acknowledgment of responsibility, acknowledgment of impact, and a concrete commitment to change. This template hits all three.

Scenario: You missed a deadline that delayed a colleague's deliverable. What to say:

Hi Jordan,

I wanted to follow up on the report I was supposed to send you by Tuesday. Missing that deadline pushed back your client submission, and I know that put you in a difficult position. That was on me — I should have flagged earlier in the week that I was running behind.

Going forward, I'll give you a heads-up at least 24 hours in advance if anything looks like it's slipping.

I appreciate your patience. Let me know if there's anything I can do to help you recover the timeline.

[Your name]

5. The Pushback Email

Subject: Re: [original topic]

Hi [Name],

I've been thinking about [the proposal/request]. I want to flag a concern before we move forward.

[State the concern clearly and specifically — what will break, what risk exists, what information is missing.]

I'd suggest [alternative approach or next step]. Would you be open to a quick call to discuss?

[Your name]

Why it works: It frames the pushback as a contribution, not a complaint. It offers a solution, not just a problem.

Disagree without damaging the relationship

The Harvard Negotiation Project's principled negotiation framework advises separating the people from the problem. In email, this means criticizing the plan, not the person. "This approach may create compliance issues" is professional. "This approach doesn't make sense" is not — even if you mean the same thing.

Scenario: Your manager proposes a launch date you believe is unrealistic given current team capacity. What to say:

Hi Sarah,

I've been thinking about the October 1st launch date. I want to flag a concern before we finalize: based on our current sprint velocity and the QA backlog, we're tracking at least two weeks behind that timeline. Launching on October 1st would mean skipping user acceptance testing, which carries real risk for the client relationship.

I'd suggest we either adjust the scope for October 1st or push to October 15th with the full feature set. Happy to walk you through the numbers on a call if that's helpful.

[Your name]

6. The Introduction Email

Subject: Introduction: [Person A] ↔ [Person B]

Hi [Name A] and [Name B],

[Name A], meet [Name B] — [one sentence on who they are and why they're relevant].

[Name B], meet [Name A] — [one sentence on who they are and why they're relevant].

I'll let you two take it from here. [Optional: one sentence on why you're connecting them.]

Best, [Your name]

Why it works: Both people get context about the other in the same email, so neither has to do research. The intro is short and lets them take over.

The forwardable intro

When making a high-stakes introduction, consider sending a separate note to each person first — asking permission to connect them and giving them context. This "double opt-in" approach, popularized by venture capitalist Fred Wilson, respects both parties' time and dramatically increases the likelihood they'll follow through.

Scenario: You're connecting a former colleague with a hiring manager at your company. What to say:

Hi Devon and Keisha,

Devon, meet Keisha — she's the Head of Product at Trellis and is building out her team. She works on exactly the kind of platform problems you've been focused on.

Keisha, meet Devon — he's a senior product manager with deep experience in fintech onboarding flows. His background at Plaid is directly relevant to what you're building.

I'll let you two take it from here. I think this one has real potential.

Best, [Your name]

7. The Out-of-Office / Handoff Email

Subject: Out of office [dates] — [coverage info]

Hi [Name],

I'm out of the office from [date] through [date], returning [date]. I won't be checking email during this time.

For anything urgent, please contact [colleague name] at [email] — they're covering for me.

For non-urgent matters, I'll respond when I'm back.

Best, [Your name]

Why it works: Clear dates, clear coverage, and sets expectations about response time. The explicit "I won't be checking email" prevents the ambiguity that causes people to follow up repeatedly.

Universal Email Principles

Subject lines matter. "Quick question" tells the recipient nothing. "Question about Thursday's client meeting agenda" gets opened.
Bottom-line up front. State your purpose in the first sentence. Don't bury the ask.
One email, one topic. If you need three things from someone, send three emails or clearly number your requests.
Read it aloud before sending. If it sounds passive-aggressive when spoken, rewrite it.
Reply within 24 hours — even if just to say "Got it — I'll get back to you by [date]."
Match the energy. If someone sends you a three-sentence email, they don't want six paragraphs back. Mirror their length and formality unless the situation requires otherwise.

On tone and ambiguity

Research from Kristin Byron at Syracuse University found that workplace emails are perceived as more negative than their senders intend — especially when the topic is sensitive or the relationship is new. When in doubt, add one sentence of warmth or context. "I know this is a lot to land on a Friday" costs nothing and changes how the message lands.

Key Takeaways

Your subject line determines whether your email gets opened. Be specific — include the topic, date, or action required.
State your purpose in the first sentence. Readers scan for relevance before they read for detail.
Effective apologies name three things: what you did, how it affected the other person, and what you'll do differently. Leave out the qualifiers.
Pushback emails work when they offer a solution. A concern without an alternative is a complaint. A concern with a suggestion is a contribution.
Format for scanning, not reading. Bullet points, bold labels, and short paragraphs reduce cognitive load and increase response rates.
Email tone is easily misread. When the topic is sensitive, read your draft aloud. If it sounds cold or clipped, it will be received that way — even if you didn't mean it.

Good email writing is a career skill. The people who write clear, respectful, actionable emails get helped more often — and that compounds over time. These templates aren't scripts to copy word for word; they're structures that make your intent legible. Use them as a starting point, then adjust for your voice, your relationship with the recipient, and the stakes of the situation.

Looking for more help? These related articles cover similar situations:

How to Write a Professional Email: 7 Templates for Every Workplace Situation