How to Write an Email When You Need a Decision, Not a Discussion

Name the choice before explaining the history

Start by stating what needs to be decided and who is being asked to decide. Keep the opening to one or two sentences. For example: “Could you choose whether we use the current template or revise it before the next client update?” That tells the reader what kind of response will move the work forward.

Then add only the context needed to understand why a choice is due now. If the recipient needs a project name, dependency, or relevant constraint, include it briefly. Move background that does not affect the decision to a later paragraph, or leave it out. A long timeline can make a small choice look like a request to reopen the whole project.

Offer options the recipient can actually choose

Present a short set of workable options, not a list of every idea anyone has mentioned. Include a recommendation only if you can explain its basis. Make clear whether the recipient can suggest another route; do not disguise a fixed decision as a choice.

Compare the options using the same criteria, such as effort, timing, or what each option leaves unresolved. Avoid labeling one option “obvious” or implying that a person who chooses differently is being difficult. If the alternatives depend on an assumption, state it so the recipient can correct it.

Subject: Decision needed: client update template

Hi [Name],

Could you choose whether we keep the current template or revise it before the next client update? We need to settle the format so [team] can prepare the draft.

Option A: Keep the current template. This takes less preparation, but it does not include [new information].
Option B: Revise the template. This adds that information, but [team] will need time to update the draft.

I recommend Option B because [specific reason]. If that reason does not fit your priorities, please say so.

Make trade-offs useful, not persuasive decoration

A trade-off is a real cost or limitation attached to an option. Name it plainly: one route may take more coordination, while another may leave a need unmet. Do not minimize the downside of your preferred choice or exaggerate the alternative’s drawbacks. The recipient should be able to see what they are accepting either way.

Keep the comparison tied to the decision. Details that are interesting but do not change the choice can wait. If a key fact is unknown, mark it as unknown rather than presenting an estimate as settled. You can also state what would change your recommendation, such as a constraint the recipient may know about.

Specify the response you need

Ask for an answer in a form that is easy to give: select Option A or Option B, approve a named proposal, or identify a concern that prevents either choice. If approval from someone else is required, say who needs to weigh in rather than treating silence as consent.

Give a date when the answer would be useful and explain the practical reason if there is one. “Please reply by [date] so [next step] can proceed” is clearer and less pressuring than “ASAP.” If the timing is flexible, say that too. Do not imply that a delay has consequences you cannot support.

Separate a decision from a discussion

A decision request can still invite relevant input. Set a boundary around that input: ask whether the recipient sees a material concern or missing option, rather than asking for general thoughts on the entire subject. This keeps the door open to useful information without making the task seem limitless.

If discussion is genuinely needed, identify the point that remains unresolved and suggest a conversation as a next step. Otherwise, avoid piling on questions about implementation, future improvements, and unrelated approvals. Those can obscure the one answer you need now.

Check that the email did its job

Before sending, read only the subject line and first paragraph. Can the recipient tell what decision is needed? Then scan the options: are they distinct, fairly described, and linked to relevant trade-offs? Finally, check that the requested reply and useful-by date are unmistakable.

After sending, confirm the outcome by reflecting the choice back in a brief reply: state the selected option, any condition attached to it, and the next step or owner. If the response is ambiguous, ask a focused clarification rather than assuming approval. If no answer arrives by the requested date, follow up with the decision, options, and timing in a concise reminder; do not treat nonresponse as agreement.

• Decision and decision-maker are explicit.
• Options and trade-offs are concise and balanced.
• The requested response, useful-by date, and next step are clear.