# How to Write an Email to a Client Without Rewriting It Five Times Canonical URL: https://headwayskills.com/knowledge/communication/how-to-write-an-email-to-a-client/ Markdown URL: https://headwayskills.com/knowledge/communication/how-to-write-an-email-to-a-client.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 write an email to a client: how formal to be, what belongs in the subject line, how to ask without hedging, and how to follow up or deliver bad news. ## Key facts - Title: How to Write an Email to a Client Without Rewriting It Five Times - Category: Communication - Primary skill: Communication - Related skills: Influence, Professional Behaviors - Primary keyword: how to write an email to a client - Source page: https://headwayskills.com/knowledge/communication/how-to-write-an-email-to-a-client/ ## What this page covers - How to write an email to a client: how formal to be, what belongs in the subject line, how to ask without hedging, and how to follow up or deliver bad news. - Practical guidance for how to write an email to a client - How this topic connects to Communication ## Detailed explanation The draft has been open for twenty minutes and you have rewritten the first line four times. Knowing how to write an email to a client comes down to five decisions: whether it should be an email at all, a subject line naming the specific thing, a greeting pitched slightly more formal than feels natural, the ask stated plainly in its own sentence, and a neutral sign-off. The wording matters far less than that order. None of those rules are obscure. The hard part is that you cannot tell, from inside your own draft, whether following them makes you sound competent or presumptuous, and a client is the one reader you would rather not test that on. ## How formal should I be when I write an email to a client for the first time? More formal than feels natural, then let the client lower it. The convention is settled and asymmetric by risk. Robert Half's guidance on client greetings is explicit that with a new client or an executive it is better to be too formal than too casual: "Dear Ms. Johnson" for a first contact, "Hi James" somewhere you arrive later — after their own replies have set that register. Which answers the question underneath the question: you are not guessing the right level on the first attempt, you are starting one notch high and following the client down. If they sign with their first name, use it next time. Sign-offs get far more thought than they deserve — "Sincerely," "Best regards," "Regards," and "Thank you" are the safe set across every source, with text abbreviations like "Tx" ruled out however well you know someone. ## What do I put in the subject line so the client actually opens it? The specific thing the email is about, in under about seven words. The length rule is consistent — LaGrowthMachine puts it at under seven words, Mailchimp's formal email guidance at under roughly 50 characters — but the reason behind it is more useful than the number. A subject line is not only a hook, it is a filing label. Clients search their inbox weeks later for the message about the invoice or the timeline. "Invoice details for March" and "Meeting request for Thursday" are still findable in November; "Follow-up," "Quick question," and "Hello" are not findable the same afternoon. The real test is not whether it sounds professional, but whether the client could find it again by typing one word they already know. ## How do I ask for what I need without sounding demanding? State the ask plainly in its own sentence, and cut the apologies wrapped around it. A tone analysis from Professional & Friendly names the specific phrases that damage the writer: "So sorry to bother you," "I hate to ask," and "if it's not too much trouble." The effect is not that they read as rude — they read as anxious, and they lower the writer's perceived authority. Hedging feels like courtesy from the inside and lands as uncertainty from the outside. The mechanism is simple: every hedge is another sentence the client works through before finding out what you want. That is also why brevity matters more than it feels like it should — length reads as work you have handed someone, not effort you put in. Say what you need, give an actual date rather than "as soon as possible," and [make the yes easy](/knowledge/influence/influence-without-authority/) — if the full request is unlikely to land, ask for the smaller version instead. The awkward part is that you cannot hear your own register from inside the draft, which is why a fifth reread rarely changes anything. That blind spot is worth checking from the outside, and seeing [how your writing actually lands](https://assessment.headwayskills.com/) tells you more in a few minutes than another pass over the same paragraph. ## How do I follow up when a client hasn't replied? After three to five business days, with a message that does not imply they did anything wrong. The timing is standard: Fyxer's follow-up guidance puts it at three to five business days after silence, and 24 to 48 hours after a meeting or a call. The wording matters more than the timing, though, and Fyxer is precise about the failure mode. "Just checking you saw this" and "Following up again" land as accusations, because both sentences assert that the client dropped something. The pattern that works instead: give the blame-free explanation up front, restate the specific item you are waiting on, and add one new piece of value so the message has a reason to exist beyond nudging. As Fyxer puts it, the best follow-up is not the most formal one, it is the one that makes replying easy. Your own reply speed works on the same principle. Separate acknowledgment from resolution: two lines confirming you have the message and saying when you will come back with an answer costs you a minute and removes the client's uncertainty entirely, which a perfectly researched reply three days later does not. ## How do I tell a client something they won't want to hear? Lead with the fact, then the reason, then what you are doing about it. Indeed's guidance on bad-news emails sets out the structure: a neutral, specific subject line such as "Update on project timeline," a short neutral opening, then the news stated plainly and early, followed by the context and the remedy. Proof-reading.com adds a warning against softening the news into jargon until it is unclear what has happened. This is the reverse of the instinct. Delivering a slipped date, you want to build the case first and arrive at the bad part cushioned. The client hunts for the bad part anyway, so every paragraph before it reads as evasion. Getting there in the second sentence is not blunt — it costs them the least time and preserves the most trust. ## Should I check with my manager before I send it? If you do not own the client relationship, yes — and it is a normal thing to do, not a sign that you cannot be trusted with it. This is the question the template libraries never address. Guides like Amitree's and Millo's are written as though the reader owns the account outright, which in the first years of a job is usually not true. Anything that commits the organization — a price, a scope, a date, a concession on a complaint — is a commitment your manager will be held to, so [one internal message](/knowledge/working-with-your-manager/how-to-write-email-to-manager/) beforehand avoids a correction afterward. The reverse is worth knowing too: once the substance is agreed, the wording is yours. The check is about what you are promising, not whether your sentences are good enough. ## Is email even the right way to send this? Sometimes not, and that decision comes first. Writing suits messages the client can act on in their own time, information that flows one way, and anything you want on the record. Conversation suits the opposite set: [building trust with someone new](/knowledge/teamwork/build-trust-at-work/), negotiating, working through a problem, and anything sensitive enough that a misread tone would cost you. Written words cannot be interrupted, corrected mid-sentence, or heard in the tone you meant. For the difficult cases the sequence is usually both. [Have the conversation](/knowledge/communication/difficult-conversations-at-work/), then send the short email recording what you agreed. The client hears the hard part from a person and keeps the written version for reference, and you avoid the defensive thread a written-first version tends to produce. Across those seven answers, notice how few were really about wording. How formal to be, what a client needs in order to decide, when to stop hedging, whether the message should have been a phone call at all — these are judgments about a person and a relationship, and no template makes them for you. Which is why the search results, running heavily to template collections like Amitree's eight and GrammarBuddy's fifteen, can be entirely correct and still leave you staring at the draft. ## What actually makes client email easier The judgments underneath those answers are not writing skills, and not specific to email either. They show up in meetings, in handovers, and in any conversation where you want something from someone who does not report to you. Three carry most of the weight in a client message. **Communication** treats email as one of its own named parts rather than a special case: lead with the main message, keep the subject line concise, copy only the people who need to be there, proofread, and reply in reasonable time. Two of its principles do disproportionate work with a client — adapting to the receiver's style, which is exactly the follow-their-register rule, and choosing the medium deliberately, which is the call-or-write decision. It also covers the drafts that are hardest to write: handling someone angry, disagreeing, apologizing properly. **Influence** — getting it and applying it — hides inside almost every client email, because almost every client email is an ask: an approval, a payment, a decision, a slipped date accepted without a fight. The preparation is the real work: understand what is in it for them and how they actually make this kind of decision before choosing a single word. Then keep the pitch simple, be honest about the drawbacks rather than spinning them, and take the small win where the full yes is unlikely. Following up on what was agreed belongs to the same skill, which is why the chase email feels less awkward once you stop treating it as nagging. **Professional Behaviors** are what a client is reading you for, whether or not they would put it that way. Writing to someone outside the organization means representing it, and the relevant norms are unglamorous: be polite, be on time with what you promised, keep confidential information out of a message that forwards in one click, and speak about colleagues as though they were copied in — which matters most on the day a client asks why someone else missed a deadline. Those are conventions anyone can learn, not a temperament you were issued. Communication alone stretches from a subject line to a difficult conversation, and it is **one of twelve everyday work skills** the free Job Skills Test scores. What comes back is not a verdict on your emails but an ordering: [where these three rank](https://assessment.headwayskills.com/) against the rest, and which one would change the most for you if you gave it some attention this year. Parts of this probably already describe how you work. You almost certainly write a different opening to a client than to the person at the next desk, without calling it a register decision. The rest is the same kind of thing — small habits you can pick up while still sounding exactly like yourself. And client email gets more consequential rather than less: as you are trusted with accounts of your own, more of your messages become the record of what was promised to someone paying for it. You stopped at a draft and went looking for how it should work instead of sending the first version, which is the step most people skip. ## See where your skills stand The only thing left is to find out where you are starting from. The Job Skills Test is a **free** self-assessment of the everyday work skills behind messages like these — how clearly you communicate, how you go about asking someone for something, and how well you read professional norms. It takes seven minutes, and it gives you a profile across all twelve skills along with the ones most worth your attention right now. Plenty of people find the first client emails the hardest part of a new job, and this turns a vague sense that yours could be better into something specific. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, seven minutes, and your results come up 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 write an email to a client: how formal to be, what belongs in the subject line, how to ask without hedging, and how to follow up or deliver bad news. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Influence, Professional Behaviors. ### 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/influence.md - https://headwayskills.com/knowledge/professional-behaviors.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-to-a-client/ Preferred summary: "How to write an email to a client: how formal to be, what belongs in the subject line, how to ask without hedging, and how to follow up or deliver bad news." ## Change log - 2026-07-07: Content collection version published.