All Things Workplace

How-to: Write an Email That Gets a Clear Decision

Sep 11, 2026 | Career Growth, How-tos

Busy leaders do not ignore you because they dislike you. They ignore you because your email hides the ask, offers no recommendation, and never states what “done” looks like. A decision email makes the call easy to give: one subject, one ask, options, your recommendation, and a reply-by time.

Time box: 15–20 minutes to draft, cut, and send. If it takes an hour, you are writing a memo. Split the memo and the ask.

Use this from the Individual Contributor hub when you need a manager call, and from the New Manager hub when you escalate to your boss. Pair with meeting agenda how-to only when live tradeoffs are required.

When to use / when not

Use when:
– A single person can decide (budget, priority, exception, go/no-go)
– Options are clear enough to list in five lines
– You have a recommendation, not just a shrug
– Email or chat is the normal channel for that leader

Do not use when:
– The topic is sensitive HR, performance, or interpersonal conflict (talk live; see how HR works)
– You need co-creation or brainstorming (workshop or doc comments)
– You are covering for missing analysis (do the work first)
– Multiple decision makers with conflicting authority (clarify ownership first; see how departments work together)

Prep

  • Decision owner: name in the To: line, not buried in a 12-person CC
  • Options: A / B / defer, with one-line tradeoffs
  • Your recommendation: pick one and say why in two sentences
  • Constraint facts: cost band, date impact, policy note (no novel)
  • Reply-by: a real time that matches urgency, not “ASAP”
  • CC list: only people who must execute or be informed the same day

If finance is involved, pre-check the number shape using finance for non-finance managers so you do not force a meeting to explain basics.

Steps

  1. Subject line first (2 min). Pattern: “Decision needed by [date]: [topic] – recommend [A/B].”
  2. Lead with the ask (3 min). First three lines: decision, options, recommendation, reply-by.
  3. Add context in bullets (5 min). Only facts that change the call. Link the longer doc.
  4. Name risks of each option (3 min). One line each. Do not bury the scary risk in paragraph four.
  5. Cut (3–5 min). Delete throat-clearing, apologies, and autobiography. Read it once as if you were the busy recipient.
  6. Send and calendar a nudge (1 min). If no reply by the deadline, send one short bump, then escalate live if needed.

Script (what to say / send)

Template:

Subject: Decision needed by Thu 3pm: [Topic] - recommend Option A

Hi [Name],

Decision: [one sentence].
Options:
A) [path] - tradeoff: [one line]
B) [path] - tradeoff: [one line]
C) Defer to [date] - tradeoff: [one line]

Recommendation: A, because [reason 1] and [reason 2].
If you prefer B, I will [consequence you will handle].

Reply with A, B, or C (or “need 15 min”).
Needed by: [day/time] so we can [downstream effect].

Context (optional read):
- [bullet]
- [bullet]
Doc: [link]

Thanks,
[You]

Bump after deadline:

Quick bump on the decision email below. Still need A/B/C by [new short time] or I will hold [downstream work] and assume deferral unless you say otherwise.

If they reply “thoughts?” with no call:

Happy to discuss. To keep moving, my recommendation remains A. If I do not hear a different call by [time], I’ll proceed with A and note it in [channel/doc].

Chat version (Slack/Teams): same structure, even shorter. Put “Need A/B/C by [time]” in the first line.

Output artifact

A saved Decision Email plus a one-line log:

Date Ask Owner Rec Reply Result
A/B/C

Keep the log for promo evidence and for your quarterly priority talks (quarterly priority reset how-to). Career growth is partly the habit of creating clear decisions others can grant; see the career conversations guide when you review a quarter of these asks with your manager.

Watch-outs

  • CC theater. Huge CCs create spectators and slow answers. Shrink the list.
  • Recommendation-free asks. “What do you think?” is not a decision request. Take a position.
  • Fake urgency. Everything ASAP trains people to ignore you. Match reply-by to real dependency.
  • Hiding the bad option. Leaders punish surprises. Put the painful tradeoff in the first screen.
  • Meeting as default. Do not offer a 30-minute meeting in the first line. Offer A/B/C, then “need 15 min” as the escape hatch.
  • Passive voice. “It was decided” helps nobody. Name who will do what after the reply.

Directors managing up can use the same format toward execs; see the Director / VP hub. Sales and delivery escalations that need a customer-facing call should prep separately with customer escalation prep.

Done looks like: subject states the decision and deadline, body fits on one screen, and the reply can be a single letter: A, B, or C.