A useful email summary lets you resume work: what was decided, what is missing and who needs to act. Use this method manually, or ask an AI assistant for a first version that you check.
1. Define the question you need to answer
Before rereading the thread, state the goal: “Can I confirm the date?”, “Which document is missing?” or “What did we approve?”. This determines which details matter. A general summary may not answer the decision in front of you.
2. Rebuild the timeline
Read new messages in order. Separate quoted earlier text from new information. Look for corrections: a date proposed on Monday may have changed by Wednesday. Keep qualifications such as “possible”, “to confirm” and “subject to” visible.
3. Separate four elements
- Confirmed decisions: what was explicitly accepted.
- Open questions: what still needs an answer.
- Next actions: the task and its owner.
- Deadlines: confirmed or merely requested, including any conditions.
If no owner or deadline is given, write “to confirm”. Do not turn a suggestion into a commitment.
4. Complete example: copy received, logo missing
All messages and names in this scenario are fictional. The summary and reply are editorial examples.
- Monday, client: “We would like to review the homepage on Thursday. We will send the copy on Tuesday.”
- Tuesday, consultant: “I can prepare the mockup once I receive the copy. Please also confirm which logo to use.”
- Wednesday, client: “The copy is attached. The logo will arrive tomorrow; could we still get initial feedback on Thursday?”
Checkable summary: the client says the copy is attached. The logo is still expected on Thursday. The consultant agreed to prepare a mockup after receiving the copy. A Thursday review was requested but not confirmed by the consultant.
- Decision: prepare the mockup after receiving the copy.
- Open question: is Thursday’s review possible with the logo still missing?
- Actions: the client sends the logo; the consultant opens the copy and checks availability.
- Deadline: Thursday is a review request, not an agreed delivery.
5. Check attachments and prepare your reply
“The document is attached” does not prove that the right version is present or readable. Open it, check amounts and dates, then check your availability. Summarising an email’s text does not replace that work.
Possible reply: “Thanks for the copy. I’m preparing the mockup and can confirm the review slot once the logo is available.” Adjust it to what you actually checked.
Use AI to summarise the thread
A useful instruction is: “Summarise this conversation, separating confirmed decisions, open questions, actions with owners and deadlines. Mark what remains to be confirmed.” Then compare each point with the source message.
Remail provides thread summaries and drafts for Gmail and Outlook. A summary can restore context, but AI may omit information or misinterpret a phrase. Review the reply before sending.
Before sharing a thread with a tool, check your organisation’s rules and the service’s data terms. Do not copy sensitive conversations into a service you are not authorised to use.
Common questions
Should every message be included?
Include context needed for the decision, especially corrections and confirmations. A short excerpt may hide a condition.
What if two messages contradict each other?
Record both versions and their dates. Ask for confirmation rather than choosing arbitrarily.
Is the summary enough to reply?
Use it as a guide. Check the originals for every promise, date, amount and attachment.
For the messages you need to answer and follow up, see our inbox organisation method.
Written by Rafik Belkadi, founder of Remail. Updated 20 October 2026.