WerasBlog

What's happening in AI, software, technology and science; plain and sourced.

Subscribe
Guides

How to Write a Business Email: A Guide to Clear, Professional Correspondence

The structure of a professional business email from subject line to sign-off, common mistakes and ready-made templates for requests, follow-ups and meeting summaries.

How to Write a Business Email: A Guide to Clear, Professional Correspondence
Image: Christin Hume · Unsplash · Unsplash License

Writing a good business email comes down to one principle: the reader should understand why the email arrived and what's expected of them within the first two sentences. To get there, use a descriptive subject line, a short greeting, your purpose in the first paragraph, details in bullet points if needed, a clear ask with a date and, finally, a short sign-off. Below, we break this structure down step by step and share templates you can use right away.

The structure of a good business email

A professional email has six parts:

  1. Subject line: Summarizes the content and, if needed, the action expected.
  2. Greeting: A short salutation that fits the company culture.
  3. Purpose statement: Why you're writing, in one sentence.
  4. Context and details: The information the reader needs to decide or do the work, in bullet points where possible.
  5. Ask and deadline: What you need, from whom and by when.
  6. Sign-off and signature: A short closing line and a signature with your contact details.

This order lets the reader understand the email from its first few lines alone. For someone glancing at email on their phone between two meetings, that makes all the difference.

How do you write a subject line?

The subject line determines whether and when an email gets opened. A good subject line is specific and, where needed, includes an action and a date.

WeakStrong
InfoMarch sales report attached
MeetingAgenda for Thursday 2 p.m. project meeting
QuestionApproval needed: New supplier contract, Friday
URGENT!!!By 5 p.m. today: Approve proposal pricing

Adding short labels like "Approval needed," "FYI" or "Decision:" at the start of the subject line helps the recipient prioritize. If the topic changes as the thread goes on, update the subject line too.

How to write a business email: rules for the body

One email, one purpose

If you cover several unrelated topics in one email, the recipient will usually reply to only one of them. If the topics are independent, send separate emails. If one topic has several questions, number them so the reply can follow the same numbers.

Conclusion first, then the reasoning

Don't greet the reader with a long backstory. Say first what you need or what happened, then give the reasoning.

  • Weak: "In our meeting with the supplier last week, a few topics came up, and they mentioned there might be some changes on pricing..."
  • Strong: "The supplier is updating prices from April; we need to approve the new quote by Friday. Details below."

Short paragraphs and bullet points

Break up paragraphs longer than three or four lines. Use bullet points for options, steps or dates. Bolding an important date or decision keeps a fast reader from missing it, but use bold sparingly.

A clear ask

Instead of "Looking forward to your thoughts," write "If the proposal works for you, could you approve it by Wednesday at noon?" If the ask goes to several people, say by name who needs to do what.

Tone and greeting

Match the formality to your relationship and your company culture. In a first email to someone you don't know, use a polite greeting with their name (in Turkish business correspondence, for example, that means the formal "siz" form and "Sayın" or "Merhaba" with the full name); if the other person switches to a more casual tone, follow their lead. A short sign-off like "Best regards" or "Thanks" is enough.

Pre-send checklist

  • The subject line describes the content and the action expected.
  • The first two sentences state the purpose clearly.
  • The ask, the owner and the deadline are clear.
  • Attachments are actually attached and have clear file names.
  • The recipients are right; is "Reply all" really needed?
  • No wrong recipients on an email with confidential information.
  • Spelling and proper names have been checked.

If you use Gmail, increasing the "Undo send" period in Settings gives you a chance to fix mistakes you notice right after hitting send.

Ready-made templates

Request email

Subject: Approval needed: [Topic], [date]

Hi [Name],

We need your approval on [topic] by [date].

  • Scope: [short description]
  • Cost / timeline: [details]
  • Next step after approval: [what happens]

If it looks good, just reply "approved" to this email. Happy to answer any questions.

Best regards, [Signature]

Follow-up email

Subject: Follow-up: [Previous topic]

Hi [Name],

I wanted to follow up on my email from [date] about [topic]. We can't move on to [dependent task] without [the decision / information]. If you can get back to me by [new date], we can keep the plan on track.

Thanks, [Signature]

Meeting summary

Subject: Summary and action items: [Meeting name], [date]

Hi all,

Here's a summary of today's meeting.

Decisions:

  1. [Decision]
  2. [Decision]

Action items:

  • [Person]: [task], [date]
  • [Person]: [task], [date]

If anything is missing or incorrect, let me know by noon tomorrow and I'll update it.

[Signature]

When replying

The same principles apply when you reply to an email. If the sender asked several questions, answer each one separately and in the same order; if needed, quote the question briefly and write your answer below it. When someone new is added to a long thread, instead of making them read the whole chain, write a two- or three-sentence summary at the top: what the topic is, where things stand and what's expected of them. That short summary saves the newcomer time and prevents misunderstandings.

How quickly you reply is part of the message too. If you can't send a detailed answer right away, send a short acknowledgment: "Got your email; I'll get back to you in detail by Thursday." That one sentence saves the other person from having to chase you.

Common mistakes

  • Using "Reply all" when it isn't needed.
  • Leaving the subject line blank, or starting a new topic under an old thread's subject.
  • Forgetting the attachment. Attaching the file first and writing the text afterward reduces this mistake.
  • Replying immediately on a tense topic. Save it as a draft and reread it after a while.
  • Writing in all caps or with lots of exclamation points.

If you also want to keep your inbox under control, check out the inbox zero and Gmail filters posts on our blog.

Conclusion

At its core, writing a business email is about respecting the reader's time. A descriptive subject line, the purpose in the first sentence, bullet-pointed details and a clear ask make things easier for both you and the recipient. Adapt the templates to your own work and run through the checklist before you hit send.

#business email#correspondence#professional communication#email management

From Weras Labs

We can help you with this

We turn what you just read into working software for your business. You talk to the person writing the code; price and timeline are clear from day one.

Frequently asked questions

How should you start a business email?

Open with a short greeting ("Hi [Name]," or a more formal salutation for someone you don't know) and state the purpose of the email in one sentence right after. Long introductions and generic pleasantries delay the main message.

How long should a business email be?

Long enough to include what the reader needs to make a decision or do the work. If an email runs longer than a screen, it's usually better to move the details into an attachment or link and give a summary in the body.

How should you end a business email?

After a clear ask or next-step sentence, use a short sign-off like "Best regards" or "Thanks." Below it, add a signature with your name, title and contact details.

When should I follow up on an email that hasn't been answered?

If you gave a date in your email, follow up after that date; if not, send a short follow-up after a few business days. In the follow-up, restate the original ask and what the delay is affecting in one sentence.

About the author

Habip Dayan

Habip Dayan

Founder of Weras Labs

Habip Dayan is the founder of Weras Labs, a company that builds software products for professionals and teams. He has been building software since 2018 and writes about AI, cloud architecture and product design.

Comments

Be respectful; no ads or personal data. Comments that break the rules are removed.