Summarise any doc, paper or meeting

Long documents bury their point. A lazy 'summarise this' gives mush; asking for a clear structure gives you something you can act on. For anything high-stakes, still read the original around the key bits.

The single upgrade that changes everything is asking for a specific shape instead of a generic summary. Key points, then decisions, then action items produces something you can act on; 'summarise this' produces beige. Structure forces the model to organise the content the way your brain wants to consume it.

A summary should differ depending on why you need it. Tell it the lens — 'summarise for someone deciding whether to invest', 'pull only what's relevant to marketing', 'the 3 things I need before the meeting'. And ask what's unclear or missing; the gaps are often more important than the content, and a plain summary hides them.

Stop reading the summary and start interrogating the document — ask follow-ups, request different depths, feed several documents at once and ask for the through-line and contradictions. But for anything high-stakes — a contract, a medical or legal document — the summary is a map, not the territory; read those parts in the original, because a summary can quietly drop the one caveat that changes everything.

1. 1Paste or upload the document.
2. 2Ask for a structured summary: key points, decisions, action items, and gaps.
3. 3Tell it your purpose so it pulls the relevant parts.
4. 4For anything important, skim the original around the points that matter.

Summarising prompts