How-To Guides
How to keep a research log that actually works — practical formats and tools for knowledge workers, consultants, and researchers who want to track what they've found, what they've read, and what conclusions they've reached.
A research log is a running record of your research process: what you searched for, what you found, what you read, what you concluded, and what questions remain open. Without one, research exists only as a collection of browser bookmarks and saved articles — useful as reference, but missing the thread of inquiry that connects them.
Knowledge workers who keep a research log make better decisions, find things faster during writing, and avoid re-doing research they've already done. This guide covers how to keep a research log that works — formats, tools, and habits.
You forget what you've already investigated. In a week-long research project, it's easy to re-visit the same sources or re-ask the same questions you already worked through. A log creates continuity between research sessions.
Source piles don't explain their own significance. A folder with 40 bookmarks tells you what you found, not what you thought about it or how it connects to your question. A research log captures the interpretation alongside the source.
Research questions evolve. You start researching "what causes user churn?" and realize midway that the real question is "what predicts churn 30 days before it happens?" Without a log, the evolution of your thinking isn't visible.
Gaps aren't obvious. When you sit down to write from your research, you discover you have three sources on one aspect and none on another. A log showing what you've covered makes gaps visible.
The simplest format for a research log: a daily journal entry with four fields.
Daily research log template:
## [Date] — Research Log: [Project Name]
### What I searched / explored today
- Searched: "B2B SaaS churn predictors" on Google Scholar
- Reviewed: Tomasz Tunguz's blog posts on retention
- Found: Gainsight 2024 CS benchmark report
### Key findings
- Companies with CS-to-customer ratios above 1:10 show 15% lower churn
- Product usage metrics are stronger predictors than sentiment scores (Source: Lincoln Murphy, 2024)
- Gap: haven't found research on mid-market vs. enterprise differences
### Open questions
- Does the CS ratio effect hold for self-service SaaS?
- Is there recent data on industry-specific benchmarks?
### Next steps
- Find the Lincoln Murphy 2024 research paper cited in the Gainsight report
- Search for PLG + churn correlation
Tools for this format:
Advantage: Low friction. Works in any notes tool. The narrative format captures thinking, not just sources.
A two-part system separates the log (what you're thinking) from the library (what you've found).
Part 1 — Research log (daily): What you searched, what you found, what you concluded, what questions remain. Written in a journal format.
Part 2 — Source library (running list): Every source you've consulted, with a brief note on its relevance. Organized by topic or by date found.
Source library format (Notion database):
Connection between parts: When the log references a source ("found Lincoln Murphy's 2024 paper"), the source library entry gives its status and relevance. When you write from your research, search the source library by topic to find relevant sources.
WebSnips captures web sources to searchable collections — functioning as the source library component of a research log.
How WebSnips supports a research log:
Finding sources during writing: During the writing phase, search your WebSnips collection for the topic of the section you're writing. "What did I save about CS ratios?" → search the collection → find all relevant captures.
For longer research projects (weeks or months), a structured Notion setup handles both log and library:
Research logbook Notion structure:
Weekly review (15 minutes): Review the week's log entries. Update the findings synthesis page with new conclusions. Check the open questions list — which are answered? Which remain?
Scenario: A management consultant is researching remote work productivity for a 3-week client engagement. Needs to produce a 20-page research report.
Week 1 setup:
Daily workflow: Morning 30-min research session → log what's searched and found → capture sources to WebSnips → end of session: write 3-5 bullet conclusions in log
End of week 1 synthesis: Review 5 days of log entries. The emerging finding: "productivity measurement varies significantly by role type." This wasn't the original research question but has become a key finding. Update open questions: "Is there industry-specific productivity measurement research?"
During writing (Week 3): Search WebSnips "remote work productivity measurement" → finds 8 sources captured with that phrase. Use the source library to identify which sources to use for each section.
By project: Each research project has its own log, source library, and synthesis. Projects don't share log entries.
By date within project: Log entries are dated. This creates a timeline of the research process — useful for understanding when findings emerged and what questions were open at each stage.
Archive after project completion: After the deliverable is submitted, archive the research log (move to an "Archive" section in Notion, or tag in Obsidian). Keep accessible for the 6-12 months when questions about the research may arise.
Don't start the log mid-project. The log is most valuable for capturing the early exploratory phase — what you searched, what you found surprising, what questions emerged. Starting a log two weeks into a project means the early thinking is lost.
Don't use the log only for sources. A log that lists only "found this source, found that source" isn't a research log — it's a bibliography in progress. Include your interpretation, your emerging conclusions, and your open questions.
Don't conflate "found this" with "read this." A research log is honest: "Found this paper but haven't read it yet" is different from "Read this paper; key finding is X."
Don't skip the open questions field. The questions you can't yet answer are what shape the next research session. Without tracking them, you lose the direction.
What's the difference between a research log and notes? Notes capture what sources say. A research log captures what you think — what you're looking for, what you found, what conclusions you're forming, what gaps remain. They serve different purposes and work best together.
How long should a research log entry be? For a daily session: 150-300 words. Enough to capture the key searches, the key findings, and the current thinking — not a comprehensive summary of every source.
What if I'm doing quick research (a few hours, not a project)? For one-off research sessions, a brief log is still valuable: what you searched, the best 3 sources found, one key conclusion. Even 100 words prevents re-doing the same research later.
A research log transforms a collection of saved sources into a record of thinking. It captures the research process — what was searched, what was found, what was concluded, what remains unknown — in a way that a bookmark library never does.
For consultants, researchers, and knowledge workers who do multi-session research on complex questions, a research log is the tool that makes the difference between a pile of sources and a research-backed argument.
More WebSnips articles that pair well with this topic.
How to build a personal knowledge wiki — practical setups using Obsidian, Notion, and other tools to create a searchable, linked knowledge base that grows more useful over time.
How to build a second brain in 30 minutes — a practical quick-start for knowledge workers who want a working personal knowledge management system without spending days on setup.
How to capture ideas before you forget them — the fastest tools and habits for getting ideas out of your head and into a retrievable system the moment they occur to you.