Most people’s notes fail in one of two ways. Either everything goes into one giant document (or one app) that becomes impossible to search, or everything gets attached to tasks and disappears the moment the task is ticked off. Both come from the same assumption: that every note should have the same kind of home.
The four homes for a note
| Home | What goes there | How long it matters |
|---|---|---|
| A task | Details, links, acceptance criteria, the next step | Until the task is done |
| A project | The brief, decisions and why, where you left off, loose ideas | As long as the project lives |
| A day | What happened, meeting notes, thoughts, things to follow up | Mostly that day, found again by date |
| Nothing (yet) | Ideas, lists, references, anything without a project | Indefinitely, organized in folders |
Task notes: the details of one thing
A task note answers “what exactly do I need to do here?” The link to the document, the three points the client raised, the command that reproduces the bug. It’s short-lived on purpose: once the task is done, you rarely need it again.
Project notes: context that outlives tasks
The most valuable notes are often the ones that don’t belong to any task: why you chose this approach, what the client said in the kickoff, what you tried that didn’t work. Attach those to a task and they vanish when it’s done. Put them on the project and they’re there every time you come back to it. A running “where I left off” line at the bottom is especially useful if you juggle several projects at once.
Day notes: what happened
Some notes are about a day more than about any piece of work: the meeting that changed the plan, a thought on the walk home, a follow-up for tomorrow. Day notes are where those go, and the date is all the organization they need. (A day note isn’t quite a journal. If you want the reflective version, see the end-of-day journal.)
Standalone notes: not everything has a home yet
A reading list. A half-formed product idea. Your packing list. These don’t belong to a task, a project, or a day, and forcing them into one just makes them harder to find. Give them folders of their own.
One rule: where will I look for this?
You don’t need a filing system to decide. Ask one question as you write: next time I need this, where will I be looking? If the answer is “when I’m doing that task,” it’s a task note. “When I come back to this project” makes it a project note. “When I think back to Tuesday,” a day note. “No idea yet” means a standalone note, and that’s a perfectly good answer.
Notes move as they grow
Notes aren’t fixed in place. A common life cycle: an idea starts as a standalone note, grows into something worth pursuing, becomes the first note on a new project, and eventually spawns concrete tasks with notes of their own. Letting notes start loose, without a project or a task, is what makes that possible. Insisting on structure up front tends to kill ideas before they’re ready.
How Zympl handles it
In Zympl, every task, project, habit, and day can carry its own markdown note, and the Notes tab holds your standalone notes in folders and sub-folders. Smart folders then gather every attached note into one place (task notes, habit notes, project notes, day notes), so a note written in passing on a Tuesday never stays buried there. It’s the same idea behind Zympl’s timers: not everything has to be a task, and a note should live wherever it actually belongs.