Summarize the email thread below for [RECIPIENT AND ROLE]. The purpose is [PURPOSE], and the required tone is [TONE]. The reader needs to make or support this next decision: [NEXT DECISION]. Here is the thread and any supporting notes: [EMAIL THREAD]. Treat the thread as a record, not as permission to infer intent. Distinguish explicit commitments from proposals, questions, and assumptions. Do not invent dates, decisions, owners, approvals, attachments, customer details, or agreement. Preserve uncertainty when the messages conflict. Do not include private or irrelevant personal details. Produce two outputs: 1. An internal summary of 180 to 250 words with these labeled sections: purpose; decisions made; key context; open questions; actions and owners; deadlines; risks or dependencies. Use bullets only for actions. If an owner or deadline is absent, write “unassigned” or “not stated.” 2. A recipient-ready follow-up email of 90 to 150 words. Include a specific subject line, a one-sentence context reminder, the decisions or points requiring confirmation, and a single clear ask with a response deadline only if one was stated in the thread. Do not sound more certain or more committed than the emails support. Before answering, check that every action has an explicit source in the thread and that the draft email does not turn a tentative suggestion into a commitment. Ask up to three clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [RECIPIENT AND ROLE] | Name who will read the summary and what they need it for. | Priya Shah, operations director, who needs a briefing before the vendor call |
| [PURPOSE] | State why you need the summary or follow-up email. | Confirm the launch date and remaining responsibilities |
| [TONE] | Describe the appropriate tone, such as neutral, concise, or warm and firm. | Concise, neutral, and collaborative |
| [NEXT DECISION] | State the decision or confirmation the recipient needs to make. | Approve either the October 14 launch or a one-week delay |
| [EMAIL THREAD] | Paste the relevant thread in chronological order, including dates and sender names when available. | Sept. 18, Jordan: design files will be ready Friday. Sept. 19, Mia: legal review may take five business days. Sept. 20, Priya: no launch date approved yet. |
How to use
- Paste the full relevant thread in chronological order and include the newest replies.
- Name the reader’s decision so the summary does not become a transcript.
- Verify any owner and deadline against the original messages before forwarding the result.
- Follow up with: “Make the follow-up email firmer while preserving every stated uncertainty.”
Variations
Executive brief
Use when a senior leader needs the thread reduced to decision-relevant facts.
Turn this email thread into a 150-word executive brief for [LEADER ROLE]. The decision needed is [DECISION], by [DEADLINE OR NOT STATED]. Extract only material facts from [THREAD]: what changed, options, recommendation if explicitly made, costs or risks, and the exact decision requested. End with a one-line recommended next move only when the thread supports it; otherwise state what information is missing. Do not include process detail, infer agreement, or invent figures. Check that each statement can be traced to the thread and that the brief makes uncertainty visible. Ask up to three questions only if needed.
Action register
Use when a thread has many tasks spread across several people.
Extract an action register from [EMAIL THREAD] for [PROJECT]. Return a table with action, owner, due date, status, dependency, and exact supporting message. Mark tasks as proposed, accepted, completed, or unclear based only on the text. Then write a short escalation note listing overdue, unassigned, and blocked items without assigning blame. Do not convert a question into a task or supply missing dates. Check that each action has one source and that duplicate actions are merged only when they are clearly the same. Ask up to three questions only if required inputs are missing.
Client recap
Use after a client thread when you need a clean written record.
Draft a client-facing recap from this thread: [THREAD]. The project is [PROJECT], and the agreed tone is [TONE]. Write a subject line and an email under 170 words with confirmed decisions, deliverables, client and team actions, and dates only where explicit. Put unresolved items in a short “Please confirm” list, then end with one focused ask. Avoid internal debate, blame, and legal or commercial promises not already made. Check that the recap does not add scope or imply approval. Ask up to three clarifying questions only if necessary.
Tips
- Summarize in chronological order first when the thread is confusing, then reorganize by decision and action for the reader.
- Quote or preserve exact wording for commitments involving price, scope, approval, or deadlines; a paraphrase can quietly change the obligation.
- Mark a missing owner as unassigned instead of guessing from who last replied.
- Keep the outgoing email narrower than the internal summary so recipients can answer one clear request.
FAQ
Can AI summarize an email thread with conflicting messages?
Yes, if you ask it to label conflicts and preserve uncertainty. Check the original thread before relying on any disputed deadline or commitment.
Should the summary include every email?
No. Include the thread relevant to the decision, but retain the source messages so someone can verify the summary.
Can the prompt write a reply too?
Yes. The second output is a follow-up draft, but it should be checked for accidental changes in scope, timing, or commitment before sending.