Professional Email Writing: A Practical Guide
Email remains the operating system of professional life — job applications, client work, internal decisions, networking, all of it. And most professionals are bad at it: vague subject lines, three asks buried in paragraph four, tone that reads colder than intended. Good email writing is a genuine career advantage precisely because the bar is low.
This guide gives you the practical system: subject lines that get opened, a structure that puts the ask where it belongs, tone you can calibrate on purpose, follow-ups that work, and the mistakes to stop making.
Put the point in the subject line and the ask in the first two sentences. One email, one ask. Match the recipient's formality, then go one notch warmer. Follow up once after a week; twice total. Proofread by reading the email as the recipient would.
Subject lines that get opened
The subject line is a headline with a job: tell the recipient what this is and what it needs. "Quick question" fails at both; "Q2 budget approval needed by Friday" succeeds at both. Include the topic, the action, and the deadline when there is one. Busy people triage by subject line alone — a clear one gets answered, a vague one gets buried.
For requests, front-load the verb: "Request: 15-min call next week", "Approval needed: vendor contract", "FYI: launch moved to Thursday". For threads, update the subject when the topic changes rather than letting "Re: Re: Re: quick question" accumulate five topics. And keep it under about 50 characters so it survives on phones.
Never leave it blank, never write "hello" or "important!!!". Multiple exclamation marks and all-caps read as either spam or panic. Urgency belongs in the words ("needed by EOD"), not the punctuation.
Structure: the ask goes first
Professionals skim. So lead with the point: one or two sentences of context, then the ask, then the supporting detail for those who want it. This is the BLUF principle — bottom line up front — borrowed from the military, and it respects everyone's time including yours.
A reliable template: greeting with the person's name; one line of context ("Following up on Tuesday's meeting…"); the ask, stated plainly ("Could you approve the attached by Thursday?"); the details or attachment reference; a clear close ("Thanks — let me know if you need anything else from me."). Five parts, rarely more than 150 words for routine mail.
One email, one ask. Bundling three unrelated requests guarantees two get ignored. If you must cover multiple topics, number them — "Three quick items:" with a numbered list — so replies can address each one. Numbered asks get numbered answers.
Calibrate your tone on purpose
Written tone defaults colder than you intend — no facial expression, no vocal warmth. Compensate deliberately: open with the person's name, add one warm line where natural ("Hope the launch went well"), and close with thanks. None of this is sycophancy; it is signal clarity.
Match the recipient's register, then go one notch warmer. If they write formally, be professional but human. If they are casual, you can relax — but never be the first to go casual with someone senior or new. When in doubt, default to slightly more formal; nobody ever resented a polite email.
Read every important email once as the recipient before sending. Check: is the ask unmistakable? Is the tone how I want to be perceived? Is anything ambiguous? This thirty-second habit catches most tone disasters and unclear asks before they leave your outbox.
Follow-ups that work
No reply does not mean no — it usually means buried. Follow up once after about a week, briefly and without guilt: forward the original with "Bumping this up — any thoughts?" or a fresh two-liner restating the ask. Keep it light; the recipient is busy, not hostile.
Two follow-ups total is the professional norm for cold or lukewarm contacts; beyond that you are pestering. For each follow-up, add value or reduce friction: attach the document again, propose specific times, shrink the ask. "Still good for a 15-min call? I'm free Tue or Thu afternoon" beats "Just checking in!!!" completely.
Track what you are waiting on. A simple "waiting for" list — or your email client's snooze/reminder feature — prevents the two failure modes: never following up, and anxiously following up twice in a day. The system remembers so you do not have to.
Mistakes that mark you as junior
Reply-all on anything not genuinely relevant to everyone — the fastest way to annoy a whole team. CC'ing someone's boss to apply pressure — transparent and resented. The vague "per my last email" — passive-aggressive; just restate the point kindly.
Proofreading failures: wrong name in the greeting (the cardinal sin — check it every time), "attached" with no attachment (say the filename in the body so its absence is obvious), and sending the draft version with bracketed notes to yourself still in it. Slow down for the final read on anything external.
Finally, the novel-length email. If it needs more than about 200 words, it probably needs a call or a document instead. Email is for decisions and coordination, not for thinking out loud at length. Write the long version for yourself, then send the short version.
Email specifically for job applications
Application emails deserve extra care because they are first impressions. Address a person by name whenever possible — "Dear Ms. Chen" beats "Dear Hiring Manager," and finding the name takes two minutes on the company site or LinkedIn. State the role and where you saw it in the first line so the reader can file you instantly.
Keep the body to three short paragraphs: who you are and why this role, one or two specific reasons you fit (mirror their language from the posting), and the close with the attachment noted. Name your attachments professionally — "Jane-Doe-Resume.pdf", not "Resume_FINAL_v3.pdf" — because the filename is visible and judged.
Send application emails Tuesday through Thursday mornings when possible; Monday inboxes are chaos and Friday afternoons are voids. And after applying, log it in your tracker immediately — company, role, date, contact — so follow-ups happen on schedule instead of from memory.
Frequently asked questions
How long should a professional email be?
As short as clarity allows — most routine emails should be under 150 words. If you are consistently writing more than 200 words, consider whether the topic needs a call or an attached document instead.
Are exclamation marks unprofessional?
One per email is fine and adds warmth; several reads as overeager or anxious. In formal or first-contact emails, consider dropping them entirely until you know the recipient's style.
When is reply-all actually appropriate?
When every recipient genuinely needs your response to do their work — a decision, a correction, or information affecting the whole thread. When in doubt, reply to the sender and add individuals deliberately.
How do I write a cold email that gets answered?
Keep it under 100 words: who you are in one line, why them specifically (show you did homework), one small clear ask, and an easy out. Specificity and brevity are the entire game — generic mass emails get ignored.
Educational content only — not professional advice. Talk to a qualified professional about personal career or education decisions.