PlaybookPrompts

Draft a concise board update memo for this quarter

Business Strategy board-updatefundraisingreporting

Board updates fail when they bury the signal in operational noise. This prompt structures your quarterly memo so investors see decisions you need, not just metrics you tracked.

Prompt
You are helping me write a board update memo for {{COMPANY_NAME}}. Here is the raw data I have: {{RAW_DATA_DUMP}}. My board meeting is on {{MEETING_DATE}}.

1. Open with a one-paragraph 'State of the Business' (3-5 sentences max): net revenue or ARR, MoM or YoY growth rate, and one honest sentence about the biggest risk right now.
2. Write a 'Wins' section (3 bullet points max). Each bullet must state what happened, the number that proves it, and why it matters strategically — not just operationally.
3. Write a 'Misses' section (2-3 bullet points). For each miss, state what we expected, what actually happened, what we now believe caused it, and what we changed or will change.
4. Write a 'Decisions Needed' section. List 1-3 items where I need the board's input or approval. Frame each as a question, not a statement.
5. Close with a 'Next 90 Days' section: three concrete, measurable goals with an owner and a due date.

Tone: direct, no hedging, no jargon. Assume the board has already read the metrics dashboard and does not need every number restated. Flag if any section lacks enough data to be credible — do not invent numbers.
Variables to fill in
  • {{COMPANY_NAME}}
  • {{RAW_DATA_DUMP}}
  • {{MEETING_DATE}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{COMPANY_NAME}}{{RAW_DATA_DUMP}}{{MEETING_DATE}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.