A request can be polite and still be hard to answer. “Let me know what you think” leaves the reader to guess what kind of response matters, what information to consider, and when you need it. Make the decision or information you want explicit, provide the context that helps someone answer, and state a clear deadline. This does not make the recipient share your priorities; it lets them judge the request and respond honestly. A few direct sentences can prevent avoidable follow-up and make it easier to tell whether the email did its job.
The useful bits
- Put the requested decision or information in a direct sentence.
- Include only context that could change the answer.
- Give a specific deadline and say what response would be useful.
Name the answer you need
Before writing, finish this sentence: “After reading this email, I need the recipient to ___.” Use a concrete action or answer, such as choosing between two options, confirming a date, or supplying a missing detail. If you need several things, separate them into distinct questions rather than bundling them into “thoughts?”
Be clear about whether you want a decision, a fact, or advice. “Please confirm whether the draft is approved” asks for a decision. “Please send the current delivery date” asks for information. “Which of these approaches seems more workable, and why?” invites judgment. A reader should not have to infer which kind of response you expect.
Give context that can affect the answer
Add the reason for the request and the relevant constraints: what is being decided, which options are under consideration, and what would make one answer useful. Keep background focused. A long history of the project can bury the question, while too little context forces the recipient to ask what the decision is about.
Separate known facts from preferences or assumptions. If a deadline comes from a planning need, say so; do not imply that the recipient has the same urgency. Where appropriate, invite them to flag a constraint or suggest a different timing. That makes your need visible without presenting your schedule as everyone else’s priority.
Make the deadline understandable
Replace “soon,” “when you can,” or “by end of day” with a date and, when useful, a time and time zone. Explain what the deadline supports, such as preparing a meeting agenda or sending a document for review. This gives the recipient something concrete to assess.
If the timing is flexible, say so and provide a preferred date rather than disguising a preference as a hard cutoff. If you truly need a response by a certain point, state that plainly. You can also ask the recipient to tell you if they cannot meet it, so silence is not mistaken for agreement.
Turn a vague ask into an answerable one
Here is a before-and-after example. The first version sounds friendly, but leaves the recipient to determine what feedback means and how quickly it is needed. The revised version names the decision, explains the relevant context, and gives the recipient room to respond if the timing or options do not work.
Vague: To: [colleague] <colleague@example.com> Subject: The plan Hi [name], Can you take a look and let me know what you think? Thanks, [sender] Answerable: To: [colleague] <colleague@example.com> Subject: Choose a review date for [document] Hi [name], I’m scheduling review of [document] before [project milestone]. Would [date A] or [date B] work better for you? Please reply with your preferred date, or suggest another date if neither works. I need to set the schedule by [date, time, time zone]. If that timing is difficult, please let me know. Thanks, [sender]
Make the response easy to compose
Offer a simple response format when it helps: “Reply with A or B,” “send the date,” or “mark any changes in the attached draft.” For a question with several parts, number them or use short bullets so the reader can answer each one. Avoid suggesting that one option is already approved unless that is genuinely settled.
A compact prompt is useful only if it leaves room for an accurate answer. If the recipient needs to explain a concern, say that a short reason would help. If you need a yes-or-no decision but a qualified answer would be important, invite the recipient to explain the qualification rather than forcing a misleading choice.
Check that the request worked
Before sending, read only the subject and the first few lines. Can you identify the requested answer, the context needed to give it, and the deadline? Then check that any date, option, attachment, or referenced document is actually included and described clearly. Remove background that does not help the recipient decide or respond.
After a reply arrives, compare it with the question you asked. Did it provide the decision or information you needed, and does it address the relevant constraints? If not, follow up with the specific missing point instead of restarting the whole discussion. If no reply arrives by the stated deadline, send a brief follow-up that restates the request and asks whether the timing still works. This confirms whether the email produced an answer, not whether the recipient shares your priorities.
- Ask: What exact decision or information do I need?
- Include: Why it matters and any constraint that could change the answer.
- State: A clear response deadline and the format that would help.
- Confirm: The reply answers the actual question; follow up on anything missing.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction