Summarize a Long Email Thread and Draft the Reply

Workflow area: Writing & Email · Tier: Foundation · Hands-on time: ~20 minutes

Long threads punish the person who joins late. The facts are scattered, positions shifted mid-thread, and the one question aimed at you is buried in message fourteen. The trick is to make the model do two separate jobs — first map the thread, then draft the reply — because a model asked to do both at once will happily answer the wrong question fluently.

When to use — and when not to

• Use it for threads of eight-plus messagesproject debates, vendor negotiations, multi-team coordination where positions evolved and you need the current state, not the history.
• Use it when you were added late"looping in Priya" threads where you must reply credibly without an hour of archaeology.
• Use it before meetingssummarizing the thread that spawned the meeting is the fastest pre-read there is.
• Skip it for short threadsunder five messages, reading is faster than prompting, and you will catch nuance the summary flattens.
• Skip it when the thread is a conflictescalations, blame threads, HR-adjacent disputes. Summaries flatten tone precisely where tone is the content. Read those yourself.

The recipe

1. 1.

   Get the thread into the tool. In Outlook with Copilot or Gmail with Gemini, the thread is already in context — skip to step 2. Otherwise, select the whole thread, copy it, and paste it into Claude or ChatGPT. Include sender names and timestamps; delete signatures and legal footers if the thread is huge.

2. 2.

   Ask for a structured map, not a summary. "Summarize this" produces a paragraph that hides exactly what you need. Ask for structure:

   Copy

   Here is an email thread, oldest message first. Map it — do not draft
   anything yet.
   
   [PASTE EMAIL THREAD]
   
   Give me:
   1. One-line context: what this thread is about.
   2. Decisions made — with who made them and in which message.
   3. Open questions — and who each one is waiting on.
   4. Anything directed at ME specifically ([YOUR NAME]) that I have
      not yet answered.
   5. Deadlines or dates mentioned.
   
   Use only what is in the thread. If something is ambiguous or
   contradicted later in the thread, say so — the LATEST position wins.
   

3. 3.

   Check the map against reality. Good output looks like this:

   Copy

   Context: Choosing a vendor for the Q3 event (Skyline vs. Meridian).
   
   Decisions:
   - Budget capped at ₹4.5L — Anita, msg 6.
   - Skyline shortlisted; Meridian dropped — Rahul, msg 11
     (note: msg 9 favoured Meridian; msg 11 reversed this).
   
   Open questions:
   - Can Skyline do AV in-house? — waiting on Rahul.
   - Contract review timeline? — directed at YOU, msg 14, unanswered.
   
   Deadlines: signed contract needed by Aug 22 (Anita, msg 13).
   

   Spot-check the two claims that matter most — open the cited messages and confirm. Reversed decisions are the classic trap: a summary that reports the loudest position instead of the final one will make your reply confidently wrong.

4. 4.

   Now draft the reply — from the map, with a frame. Tell it who you are, what you owe, and what you want:

   Copy

   Based on that map, draft my reply to the thread.
   
   I am: [YOUR NAME, YOUR ROLE]
   I need to: answer the contract-review question (answer: legal needs
   5 working days, so review must start by Aug 14) and confirm I
   support the Skyline decision.
   Tone: [e.g. "brisk, collaborative"]
   Length: under 100 words.
   
   Address every open item directed at me. Do not reopen decided
   points. Do not invent commitments beyond what I stated above.
   

5. 5.

   Edit, verify, send. Check every date and name against the thread, cut anything the model padded in, and add one sentence in your own voice. Reply-all threads have long memories — the thirty-second check is cheaper than a correction email.

Make it yours

• M365 Copilot in Outlook: open the thread and use Summarize — Copilot cites the specific emails behind each point, so click the citations to verify instead of scrolling. Then use Draft with Copilot on the reply and paste the step-4 frame into the instruction box.
• Gemini for Workspace in Gmail:Summarize this email appears on long threads automatically; follow up in the side panel with "what questions in this thread are unanswered, and who is each waiting on?" before asking Help me write for the reply.
• Claude or ChatGPT with a pasted thread: best when the thread spans forwarded fragments from multiple mailboxes. Paste chronologically and say so — models assume the order you paste is the order things happened.
• The weekly variant: paste your five worst threads on Friday and ask for a single "what I owe people" table. Ten minutes, and Monday-you starts clean.

Quality check

• The latest position winswhere the thread reversed itself, your summary and reply reflect the final call, not the loudest one.
• Every "open item aimed at me" is answeredcross off each one against the reply before sending.
• Dates and names verifiedclick through to the source messages for anything you will act on.
• No reopened decisionsthe reply must not relitigate what the thread already settled.
• It sounds like youone hand-written sentence minimum.