Long threads are difficult because they mix history with decisions. A useful summary is not a shorter copy of every message. It is a map of what is settled, what is still unclear, and what somebody needs to do next.
Read for changes, not chronology
Start at the latest message and work backwards only when you need the context behind a claim. Look for words such as “agreed,” “instead,” “blocked,” and “by Friday.” They often mark a change in state.
Do not assume the most recent message contains the final decision. A later “sounds good” may be acknowledging a detail, not accepting the whole plan. Keep the subject and sender attached to anything that remains ambiguous.
Write a decision-first summary
- Decision: what the group has actually agreed to.
- Evidence: the facts or links that support it.
- Open questions: unresolved choices, with an owner if known.
- Next reply: the smallest message that moves the thread forward.
Keep the summary separate from your interpretation. If you are unsure, mark it as an open question instead of turning a guess into a commitment.
Protect sensitive detail
Before sharing a summary, remove personal information and credentials. A shorter thread is still sensitive if the summary repeats the wrong details. Keep the original message available for audit, but make the working note safe enough to forward to the people who need it.