# How to Send a Professional Email, Step by Step Canonical URL: https://headwayskills.com/knowledge/communication/how-to-send-a-professional-email/ Markdown URL: https://headwayskills.com/knowledge/communication/how-to-send-a-professional-email.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 step-by-step guide to sending a professional email: choosing the medium, the subject line, the right greeting, and the 60-second check before you send. ## Key facts - Title: How to Send a Professional Email, Step by Step - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Building Confidence - Primary keyword: how to send a professional email - Source page: https://headwayskills.com/knowledge/communication/how-to-send-a-professional-email/ ## What this page covers - A step-by-step guide to sending a professional email: choosing the medium, the subject line, the right greeting, and the 60-second check before you send. - Practical guidance for how to send a professional email - How this topic connects to Communication ## Detailed explanation Most people rewrite a four-line email three or four times before sending it — not because the words are wrong, but because nobody ever taught them what "professional" is supposed to sound like in writing. How to send a professional email comes down to a short sequence: send it from a [professional address](/knowledge/communication/professional-email-address/), with a subject line of four to eight words naming the topic, a greeting matched to the relationship, your main point in the first two sentences, one clear request with a deadline, and your full name at the end. Then proofread, confirm the attachment, and add the recipient last. What the format guides leave out is the decision that comes before any of that: whether this should be an email at all. ## How to send a professional email, step by step Eight steps, in order. The early ones take about thirty seconds each and prevent most of what goes wrong later. ### 1. Decide whether email is the right medium Email is the right choice when the message is informational, when you want a record of what was agreed, or when you are making a request the other person can handle in their own time. It is the wrong choice for [anything sensitive](/knowledge/communication/difficult-conversations-at-work/), anything complicated enough to need real back-and-forth, and anything you are effectively negotiating. Those belong in a conversation, where you can hear the reaction and adjust as you go. Almost none of the guides that dominate search results for this topic ask this question — they open at the subject line. But no amount of correct formatting rescues a message that should have been a five-minute call, and this is the only mistake on the list you cannot fix later. ### 2. Set up the sender and recipient fields Send from an address that reads as yours: some form of your name, on your school or company domain if you have one. Put in the To: field only the people you actually need something from. Cc is for people who need to see the message but not act on it, and every extra name lowers the odds that any one recipient treats the request as theirs. Check the spelling of the recipient's name against their own signature rather than your memory of it. Then do something that feels backward: leave the To: field empty while you write. You will fill it in at the last step, and the reason for that will be clear by then. ### 3. Write a subject line that names the ask Four to eight words, naming the topic or the action, ideally under fifty characters. Overloop's email format guide puts the contrast plainly: "Confirm Q3 pricing by Friday" gets opened, while "Quick question" gets skimmed and archived. The mechanism is triage. Someone with two hundred unread messages decides from the subject line alone whether yours can wait until Thursday, so a vague subject does not merely look weak — it delays the reply you are anxious about. If there is a deadline, put it in the subject. Most people find it easier to write once the body exists — write it last, place it first. ### 4. Choose a greeting that matches the relationship There is a ladder here rather than one correct answer. "Dear Mr. Smith" or "Dear Professor Smith" is the safe register for first contact with someone senior or someone outside your organization. "Hello Sarah" sits in the middle. "Hi Sarah" is the working default inside most companies. When you cannot tell which title someone uses, the more formal option costs you nothing. The rule worth taking from the format guides is to mirror the formality of the recipient's own last message to you. That turns an unanswerable question about style into an observable one. No study settles the right level of formality for a given workplace — every source on this subject is convention rather than research, which makes the recipient's own writing better data than any general rule. ### 5. Lead with your main message Put the point in the first two sentences, then give only the context the recipient needs in order to act on it. Guidance from Indeed and from the University of Florida's professional email tips converges on the same shape: three to five sentences, and no more than three short paragraphs. Length is a courtesy question rather than a style question. A long email does not just take longer to read; it moves the work of finding the point from you onto the person you are asking for a favor. If you are attaching something, name it in the body instead of letting it appear unexplained at the bottom, and check the size and format before you attach. Guides on emailing attachments flag oversized or unopenable files as a silent failure: the message arrives, the file will not open, and you never learn why the answer did not come. ### 6. Make the ask and the timeframe explicit Close the body with one specific action and when you need it. "Could you confirm by Wednesday whether the room is free?" does work that "let me know your thoughts" does not. Vague closings feel polite, and they are the most common reason a carefully written email gets read and then forgotten: the recipient has to work out what you want and by when, and that effort pushes the message down the pile. Ask for one thing. If you genuinely need two, number them. ### 7. Close with a sign-off and a signature Sign-offs ladder much as greetings do. Grammarly's guide to ending emails places "Sincerely" at the formal end, treats "Kind regards" and "Best regards" as the professional default that works almost anywhere, and keeps a bare "Best" for a thread already in motion. Follow it with your full name, and at work with your role and one way to reach you. Set the signature block once in your email client and it stops being a decision you have to make. ### 8. Run the pre-send check, then send Read the message aloud. Proofreading guides recommend this because your ear catches what your eye slides past: dropped words, and correctly spelled words that are the wrong word. Then confirm the attachment is actually attached and is the file you meant to send. Recipients come last. This is the ordering that pre-send checklists such as the one from Standss recommend, and the reason is mechanical rather than motivational: an empty To: field makes an accidental early send impossible. You are not relying on remembering to be careful — you have arranged things so that a slip has nothing to act on. Filling in the recipient becomes the deliberate act of sending, and the whole check takes about a minute. ## When you keep rewriting instead of sending If you have been [redrafting the same four lines](/knowledge/self-awareness/perfectionism/) for twenty minutes, the problem has stopped being the email. Sources written for students name this openly: email etiquette is rarely taught anywhere, so a [first message to a professor](/knowledge/communication/email-introduction-examples/) or an employer feels far heavier than four lines should. Several offer a reframe worth borrowing — emailing a professor is low-stakes practice for the message you will send a manager in two years. Two limits help more than further editing does. Give yourself a fixed number of rereads, usually two, and decide before you start what time you will send. Then send at that time. The email will not be perfect. Almost none of them are, and almost nobody notices. It is worth noticing what else sits in this category. Email conventions are one of a whole set of everyday work habits that nobody sits you down and explains, and [checking which you already have](https://assessment.headwayskills.com/) takes a few minutes — most people turn out to have picked up two or three of them without ever registering it. ## What makes this easier the second time Read back over those eight steps and notice how little of the work was about wording. Choosing the medium, reading the register, naming the ask, and sitting with the discomfort long enough to press send are judgment calls, and they are the same calls that surface in a meeting request, a phone call, or a conversation you have been putting off. **Communication** covers more of that list than you might expect: leading with the main message, keeping the subject line short and concrete, choosing only the recipients who need to be there, and proofreading before you send. It also covers the decision most email advice skips — whether writing is the right channel at all, given that building trust, handling sensitive subjects, and anything you need to negotiate go better in conversation. That reframes the task. You are not formatting a message; you are deciding what the message is and where it belongs. **Professional Behaviors** is the layer underneath the tone question. Email is where workplace etiquette becomes visible, permanent, and forwardable, which is exactly why the register question feels loaded. Being polite, keeping confidential things out of writing, and describing absent colleagues as though they were reading over your shoulder are the norms that decide what belongs in an email in the first place. None of that is obvious, and none of it is a character trait — it is a set of conventions, and conventions can be learned in an afternoon. **Building Confidence** is what closes the gap between a finished draft and a sent message. What works is not waiting to feel ready but acting before you do: deciding in advance when you will write and when you will send, accepting that the discomfort comes along anyway, and letting the evidence accumulate. After ten sent emails the eleventh takes four minutes, because by then you have proof rather than reassurance. None of the three is a trait you either have or lack; each is a behavior that gets steadier with use. The free Work Skills Test measures all three, along with **the nine others in the same set of twelve**. Where people usually get stuck is not knowing which one is the actual bottleneck — the etiquette, the clarity, or the hesitation — and [seeing which to build first](https://assessment.headwayskills.com/) beats trying to improve all of them at once. ## Making this your own Some of this may already describe how you work. You might reread before sending without being told to, or default to the more formal greeting when you are unsure. The difference between someone who finds these emails easy and someone who dreads them is rarely nerve or talent; it is a handful of habits picked up somewhere along the way, and habits stay available. You do not have to write like a different person to sound professional — a more direct version of how you already write is usually the whole change. Written messages also carry more as you take on more: more people read them, more decisions get made from them, and more of your work happens through them. That is a reason to settle this while the stakes are small — and it is one of the easier things to settle. By reading this far you have already done the part most people skip: you looked up how it is supposed to work instead of guessing. The open question is which of these habits deserves your attention first. ## See where your own skills stand That question has a quick answer, and you can get it privately, without telling anyone you are working on it. The Work Skills Test is a **free** self-assessment of twelve work skills — Communication, Professional Behaviors, and Building Confidence among them — and it takes about seven minutes. What comes back is a profile showing where you stand and which one or two skills would make the biggest difference right now. There is nothing to revise for; you answer honestly and read the result. **Take the skills test** Free, about seven minutes, and nothing to prepare. ## 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 step-by-step guide to sending a professional email: choosing the medium, the subject line, the right greeting, and the 60-second check before you send. ### 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-send-a-professional-email/ Preferred summary: "A step-by-step guide to sending a professional email: choosing the medium, the subject line, the right greeting, and the 60-second check before you send." ## Change log - 2026-07-07: Content collection version published.