# Writing Emails in English: Examples You Can Follow Step by Step Canonical URL: https://headwayskills.com/knowledge/communication/writing-emails-in-english-examples/ Markdown URL: https://headwayskills.com/knowledge/communication/writing-emails-in-english-examples.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving communication at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer See how a professional email in English is built, step by step, with a full worked example, greeting and sign-off options, and the mistakes to avoid. ## Key facts - Title: Writing Emails in English: Examples You Can Follow Step by Step - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Building Confidence - Primary keyword: writing emails in english examples - Source page: https://headwayskills.com/knowledge/communication/writing-emails-in-english-examples/ ## What this page covers - See how a professional email in English is built, step by step, with a full worked example, greeting and sign-off options, and the mistakes to avoid. - Practical guidance for writing emails in english examples - How this topic connects to Communication ## Detailed explanation When you are writing emails in English, the message has six parts: a specific subject line, a greeting, an opening line that says why you are writing, a short middle that carries the details, a clear request, and a sign-off with your name. Get those six in the right order and the English itself matters far less than you expect. Most people looking for examples are not short of vocabulary. They are short of a standard — something to hold a draft against, so they can tell whether it reads as professional, too stiff, or accidentally blunt. That is exactly what a good example gives you. The catch is that a sample only teaches you anything if you can see the pattern underneath it. So here is the pattern first, one step at a time, and then a complete email built from it. ## The eight steps for writing emails in English, with an example at each stage The order below is chronological, and the dependencies are real: each step is easier once the one before it is settled. It is worth noticing where drafts actually go wrong. Steps one to three happen before you type a single sentence of the message — and that is where most of the damage is done, long before anyone reaches for a dictionary. ### 1. Decide what the email is for — and whether it should be an email Indeed's guide to professional emails suggests finishing one sentence before you draft anything: *I'm writing this email to ___.* Treat it as a gate rather than a warm-up. If you cannot complete it in a single clause, the message is not ready to be written yet. The same sentence catches the emails that should never have been emails. Writing is the right channel when the reader needs time to think, when you want a record of what was agreed, or when the information only travels one way. A disagreement or a sensitive topic will nearly always go faster in a conversation. *Example:* I'm writing this email to ask Ms. Alvarez to approve the revised budget before Friday. ### 2. Choose your recipients before you write Who is in the To line changes how you write everything after it, which is why this comes before the words and not after them. Indeed's guidance is to address the person most likely to have the information, and to check To, Cc, and Bcc deliberately rather than as a final formality. The working rule: To is for the people who must act, Cc is for the people who only need to know. Superhuman's roundup of etiquette failures puts reply-all abuse among the most commonly cited mistakes, and the risk it names is not just noise — [confidential information](/knowledge/professional-behaviors/confidentiality-in-the-workplace/) can reach an entire distribution list in one click. Before you reply to everyone, check whether everyone actually needs your answer. ### 3. Write the subject line as a summary, not a label According to EC English, the subject is the first piece of information the recipient sees, and an unclear one can push a reader to delete the message without opening it. [Keep it short](/knowledge/communication/concise-communication/), and state the purpose in as few informative words as you can. The difference is between labeling the topic and summarizing the message. *Question* is a label. *Question about Friday's budget approval* is a summary — the reader knows what it is and roughly what it will cost them before they open it. ### 4. Pick a greeting that matches what you know about the reader Greeting choice is not a matter of taste; it follows from what you know. Wall Street English and EC English both list the same set: *Dear Mr/Mrs/Ms* plus the surname when you know the name, *Dear Sir or Madam* or *To whom it may concern* when you do not, and a first-name greeting for colleagues you already work with. Whatever you choose here sets the formality the rest of the email has to hold. When you are unsure, start one notch more formal than you think you need and follow the other person's lead in later messages. Reading which level a situation calls for is judgment rather than vocabulary, and it is one of the things [seeing where your communication stands](https://assessment.headwayskills.com/) can make visible, since it is a skill you can build rather than a fact you look up. ### 5. State your purpose in the first sentence Grammarly's formal email structure is three short paragraphs, and the first one does a single job: state why you are writing, in one sentence, before any background. This is worth pausing on, because it runs against the habit many writers bring from other languages and traditions, where the reasoning is laid out first and the request arrives at the end. English business email inverts it. The reader wants the point, then the evidence. *Example:* I'm writing to ask for your approval on the revised Q3 budget. ### 6. Give the details in one short middle paragraph The middle paragraph carries what the reader needs in order to act: dates, references, what is attached, what changed. Nothing else. Long, complicated paragraphs are one of the markers Mailchimp names in unprofessional emails, precisely because they bury the point the reader is looking for. If a detail does not help the person do the thing you are about to ask for, it does not belong here. ### 7. Make the request explicit — and soften it The last paragraph is the ask, and it needs both parts: a clear request and a specific next step. Vagueness here is what produces the reply that says only *thanks, noted.* Softening is the part that most often goes wrong for second-language writers, and the fix is small. Modal verbs do almost all the work: *Could you please confirm...* reads as professional where *Confirm this...* reads as brusque. Grammarly and Wall Street English add two more register rules for formal messages — avoid contractions, and hold back emoji and exclamation marks until the other person has used them first. Then close with one polite sentence, a sign-off such as *Sincerely*, *Kind regards*, or *Best*, and your full name with your title where it is relevant. ### 8. Proofread, then check the top of the email again Read the draft out loud. Indeed recommends it specifically because it catches what silent reading skips: awkward phrasing, run-on sentences, missing words. For anyone writing in a [second language](/knowledge/communication/international-business-communication/) it is unusually useful, since those are exactly the problems a grammar checker passes without comment. Then go back up and re-check the recipients, the subject line, and the spelling of the reader's name. Those are the errors a reader notices first, and the ones you cannot take back once the message is gone. ## A complete example, from subject line to sign-off Here is the whole pattern assembled into one email. It is around ninety words, which is normal — most work emails should be shorter than people expect. > **Subject:** Approval needed — revised Q3 budget (by Friday) > > Dear Ms. Alvarez, > > I'm writing to ask for your approval on the revised Q3 budget. > > The updated version is attached. It reflects the two changes we discussed on Monday: the training line is reduced by 8 percent, and the software renewal has moved to September. Nothing else has changed. > > Could you please confirm your approval by Friday, so that finance can process it in this cycle? I'm happy to walk you through the changes if that would be easier. > > Kind regards, > > Tomas Lindberg > Project Coordinator, Northline Every part is doing one job. The subject summarizes and gives the deadline. The first sentence is the purpose. The middle paragraph is only the details needed to decide. The request is explicit, softened with *could you please*, and tied to a reason. ## Mistakes that undo an otherwise good email The markers that make an email read as unprofessional are not the ones most people worry about. Across Superhuman's and Mailchimp's lists, the recurring offenders are vague subject lines, missing greetings, ALL CAPS, reply-all abuse, and paragraphs so long the point disappears inside them. Grammar and vocabulary errors are not at the top of either list. That is reassuring and uncomfortable at once. Your English is less exposed than you think; your judgment about structure, recipients, and tone is more exposed. Email strips out [the cues that carry tone](/knowledge/communication/written-communication-in-the-workplace/) in a conversation, so the wording holds weight it never would in speech. ## The skills that make this easier every time Look back at what the eight steps actually asked of you. Choosing a channel. Deciding who needs to act. Leading with the point. Reading how formal a relationship is. Almost none of it was English. **Communication** is the skill doing most of the work here. It covers the choice between writing and talking — writing when the reader needs time, when you want a record, or when the message travels one way — and it covers the email habits themselves: main message first, a concise subject line, only the recipients who need to be there, proofreading, and replying in good time. The eight steps above are that skill applied to one channel. **Professional Behaviors** covers the layer the samples never explain: being polite, being timely, handling confidential information carefully, and matching your formality to the situation rather than to a template. It also names the tones that quietly damage a working relationship — the passive message that avoids saying anything, the sharp one that reads as an attack, the steadily negative one. In email, where the reader has no face or voice to check against, those are easy to send by accident. **Building Confidence** is the one that decides whether any of this gets used. Plenty of people can write a perfectly good email and still leave it in drafts, rereading it. That is the practical part of this skill: deciding in advance when you will write and send, accepting the discomfort rather than waiting for it to pass, and letting evidence accumulate. Reading fifty sample emails produces no evidence. Sending five produces some. None of the three is fixed, and none of them is really about email — they show up wherever your work touches other people. The free Job Skills Test measures all **twelve work skills** this framework covers, so it gives you something a collection of email templates cannot: [how your wider skills score](https://assessment.headwayskills.com/), including the ones you have never thought to look at. ## Where this goes next Some of this probably already describes how you work. You read past the sample email to the pattern underneath it, which is not what most people do — most copy the sample, send it, and learn nothing they can reuse next week. That instinct is worth more than any template you could collect. It is also worth knowing that written messages carry more weight as your responsibilities grow, not less. More of your work reaches people who never see you in person, and the email is the whole impression. That points at something you can act on: these are learnable habits, not fixed traits, and you can build them without becoming a different kind of person at work. Which leaves one question worth answering before you go back to your inbox — not how your last email read, but where your work skills stand overall. ## See where your skills stand The only thing left is to find out. The Job Skills Test is a **free** self-assessment of your work skills — you answer it on your own, at your own pace, with nobody watching. It shows you how you score across all twelve of the skills that shape working life, so you can see which ones would make the most difference to you right now, rather than guessing. Look at it whenever it suits you. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, takes 7 minutes, and your results appear the moment you finish.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? See how a professional email in English is built, step by step, with a full worked example, greeting and sign-off options, and the mistakes to avoid. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Professional Behaviors, Building Confidence. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/professional-behaviors.md - https://headwayskills.com/knowledge/confidence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/communication/writing-emails-in-english-examples/ Preferred summary: "See how a professional email in English is built, step by step, with a full worked example, greeting and sign-off options, and the mistakes to avoid." ## Change log - 2026-07-07: Content collection version published.