---
title: How to Write a Decision Memo Executives Will Read (Template)
url: "https://goremy.ai/blog/articles/how-to-write-a-decision-memo-executives-will-read"
author: Luis Chavez-Mattos
editor: Luis Chavez-Mattos
editor_title: Director, Product
published: "2026-11-19T05:40:17.573Z"
updated: "2026-11-19T05:40:19.903Z"
topic: Business Writing Templates
description: Copy a one-page decision memo template, see a filled-in example, and use an AI prompt to draft it so an executive can say yes, no, or ask one question.
---

# How to Write a Decision Memo Executives Will Read (Template)

> Copy a one-page decision memo template, see a filled-in example, and use an AI prompt to draft it so an executive can say yes, no, or ask one question.

Edited by Luis Chavez-Mattos, Director, Product · Published 2026-11-19

## How do you write a decision memo?

Write a decision memo by putting the decision you need in the first two lines, with a deadline and the name of the person who decides. Follow with your recommendation, the options you weighed (including doing nothing), the cost and risks of each, and what happens next if the answer is yes. Keep it to one page. The reader should be able to approve, reject, or ask one specific question without calling you.

The template, a worked example, and an AI prompt are all below.

## TL;DR

- **Lead with the ask.** The first two lines state the decision, who makes it, and by when. Background comes after.
- **Recommend one option.** A memo that lists choices without picking one hands the executive your homework.
- **Always include "do nothing" as an option.** It shows the cost of waiting and answers the first question most executives ask.
- **One decision per memo, one page per decision.** If you need two approvals, write two memos.
- **AI is good at structure and tightening, bad at facts.** Give it your notes and numbers, tell it to flag gaps, and check every figure yourself.
- **Test the memo on a skeptic before sending.** Ask a colleague, or an AI playing the executive, to find the question you did not answer.

## What is a decision memo, and how is it different from a status update?

A status update tells people what happened. A decision memo asks someone with authority to choose something. That difference changes everything about how you write it.

In a status update, the reader can skim, nod, and move on. In a decision memo, the reader has to take responsibility for an outcome. They will only do that if they trust that you have thought about alternatives, know the risks, and are not asking them to do your analysis for them.

Strategy teams, chiefs of staff, program managers, finance partners, and operations leads write these constantly, because executives have little time and many calls to make. The one-page memo is how a busy person gets enough context to decide without a meeting.

A decision memo is not a research report, a pitch deck in prose, or a place to show how much work you did. The work goes in an appendix, or stays in your head until someone asks.

## What should a decision memo include?

Every strong decision memo answers the same questions, in roughly the same order:

1. What do you want me to decide, and by when?
2. What do you recommend?
3. Why does this need a decision now?
4. What else did you consider?
5. What does your recommendation cost, and what could go wrong?
6. What happens next if I say yes?
7. What do you need from me besides the decision?

If a section does not help the reader answer one of those, cut it.

## The decision memo template (copy this)

Paste this into a document. Replace everything in brackets. Keep it to one page, not counting an optional appendix.

```
DECISION MEMO

To: [Name of decision maker]
From: [Your name, role]
Date: [Date]
Decision needed by: [Date, and why that date]
Decision type: [Approve / Choose between options / Endorse and escalate]

1. THE DECISION
[One or two sentences. "I am asking you to approve X by [date] so that Y."]

2. RECOMMENDATION
[One sentence naming the option you recommend. Then one sentence on the main reason.]

3. WHY NOW
[Two or three sentences. What changes if we wait: a deadline, a cost, a risk, a window closing.]

4. OPTIONS CONSIDERED

| Option | What it means | Cost | Main benefit | Main risk |
|---|---|---|---|---|
| A. [Recommended] | | | | |
| B. | | | | |
| C. Do nothing | | | | |

5. WHY THIS OPTION
[Three to five sentences or bullets. The reasoning that makes A better than B and C.
Use numbers and name their source.]

6. RISKS AND HOW WE WILL HANDLE THEM
- [Risk 1]: [mitigation, owner]
- [Risk 2]: [mitigation, owner]

7. WHAT HAPPENS IF YOU APPROVE
- [Step, owner, date]
- [Step, owner, date]
- [How we will know it worked, and when we will report back]

8. WHAT I NEED FROM YOU
[Approval, a budget line, an introduction, a message to another team. Be specific.
If you have an open question you could not resolve, put it here.]

APPENDIX (optional)
[Data tables, detailed cost build-up, stakeholder input, links to source material.]
```

A few notes on why it is built this way:

- **Decision type** tells the reader how much thinking you want from them. "Approve" is a yes or no. "Choose between options" invites a conversation. "Endorse and escalate" means you need their support to take it higher.
- **Decision needed by** should have a reason attached. "By Nov 15, because the vendor price expires Nov 30" is a real deadline. "ASAP" is not.
- **Do nothing** goes in the table every time. Sometimes it is the right answer, and the reader should be able to see that you considered it honestly.
- **What I need from you** is separate from the decision on purpose. Executives often approve something and then discover they were also expected to make a call, fund a headcount, or talk to a peer.

## What does a filled-in decision memo look like?

Here is a worked example. The company, numbers, and vendors are invented for illustration. Replace them with your own sourced figures.

```
DECISION MEMO

To: Dana Whitfield, COO
From: Priya Nair, Finance Operations
Date: November 3
Decision needed by: November 15 (renewal notice deadline is November 20)
Decision type: Approve

1. THE DECISION
I am asking you to approve consolidating our three expense and travel tools
into one platform before the November 20 renewal notice deadline.

2. RECOMMENDATION
Move to Option A, a single platform, because it removes duplicate spend and
gives Finance one set of expense data instead of three.

3. WHY NOW
Two of the three contracts auto-renew for 12 months on December 1. If we miss
the notice deadline, we are committed through next year. Year-end is also the
lowest-volume period for expense reports, which makes migration easier.

4. OPTIONS CONSIDERED

| Option | What it means | Cost (annual) | Main benefit | Main risk |
|---|---|---|---|---|
| A. Consolidate (recommended) | Move all teams to Vendor X | $210K | One system, one policy | Migration effort in Q1 |
| B. Consolidate on current tool | Expand Vendor Y to all teams | $240K | No new vendor | Missing features for Sales travel |
| C. Do nothing | Renew all three | $310K | No change for employees | Duplicate spend, three data sources |

5. WHY THIS OPTION
- Saves about $100K a year against doing nothing (Finance contract review, Oct).
- Sales and Field teams get mobile receipt capture, which Vendor Y lacks
  (confirmed in the product demo, Oct 24).
- Audit prep currently takes about three weeks of manual consolidation;
  one system removes most of that (estimate from the Controller's team).

6. RISKS AND HOW WE WILL HANDLE THEM
- Employees resist a new tool: phased rollout by department, with a named
  champion in each. Owner: Priya.
- Data from old systems is hard to reach after cancellation: export and archive
  before cutoff. Owner: IT, with Finance sign-off.

7. WHAT HAPPENS IF YOU APPROVE
- Nov 18: Finance sends non-renewal notices for two contracts. Owner: Priya.
- Dec to Jan: contract signed, configuration, pilot with Finance and Legal.
- Feb to Mar: department rollout. Report back to you at end of March with
  adoption rate and cost versus plan.

8. WHAT I NEED FROM YOU
Approval by November 15, and a short note to department heads announcing the
change so champions have air cover.

APPENDIX
Cost build-up, vendor comparison, and IT's security review summary.
```

Notice what the example does. The ask is in the first section. Every number has a source or is labeled an estimate. The risk section names owners. The reader can approve this in under two minutes, or push back on a specific line.

## How do you write a decision memo with AI?

AI is useful for the parts of this job that are about structure and clarity: sorting messy notes into the template, tightening long paragraphs, and spotting what is missing. It is not a source of facts. The numbers, quotes, and claims need to come from you.

Paste your raw notes into a chat assistant along with the prompt below.

```
You are helping me write a one-page decision memo for a senior executive.
Use the template below exactly. Do not add sections.

Rules:
- Put the decision, the decider, and the deadline in section 1.
- Recommend one option. If my notes do not make clear which, ask me before writing.
- Always include "do nothing" in the options table.
- Use ONLY facts and numbers from my notes. Do not invent figures, vendors,
  dates, or quotes. Where a section needs information I did not provide, write
  [NEEDED: what is missing] instead of guessing.
- Plain language. Short sentences. No jargon, no filler, no marketing tone.
- Keep the total under 450 words, not counting the appendix.
- After the memo, list the 5 hardest questions an executive might ask that the
  memo does not yet answer.

TEMPLATE:
[paste the template from above]

MY NOTES:
[paste everything: the situation, the options, the numbers and where they came
from, deadlines, who is involved, concerns you have heard]
```

The last instruction is the most useful one. Asking for the questions the memo does not answer gives you a punch list before the executive does.

### What to check in the AI's draft

- **Every number.** Compare each figure against your notes. AI sometimes rounds, merges two numbers, or fills a gap with something plausible.
- **The recommendation.** Make sure the memo recommends what you actually believe, not whichever option your notes described most.
- **The deadline logic.** Confirm the "why now" is real and the dates are right.
- **Any [NEEDED] flags.** Fill them in or delete the claim. Do not leave a placeholder in a memo that goes up.
- **Tone.** Cut anything that sounds like a press release. Executives notice.

### Where not to trust AI

Do not rely on it for facts about your company, such as headcount, budget, contract terms, or what a colleague said. Do not let it characterize someone's position ("Legal supports this") unless you wrote that. And do not paste confidential material into a tool your company has not approved. Check your company's policy first; if you cannot share the real numbers, write the memo with placeholders and fill them in yourself.

## How do you make sure an executive actually reads it?

A good template gets you most of the way. The rest is judgment about what this particular reader needs.

**Write the first two lines for someone who stops reading there.** If they only read the decision and the recommendation, can they act? If not, rewrite.

**Pre-wire before you send.** Talk to the people the decision affects or who have a stake in it. If Legal, IT, or a peer VP will have an objection, you want to hear it first and either address it in the memo or note that you discussed it. An executive who is surprised by an objection in the memo will often delay the decision.

**Say what you are unsure about.** One honest line, such as "The migration estimate is based on one vendor's figures; I have asked for a second quote by Nov 10," builds more trust than a memo that sounds certain about everything.

**Use a table only for comparisons.** Options belong in a table. Reasoning belongs in sentences or short bullets.

**Cut your own favorite paragraph.** The analysis you are proudest of usually belongs in the appendix.

**Send it the way that executive prefers.** Some read on a phone in the gap between meetings. Check that the table is readable on a small screen. Others want a printed page before a meeting. Ask the executive's chief of staff or assistant if you do not know.

## What mistakes make a decision memo fail?

- **Burying the ask.** Three paragraphs of context before the request means the reader forms an opinion before knowing the question.
- **No recommendation.** "Here are three options" reads as "I did not want to commit." If you cannot recommend, say so and say what information would let you.
- **Asking for two things.** "Approve the budget and choose the vendor" is two decisions. Split them or sequence them.
- **Missing the cost of waiting.** If nothing happens when the decision is delayed, the executive will delay it.
- **Unsourced numbers.** "We'll save 30%" with no origin invites the reply "Where did that come from?"
- **Hiding the downside.** Risks you do not name get found by someone else, and then they doubt everything else in the memo.
- **Length.** If it runs past a page, the reader will skim. Move detail to the appendix.

## How do you track decisions after the memo is sent?

A memo that gets approved still needs follow-through. Most teams track this in a shared spreadsheet or an email thread, and both tend to rot. Who asked for what, which memos are waiting on a decision, which approvals have deadlines coming up, and what was decided last quarter all end up scattered.

If you send memos regularly, a small internal tool can fix that. Something like a memo submission form that records the decider, the deadline, and the decision type, plus a log showing status, a decision date, an owner for each next step, and a reminder when a deadline is close. [Remy](https://goremy.ai) builds this kind of app from a plain-English description: you describe the form, the log, and who can see what, and it produces a working full-stack app with a database and sign-in, deployed to a live URL. That gives a strategy or chief of staff team one place to see open decisions, instead of searching inboxes.

## Frequently Asked Questions

### How long should a decision memo be?

One page for the body, which is under about 450 words with a small options table. Put supporting data, detailed calculations, and stakeholder notes in an appendix. If the decision is large and complex, the body can stretch a little, but the first two lines should still carry the full ask.

### What is the difference between a decision memo and a briefing memo?

A briefing memo informs: it gives background so the reader understands a situation. A decision memo asks for a specific choice by a specific date, and includes your recommendation. If you do not need anything from the reader, write a briefing. If you need a yes or no, write a decision memo.

### Should I include more than one option?

Yes, usually two or three, including doing nothing. Presenting a single option makes the memo look like a foregone conclusion and gives the reader nothing to compare. You should still recommend one clearly. If there truly is no alternative, say so and explain why.

### Can AI write a decision memo for me?

AI can turn your notes into the template, tighten the language, and list questions you have not answered. It cannot supply your facts, so give it your numbers and tell it to mark gaps instead of guessing. You are still the author, and you are accountable for every claim in the memo.

### What if the executive says no, or does not respond?

Ask what would change the answer, and record it. If you hear nothing by the deadline, [follow up once with a short note](https://goremy.ai/blog/articles/write-work-emails-faster-with-ai) restating the date and what happens if no decision is made. A well-written "do nothing" row in your options table makes that follow-up easier, because the consequence is already on the page.
