Summarize without losing the meaning

What you’ll be able to do

• Distinguish summary, extraction, and interpretation.
• Create a brief that preserves caveats and unresolved questions.
• Audit an action list against its original notes.

Three tasks that look similar

A summary compresses the main ideas. An extraction pulls defined fields from the source. An interpretation explains what the material may mean. If you need a record of commitments, ask for extraction before asking for a polished summary.

A useful brief should serve a specific reader. A volunteer needs the next action. An organizer may need decisions, dependencies, and open questions. “Summarize this” leaves the assistant to guess what to keep.

Work from a small, complete source

Use these fictional meeting notes:

“Lena will draft the invitation by Thursday. Omar will ask the library whether the room has a projector; no deadline was agreed. The group discussed Saturday, but the date depends on room availability. A 20-seat limit was suggested, not approved. Next meeting: Tuesday at noon.”

A faithful extraction contains:

• Invitation draft — owner Lena — due Thursday.
• Projector inquiry — owner Omar — due date not specified.
• Workshop date — not confirmed; depends on room availability.
• Capacity — 20 seats proposed, not approved.
• Next meeting — Tuesday at noon.

It must not turn a suggestion into a decision or a dependency into a confirmed date.

Try a source-grounded brief

Use only the fictional notes below.
First extract: confirmed decisions, actions, owners, deadlines, proposals, and open questions.
Write “not specified” when an owner or deadline is missing.
Then produce a 100-word brief for the organizing team.
Keep proposals separate from approved decisions. Preserve dependencies and uncertainty.

Notes: Lena will draft the invitation by Thursday. Omar will ask the library whether the room has a projector; no deadline was agreed.
Saturday was discussed, subject to room availability. A 20-seat limit was suggested, not approved.
Next meeting: Tuesday at noon.

Your practice: run a two-pass review

1. Run the extraction prompt and compare every field with the notes.
2. Underline any item that changes the strength of the source: proposed becomes approved, may becomes will, or discussed becomes decided.
3. Correct the extraction before asking for the final brief.
4. Ask for a revised brief based only on the corrected extraction.
5. Check that every sentence in the brief can be traced back to the notes.

Your finished artifact: The original notes, corrected extraction, and final brief. A teammate should be able to identify both the next action and what remains unresolved.

When the document is long

Break the work into meaningful sections, identify the document version, and preserve page or section labels where available. Review section summaries against their sources, then create a combined brief. Check the combined brief for contradictions and caveats lost during compression. A shorter result is not automatically a more faithful one.

A common mistake

Asking for an extremely short summary of a document containing important exceptions. If a caveat changes what someone should do, it deserves space. Change the length limit before removing the caveat.

Reflection

Which detail would cause the biggest practical error if it disappeared? Explain why that detail must survive the summary.

Transfer to your own work

Use non-sensitive notes from a meeting, class, or volunteer project. If you cannot share the original material with the tool, practice with a fictional version that preserves the structure of the task.