Notes

How to organize notes so you can find them again

By Interval · 13 min read

In this article

You know you wrote it down. The address, the decision, the idea that finally made sense. Unfortunately, you also have a note called “Ideas”, another called “Ideas new”, and a screenshot of something that might contain the answer.

Organizing notes gets easier when you stop asking where every note belongs and start asking how you'll find it again. A useful title, a little context, and a clear distinction between information and action can do more than an elaborate folder tree.

A stack of notebooks and a pen beside a white keyboard
Photo by Marissa Grootes on Unsplash · License

This guide gives you a practical system for personal and work notes: one place to capture, a few recognizable homes, titles you can search, and a small amount of maintenance. You'll also find examples of renamed notes, a meeting-note structure, and a way to clean up an existing collection without starting over.

Start with the job the note needs to do

Not every note needs the same structure. A shopping idea, a project decision, and a set of instructions serve different purposes. Treating them all as miniature documents can make taking notes feel like paperwork.

Before organizing a note, ask what future-you will need from it. Is it something to remember, something to understand, something to use again, or something that should become an action? The answer tells you what information needs to stay visible.

A restaurant note might need the name, area, and why you saved it. A project note might need the decision, the reason, and the next step. A recipe needs ingredients and instructions. None of those automatically benefits from a dozen tags.

If a note contains a task, separate the action from the surrounding information. “Ask Sam which version is approved” belongs on your task list. The comparison between versions belongs in the note. You can keep them connected without relying on the note to remind you at the right moment.

This distinction is especially useful for meeting notes. A page can be beautifully organized and still fail you if the one promise you made stays buried in the fourth paragraph.

Getting Things Done separates reference material from actionable items. That distinction helps when a meeting note contains both background information and a promise you need to keep.

Choose one reliable place for new notes

You don't have to move every existing note into one app today. Start by deciding where new, unclassified information lands. This is your capture place, not necessarily its permanent home.

Choose somewhere you can reach in the situations where ideas actually appear. If you usually remember things while walking, a notebook left at your desk won't solve that problem. If your workplace restricts personal apps, your work capture place may need to stay separate.

Keep the capture step light. Write the useful detail, add a recognizable title if it's easy, and return to what you were doing. A system that requires choosing a folder, three tags, and a template before saving a thought creates friction at exactly the wrong moment.

Give the capture place a review point. That might be the end of a work session or part of a weekly review. Without a review, an inbox can become another permanent pile, just with a more reassuring name.

During the review, decide whether each item is useful reference, an active project note, a task, or something you can delete. You aren't obliged to preserve every thought. Capture can be generous while keeping can be selective.

If the collection is a mix of ideas, worries, and unfinished tasks, use a brain dump before deciding which entries need permanent notes.

Use a small number of homes

Start with categories you already understand. Work, Home, Personal projects, and Reference may be enough. Someone else might prefer individual active projects plus a single archive. There isn't a universally correct folder system.

A good folder answers a question you'd naturally ask later. “Where did I put the information about the move?” is more useful than “Was that an Inspiration item or a Knowledge item?” If two categories repeatedly feel interchangeable, combine them or define a clearer boundary.

Avoid making a folder for every note. A folder becomes useful when several related notes need to be found together. Until then, a clear title may do the job with less maintenance.

Keep active work easy to reach. You can archive completed projects without deleting the information, leaving the current view less crowded. The archive doesn't need to be beautifully arranged if search and recognizable titles make it usable.

Sensitive information deserves a separate decision. Don't place passwords, identity documents, private client information, or medical records into a general notes collection simply because it's convenient. Check the storage and access requirements for the information you're keeping, especially at work.

Write titles for the person who will search later

A title should contain the words you'll probably remember. That often means a person, project, place, topic, or decision, rather than a clever label. “Kitchen measurements for new shelves” is easier to retrieve than “Home thoughts”.

Include a date when time is part of the meaning. A meeting, appointment, or version-specific decision often benefits from one. A general list of packing essentials probably doesn't need the day you first wrote it in the title.

Put the distinctive words early. “Lisbon: places to eat near the station” gives you a useful topic before the details. “Some ideas about where we might eat during the trip” makes the same information harder to scan.

The Nielsen Norman Group's explanation of recognition and recall describes why visible cues can make information easier to identify than asking people to remember it unaided. For notes, recognizable titles and short summaries are a practical application of that design principle, not a guarantee that any folder system will work for everyone.

Use your own language. If you always think “taxes”, putting everything under “annual financial compliance” adds a translation step. Search works best when the words you save overlap with the words you'll later try.

Eight vague notes, rewritten so you can find them

You can improve an existing collection without rewriting the body of every note. Start with titles that hide the topic, then add one sentence of context where necessary.

  • “Ideas” becomes “Balcony garden: plants that tolerate shade”.
  • “Meeting” becomes “Website review: decisions and next steps, 12 November”.
  • “Stuff to buy” becomes “Moving day: supplies still needed”.
  • “New project” becomes “Family recipe book: sections and photo ideas”.
  • “Links” becomes “Beginner swimming lessons near work”.
  • “Important” becomes “Insurance renewal: questions to ask before Tuesday”.
  • “Notes from Sam” becomes “Kitchen shelves: Sam's measurements and materials”.
  • “Things to remember” becomes “Cat sitter: feeding, medication instructions, and contacts”.

Notice that these titles don't all follow a rigid formula. They share a purpose: identify the subject and why the note exists. A date appears where it helps distinguish one meeting from another.

Don't add details you don't actually know. If you're unsure whether measurements are current, say so inside the note. A confident-looking title attached to outdated information can be more troublesome than a messy but honest page.

Once you've renamed a few notes, try searching for them as you normally would. If you still can't find one, add the missing word or context. That small retrieval test tells you more than whether the folder tree looks tidy.

Keep the important part near the top

Long notes are easier to use when the first few lines explain what they're for. You don't need an executive summary for a grocery list, but a project note benefits from a short orientation.

Try opening with the current decision, status, or question. For example: “We're choosing between the two smaller tables. Check whether either fits through the stairwell before ordering”. The measurements and links can sit underneath.

Use headings when a note contains different kinds of information. Decisions, Questions, Next steps, and Reference are often enough. The headings should help you jump to something, not decorate every few sentences.

Break up paragraphs when the topic changes. A note written in a rush can be cleaned up later by separating decisions from background, rather than rewriting every sentence. Preserve useful context while making the action easier to see.

If a note keeps growing, consider whether part of it deserves its own page. A project overview can link to separate research, meeting notes, and instructions. Splitting is useful when it improves retrieval, not simply because a page has reached an arbitrary length.

For notes you need to learn from, Cornell's note-taking resources offer a different kind of structure. Study notes and a quick record of a decision don't always need the same format.

A meeting-note structure that keeps decisions visible

Start with the meeting's purpose and date. Add participants if knowing who was involved will matter later. Then use three sections: Decisions, Actions, and Context.

Under Decisions, record what was agreed and any condition that could change it. “Use the shorter homepage draft, pending legal review” is more accurate than “Homepage approved”. The condition matters when someone later asks whether they can publish it.

Under Actions, name the work and its owner. “Jamie to send the final images by Thursday” gives more information than “Images”. If there isn't an agreed date, don't invent one just to fill a field. Record that the timing still needs confirming.

Under Context, keep the reasoning, alternatives, and links that would help someone understand the decision. You don't need a transcript unless there's a specific reason to preserve one. A useful record is often shorter than the conversation that produced it.

After the meeting, move your own actions into your task list and link back to the note where appropriate. This is the bridge between remembering a discussion and actually following through on it.

A note can also hold your place in unfinished work. These restart-note examples show the small amount of context that can help after an interruption.

Organize project notes around the current question

A project can collect a lot of material before its next step becomes clear. Research, drafts, screenshots, and half-formed ideas all look relevant while you're collecting them. Later, the pile can obscure the decision you were trying to make.

Create a simple project overview that answers: what are we trying to do, what have we decided, what's still open, and what's next? Link supporting notes underneath those answers. This gives the collection a front door.

For a kitchen refresh, the overview might say the budget is fixed, painting is decided, lighting is unresolved, and the next step is checking the electrician's availability. Inspiration images remain useful, but they no longer have to carry the whole project.

Mark outdated decisions clearly. If you change direction, add a brief update explaining what replaced the old choice. You don't have to delete the history, especially if the reason could matter later. You do need to prevent an old plan from looking current.

When the project ends, write a short closing note if there's knowledge worth keeping. Include what was completed, where the final files live, and anything you'd do differently next time. Then archive the active material so it stops competing with current work.

How to clean up years of messy notes

Don't start by opening the oldest note and working forward. Begin with what you're using now. Identify active projects, important reference information, and the notes you've searched for recently. Improving those gives you an immediate return.

Create a temporary archive for material you aren't ready to sort. This is a way to reduce visual clutter while preserving information, not a declaration that every old note is valuable. Give the archive a clear name so you remember what it contains.

Work in small, topic-based passes. You might sort travel notes one day, then old work notes another. A topic gives you context for deciding what belongs together and what duplicates something you already have.

For duplicates, keep the most useful version and bring over any missing information. Be careful with dates, attachments, and shared links. Two notes with similar titles may record different decisions, so don't delete them solely because they look alike.

Stop when the collection is usable. You don't need to achieve a completely empty inbox or perfectly categorized archive before your notes can help you. The practical test is whether you can capture new information and retrieve the important old information without excessive searching.

A retrieval test for your note system

Choose three notes you expect to need again. Close them, wait until you're doing something else, then try finding them using the title, folder, or search words that come naturally to you. Notice where you hesitate.

If you remember the person but the note only contains a project code, add the person's name where appropriate. If you remember the decision but not the meeting date, put a brief decision summary near the top. Adapt the note to how you look for it.

If a search returns too many similar results, improve the distinctive details. A location, project name, or purpose can narrow the field. Avoid adding dozens of speculative keywords that make the note less readable.

If you repeatedly look in the wrong folder, reconsider the folder choice. A system isn't successful because you can explain its logic while looking at it. It needs to make sense when you're tired, distracted, or returning after several weeks.

Repeat this test after making changes. You may discover that three renamed notes solve the problem, while a full reorganization would have cost an afternoon. Let actual retrieval problems guide the maintenance.

Keep the system useful with a small review

During a weekly review, look at recently captured notes and active project pages. Move obvious tasks to your task list, add missing context, and archive material that's no longer active. Leave settled reference notes alone unless something changes.

Watch for notes that have become holding pens for unrelated ideas. Split them only when the mixture makes them hard to use. A broad “Things to try” list can be perfectly useful if you know that's where casual ideas live.

Review shared notes with extra care. Check that the content is appropriate to share and that the link points to the version you intend. Avoid treating a public link as a private filing tool. Sharing is a separate decision from organizing.

If maintaining the system starts taking more effort than finding information, simplify it. Remove a category, stop using a tag that adds no value, or shorten a template. Organization should reduce the work around your notes.

Our weekly review checklist includes a place for loose information without making note sorting the whole event. You can use that small review point instead of continually reorganizing while you're supposed to be doing something else.

Questions about organizing notes

Are folders or tags better?

Folders give notes a visible home. Tags can connect notes across topics. Neither is automatically better, and using both isn't automatically more organized. Start with the simpler approach that answers your real retrieval needs.

If a note belongs to one active project, a folder may be enough. If you often need to find material that crosses several projects, tags may help where your chosen tool supports them. Don't add a tagging routine just because the option exists.

Should I keep tasks inside notes?

Keep supporting information in notes, but make time-sensitive actions visible in the place you check for work. A task buried in a long note depends on you remembering to open that note at the right time.

For example, keep the research about a purchase in a note and put “Choose between the two shortlisted options” on your task list. The note provides context; the task provides a visible next step.

Do I need to rewrite rough notes?

Only when the roughness prevents you from using them. Add a title, a date, or a sentence explaining an abbreviation before deciding to rewrite the whole page. Notes don't need to read like published articles.

The useful standard is whether future-you can understand what matters. A short, imperfect note that leads you to the right decision is doing its job.

How can I start without moving everything?

Choose a capture place for new notes and improve the active notes you already use. Leave the old collection where it is while you decide what is worth bringing over. A gradual change gives you a chance to test the system before committing to a migration.

In Interval, you can keep standalone ideas in Notes, organize related notes into folders, and keep task-specific context with the task. Start with one note you want to find again. Give it a clear title and a useful first line. That's enough to begin.

Sources and further reading

Get it out and get on

Because planning shouldleave you with moreheadspace, not less.