How to Write a Cover Letter That Gets Read
The same discipline applied to the highest-stakes message you will write: one page, one argument, read in under a minute.
Read the guide →
A professional email is not judged on politeness. It is judged on whether the person reading it on a phone, between meetings, can tell in four seconds what it is about and what they are supposed to do. Most emails fail that test: the subject line says nothing, the first paragraph is throat-clearing, and the actual request is buried in the middle of paragraph three, if it is there at all. Over five short sessions this guide rebuilds the email from the outside in — subject, opening, the single ask, tone under pressure, and the follow-up — using emails you actually have to send. Nothing here is about sounding clever. It is about being easy to answer.
What you'll be able to do: In five short sessions, rewrite the emails you already send so they are clear in four seconds and easy to reply to in one.
Outcome: "My subject lines say what the email is about and what kind of thing it is."
Open your sent folder and read only the subject lines of your last ten emails. Count how many you could act on without opening the message.
A subject line has one job: let someone decide, without opening it, what this is and when it needs them. That means it should carry a topic and, where it matters, a type — a question, a decision, an action with a date, or pure information. "Quick question" and "Following up" carry neither and are invisible in a list of sixty. Length matters because phones truncate around 35–45 characters, so the useful words go first. Avoid the two traps at the ends of the range: a vague subject makes the email easy to skip, and an artificially urgent one ("URGENT", "ASAP") works exactly once before people stop believing you. If an email genuinely contains no ask, say so in the subject — "FYI:" or "No action needed:" is a kindness that gets your future emails opened.
"Quick question" → "Question: which supplier for the March print run?" — now it is answerable in one line. "Following up" → "Still need your sign-off on the Q1 budget (was due Friday)" — states the object and the stake. "Meeting" → "Decision needed by Thu: move the team meeting to Wednesdays?" — type, deadline and topic in eleven words, with the important ones at the front. "Update" → "FYI, no action: warehouse move finished Tuesday" — explicitly releases the reader. Each rewrite is longer, and each is faster to deal with, which is the trade that matters.
Outcome: "My emails start with the point, not with a run-up to it."
Take any email in your sent folder and delete its entire first sentence. Read what is left. Most of the time it is better.
Almost every weak email begins with a paragraph that exists only because the writer had not decided what to say yet: "I hope this email finds you well. I am reaching out because I wanted to touch base regarding..." The reader's eye slides straight past it looking for content, which means your real opening is wherever the content actually starts. Put it first. A working opening does one of two things: it states the ask, or it states the context in a single line and then the ask. One line of warmth is fine and often right — "Hope the launch went well" costs nothing and means something if it is specific. What does not work is generic warmth plus throat-clearing plus a delayed point. And if you are writing to someone who does not know you, the first line has one extra job: say who you are and why you, specifically, are writing to them.
Before: "Hi Marta, I hope you're doing well and that the week has been going smoothly. I wanted to reach out and touch base with you regarding the matter of the supplier contracts that we discussed at some point last month, as I believe there may be some outstanding items that still require attention from your side before we are able to proceed further." — 61 words, no ask. After: "Hi Marta — the supplier contracts need your signature before we can place the March order. Two documents, both attached. Could you send them back by Thursday? Happy to walk through the changed clauses if that's easier." — 38 words, the ask is in the first sentence, the deadline is explicit, and the offer of help removes the most likely reason for delay.
Outcome: "Each email I send asks for one thing, and the reader can see exactly what it is."
Find a sent email that asked for two or more things. Check whether you got answers to all of them. Usually you got the last one.
An email with four questions in it reliably gets one answered — usually the easiest or the last. This is not rudeness; it is how people read on phones. The fix is structural: one email, one ask, and where that genuinely cannot work, make the asks impossible to miss by numbering them and giving each its own line. The ask itself needs three parts to be actionable: what you want, who is doing it, and by when. "Let me know your thoughts" has none of the three. "Could you confirm the delivery date by Wednesday?" has all three in nine words. Where several people are on the copy line, name the person who owns the action — an ask addressed to everybody is an ask addressed to nobody. And put the ask somewhere the eye lands: its own paragraph, near the top, not trailing off the end of a long one.
The original asks, in one dense paragraph, about the venue, the catering budget, whether Tom is presenting, and if anyone has the attendee list. It gets a reply about Tom and nothing else. Restructured: the subject becomes "3 decisions needed for the May offsite (by Fri)". The body opens with one line of context, then three numbered lines, each naming an owner: "1. Venue — Priya, can you confirm Hall B or the annexe? 2. Catering — is €35 a head still the cap? 3. Attendee list — Sam, do you have the current version?" The fourth item, whether Tom is presenting, is pulled out entirely and sent to Tom as its own email, because it is a different conversation with a different person. All three numbered items come back within a day.
Outcome: "I can write a refusal, a delay or a correction without either grovelling or picking a fight."
Write the sentence "We will not be able to do this" and then write it three more ways. Notice which versions add words without adding clarity.
Difficult emails fail in two opposite directions: over-softening, where so many hedges and apologies pile up that the reader is unsure whether they have been told no, and compression, where a two-line refusal reads as contempt because email strips out the tone your face and voice would have supplied. One structure handles almost all of them: state the outcome, give the reason in one sentence, offer what you can actually offer. Outcome first, because burying it makes the reader hunt for it. One reason, because a stack of justifications reads as defensiveness. An offer, because their real question is "so what happens now?" Apologise once, for the specific thing, then stop. And when you are angry, write it and do not send it — the version you write the next morning is always shorter.
Too soft: "So sorry to be a pain, I know this is really annoying and I feel terrible about it, but there may possibly be a slight delay, though I'm hoping it won't be too bad and I'll do my absolute best..." The reader still does not know when the work is coming. Too blunt: "Report will be late. Ill last week." Accurate, and it reads as if the reader's problem is not the writer's concern. Working version: "The report will be with you Thursday rather than Monday — I was out sick last week and the data pull slipped with it. Sorry for the change. If Monday is fixed for the board pack, I can send the finished sections and the numbers on Monday and the analysis on Thursday. Which would you prefer?" Outcome, one reason, one apology, and a real choice handed back to the reader.
Outcome: "I have a follow-up rhythm that gets answers without damaging the relationship."
Find the oldest unanswered email in your sent folder. Decide right now whether it needs a follow-up, a different channel, or dropping.
Silence usually means the email arrived at a bad moment, not that the answer is no. A good follow-up assumes that and makes replying easier than it was the first time. Three things make it work. Timing: give it enough room to be reasonable — commonly three to five working days for a normal request, sooner if there is a real deadline, and say what the deadline is. Restating: reply in the same thread so the original is right there, and repeat the ask in one line rather than writing "just bumping this" and making them scroll. Lowering the bar: offer a version that takes them ten seconds — a yes/no, two options, or an explicit "if it's easier, I'll assume X and proceed." That last one is the most effective sentence in professional email, because it lets a silent reader stay silent and still move the work forward. After two follow-ups, stop emailing: change channel, ask someone else, or let it go. A third chase converts a busy person into an annoyed one.
Original on Monday: a request for sign-off on two contracts, no reply. Thursday, same thread: "Hi Marta — bumping this one. I need your signature on the two attached contracts before we can place the March order. Is Friday realistic, or should I push the order to the following week?" That is the ask restated, plus an easy out that is still an answer. Still nothing by Tuesday. Second and final follow-up: "No rush if you're buried — but I need to tell the supplier something today. Unless I hear otherwise by 4pm, I'll move the order to the 12th and we can sign this week." Reply came in eleven minutes. The default did the work: silence became a decision instead of a blockage, and nobody had to feel chased.
The complete guide — all 5 chapters, every checklist and exercise — as a clean, printable PDF. No email required.
A one-page cheat sheet of the five chapters, a 75–90 minute workshop script to run this live with someone else, and 12 affirmations and reflections to keep nearby.
Every guide on this site is produced with the Self-Directed Learning Framework: instead of an article that explains a topic at you, the framework turns it into a structure you work through — each chapter with one outcome, a starting action under twelve minutes, the minimum you actually need to know, a worked example, a checklist, and exercises. It starts from three questions:
Topic: Writing clear professional emails that get replies.
Outcome wanted: Send emails with a subject line, a single ask and a tone that fit the situation — and know how to follow up without nagging — within five days.
Starting point: Writes emails daily, gets slow or missing replies, and is not sure why.
The prompt framework behind it is public: see the C.R.A.F.T. prompt framework, including the exact prompt that generated this library.
The same discipline applied to the highest-stakes message you will write: one page, one argument, read in under a minute.
Read the guide →Free, self-paced guides across everyday, professional and academic topics.
See all guides