# How to Start a Professional Email Without Rewriting Line One Canonical URL: https://headwayskills.com/knowledge/communication/start-a-professional-email/ Markdown URL: https://headwayskills.com/knowledge/communication/start-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 How to start a professional email: seven steps from subject line to first sentence, with a rule for choosing between Dear and Hi, and the openings to skip. ## Key facts - Title: How to Start a Professional Email Without Rewriting Line One - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Building Confidence - Primary keyword: start a professional email - Source page: https://headwayskills.com/knowledge/communication/start-a-professional-email/ ## What this page covers - How to start a professional email: seven steps from subject line to first sentence, with a rule for choosing between Dear and Hi, and the openings to skip. - Practical guidance for start a professional email - How this topic connects to Communication ## Detailed explanation The message itself is written. The greeting is not, and you have now typed and deleted "Hi," "Hello," and "Dear" in some order while the cursor sits at the top of the draft. To start a professional email, write a specific subject line of under ten words, greet the recipient by name — "Dear" plus title and surname for someone senior or unfamiliar, "Hi" plus first name for a colleague you already work with — and use the first sentence to state why you are writing. Every list of greetings on the first page of results says a version of that. What none of them tells you is which of those two situations you are actually in, and that call gets made two steps before you type a word. ## How to start a professional email in seven steps The order below matters more than it looks. Each step decides something the next one needs, which is why the opening is so hard to write in isolation: people usually get stuck at step four while the real problem is sitting back at step one. ### 1. Decide what you want the reader to do Before any wording, name the single action or answer you need. The step-by-step guides from Hunter.io, Grammarly, and PaperTrue all begin here rather than with vocabulary, and the reason shows up immediately in the drafts that stall. A first line like "I have a question" is almost never a vocabulary failure. It is what an undefined purpose looks like on the page: the writer does not yet know what they are asking, so the sentence hedges. Once the ask exists in one plain phrase — a signed form, a meeting slot, a decision on the proposal — the opening line has something to be about. ### 2. Place the recipient on the formality scale Two questions settle this. Do you already work with this person, and is this your first written contact? Grammarly, LanguageTool, and Adobe converge on the same rule: formality follows the relationship and the hierarchy, not your own preference or how friendly you feel. Someone senior, someone you have never emailed, or an official first approach sits at the formal end. A teammate you message weekly sits at the familiar end. Most people land in the middle. Worth separating from politeness: Fyxer and Revo both point out that "Hey," exclamation marks, emojis, abbreviations, and slang are perfectly correct in chat and wrong in a first email to a client or a senior leader. The same words change value with the channel. Getting that wrong is not rudeness, it is a register mismatch, and it is the single most common reason a well-meant email reads as careless. Reading the person on the other end is the part no template hands you, and it does not only apply to email. If you would rather not learn it one uncomfortable message at a time, a short assessment will show you [where that judgment already holds](https://assessment.headwayskills.com/) and where it is still guesswork. ### 3. Write the subject line before the greeting It is composed early because it is read first. The convention across the guides — Fyxer and Grammarly among them — is roughly eight to ten words at most, specific rather than general. Treat that as an editorial norm rather than a measured finding; no study sits behind the number. What the guides agree on more firmly is the failure mode. A subject line of "Important," "Hi," or "Quick question" gives the recipient nothing to sort by, so it drifts down an inbox where more legible messages get handled first. And "free," "urgent," or a row of exclamation marks pushes the other way, reading as spam-adjacent before anyone has opened it. Name the thing: the project, the form, the date. ### 4. Choose the greeting and check the name Now the decision from step two pays out. Formal takes "Dear" plus title and surname. Standard takes "Hi" or "Hello" plus a first name. The awkward case is a name that tells you nothing about title or gender, and there is a clean answer for it: use the full name. Adobe and Grammarly both recommend "Dear Jordan Williams" precisely because it stays formal while assuming nothing. That is a better move than guessing an honorific, and a far better one than falling back on "To Whom It May Concern" or "Dear Sir or Madam." LanguageTool and Proton discourage both, and the reason is more pointed than sounding dated: they tell the recipient you did not find out who you were writing to. For a job application, where the name is usually two minutes away on a department page, that reads as a research failure rather than a style choice. Then spend the extra few seconds on spelling. Adobe and Grammarly single this out as the highest-cost opening error, because a misspelled name colors how carefully everything after it gets read. Copy it from their signature block or profile rather than from memory. ### 5. Say why you are writing in the first sentence Lead with the main message. The recipient is scanning to work out what is being asked of them, and the opening sentence is where they expect to find it. This is also where the concrete beats the vague by a wide margin. Grammarly's guidance replaces "Just checking in" with "I'm following up on the proposal I sent last week," and swaps a general nudge for "I wanted to check on next steps for" a named project. Both versions are equally polite. Only one of them lets the reader answer without first reconstructing which thread you mean. ### 6. Decide whether the pleasantry earns its line Here the sources genuinely disagree, which is worth knowing if you have been reading them all and feeling more confused rather than less. LanguageTool still lists "I hope this email finds you well" among standard polite openers. Grammarly's guidance points the other way, toward cutting throat-clearing in favor of a purposeful first sentence. The resolution is not that one side is wrong. The courtesy line is not forbidden, it is simply not load-bearing — it costs the reader a line before the point arrives. So keep it where a real relationship makes it read as warmth rather than filler, and where you can make it specific enough to mean something. Drop it when you are writing to someone busy or unfamiliar, where the fastest courtesy you can offer is telling them what this is about. ### 7. Read the first three lines aloud, then send Grammarly and PaperTrue both recommend reading the message aloud before sending, and they are specific about why: it catches awkward phrasing, which spellcheck cannot see. Since tone is what you were worried about in the first place, the subject line, the greeting, and the opening sentence are the three that repay it. Check the recipient list. Then send it, rather than opening a fourth round of edits. The fluency you are looking for comes from messages that went out, not from greeting lists read one more time. ## What makes the opening easier the next time Read those seven steps back and notice how few of them turn on vocabulary. One is about knowing your own purpose, two are about reading another person, one is about caring enough to check a spelling. The words on line one are the visible end of all that. **Communication** is doing most of the work, and its written side is narrower than it sounds: lead with the main message, keep the subject line concise, send only to the people who need it, proofread, reply in reasonable time. Add adapting to the receiver rather than to your own default, and you have essentially reproduced the steps above from first principles. That is why the principle travels further than any list of greetings — it tells you what to do with a recipient the list never anticipated. **Professional Behaviors** are the reason a greeting carries weight at all. Politeness, humility, and treating everyone impartially are not abstractions in an email; they show up in whether you looked up a name, which honorific you reached for, and how much of someone's attention you assumed. The impartial part is easy to miss: the same care goes into the message to the person who is junior to you as into the one to the director. And none of this is intuition you were supposed to arrive already holding. These are conventions, which means they are learnable, and checking them before you send is exactly how people learn them. **Building Confidence** is the skill for the twenty minutes you just spent on one line. Rewriting an opening is rarely about the opening; it is discomfort with sending something you cannot take back. What helps is deciding in advance how you will open before you sit down to write, and getting past only the first step rather than the whole message. The rest follows from evidence: each email you actually send makes the next one cheaper to write, which is a slower fix than a template and a permanent one. A short assessment will tell you which of those three to put your attention on first. It does not stop at three, though — there are **twelve of these work skills** in the framework, and it reads them together, because the one slowing you down is often not the one you came looking for. It is free, and you can [see which to build first](https://assessment.headwayskills.com/) before the next message you have to think this hard about. ## What this turns into later You have probably made this call before without giving it a name — the time you moved from "Hi" to "Dear" because their reply came back signed with a full title, or dropped a pleasantry that suddenly looked like padding. Which is the useful part, because it means the gap here is not about who you are. Nobody starts out fluent at writing to people who have authority over them and no context on them. It comes from sending a lot of those messages and noticing what came back, and you get there in your own voice rather than borrowing someone else's idea of what professional sounds like. The stakes also rise quietly. The email asking for a form becomes the email asking for a reference, a budget, a decision. You are reading this with the draft still open in another tab, which is the instinct that makes all of this easier to build — checking the convention first, rather than working it out from a reply that landed oddly. What is left is knowing which parts to work on. ## Start from where you already are You know what goes at the top of the message now. The open question is what else is running underneath it. The Job Skills Test is a **free** self-assessment of the twelve work skills that carry the most weight in the first years of a career, communication among them. You take it on your own, and it gives you a read on where you stand across all twelve, plus the two or three that would make the biggest difference to work on next. Run it before you send the message you came here to write, and you will know whether what needs building is the wording or the read on the person receiving it. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, 7 minutes, and your results appear as soon as 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? How to start a professional email: seven steps from subject line to first sentence, with a rule for choosing between Dear and Hi, and the openings to skip. ### 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/start-a-professional-email/ Preferred summary: "How to start a professional email: seven steps from subject line to first sentence, with a rule for choosing between Dear and Hi, and the openings to skip." ## Change log - 2026-07-07: Content collection version published.