What you will learn
- State a specific request early.
- Supply context and a realistic response path.
- Edit for clarity, tone, and appropriate recipients.
Define the reply you need
Before drafting, complete the sentence: “After reading this, the recipient should be able to…” You might need approval, a choice between dates, a factual answer, or acknowledgment of a change. If you cannot name the response, the recipient may not be able to infer it either. Sometimes the right message is information only; say so.
Write a subject line that identifies the topic and action. “Choose a workshop date by Thursday” is more useful than “Important.” Put the request in the opening paragraph, with the actual date if timing matters. A deadline should reflect a real dependency, not an attempt to make your message outrank everyone else’s work.
Include enough context to decide
Explain briefly why the request exists and what the recipient needs to assess it. If you seek approval for a room booking, include the date, purpose, cost, and relevant limit. Do not force the reader to search a long thread to discover a number that you already have. At the same time, move background detail into a clearly named attachment or optional section.
Separate facts from proposals. “The room is available” differs from “I propose reserving the room.” Distinguish a confirmed arrangement from an assumption. If an attachment is essential, state what the reader should inspect in it, and check that it is actually attached and accessible before sending.
Make responding straightforward
A bounded request lowers the effort of replying. “Would Tuesday at two or Wednesday at ten work? If neither does, please suggest another time” is easier to answer than “When are you free?” Use options when they fit the situation, but do not hide an open decision inside a forced choice.
For several questions, number them and explain which one is urgent. Avoid bundling unrelated topics merely because they involve the same person. If a full response requires substantial work, offer a smaller first step, such as confirming who owns the issue. Consider whether a short conversation would resolve ambiguity faster than another long email.
Review tone and the sending context
Read the message from the recipient’s position. Remove blame, unexplained abbreviations, and unnecessary apologies that obscure the request. Politeness does not require vagueness. “Could you confirm the quantity by Thursday so we can place the order?” is both direct and respectful. Allow room for constraints you may not know about.
Check recipients, names, dates, links, and confidentiality. Copy only people who need the information or have a defined role. If you follow up, refer to the original request and the relevant dependency instead of implying that silence proves neglect. A well-written email increases the chance of a usable response; it cannot create time, authority, or willingness the recipient lacks.
A fictional room-booking email
Harun coordinates a staff learning session. His first email says, “Any thoughts on the training?” and includes a long discussion thread. Nobody knows whether he wants topic suggestions or booking approval. He rewrites it: “Please approve the Thursday room booking, costing 80 units, by Tuesday noon so the reservation can be held.”
He adds the purpose, participant count, and an alternative room, then asks the manager to approve one option or identify a concern. The manager replies with a budget question. The message has not guaranteed approval, but it has produced a response that moves the decision forward.
Rewrite a message around one response
- Select an unsent or anonymized email with an unclear request.
- Write the desired response and place it in the first paragraph.
- Add only the facts needed to answer and clarify any deadline.
- Check the subject, recipients, attachments, and reply options.
Further reading
- CDC: Plain Language Materials and ResourcesPlain-language guidance informs the principle of writing for a particular audience; workplace examples are original.