Note-taking method
Best Progressive Summarization for Journalists
Layer summaries on top of captured content as you revisit it. For journalists, the working week is interview transcripts, source contacts, and story threads that don't connect. The rest of this page is the method, cut for that week.
By tentus team · Updated 2026-09-20
What Progressive Summarization actually asks of you
You don't summarize everything once; you summarize a little more each time you return to a source.
First pass: highlight. Second pass: bold the highlights. Third: a short summary at the top. Most sources never earn the second pass — that is the method working, not failing.
How journalists put it to work
- 1
Sources and what they said, linked
Every contact's statements are captured as quotes with the conversation they came from. When a story breaks open, what each person said — and when — is a search, not a shoebox.
- 2
Story threads that accumulate
Angle ideas capture as they occur, linked to the evidence that supports them as it arrives. The piece you write in March was mostly gathered in January.
- 3
Chronology on demand
Events, statements, and documents captured with their dates reconstruct into a timeline. In reporting, the order things happened in is often the story.
The capture habit, the linking, and the retrieval are the parts tentus automates — progressive summarization without the daily upkeep.
Try it with tentus
tentus makes Progressive Summarization practical for journalists. Capture, link, and retrieve without the busywork.
Other methods worth trying
Progressive Summarization for other roles
Product Managers
juggling research, specs, stakeholder feedback, and launch plans across multiple tools.
Software Engineers
losing context between code reviews, incident postmortems, and technical research.
Designers
scattered moodboards, design critiques, and research that never gets referenced again.
Researchers
drowning in PDFs and citations with no way to connect findings across projects.