How to organize notes by project (folders are the wrong unit)
You have an idea on the train. It concerns a client, it feeds an article you're writing, and it might become a product feature. You open your notes app, and the first thing it asks you is: which folder?
There is no right answer. That's the problem, and it isn't yours.
A folder asks you to choose a single home for a note at the exact moment you know least about what you're writing. You choose anyway, because you have to move on. Three months later you look for that note in the other two folders.
Filing is paid on the way in and only repays on the way out
This is the imbalance that eventually collapses every folder system.
Filing is real work. It requires holding the whole structure in your head, deciding where the new piece belongs, and sometimes inventing a category. That work has a cost, and you pay it on every single write.
The benefit only arrives when you go looking for something — which is far rarer, and usually weeks later.
A system that charges a lot at the entrance and refunds little at the exit always ends the same way: you stop putting things into it. Not from a lack of discipline, but from a rational trade. The note that isn't worth thirty seconds of filing never gets written — and that's nearly always the one that most needed capturing, because at the moment you have it you don't yet know what it's worth.
It's the same mechanism as quick capture on mobile: friction doesn't lower the quality of what you write down, it lowers the quantity, starting with the least-formed ideas.
A project isn't made of documents
The second flaw runs deeper, and nobody mentions it because we've all learned to live around it.
Open the folder for a real project — a site rebuild, a client, a book in progress. What would it need to contain for you to have the whole thing in front of you?
Notes, yes. But also: who's involved, what you last said to each of them, what you promised, what's still outstanding, and which decisions have already been made and when.
A folder can only hold files. Everything else lives elsewhere — people in the address book, promises in your inbox, deadlines in a task list, decisions nowhere at all. So you never actually have the project in front of you. You have its documents.
That's why preparing for a meeting takes twenty minutes even though you already hold all the information. It's complete, and scattered across four tools that don't talk to each other.
File afterwards, by reference instead of by location
The alternative is a single inversion.
Instead of deciding where the note will live, you write first and then say what it relates to. A mention is enough: the project's name, a client's name. The note stays where it landed, and it shows up on its own in every project it mentions.
Three things change, and all three matter.
One note can belong to several projects without being duplicated. The idea from the train touched a client, an article and a feature: it appears in all three, with no copy and no version that quietly drifts.
Filing becomes reversible. A badly chosen folder has to be undone by hand, file by file. A mention is corrected in a second, and nothing breaks elsewhere.
The project assembles itself. You don't have to build the structure before you have the material — the opposite of what folders demand, and the only order that matches how a project actually appears: scattered fragments first, then one day the realization that they form a whole.
Organizing stops being a blind decision made at the start and becomes an observation made at the end.
What a project page has to pull together
The test is simple. Open a project page and ask whether you could walk into a meeting with only that on screen. It takes four things.
The notes that mention it, in chronological order. The order matters: it's what lets you see a position shift over time, which no single note ever shows.
The people involved, with direct access to each one's history. Most projects are relationships first; treating them as documents loses the part where the work actually happens.
Open commitments, including what you promised someone out loud. A promise made in a meeting is a task belonging to that project, not a stray line in a general list.
Decisions, dated. Together with what you knew when you made them — the first thing to disappear, and the thing you most regret not having.
If those four live in four tools, the project exists nowhere. It exists only in your head, rebuilt from scratch each time, with whatever gaps that implies.
When a folder is still the right tool
In fairness: folders aren't a bad idea. They're excellent at what they're actually for.
If your items are large binary files — photos, exports, signed contracts, deliverables — a folder is the right answer. A binary has a location, and it belongs in exactly one place.
If your structure is stable and known in advance — accounts by year, invoices by client — a hierarchy costs you nothing, because no decision is required on each addition.
Folders break on one specific case: ideas still taking shape, which belong to several things at once and whose destination you don't yet know. Which is to say, precisely the material you generate all day.
Where to start
Don't set out to refile what you already have. That's several hours of work for an improvement you won't feel.
Take the project you're working on this week. Give it a page, named the way you'd say it out loud. Then, for five days, simply mention it in whatever you write as you go — moving nothing, reorganizing nothing.
On Friday, open the page. You'll find the project's week already assembled, with the people and the deadlines sitting alongside the notes. That's the difference between a folder and a project, and five days demonstrate it better than any argument.
In Keepsake, mentioning #project name# in a note, a task or an entry is enough: the project page gathers the notes, contacts, tasks and timeline on its own. Try it free for 30 days →