Turn a Long Email Thread Into What I Need to Do
Turn a long email chain into a concise summary, clear decisions and actions, then prepare the reply the thread actually needs.
Step 01
Summarise the thread
Summarise This Email Thread
Turn a long email chain into a reliable short summary that preserves who said what, what changed and what is still unresolved.
Summarise this email thread so I can understand the situation without rereading the whole chain. Preserve chronology and attribution where they matter. Give me: 1. One-paragraph overview of what the thread is about. 2. Timeline of the important developments in order. 3. Key decisions already made. 4. Important facts or commitments, including who made them. 5. Issues that are still unresolved. 6. The latest position at the end of the thread. Rules: - Do not treat an early proposal as a final decision if later emails changed it. - Do not merge different people's views into one "team" position unless the thread supports that. - Flag ambiguous dates, owners or decisions. - Ignore greetings, signatures and repeated quoted text unless they change the meaning. - Do not invent context that is not in the thread. Email thread: [PASTE OR ATTACH THREAD]
Step 02
Find decisions, questions and actions
Extract Decisions, Questions and Actions From This Email Thread
Extract the decisions, open questions and actions buried in a long email thread, with owners and deadlines only where the thread actually states them.
Extract the decisions, questions and actions from this email thread. Create three sections: 1. Decisions For each decision include: - what was decided; - who appears to have agreed or decided it; - when it was decided, if clear; - any condition or caveat. 2. Open questions For each question include: - the question; - who raised it; - whether anyone answered it; - what is still unresolved. 3. Actions For each action include: - action; - owner, if stated; - deadline, if stated; - status: New / In progress / Appears complete / Unclear. Do not assign an owner or deadline just because one would be useful. Write "Not stated" when the thread does not establish it. Finish with "What I probably need to do next" based only on actions explicitly assigned to me or clearly requiring my response. If my identity is not obvious, ask me who I am in the thread. Email thread: [PASTE OR ATTACH]
Step 03
Draft the reply
Draft the Reply This Email Thread Needs
Draft the reply a long email thread actually needs, using the latest position and unresolved points rather than replying to every message individually.
Draft the reply this email thread needs now. I will provide: - the thread; - who I am in the conversation; - what outcome I want from my reply; - any facts or decisions I need to add. First identify privately from the thread: - the latest agreed position; - what remains unanswered; - what requires a response from me. Then draft one email that: 1. Opens with the current position rather than retelling the whole history. 2. Answers questions directed to me. 3. Confirms decisions or actions only where they are actually agreed. 4. Makes my requests or next steps clear. 5. Uses a concise, professional tone. Do not invent missing owners, dates, approvals or commitments. If a crucial point is unresolved, mark it as a question rather than quietly deciding it. Thread: [PASTE OR ATTACH] I am: [NAME / ROLE] What I need the reply to achieve: [OUTCOME] Additional confirmed information: [OPTIONAL]
Pack details
- Prompts
- 3
- Category
- Work & Communication
- Use case
- Email Triage
- Updated
- 26 Aug 2026