thinkhard.SI

Prompt repository Email, meetings & presentations

Send a follow-up email after an internal meeting

You need to tell attendees what was agreed, who owns what, and by when, while the meeting is fresh.

Registry no.
OFF-013
Collection
Email, meetings & presentations
Laid out for
Any chat model
Score
10 out of 10
Blanks to fill
7
Added

Email, meetings & presentationsAny chat

The prompt

Score 10 of 10, Excellent

Use it when You need to tell attendees what was agreed, who owns what, and by when, while the meeting is fresh.

  • {{meeting_name}}
  • {{meeting_date}}
  • {{attendees}}
  • {{also_send_to}}
  • {{next_check_in}}
  • {{notes}}
  • {{correction_deadline}}
Full prompt and why it works
Prompt
Write the follow-up email I will send after an internal meeting I ran, so that attendees see in under a minute what we agreed, what they personally own and by when.

Meeting: {{meeting_name}}, held {{meeting_date}}
Attendees: {{attendees}}
Also sending to (people who were not there): {{also_send_to}}
Next check-in: {{next_check_in}}

My notes:
"""
{{notes}}
"""

Format:
- Subject line: the meeting name, "follow-up" and the date.
- One opening sentence thanking people and saying what the email covers.
- Agreed: up to 5 bullets, each a decision as it was agreed.
- Actions: grouped by owner so each person can find their name, for example "[Name]: send the revised budget to finance by [date]". One named person per action, not a team, and each action starts with a verb.
- Still open: questions raised but not settled, with who is following up if my notes say.
- The next check-in, then a closing line asking people to reply by {{correction_deadline}} if I have missed or misstated anything.

Keep it under 200 words, written in the first person from me. The tone should be plain and factual.

Rules:
- Record only what my notes show was agreed. A suggestion nobody confirmed goes under Still open, not Agreed.
- If an action has no owner or date in my notes, write "Owner: to confirm" or "Date: to confirm". Do not assign one, because an invented owner tends to become a real dispute.
- Leave out who said what, side discussions and anything my notes mark as confidential, since the email may be forwarded or read by people who were not in the room.

If my notes are too thin to tell what was decided, say so before the draft and list what you need from me.

Variables

{{meeting_name}}
The meeting's name or topic.
{{meeting_date}}
When it took place.
{{attendees}}
Who was there, by name or role.
{{also_send_to}}
Anyone else who gets the email, or "nobody else".
{{next_check_in}}
The date of the next meeting or check-in, or "none set".
{{notes}}
Your notes from the meeting, however rough.
{{correction_deadline}}
When people should flag corrections, for example "end of day Thursday".

Why it works

  • Format. Actions are grouped by owner, so each person finds their own tasks without reading everyone else's.
  • What to avoid. No owner or date is filled in that the notes do not show, and unconfirmed suggestions stay open, so the email records the meeting rather than a tidier version of it.
  • What good looks like. Asking for corrections by a set time turns the email into the agreed record once that time passes.

How to use it

  1. Press Fill in variables and type your details into each blank. What you type stays in this browser.
  2. Copy the filled prompt into the AI tool you already use, such as ChatGPT, Claude or Gemini, or open it in the Grader or the Prompt Tester here.
  3. Before you rely on it, try it on three or four real examples. The Prompt Tester runs them all at once and shows which ones go wrong.
Use it from code

Get this prompt as JSON from the free REST API, with your own text in the blanks, or let an AI assistant fetch it through the MCP server. No key.

curl -s https://thinkhard.si/api/v1/prompts/meeting-follow-up-email

With the MCP server added to Claude, ChatGPT, Cursor or VS Code, call get_prompt with {"prompt": "meeting-follow-up-email"}, or just ask for it by name.