Write a Subject Line That Says the Thing
The subject line is the part of your email a busy person sees first. Gmail and Outlook both show the sender, the subject, and a grey preview of your opening line in the inbox list, so those two pieces decide whether the message gets opened now, later, or never. Name the topic, the action, and the date. “Approval needed: vendor contract, by Thursday 3 pm” tells the reader exactly what you want. “Quick question” could be about anything.
Some patterns worth borrowing: “Decision needed: …”, “Need by Friday: …”, “No action, for your records: …”, and “Question about invoice 4471”. If the thread drifts to a new topic, change the subject on your next reply. In Outlook, double-click the message to open it in its own window, then edit the subject box. In Gmail, click the small arrow beside the recipient line in a reply and choose Edit subject. The side benefit is that you will find the message when you search for it months from now.
One Ask Per Email, Stated at the Top
Put the bottom line in the first sentence, then give background underneath for anyone who wants it. For example: “Can you approve the $1,200 design budget by Thursday? The quotes are below.” A reader who stops after one line still knows what you need.
Keep to one ask. When an email carries three questions, the reply often covers only the easiest one and the rest quietly disappear. If you truly have three things, send three emails, or say “three quick questions” in the opening line and number them. Separate messages also let each topic be forwarded, filed, or answered by a different person.
Make the ask easy to answer. A yes or no works well, and so does a choice: “Does Tuesday at 10 or Wednesday at 2 work for you?” When several people are on the message, put the person who must act in the To field, use their name in the first line, and move everyone else to Cc.
Length Discipline: Make Every Sentence Do a Job
Try this test on your draft: if the reader saw only the first two sentences, could they act? If not, move things up. Then cut the greeting down to one line, the recap of events they already know, and any apology for writing at all. Keep paragraphs to one to three sentences and use bullets only for items that are truly parallel, such as three dates or a list of files.
For long material, attach it and say in one line what is inside and where to look, for example “Page 4 has the pricing table.” Before sending, glance at the message the way it will appear in a phone preview. If your request sits below the first few lines, it is too low. The federal plain language guidelines are a useful reference here, with practical advice on short sentences, active voice, and everyday words.
Tone for Colleagues Versus Outsiders
With teammates, be direct. First names, no formal sign-off, and a plain request such as “Can you send the draft by noon?” read as efficient, not rude. Skip the stacked pleasantries; people you work with daily do not need them.
With someone outside your company, or anyone who does not know you, spend one line on who you are and why you are writing, then make the ask. Use full sentences and spell out times completely: “Thursday, 15 November, 3 pm Eastern” leaves no room for a missed time zone. When writing to someone senior, shorten the message but do not drop the courtesy. Avoid sarcasm, all caps, and strings of exclamation marks, because none of them carry the tone you intended. A disagreement or anything emotional is better handled by phone, with a short email afterward to confirm what was agreed.
Follow-Ups and Filler That Reads as Machine-Written
For a routine request, wait two business days before nudging. If a deadline is close, one day is fair. Reply on the original thread so the history travels with your note, and keep the nudge short: “Still need a yes or no on the Thursday budget. Reply ‘approved’ and I’ll go ahead.” Use Outlook’s Follow up flag or Gmail’s Snooze to bring the message back to the top of your inbox at the right time. If a third attempt over about a week gets nothing, switch channels, call, or ask whether someone else should own the decision. It also helps to have filter rules that stop clutter, so replies are not buried under newsletters, and filters that actually work keep important senders visible.
Now check for filler. Text that sounds machine-written tends to share the same habits: openers like “I hope this email finds you well” and “I wanted to reach out regarding”, closers like “Please don’t hesitate to contact me”, vague praise words such as “robust” and “seamless”, a final paragraph that repeats the one above it, and lists that always come in neat groups of three. Every sentence is also about the same length. The fix is a deletion test. Remove a sentence, and if the message loses nothing, it was filler. Where a general statement remains, swap in a name, a number, or a date. Reading the email aloud catches most of the rest, and if you started from an AI draft, add your own specifics before it goes out.