Start with the result you need
Before you write, ask yourself: What should the recipient know or do after reading this email? You might need an answer to a question, approval of a plan, help with a problem, or confirmation of a meeting time. If you cannot name the result, the recipient may struggle to work it out too.
Keep one main purpose per email when you can. A message about a community event, for example, is easier to answer if it asks for confirmation of the venue rather than also raising unrelated questions about next month’s newsletter. If several points belong together, put the most important request first and make the others easy to spot.
Think about who will receive the message. A colleague involved in a project may need only a short reminder; someone seeing the issue for the first time will need a little background. The aim is not to include everything you know. It is to give the reader enough information to respond.
Make the subject line do useful work
The subject line should tell the reader what the email concerns. Labels such as “Question” or “Important” give little guidance. A subject like “Question about Thursday’s room booking” identifies the topic before the message is opened. If you need a response, you can make that clear too: “Please confirm Thursday’s room booking.”
Use words the recipient will recognize, such as the name of a project, service, event, or document. Be specific without trying to fit the whole email into the subject line. “Volunteer rota: availability for June” is more helpful than either “Rota” or a long sentence explaining every shift.
If you reply to an existing email and the conversation has moved to a different topic, update the subject line or start a new message. That makes the new request easier to find later. Avoid marking a routine message as urgent; when timing matters, explain the reason and give a clear deadline in the email itself.
Give context, then ask directly
Open with a greeting and a sentence that puts the request in context. For example: “I’m preparing the notice for Saturday’s workshop and need to confirm the start time.” Then state the action you want: “Could you confirm whether it starts at 10 a.m. or 10:30 a.m.?” The reader should not have to infer the question from a long account of how the uncertainty arose.
A useful request names the action, any information needed to complete it, and a reasonable time frame. “Could you review the attached flyer and send any changes by Wednesday afternoon?” is easier to act on than “Let me know what you think.” If a deadline is flexible, say so. If there is no deadline, you do not need to invent one.
When you ask more than one question, separate them into short sentences or a numbered list written as plain text. Keep related background close to each question. Before sending, check whether the recipient has what they need: Is the document attached? Have you identified which version you mean? Have you made it clear who is responsible for the next step?
Keep the message easy to read and answer
Short paragraphs help readers find the point, especially on a phone. Put the purpose near the beginning rather than hiding it after several paragraphs. Use familiar words where possible, and explain abbreviations that a new recipient might not know. A polite tone matters, but long apologies or elaborate introductions can make the request harder to see.
A simple structure works for many everyday emails: greeting, reason for writing, relevant details, request, and closing. For example: “Hello Sam, I’m updating the contact list for the neighborhood group. Could you confirm which email address we should use for you? A reply by Friday would help me finish the list. Thanks, Alex.” The message is brief, but the task is clear.
Consider how much personal information is necessary. If you are asking for help with an account or service, describe the problem without putting passwords or other sensitive details in the email. You can ask which secure channel to use if more information is needed.
Check the final details before sending
Read the email once from the recipient’s point of view. Can they identify the topic from the subject line? Is the requested action stated plainly? Can they find any date or time they need? If the answer to one of these is no, a small edit may save an extra exchange of messages.
Check names, addresses, attachments, and dates. Make sure “Reply all” is necessary before using it, particularly when a large group received the original message. If the email discusses a change to a shared plan, say whether you are asking for a decision or simply informing people.
Finally, end in a way that matches your request. “Please let me know which option works for you” invites a specific answer; “Thanks for checking” suits a request for confirmation. A clear email does not need to sound formal. It needs to make the next step easy for the person reading it.
