Systems fail in the second year
The first month of a new note application is pleasant. You make a few folders with promising names, write a dozen notes, and everything is where you expect because you remember writing it.
Six months later the folders contain a mixture of things that no longer share anything in common, and you cannot remember which one you filed something under. A year later you search for a phrase you are certain you wrote, and it does not come up, because you wrote it in a different wording.
None of this is a failure of discipline. It is what happens when a structure is designed for a person who knows everything inside it, and then handed to a person who does not.
Start with an inbox, and mean it
The single most useful piece of structure is a place where notes land before anyone decides anything about them. Call it an inbox, a dump, or untitled — the name does not matter. What matters is that capturing never requires a decision.
Every filing decision made at capture time is a decision made with the least information you will ever have. You do not yet know what the note is for. Forcing a folder choice at that moment produces a folder system built out of guesses that harden into habits.
The inbox only works if it actually gets emptied. An inbox nobody processes becomes a second archive with worse organisation than the first.
Name the claim, not the topic
Most notes are named after their subject: Pricing, Meeting notes, Ideas. A year later those titles are useless, because you do not search for a subject — you search for something you concluded.
A name that states a claim is easier to find and easier to judge. Compare:
- Pricing — will contain the pricing discussion, somewhere.
- Annual pricing loses to monthly in small teams — a position you can search for, disagree with, or act on.
The second requires you to know what you think the moment you write it, which is a feature. If you cannot state the claim, the note is not ready to leave the inbox.
The test that keeps titles honest
Read the title alone. If it could describe any of a hundred other notes, rename it. A title is not a label on a drawer; it is the first sentence of the note's use.
One note per idea, not per source
Filing by source feels natural — one note per article, one per meeting, one per book. It mirrors how the information arrived, which is the only thing that stops mattering over time.
When you return to an article note a year later, you find six unrelated ideas stacked together, and the one you needed is buried in the fifth paragraph. Splitting them costs an extra minute at the time and saves the search later.
The exception is genuinely chronological material: a log of what happened, a diagnosis trail, a record of a decision. Those belong together because their value is the sequence.
Search beats folders, if you feed it
Folders answer the question "where did I put this", which is a question about your past behaviour. Search answers "what did I write about this", which is the question you actually have.
Search only works if the text survives into the note. A screenshot of a paragraph cannot be searched. An image of a whiteboard cannot be searched. A link to an article cannot be searched — only the parts of it you copied can be.
This is the quiet argument for keeping text as text. Every note stored as an image is a note you can only find by remembering when you saved it.
Practical test: search your archive for a phrase you know you saved. If it cannot be found, the archive has an image or link problem, not a folder problem.
Deleting is maintenance
An archive nobody deletes from does not stay the same size — it grows faster than its usefulness. Notes that no longer matter make the ones that do harder to find, and they make every search result slightly worse.
The instinct against deleting is the fear of losing something. But a note you cannot find has already been lost; deleting it only removes the pretence. The real loss happens earlier, when it was written down and never turned into anything.
A useful rule: if you would not use it in the next six months, and it is not a record you are required to keep, it can go.
The monthly pass
Once a month, open only the inbox and the notes you touched in the last thirty days. For each one, make one of three decisions:
- Give it a claim. Rename it to state what it says, then file it.
- Merge it. If it says the same thing as something older, combine them and delete the weaker one.
- Delete it. No hesitation, no "maybe later".
Thirty minutes a month is enough for most people. The point is not tidiness; it is that the archive keeps answering the question it exists to answer.
What to do when it breaks anyway
It will break. You will skip two months, the inbox will reach four hundred notes, and the thought of processing it will be unpleasant enough that you skip a third.
The repair that works is not a reorganisation. Reorganising four hundred notes is the same decision repeated four hundred times, and it fails for the same reason the original structure failed. The repair is to declare the old inbox an archive, leave it untouched, and start a new one. Nothing is lost; the old material is still searchable, and it is no longer blocking the next note you want to write.
A system you can abandon once a year and restart in an afternoon is more durable than one that demands perfect maintenance forever.
Where Papscroll fits
Papscroll keeps notes as plain Markdown text, so the things this guide depends on stay true: text is searchable, titles are yours to change, and nothing is locked into a format that stops being readable. Notes sync across the Android app, the web app, and the browser extension, and each note keeps the source it came from attached.
None of that is a system on its own. The inbox, the claim-shaped titles, and the monthly pass are decisions you make — the tool only has to not get in the way of them.