Use cases
Research Log — where it earns its place
On Research Log —
The perfect source, found at midnight in the fourteenth open tab, is gone by morning. Research Log is the habit that saves you: a running record of what you looked into, what you found, and where it lives, kept as you go rather than reconstructed in a panic. Future-you, writing the thing up, will be quietly grateful. On this page: three concrete ways someone whose thinking has begun to accumulate reaches for the Research Log, and the signals that tell you it fits.
When the Research Log earns its place
As a tracker, the Research Log keeps everything it needs to keep the picture honest — no more, no less — so the record is small enough to actually read back.
Most tools in this category — Notion, Obsidian sync, second-brain SaaS with monthly tiers — solve a version of the same problem, then bill you monthly for the privilege of remembering it. The Research Log takes the opposite bargain: one file, once, kept.
Three scenarios drawn from study, academic, and curious
The everyday one: you open the Research Log on a Tuesday morning, log what needs logging, and close it. Two minutes. The record is more honest than the app that pinged you to remind you.
The specific one: — the workflow it names is the record that most needs a home outside a subscription. Some people use only the Research Log. Some fold it into a Swiss Knife next to five others. Both are correct.
The out-of-band one: months later, you want to look back. The Research Log still opens because it is a file. There is no login lapsed, no export deadline missed. The record is where you left it.
Signals it fits someone whose thinking has begun to accumulate
You want a knowledge surface that behaves like a document, not a service. You are comfortable typing your own numbers in. You would rather own the file than rent the log. Weight in the knife: 1. Manual: no manual — the tool is its own instructions.
Signals it fits
- You do this kind of record-keeping more than onceThe Research Log pays back every time you don't have to reinvent the shape.
- You want it offline, on your own machineNo account, no cloud, no vendor between you and the record.
- You're comfortable with a hand-kept fileThe Research Log is a document. It behaves like one.
Questions people ask
What goes into a Research Log?
Whatever your digging turns up: the questions you chased, the sources you found, the notes on what they said. The discipline is writing it down at the moment of finding, and the log makes that easy.
Is this a full replacement for Notion?
For the working core of what most people use it for — yes. For enterprise features (team seats, integrations, auto-import), no. The Research Log is deliberately smaller and more honest about its scope.
Who is the Research Log not for?
Someone whose thinking has begun to accumulate's opposite: a team that needs shared cloud state, or someone who wants automation over ownership. Use a SaaS for that; use this for the file.
A knowledge surface that opens where you left it, on the machine you left it on.