TL;DR:
A newcomer needs four things from a thread: what was decided, what is still open, who owns what, and the dates.
Read the thread once to mark those four, then write from your marks, not from the order of messages.
Link or attach the thread but never make the summary depend on it.
You are adding a new person to a project, and the email thread about it has 30 messages. Forwarding it with "see below" hands them an hour of reading and a puzzle: which of the 30 messages is still true? A good summary does that work for them in a few lines.
What a newcomer actually needs
Threads are written in the order things were said, but a newcomer needs them in the order things matter. Early messages often contain ideas that were later dropped. Late messages contain the decisions. So do not retell the story. Pull out four things.
Decisions. What was agreed, and roughly when.
Open questions. What is still undecided, and who is deciding.
Owners. Who is doing what next.
Dates. Deadlines and upcoming meetings, written as full dates.
Read in two passes
Skim from the bottom: Start with the newest messages. They show the current state, and you will recognize what earlier messages were about.
Mark as you read the whole thread: Use a note or a document with four headings: decisions, open questions, owners, dates. Add each item with the name of the sender and the day it appeared.
Resolve conflicts: If one message says Friday and a later one says Monday, keep the later one, unless someone objected in between. If you cannot tell, list it as an open question.
Write bullets, not paragraphs: One line each. Start with the topic word, then the fact.
Check names and dates against the thread: Open the original once more to confirm every owner and date.
Worked example: a 30-message thread into five bullets
Suppose the thread is about a customer event. Over 30 messages, people debated three venues, a budget, a guest list, a catering vendor and a date. Here is what your notes might look like after the second pass.
Type | Item | Source |
|---|---|---|
Decision | Venue: the library hall | Message 14, Dana |
Decision | Budget capped at 4,000 dollars | Message 19, Mehmet |
Open question | Catering vendor: two quotes, no choice yet | Messages 22 to 27 |
Owner | Dana books the hall; Priya compares catering quotes | Messages 28 and 29 |
Date | Final guest list due 3 March; event on 21 March | Messages 21 and 30 |
Now turn the notes into five bullets that can go in an email body:
Decided: the event is in the library hall (Dana, message 14).
Decided: the budget is capped at 4,000 dollars.
Open: choose between the two catering quotes; Priya is comparing them.
Next: Dana books the hall; Priya reports on catering.
Dates: guest list due 3 March, event on 21 March.
Check it. Five bullets cover all four types, and every item can be found in the thread if the newcomer wants proof. The dates are written out so they cannot be misread as relative ("next Friday" changes meaning the day after you send).
Add a one-line opening such as "Here is where the event planning stands as of today", then the bullets, then a line that links to or attaches the full thread for reference. The newcomer can now reply with a question that matters.
Choosing the right format for the reader
A summary can go in the body of a new email, at the top of a forwarded message, or in a shared document. For one newcomer, the top of a forward is usually best, because the thread sits right below it for reference. For a group, a short email with the bullets and a link to a shared note is easier to keep up to date.
Put the most urgent item first, even if it was decided last. If something must happen by tomorrow, the reader should see it before anything else. Then order the rest by how soon the reader has to act, not by when it was discussed.
Use the same words the thread used for names of things. If the team called the project "the autumn event", do not rename it in your summary, or the newcomer will not recognize it when they open the thread. Spell out abbreviations the first time you use them, since a newcomer may not know them yet.
Mistakes to avoid
Retelling the thread in order. That is the long way round.
Including every opinion. Summarize the outcome and mention a disagreement only if it is still live.
Leaving out the owner. A fact without an owner means nobody acts.
Using relative dates. Write "3 March", not "next week".
Putting your own opinions into a neutral summary. If you have a view, add it as a separate line.
Forgetting to check with the people named. A quick "did I get this right?" avoids mistakes.
When the thread is very long
If you have a thread of dozens of messages, work in chunks: summarize messages 1 to 10, then 11 to 20, and so on, and merge the notes at the end. Later chunks override earlier ones where they conflict. Do the same when the thread splits into side conversations; summarize each branch under its own heading.
If you work with a long thread often, DuckyHelper can see your screen while you scroll and talk it through with you out loud, which some people find easier than reading alone. Always check any summary against the original, whoever or whatever helped you draft it.
Summaries pair well with a clean handover. See handing off an email conversation to a colleague for how to introduce the new person, and replying to a customer complaint for threads with a customer.
Frequently asked questions
How long should the summary be?
As short as covers the four types. Five to eight bullets is usual; a longer one suggests the thread covers several topics.
Should I attach the whole thread?
Yes, as a reference. The summary should still make sense without it.
Get started
