Write a TL;DR: Summarise Long Messages and Documents in Four Lines
Busy readers want the point first. A four-line TL;DR tells them what this is, what changed or was decided, what you need from them and where the details are. Learn the format with before-and-after examples for emails, reports and threads.
Who this is for and when to use it
Use a TL;DR ("too long; didn't read") when you send something longer than a screen: a report, a long email, a project update or a thread with thirty replies that someone has to catch up on. It suits people who write to managers, clients or teams, and students who need to summarise reading. The summary goes at the top, so the reader can decide in ten seconds how much more to read.
The four lines
- What this is. One line on the topic and purpose, such as "Update on the venue booking for the March workshop".
- What changed or was decided. The main finding or outcome, in plain words.
- What I need from you, and by when. A specific action and a date, or "No action needed".
- Where the details are. The section, attachment or link to read if they want more.
Each line should be one sentence. If a line needs two, you probably have two points and should decide which one matters most.
Before and after
Before: a 400-word email beginning "Following our discussion last week and the subsequent conversations with the venue and the catering team, I wanted to share some thoughts on where we are..." After, at the top of the same email: "TL;DR: 1) Update on the venue and catering for the March workshop. 2) The venue is confirmed for 14 March; catering is still waiting for a quote. 3) Please approve the 40-person booking by Friday 6 March. 4) Costs and options are in the table below." The detail stays; the reader gets the point and the request first.
Summarising a long thread
For a thread that has gone round in circles, scan from the first message to the last and pull out three things: the question, the options discussed and the current position. Then write: "Summary of the thread: we are deciding between A and B for X. Most people prefer A because of cost; two concerns about timing remain. Decision needed from [name] by [date]." Post it at the end of the thread or as a new message. Check it against what people actually wrote, not what you remember. If someone disagrees with your summary, that is useful: the disagreement was there already.
Write for the reader
- For a manager: lead with the decision or risk and what you need from them.
- For a team: include who does what and when.
- For a client: use their words and avoid internal terms.
- For someone returning after leave: give the current status, then what they must do first.
- For your own notes or study: list the main argument, the evidence and your questions.
The same four lines work in weekly status updates and at the top of meeting notes. For the email around it, see how to write a clear email.
Check accuracy and do not distort
A shorter version must still be true. Before you send it:
- Check the facts. Dates, amounts and names must match the full text.
- Keep qualifications that matter. If the main finding is uncertain or depends on a condition, say so in the summary, not only below.
- Do not bury bad news. Delays, risks and costs belong in the top lines.
- Do not add new claims. The summary should contain nothing that the document does not.
- Show who said what. In a thread, attribute opinions to people or groups, instead of writing "everyone agrees".
When not to summarise
Do not use a TL;DR to replace material that people must read in full, such as legal terms, safety instructions, medical information or contracts. For these, use a summary only as a pointer and make clear that the full text matters. Likewise, for an upset or sensitive message, a four-line summary can feel cold. Speak to the person first. To prepare, see preparing for a difficult conversation.
Edge cases
- No action needed. Say so in line three. It is a relief to the reader.
- Several actions for different people. Use a short list with names and dates instead of one sentence.
- Readers who skim only the subject line. Put the essentials in the subject too, such as "Approve venue booking by Fri 6 March".
- A very long document. Write a TL;DR for each section as well as one overall summary.
- Translated or cross-cultural readers. Use simple words and short sentences, and avoid idioms.
Plain-text template
TL;DR 1. What this is: ____________________ 2. What changed / was decided: ____________________ 3. What I need from you: ____________________ By: ________ (or: No action needed) 4. Where the details are: ____________________ Accuracy check: [ ] Dates, amounts and names match the full text [ ] Important caveats and risks are in the top lines [ ] Nothing in the summary is missing from the document [ ] The reader can act without opening the full text
A four-line TL;DR says what this is, what changed, what you need and where the details are. Write it for your reader, check it against the full text, keep caveats and bad news in view and do not use it for material that must be read in full.
Open the last long email you sent and write its four lines at the top. Then use the same format for weekly status updates, meeting notes that turn into actions and any clear email you send.