Progressive Summarization: How Forte's Layered Note Method Works
Updated · 16 min read

Listen to this post
Contents
- TL;DR
- Table of Contents
- What progressive summarization is and the problem it solves
- The layers, one by one
- Layers 0 and 1: keep the source, capture the best of it
- Layer 2: bold what matters
- Layer 3: highlight the best of the best
- Layer 4: the executive summary
- Layer 5: remix
- How the workflow actually runs
- What the numbers look like
- A worked example
- Where it goes wrong
- How it differs from other approaches
- Using it on articles, papers and podcasts
- Students
- Professionals
- Podcasts and video
- Our perspective
- Running the method inside Omphalis
- A simple way to start this week
- FAQ
- What are the layers of progressive summarization?
- Do I need to apply every layer to every note?
- When should I do each layer?
- Is progressive summarization the same as using an AI summarizer?
- Can I use it for PDFs, podcasts and videos?
- Sources
- Recommended
Progressive summarization is a way of condensing saved material in small passes over time, so the best ideas in a note become easy to find later. You capture a source once, then bold, highlight and summarize it only when you come back to it for a real reason. Most notes stay lightly processed. A few earn the full treatment. That is the whole idea, and it is more forgiving than it sounds.
This guide explains where the method comes from, what each layer does, how to run it as a workflow, where it goes wrong, and how to adapt it for articles, research papers and podcasts.
TL;DR
- Progressive summarization, created by Tiago Forte, compresses a saved note in stages, only when you revisit it and only as far as its value justifies.
- There are five working layers on top of the original source: capture, bold, highlight, executive summary, and remix.
- Forte's own guidance says most notes should stop early. A small minority ever reach the summary or remix stages.
- The main failure is not skipping layers. It is mistaking highlighting for understanding, or over-processing notes you will never use.
- For long reading, keep the source one click away so every summary can be checked against the original passage.
Table of Contents
- What progressive summarization is and the problem it solves
- The layers, one by one
- How the workflow actually runs
- Where it goes wrong
- Using it on articles, papers and podcasts
- Our perspective
- Running the method inside Omphalis
- A simple way to start this week
- FAQ
- Sources
What progressive summarization is and the problem it solves
Most people who save things online have the same experience. The article gets clipped, the PDF gets filed, the podcast gets bookmarked, and none of it is seen again. Notes pile up as long, dense walls of text that nobody wants to reread.
Tiago Forte, who runs Forte Labs, introduced progressive summarization as a response. In his original post, he describes it as opportunistic compression: you distill a note in multiple layers, spread over time, to make it discoverable and usable for future needs. Instead of trying to fully process every source the moment you save it, you do a little each time the note comes back in front of you.
The framing that makes this click is time. The challenge is not moving information between apps. It is moving it through time, to a future version of you whose projects you cannot predict. Forte describes the practical result as a note collection that stops being a dense jungle and becomes an archipelago of accessible islands, where rich triggers and prompts help you recognize and retrieve earlier insights.
Two goals pull against each other here. Compression makes a note quick to scan. Context makes it truthful and understandable. Progressive summarization tries to hold both by compressing in layers and leaving every earlier layer intact underneath.
The layers, one by one
The layers are numbered from the source upward. Per Forte's description, Layer 0 is the original full-length source and Layer 1 is the content you first brought into your note-taking program. Each higher layer is a smaller, denser subset of the one below it.
| Layer | What you do | What it gives you |
|---|---|---|
| 0 | Leave the original source as it is | The full context to return to |
| 1 | Capture the passages or ideas worth keeping | A searchable note instead of a lost tab |
| 2 | Bold the best keywords, phrases or sentences | A note you can skim in a minute or two |
| 3 | Highlight the best of the bolded parts | A 10-second read of the core idea |
| 4 | Write an executive summary in your own words | A note you can use without rereading |
| 5 | Remix the material into something new | Original work built from your reading |
A few notes on each.
Layers 0 and 1: keep the source, capture the best of it
Layer 0 is the source itself, and it never changes. Layer 1 is what you pulled out of it. The discipline at this stage is selectivity. Capturing a whole article is rarely useful, because you have just moved a long text from one place to another. Capture the passages that made you stop, and keep a link back to where they came from.
Layer 2: bold what matters
When you return to a Layer 1 note, bold the keywords, phrases or sentences that carry the argument. If you skimmed only the bold text, you should get the gist. This is the first real act of compression, and it takes minutes.
Layer 3: highlight the best of the best
Layer 3 highlights a subset of what you bolded. A good test: if you only had ten seconds, which parts would you read? Very few notes deserve this pass. It is reserved for material you keep coming back to.
Layer 4: the executive summary
At Layer 4 you stop marking up other people's words and write your own. A short summary at the top of the note, in your language, shows whether you understood the source or only recognized it. This is also where the method meets real learning, not just organizing.
Layer 5: remix
Layer 5 is using the material: an essay, a presentation, a literature review paragraph, a decision memo. Forte says it applies to a very small share of notes, because most reading never becomes output, and that is fine.
How the workflow actually runs
The workflow is less a procedure than a habit with a stopping rule. Here is a version you can start with.
- Capture (Layer 1). Save the source and pull the passages that matter into a note. Do it quickly, ideally the same day.
- Wait for a reason. Do not process further now. The method defers deep work until the note is needed, and you revisit it during routine reviews or when a project calls for it.
- Bold on the second visit (Layer 2). If you opened the note because you needed it, that is a signal it is worth more investment. Bold the strongest lines.
- Highlight on the third visit (Layer 3). Only if the note keeps proving useful.
- Summarize in your own words (Layer 4). Do this when you are about to rely on the note for something real.
- Remix (Layer 5). Pull it into the work you are producing.
The logic is a trade between effort and risk. Reading, highlighting and summarizing are time-consuming but low-risk, so you can do them ahead of need. Execution and decisions are faster and riskier, so they wait until there is a concrete use. The layers are how you spend the cheap kind of effort where it is most likely to pay back.
What the numbers look like
Forte gives rough proportions in his guidelines post: about 50% of the sources you consume become Layer 1 notes, about 25% reach Layer 2, 20% reach Layer 3, 5% reach Layer 4, and less than 1% reach Layer 5. Read those as illustrations of the shape, not targets. The point is that each layer filters hard. If you are bolding and summarizing everything, you are doing something other than what the method describes.

A worked example
Say you read a long article on how remote teams make decisions.
- Day 1: you capture six paragraphs into a note, plus the link. Five minutes.
- Three weeks later: you are drafting a team proposal and search your notes. The article comes up. You bold about a dozen lines, the ones that bear on async decision-making. Ten minutes.
- Two months later: you are preparing a talk and open it again. Now you highlight the three sentences that carry the argument.
- Before the talk: you write four lines at the top in your own words: the claim, the evidence, where you disagree, and what you will do differently.
At each step you spent time because you had a reason to, and the note got faster to use. If the proposal had never happened, the note would have stayed at Layer 1 and cost you almost nothing.
Where it goes wrong
The method has real limits, and they are worth naming plainly.
Treating it as a funnel everything must pass through. Forte is explicit that not every note needs every layer: processing should go to notes with higher utility, and average notes can stay at Layer 1. Meticulous people tend to over-process, which is inefficient because most information does not need full distillation.
Confusing highlighting with understanding. Bolding a sentence feels productive. It is also easy to do while barely following the argument. The summary at Layer 4 is the real check, and if you cannot write it, you have found a gap, which is useful information. Critics of the method make a related point: it can encourage collecting and compressing in place of thinking. We think that risk is real, and it is why we would never skip the Layer 4 step on anything important.
Compressing away context. A highlighted fragment can mean something different from the passage it came from. The method's safety net is that earlier layers stay in place, so you can always step back down to the surrounding text. That only works if the source and the surrounding context remain easy to reach.
Doing it too early. Summarizing the moment you save a source means you are guessing what will matter. Waiting for a real project gives you a better filter.

How it differs from other approaches
Progressive summarization is about designing individual notes for discoverability through small bursts of compression over time. That sets it apart from tagging-first or notebook-first organization, where the effort goes into where a note lives rather than what is in it. It also differs from one-shot summarizing, where you condense a source once and discard the rest. The layered approach keeps the full text and the compressed versions together.
The two are not enemies. A light folder structure plus layered notes is a common pairing. If you want help with the organizing side, our guide to organizing notebooks in 5 to 15 minutes a week covers a routine that fits well alongside it.
Using it on articles, papers and podcasts
Students
Course readings are a natural fit, because you read far more than you will ever cite. Forte Labs documented a class where undergraduates learned the method, with the goal of making course reading notes scannable for studying and for research papers, so they could retrieve them later without digging through old class threads.
A practical student version: capture while reading, bold after the lecture that covers the reading, highlight and write a summary when exam or paper time arrives. For research papers specifically, our walkthrough on summarizing research papers in three passes applies the same just-in-time idea to dense academic text. If you work in PDFs, the PDF highlighting strategy that turns highlights into flashcards shows what to do with Layer 2 and 3 marks once you have them.
Professionals
For people curating industry insights, the payoff is retrieval under pressure. When a client question or a strategy deadline lands, you want to scan twenty notes in ten minutes and drill into the two that matter. That is what Forte calls a layered path of discoverability: scan the condensed peaks first, then go down through preserved context when a passage deserves a closer look.
Our guide to taking notes from articles so you can use them later works as a practical Layer 1 manual. And if you want the bigger system around this habit, the 30 to 60 day plan for building a second brain lays out a rollout.
Podcasts and video
The layers translate to audio and video, with one adjustment: Layer 1 is a timestamped moment or transcript passage instead of a paragraph. Capture the three moments that made you pause, and treat them like any other Layer 1 note. When you revisit, bold within the transcript excerpt and write the summary in your own words. The key is the same: keep the pointer back to the full source.
Our perspective
We build a reading environment, so we have a stake in this question, and we will be direct about it.
Progressive summarization gets one thing very right: you should not decide what matters before you know why you are reading. It gets another thing right too: earlier layers stay. Compression that destroys context is a trap, which is why we think the source should never be more than a click away from any highlight, summary or note.
Where people struggle is the step the method leaves to you. Bolding is easy. Understanding a difficult passage well enough to summarize it in your own words is hard, especially in dense papers or unfamiliar fields. A highlight on text you did not understand is a decoration, and a speedy AI summary can create the same false fluency, the feeling of having understood without the substance.
So we design for comprehension first. Notes should attach to the original passage, difficult passages should be explained where you read them, and questions should be answered with citations back to the source, so that your Layer 4 summary is built on something you actually grasped. Use layers to decide how much effort a note deserves. Use understanding to make that effort count.
— Omphalis Team
Running the method inside Omphalis
You can do progressive summarization with almost any tool, including paper. What matters is that the source, your marks and your notes stay together. In Omphalis, you save articles, papers, podcasts and videos, read them in a cleaned and structured view, and keep your notes attached to the original passages, so that a highlight reopens the passage it came from. That makes Layer 2 and Layer 3 reversible and Layer 4 honest: when you write a summary, the full text is still there to check against. When a passage is hard, you can ask for an explanation or ask a question and get an answer with citations from the source. It also imports PDFs, EPUBs, Word documents and feeds, and supports narrated listening for the times you want to hear a piece first.

There is a Free plan to try the workflow on a few sources. Paid plans are Pro at $9 per month ($90 per year), Premium at $19 per month ($190 per year) and Scholar at $39 per month ($390 per year), and they include features such as deep reading, PDF extraction, advanced listening and import and export. Details are on the pricing page. If you want to see how attaching notes to passages works before committing, start with our guide to attaching notes to quotes, or read about the digital commonplace book habit that pairs naturally with layered review.
A simple way to start this week
Do not set up a system first. Pick the five things you saved most recently and that you still care about.
- Reopen each and delete anything you would never reread.
- For the one tied to a current project, bold the key lines.
- Write two sentences at the top for that note: what it claims and why it matters to you.
- Leave the other four at Layer 1.
- Next week, repeat with whatever you actually needed.
That is it. If a note never comes up, it never costs you more. If it keeps coming up, it gets denser and more useful each time. The method rewards attention to what you actually use, and that is a better filter than any rule you could set in advance.
FAQ
What are the layers of progressive summarization?
There are five working layers above the original source, which is Layer 0. Layer 1 is the captured content, Layer 2 bolds the best passages, Layer 3 highlights the best of the bolded text, Layer 4 is an executive summary in your own words, and Layer 5 remixes the material into new work. Each layer is a smaller subset of the one before it.
Do I need to apply every layer to every note?
No. Forte's guidelines say processing should focus on notes with higher utility, and ordinary notes can stay at Layer 1. In his rough proportions, only a small share of sources ever reach Layer 4, and under 1% reach Layer 5. Over-processing is the most common mistake.
When should I do each layer?
When you revisit a note for a real reason, not at the moment you save it. A second visit might earn bolding, a third might earn highlights, and a summary comes when you are about to rely on the note. Waiting means your effort follows actual need.
Is progressive summarization the same as using an AI summarizer?
No. A one-shot summary replaces the source with a shorter version, and you may never read the original. Progressive summarization keeps every layer and the full text, and it asks you to write your own summary at Layer 4. AI can help by explaining difficult passages, but the understanding still has to be yours.
Can I use it for PDFs, podcasts and videos?
Yes. For PDFs, highlights work as Layers 2 and 3. For audio and video, capture timestamped moments or transcript passages as Layer 1 and process them the same way. What matters is keeping a link from each note back to the full source.
Sources
- Progressive Summarization: A Practical Technique for Designing Discoverable Notes, Forte Labs
- Progressive Summarization II: Examples and Metaphors, Forte Labs
- Progressive Summarization III: Guidelines and Principles, Forte Labs
- Second Brain Case Study: Teaching Progressive Summarization in an Undergraduate Classroom, Forte Labs
- Use Progressive Summarization, Every / Forte Labs