Summaries
Summaries are a fast orientation layer for sources and project material. They help you decide what to read closely, what to ignore, and what to ask next.
What this page covers
Learn how summaries are generated, what they can omit, and how to use them to triage sources.
What summaries are for
Use summaries to:
- triage a long source
- compare several sources quickly
- identify main claims and limitations
- prepare questions for chat
- decide whether a source belongs in the project.
Do not use summaries as the final authority for important claims. Verify with the source.
Useful summary fields
| Field | Question answered |
|---|---|
| Topic | What is the source about? |
| Main claim | What does it argue or show? |
| Method | How did it reach the result? |
| Findings | What are the key results or conclusions? |
| Limitations | What should be treated carefully? |
| Relevance | Why does it matter for this project? |
| Follow-up questions | What should you ask or verify next? |
Reading summaries critically
Good summaries preserve uncertainty. Be cautious when a summary:
- omits limitations
- makes a strong claim without a source passage
- collapses disagreement across sources
- treats an abstract as the full paper
- ignores methods or sample size.
Summary versus synthesis
A summary explains one source or item. A synthesis compares multiple sources and builds a higher-level answer. Use Synthesize across multiple sources when the task requires comparison or judgment.
Best practice
After using a summary to triage, open the source and save your own verified takeaway in a note.
Use summaries to triage sources
Use this guide to read source summaries and decide what to read closely, what to skip, and what to ask next.
When to use summaries for triage
Use summaries when a project has more sources than you can read closely. A summary helps you decide which sources deserve detailed attention first.
Before you start
Decide what you are triaging for. Different decisions need different criteria:
- Relevance to a specific research question
- Strength of evidence or methodology
- Limitation or caveat coverage
- Disagreement with your current understanding
- Usefulness for a piece of writing or presentation
Read each summary against that criterion and record why the source should advance or be set aside.
Steps
- Open a source from the project list.
- Read the summary for that source.
- Identify the main claim, method, findings, and any limitations mentioned.
- Decide: read closely now, return later, or skip.
- Repeat for the next source.
Create a triage note
A triage note captures your decisions so you can act on them:
| Source | Why it matters | Read closely? |
|---|---|---|
| Paper A | Strong method match for the question | Yes |
| Paper B | Background context only | Later |
| Report C | Has useful definitions | Partial |
Move from triage to evidence
Summaries help you decide what to read next. They do not replace the source passage. After a source advances, open it and verify the relevant evidence before citing it in a note or report.