Write a post-meeting confirmation email

Auteur: AILesson4 min de préparationTesté avec:ChatGPTRévisé: 2026-08-28

Réponse rapide

Confirm what was decided, assigned, and left open without upgrading discussion into agreement. Fournir: Meeting notes, Recipients and context, Reply and tone rules. Résultat attendu: A send-ready confirmation email and a list of gaps to resolve.

1

Ajouter votre contexte

Votre texte reste dans ce navigateur. AILesson Prompts ne l’envoie ni à un modèle ni à un serveur.

2

Votre prompt

Les champs non remplis restent visibles sous forme d’espaces réservés, afin que vous puissiez quand même copier et modifier le prompt.

Write a post-meeting email confirming decisions and next steps.

Meeting notes:
[notes]

Recipients, attendance, and required confirmations:
[recipients]

Tone, correction deadline, and unresolved-item rules:
[style]

Use only the notes. Separate confirmed decisions, proposed options, actions, and open questions. Preserve exact owners, dates, dependencies, conditions, and dissent. Write Owner not specified or Due date not specified where needed; do not assign work by inference. Make corrections easy by asking recipients to identify inaccuracies by the stated time, but do not treat silence as approval unless that rule was explicitly agreed. Return: subject, concise email, and missing-information checklist.
Essayer dans le Playground
Privé par défautL’assemblage du prompt se fait localement dans votre navigateur. Évitez de placer des informations confidentielles dans un service d’IA, sauf si votre organisation l’autorise.

De l'entrée au résultat

Un exemple détaillé

Voyez comment un contexte concret transforme cette recette en résultat utilisable.

Entrée réelle

Meeting notes
18 June website launch meeting. Decided: keep 8 July public launch if accessibility testing passes. Noor will deliver revised keyboard-navigation fixes by 24 June. Eli will run the retest; no date assigned. Marketing suggested announcing on 1 July, but the group did not decide. Open: who makes the final go/no-go call and what severity of accessibility issue blocks launch. Rosa disagreed with announcing before retest completion.
Recipients and context
All six attendees, including Rosa; the project sponsor did not attend. Recipients should verify the record and clarify ownership gaps.
Reply and tone rules
Neutral and concise. Ask for factual corrections by 20 June 17:00, but explicitly say open questions still require replies.

Exemple de sortie

Subject: 18 June launch meeting—decisions and open items

Hi all,

Here is my record of the 18 June meeting.

Decision: retain the 8 July public launch, conditional on accessibility testing passing.

Actions: Noor—deliver revised keyboard-navigation fixes by 24 June. Eli—run the accessibility retest; due date not specified.

Not decided: Marketing proposed a 1 July announcement. Rosa opposed announcing before the retest is complete.

Replies still needed: who owns the final go/no-go decision; what issue severity blocks launch; and the retest due date. Please send factual corrections to this record by 20 June at 17:00. Silence will not resolve the open questions.

Thanks, [Sender name]

Missing information: sender name, retest date, go/no-go owner, blocking threshold, and whether the absent sponsor must approve.

Pourquoi cela fonctionne

  1. 1

    Separating decisions from proposals prevents a polished recap from creating false commitments.

  2. 2

    Visible missing owners and dates turn documentation gaps into concrete follow-up.

Vérifier le résultat

  • Are confirmed decisions clearly separated from proposals and questions?

  • Do action owners and dates appear exactly as recorded?

  • Does the correction request avoid treating silence as approval?

Utilisez-la en toute confiance

Questions fréquentes

Des réponses pratiques sur le bon moment pour utiliser cette recette, ce qu’il faut fournir et les cas où une vérification humaine reste nécessaire.

What should I prepare before using “Write a post-meeting confirmation email”?

For “Write a post-meeting confirmation email,” prepare Meeting notes, Recipients and context, and Reply and tone rules. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Write a post-meeting confirmation email” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A send-ready confirmation email and a list of gaps to resolve—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Write a post-meeting confirmation email”?

The published test record for “Write a post-meeting confirmation email” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

Faites avancer votre travail