Write a follow-up email after this meeting. Recipient and relationship: [RECIPIENT CONTEXT] Meeting purpose and notes: [MEETING NOTES] Decisions, owners, and deadlines: [ACTIONS AND DEADLINES] My requested next step: [CLEAR ASK]
Tone and sending context: [TONE AND CONTEXT]
Write an email that is easy to scan on a phone and does not make the recipient reconstruct the meeting. Open with a brief, genuine reference to the purpose or useful discussion. Then separate confirmed decisions from open questions. List action items with a named owner and date only when those were actually agreed; if an owner or date is uncertain, phrase it as a proposed next step rather than a commitment.
Make one clear request or confirmation at the end. If I am following up after an interview, thank the interviewer and connect one specific conversation point to my relevant experience without restating my resume. If this is a sales, client, or internal meeting, avoid implying approval, budget, scope, or a promise that was not explicitly made.
Output: (1) a ready-to-send subject line, (2) the email body in 120–220 words unless my context requires less, and (3) a one-line list of any vague note that I should resolve before sending. Keep the language warm but concrete. Do not invent meeting details, timeline commitments, praise, attachments, or agreement.
Before answering, check that every action item has either an owner and deadline from my notes or is clearly labeled as proposed. Check that the ask can be answered with a reply or one defined action. Ask up to 3 clarifying questions only if a required input is missing.Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [RECIPIENT CONTEXT] | State who will receive the email, their role, and your relationship to them. | Elena Ruiz, director of operations at a prospective client; we met after a product demonstration. |
| [MEETING NOTES] | Paste the key discussion points, decisions, concerns, and exact facts from the meeting. | Discussed reducing manual onboarding steps for their 14-person support team. Elena asked about SSO timing and export formats. She said their procurement review starts in mid-May. |
| [ACTIONS AND DEADLINES] | List agreed action items, owners, dates, and anything that remains tentative. | I will send the security overview by Thursday. Elena will confirm which HRIS export format their team uses. No meeting date was agreed. |
| [CLEAR ASK] | State the single confirmation, decision, document, or next action you want from the recipient. | Ask Elena to confirm the HRIS export format and suggest two times for a technical review next week. |
| [TONE AND CONTEXT] | Specify the desired tone and relevant context such as interview, client project, or internal planning. | Professional, helpful, and brief; do not imply that procurement approval is likely. |
How to use
- Write notes immediately after the meeting and distinguish what was said from what you inferred.
- Include only commitments that have an owner and a realistic date.
- Check names, dates, meeting links, and attachment references before sending.
- Then send: “Make this a 90-word version for a busy executive while preserving the ask and action owners.”
Variations
Interview thank-you
Use this after a job interview.
Draft a thank-you email after my interview with [INTERVIEWER AND ROLE]. The conversation covered [CONVERSATION DETAILS], and my relevant evidence is [MY RELEVANT EXPERIENCE]. Write 100–150 words: thank them, refer to one specific discussion, briefly connect it to one supported qualification, and restate interest without sounding presumptive. End with a polite next-step sentence. Do not claim I would solve problems we did not discuss or imply an offer. Output a subject line and email. Ask up to 3 questions only if required details are missing.
Manager recap
Use this after a one-on-one with your manager.
Write a concise recap to my manager after our meeting. Notes: [MEETING NOTES]. My commitments: [MY ACTIONS]. Decisions or support I need: [OPEN ITEMS]. Use headings for Decisions, My next steps, and Questions or dependencies. Keep the tone practical and avoid documenting sensitive performance feedback more broadly than needed. State deadlines only if agreed. Output a 100–180 word email or Slack message based on [CHANNEL]. Flag unclear ownership. Ask up to 3 questions only if needed.
Networking follow-up
Use this after an informational conversation.
Write a networking follow-up to [PERSON AND CONTEXT] after our conversation about [TOPICS DISCUSSED]. Include one specific point I found useful, a short update on [MY CONTEXT], and this low-pressure request: [REQUEST]. Keep it under 130 words and make the request easy to decline. Do not overpraise, ask for a job directly unless my request says so, or invent shared interests. Provide a subject line if the channel is email. Ask up to 3 questions only if essential information is missing.
Tips
- Send a recap within 24 hours when the meeting produced decisions or action items; delay makes ownership and exact wording less reliable.
- Separate “we agreed” from “I propose” because a vague recap can accidentally create scope or timeline commitments.
- For an interview thank-you, one accurate reference to the conversation is stronger than a general paragraph about enthusiasm.
- If there are several recipients, name action owners in the email body so a group thread does not diffuse responsibility.
FAQ
Should I include meeting notes in a follow-up email?
Include only the decisions, actions, and unresolved questions that recipients need. A full transcript is rarely useful and can create confusion or sensitivity concerns.
How soon should I send a meeting follow-up?
Send it the same day or next business day for most professional meetings. For interviews, a thank-you within 24 hours is customary.
Can AI infer action items from a transcript?
It can extract candidates, but confirm them against your notes. A statement of interest is not necessarily a commitment or a deadline.