Months after a project ends, you may remember “the red sign-off sheet,” a client's old abbreviation, or the season the work ended. A title like “Meeting notes 4” leaves you with few of those clues. Search for the decision using those words while keeping the project folder closed.
Take six notes from a closed project. Pick a decision, the final deliverable and a useful failure record among them. Write down two likely search phrases for each item before opening the notes. Ask a colleague familiar with the project for a phrase if they are likely to use a different name for it.
Start with a search that can fail
In Obsidian Search, quoted phrases and content, filename and path operators let you check where a clue would need to appear. Try the phrase by itself, then narrow to the project folder. A query like path:"Projects/Lantern" "external review" is useful only if you can remember that folder name. Try the name that was used in chat and the older client abbreviation without the path to see whether the note turns up.
For each missing result, note why the word was absent or buried. A decision might use a formal project name that nobody remembers. A template might have repeated the phrase in ten irrelevant notes. Slipping one exact phrase into the relevant paragraph can do more than adding the same new tag to every note.
Give each clue a home
Put a subject or result in the title, such as “Lantern sign-off for print proofs.” Keep alternate spellings and names near the beginning of the note or as properties where your search tool indexes them. One or two purposeful tags, such as #decision and #handoff, work across projects. Use a stable link from a project summary to a record with the supporting details. Obsidian's internal link guide explains how a link can have display text separate from the destination.
Record the rank of the intended note on the first page of results. A search returning 30 notes has different value if the decision is second instead of twenty-ninth. Keep terms that move the right item up without creating a flood of matches.
Search by the thing you remember
Suppose a report from a closed project is filed under the client's current name, Merrow. People on the project still call the work Lantern. You remember that the decision affected the red sign-off sheet. Start with that phrase and record which file you expect to find. Then try “Lantern” alone. If the first search misses and the second finds only old draft notes, open the accepted decision and look at the words an unfamiliar reader would see.
The result might be titled “Review 4” and refer to the sheet by an internal document number. Change the title to name what the meeting approved. Add a short sentence explaining that the decision covered the red sign-off sheet used in Lantern. Include the old file number if it will help someone find the attachment. Keep the context in the document where a reader can recognise the result once it appears, even if they never read the project summary.
If many notes match the same phrase, check one or two hits to find out why. A repeated footer or template can drown a distinctive clue. If half the notes say “external review” in a fixed heading, add a narrower phrase to the actual decision and try both terms together. Removing every repeated heading can make notes harder to scan. Fix the place where a reader expects to find the answer first.
Measure the searches you can rerun
Make a log with the remembered phrase, the expected file, the first matching position, and the next useful clue. For an old project with dozens of notes, try a first pass without a date or path. Then repeat with the detail you really knew, such as the month of the external review. Leave “not found” in the log when the note is missing. A blank line tells the next reader little about whether that search was ever performed.
| Result from a six-note trial | Smallest fix to try |
|---|---|
| The client's old nickname finds only draft notes | Include the nickname once in the accepted decision or in the linked summary. |
| The decision is in the results but hard to recognise | Give it a title that names the decision and use that label in the summary link. |
| The file appears only when you search by its exact folder | Add the phrase a colleague used in the project log to the note itself. |
| A link opens a second note with the same title | Point the link at the intended file and check its heading and attachment. |
Read the changes through the eyes of someone who joined the team late. Ask which version they would trust and how they would tell. A note called “Client review, red sheet” may still look like a draft if its first paragraph says nothing about the outcome or owner. Add the date and name the record that prompted it. Keep a stable summary page with links to decisions that have been replaced so an old date remains intelligible.
Distinguish a missing clue from a moved file
If a note used to turn up under a specific path and now none of the searches find it, open the app's excluded-file settings. Obsidian's search help describes how excluded files are omitted and how operators can search filenames and paths. Confirm the file is still inside the vault and not solely in an archive the app cannot see. A deliberate move out of the searchable vault requires an index or another place to look.
Once the right note appears, use a link from the main project record to check the destination as well as the search result. Open any supporting evidence you expect to find. If folders moved after completion, use the linked-note rename test to examine the broken reference. Keep the log with the approved project material, so it can be repeated by the next person who cannot remember what the decision was called.



