# How to Write an Email: Examples for Every Common Situation Canonical URL: https://headwayskills.com/knowledge/communication/how-to-write-an-email-example/ Markdown URL: https://headwayskills.com/knowledge/communication/how-to-write-an-email-example.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 A professional email has six simple parts. See how to write an email, with clear examples for requests, applications, follow-ups, thank-yous, and more. ## Key facts - Title: How to Write an Email: Examples for Every Common Situation - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Building Confidence - Primary keyword: how to write an email example - Source page: https://headwayskills.com/knowledge/communication/how-to-write-an-email-example/ ## What this page covers - A professional email has six simple parts. See how to write an email, with clear examples for requests, applications, follow-ups, thank-yous, and more. - Practical guidance for how to write an email example - How this topic connects to Communication ## Detailed explanation The short answer to how to write an email: use six parts — a subject line that names your purpose, a greeting matched to the person, an opening line that says why you're writing, a short body with the details, a courteous sign-off, and a signature with your name. Fill those six in, and almost any email works. The format is the easy part. What actually slows people down is the situation — writing to a professor you've never met, chasing a reply without sounding pushy, saying sorry for a mistake without groveling. So the fastest way to get it right is to see that format filled in for the messages you actually send, which is what the examples below do. ## How to write an email: the parts every message needs Before the examples, here's the skeleton every one of them shares. The **subject line** names the topic in about six to ten words; guides from Indeed to university writing centers suggest keeping it under roughly 40–60 characters and front-loading the words that matter, since many email apps cut off long subjects on a phone — "Question about Friday's deadline" beats a bare "Question." The **greeting** matches how well you know the reader: "Dear [Name]" for a formal or first message, "Hello [Name]" as a safe middle, "Hi [Name]" for people you work with. The **body** leads with your main point instead of burying it; most guides land around 50–125 words, with paragraphs of four or five sentences and enough white space to scan. Close with a **sign-off** — "Best," "Kind regards," "Regards" — and a **signature** with your name, plus your role and a way to reach you on anything professional. Skip slang and emojis in a [formal note](/knowledge/communication/formal-email/), and proofread before you send. If you've ever [reread a two-line message](/knowledge/self-awareness/perfectionism/) five times before hitting send, the six parts were never your problem — the judgment calls were. Those calls get easier the more you notice which ones come naturally to you, so it can help to [gauge your email habits](https://assessment.headwayskills.com/) before your next message that matters. ## Email examples for the situations you'll actually face The parts stay the same; the wording shifts with the situation. Here are six of the emails you're most likely to write, each with a short model you can adapt. ### 1. Asking someone for something The most common email you'll send is a request — to a professor, a manager, or a team you don't know. Put the ask in the first line, give just enough context to make it easy to say yes, and name a specific date instead of "ASAP." A small, clear request gets a faster reply than a long, hedged one. > **Subject:** Extension request — ECON 210 problem set > > Hi Professor Lee, > > Could I have until Monday to hand in this week's problem set? I was out sick Thursday and Friday and want to submit work I'm actually happy with. I'm glad to share a doctor's note if that helps. > > Thank you,\ > Maya Torres ### 2. Applying for a job or internship When you email an application or introduce yourself to a recruiter, the reader decides in seconds whether to keep going. Name the role in the subject, say in one sentence why you fit, and point to your attached CV rather than retyping it. Warm, brief, and specific beats long every time. > **Subject:** Application — Marketing Intern (Jun–Aug) > > Dear Hiring Team, > > I'm applying for the summer Marketing Intern role. I'm a final-year communications student, and the campaign work in your posting is exactly what I've been building toward. My CV is attached, and I'd welcome the chance to talk it through. > > Best regards,\ > Sam Okafor ### 3. Requesting a meeting A meeting request lives or dies on how easy you make it to say yes. Put the topic — and, if you can, a proposed time — right in the subject line. Offer two or three specific slots so the reader picks instead of negotiating, and say in one line what the meeting is for. > **Subject:** 20 minutes to review the Q3 timeline? > > Hi Dana, > > Could we grab 20 minutes this week to walk through the Q3 timeline before it goes out? I'm free Tuesday after 2pm or Thursday morning — whichever is easier for you. > > Thanks,\ > Priya ### 4. Following up when you hear nothing back Silence usually means the reader is busy, not uninterested. Career sites like The Muse suggest waiting about a week, then replying on the original thread so the context is right there. Keep the nudge short, and open with something soft like "just checking in" so it doesn't read as pushy. > **Subject:** Re: Application — Marketing Intern (Jun–Aug) > > Hi again, > > I wanted to kindly check in on my application from last week — I'm still very interested in the role and happy to send anything else that would help. Thanks for your time. > > Best,\ > Sam Okafor ### 5. Saying thank you after an interview Send this within about a day, while you're still fresh in the interviewer's mind. Thank them, mention one specific thing from the conversation so it doesn't read like a template, and restate your interest in a line. Short is fine here — the gesture matters more than the length. > **Subject:** Thank you for your time today > > Dear Ms. Alvarez, > > Thank you for talking through the analyst role today. I especially enjoyed hearing how your team supports new hires in their first month — it's exactly the kind of start I'm looking for, and it left me even more excited about the position. > > Best regards,\ > Jordan ### 6. Apologizing for a mistake When you've slipped up, a clean email beats a long one. Name what happened plainly, [take responsibility](/knowledge/confidence/learn-from-mistakes/) without over-explaining, and move straight to the fix. One apology is enough; the reader mostly wants to know it's handled. > **Subject:** Correction — wrong figures in this morning's report > > Hi team, > > I sent the sales report this morning with last month's numbers by mistake. The corrected version is attached, and I've double-checked the totals. Sorry for the mix-up and any confusion it caused. > > Best,\ > Alex ## The skills that make email feel easy Look across those six examples and the software barely matters. What makes each one work is reading the person on the other end, being clear, and having the nerve to send. Those are skills — and a few specific ones carry most of the load. **Communication** is the obvious one, and email is among its most everyday tests. Leading with your point, keeping it brief, matching your greeting to the reader, making a clean ask — that's communication in written form. In this framework it isn't about big vocabulary or grammar drills; it's the small, deliberate choices that get you understood quickly and pleasantly by whoever's reading. **Professional Behaviors** is the etiquette layer every email sits inside: matching your formality to the relationship, staying polite when you're annoyed, being careful with anything confidential, and writing about other people as if they'll read it. It's not dress codes or office politics — just the quiet signals of respect that make a message feel considered rather than careless. **Building Confidence** is the part that's really about hitting send. If you rewrite a short email ten times or leave an important one sitting in drafts, the format was never the issue — it's the worry about getting it wrong. In this framework confidence is built by doing: send the message, watch it land fine, and the next one comes easier. A good example lowers the stakes enough to start. Here's the encouraging part: every one of these habits is learnable. A free Work Skills Test can show you where your own writing stands right now — communication, professional behavior, and the confidence to hit send are three of the twelve skills it looks at. If these examples left you second-guessing your own emails, that's a good reason to see [which skills to build first](https://assessment.headwayskills.com/). Some of this may already sound like how you work — pausing to picture who will read the message, or giving it one more read before it goes out. That instinct is the skill in motion, and it sharpens with every email you send. The clumsy parts aren't fixed limits; they're just the moves you haven't practiced yet, and you can smooth them out while still sounding like yourself. It matters more as you go, too. The further into a job you get, the more of your work happens over email, and the more a clear, well-judged message shapes how people read you. The encouraging part is specific: you're already paying attention to how your writing lands, which is the exact habit most people never stop to build. What's left is simply seeing where you stand. ## See where you stand The only thing left is to find out where you're starting from. The **free** Work Skills Test is a short self-assessment of your everyday work skills — communication among them — that shows where you stand across all twelve and points you to the few that will make the biggest difference to how you come across, on email and in person. It takes about seven minutes, and instead of a blunt pass-or-fail, it hands you the specific, learnable places worth your attention next. **[Take the skills test](https://assessment.headwayskills.com/)** *A quick, free snapshot of where your work skills stand today.* ## 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? A professional email has six simple parts. See how to write an email, with clear examples for requests, applications, follow-ups, thank-yous, and more. ### 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/how-to-write-an-email-example/ Preferred summary: "A professional email has six simple parts. See how to write an email, with clear examples for requests, applications, follow-ups, thank-yous, and more." ## Change log - 2026-07-07: Content collection version published.