Before drafting, decide what the recipient needs to understand or do and whether email is the right channel. A routine update, a sensitive record and an urgent incident may require different channels and permissions. This guide offers a drafting check, not a rule that all relationships use the same formality or response deadline.
Revise an ambiguous request without inventing a deadline
Weak constructed draft: “Can you look at this soon?” The recipient cannot identify the version, decision or meaning of “soon.” A usable revision is: “Please check the delivery assumption in section 2 of draft v 3. Comment in the restricted document; tell me if the proposed Friday deadline is not feasible.” The subject can be “Review requested: delivery assumption, draft v 3.”
The changes do different jobs: section 2 limits scope; v 3 identifies the material; a document comment identifies the response channel; “proposed” keeps an unagreed date from becoming an order. Before sending, confirm the actual recipient and access. This is annotated writing, not a message sent or a claim that one tone fits every workplace.
Put the purpose and action together
Use a specific subject and state the reason early. Include the context needed to act, then a request or next step. A deadline should be relevant and feasible, with a time zone when necessary. Do not mark every message urgent.
Constructed example: “Please review section two of the attached draft by the agreed Friday deadline. The unresolved point is the delivery assumption; comments in the document are sufficient.” The recipient can identify the task and the open question. This is an example, not a message sent by this site.
Check the draft against the recipient's question
| Recipient needs to know | Your draft includes | Verify before sending |
|---|---|---|
| Why this arrived | Purpose and relevant context | Correct person and channel |
| What action is wanted | A specific request or no-action update | Authority and feasible timing |
| Where the material is | Correct attachment or restricted link | Version, access and sensitive content |
| What happens next | Follow-up or decision point | No unsupported promise |
The U.S. GSA plain-language guides focus on content an audience can understand. We apply that communication principle here; the guides are not a universal email etiquette law for private correspondence.
Review privacy and access separately
Check recipient autocomplete, copied recipients, attachment contents and link permissions. A clear message can still disclose the wrong record. Do not include passwords or access codes, and use the appropriate approved channel for sensitive information. A file name alone does not prove the correct file was attached.
Handle replies as part of the task
Keep the relevant question and answer visible without copying an entire unrelated thread. If you cannot complete the request, state what is possible or what information is missing. There is no single 24-hour reply rule for all contexts. A useful final check is whether the intended recipient can identify the next action without guessing.