How to write better summaries of long recordings

A two-hour lecture or a long meeting holds far more than you can remember. A good summary is what makes it useful later. It is short enough to read in a few minutes and complete enough to jog your memory. Whether you write it by hand or start from an AI draft, the same principles apply.

Start by deciding what the summary is for

The right summary depends on how you will use it. Before you begin, choose one of these purposes:

• A quick refresher: a few lines to remind you of the main argument before a seminar.
• Exam revision: definitions, steps, causes and comparisons that could be tested.
• Action notes: decisions, owners and deadlines from a meeting.
• Reference: a detailed record you can search for exact points later.

This is the same trade-off as choosing between a concise and a detailed summary in QuickNotes. Concise suits the refresher, and detailed suits revision and reference. Picking the purpose first stops you from writing something that is too long to reread and too vague to use.

Find the structure of the recording

Long recordings rarely wander at random. Lectures usually have an outline, even if the lecturer never says it: an introduction, three or four main topics, examples, and a wrap-up. Meetings follow an agenda, formal or not. Interviews move through themes. Your first job is to identify these sections.

If you have a transcript, this is quick. Skim it and put a short heading on each stretch, for example "Definition of inflation", "Two causes", "Worked example", "What to read next". Those headings are the skeleton of your summary.

Keep the load-bearing parts

Under each heading, keep only what a reader would miss. A useful checklist:

• Claims and conclusions: what the speaker says is true or should be done.
• Reasons: the "because" that supports each claim.
• Definitions and key terms: in the speaker's words if they were precise.
• Numbers, names and dates: anything that would be hard to reconstruct.
• Examples: one strong example per idea is usually enough.
• Open questions and next steps.

Cut repetition, jokes, tangents, and filler. Spoken language is redundant by nature, and much of what people say is signposting ("as I mentioned earlier") that adds nothing on paper.

Write in short, plain sentences

A summary should read quickly. Prefer bullet points or short paragraphs, start each with the main idea, and use verbs. Compare "Discussion of budget concerns" with "The team agreed to cut the event budget by 10 percent because sponsorship fell through". The second version records a decision and a reason, and you can act on it.

Use the two-pass method

1. Pass one, coarse: write headings for each section and one line for each. Total length: about a page or less.
2. Pass two, refine: for the sections that matter most, add the reasons, definitions and examples. Leave low-priority sections as one-liners.

This keeps you from spending 80 percent of your effort on the first half of the recording, a common mistake when you summarize as you listen.

Where an AI summary helps, and where it does not

An AI summary saves the tedious first pass. QuickNotes transcribes a recording and then writes a concise or detailed summary, so you start with a structure to edit instead of a blank page. It is particularly useful for long recordings, where reading a summary and then diving into the transcript for details is faster than listening again.

But AI summaries have known weaknesses, so check them:

• Errors from the transcript carry over. If a name or number was mistranscribed, the summary may repeat it.
• Emphasis can be wrong. The summary may treat a passing remark as central, or skip something the lecturer stressed.
• Nuance gets flattened. Qualifiers such as "in most cases" or "under these assumptions" may disappear.
• Specialist terms can be garbled, especially in noisy audio or unusual vocabulary.

Treat the summary as a draft. Read it against the transcript, correct what is off, and add what is missing.

A quick verification routine

1. Read the summary once without stopping.
2. Pick the three claims that matter most and search the transcript to confirm each one.
3. Check every number, name and date against the transcript, slides or documents.
4. Write one sentence in your own words about what the recording was about. If that sentence does not match the summary, something is off.

Recordings that make better summaries

You can help the summary before it exists by recording well. Sit close to the speaker, reduce background noise, and, if you are running the meeting, state the purpose at the start and recap decisions at the end. A clear recap gives both you and any AI tool a strong anchor to summarize from. For lectures, our guide on recording a lecture covers placement and etiquette, and meeting notes summary covers the meeting case.

An example of the difference

Suppose a lecture spends ten minutes on how interest rates affect borrowing. A weak summary says "The lecturer discussed interest rates and borrowing." A strong one says "Higher interest rates make borrowing more expensive, which reduces spending and slows inflation, but too much slows growth." The second version is what you would want to read the night before an exam. When you edit an AI draft, aim for that level of specificity.

From summary to memory

A summary is not the end. If the recording is for study, turn the summary into questions and test yourself, which is what Study mode does with 10 flashcards and a 5-question quiz built from the summary. Our article on turning lecture notes into flashcards explains how to do that well.

To recap: choose a purpose, find the structure, keep the load-bearing parts, write plainly, and verify anything an AI drafted. A summary you trust is a summary you will actually use.

Related reading