An article you might need for a future project. A restaurant someone recommended. A tool to evaluate ‘when things calm down.’ These items have no deadline and no project, which is exactly why task lists and folders both mishandle them: the task list turns them into guilt, and the folder turns them into archaeology.
Someday items are not tasks
Giving a saved article a fake due date does not make it urgent; it makes your task list lying. Snoozing ‘read this’ for the ninth time trains you to ignore the list—including the parts of it that are real. A saved item is not a commitment, and storing it as one poisons the actual commitments.
Folders demand a prophecy
Filing requires predicting the future retrieval context: does the design teardown go under ‘Marketing,’ ‘Inspiration,’ or ‘Competitors’? Months later you will search by situation—‘we are rebuilding onboarding’—not by whichever taxonomy you guessed on a Tuesday.
Save the trigger, not just the thing
Add one sentence about the future situation in which this becomes relevant:
- ‘If we ever rebuild the onboarding flow, this teardown is the benchmark.’
- ‘Restaurant for when Marta visits—she loved the Georgian place.’
- ‘Candidate tool if the export script breaks again.’
Let the moment find the item
When the situation arrives, you will search with the words of the situation—and semantic retrieval matches them against your trigger sentence, not against a folder name. Discovery replaces filing memory: the item resurfaces because its stated purpose finally came true.
How to write a trigger sentence
The trigger is a conditional, and the grammar matters more than the length. Start with ‘if’ or ‘when’ and describe the future situation in the words you would use while inside it—not the words you are using now, while cataloguing.
‘Useful article about pricing’ is a description and will not be searched for. ‘If we ever revisit usage-based pricing, this is the teardown to read first’ names a situation, and the situation is what you will type when it arrives. The difference is that the first sentence describes the item and the second describes you.
One additional habit pays for itself: name the person or project if either is involved. ‘When Marta visits’, ‘if the export script breaks again’, ‘for the onboarding rebuild’—each of those is an anchor that pins the item to something concrete enough to search against months later.
The honest limit: most of it will never come back
This method improves the odds; it does not make someday items reliable. The large majority of what anyone saves for later is never retrieved, and the reason is usually that the anticipated situation simply never arrived—not that retrieval failed.
That is worth accepting rather than engineering around, because the alternative is a periodic review of a someday pile, which is a chore nobody sustains and which mostly reconfirms that you still might want these things. The saving is cheap; the reviewing is what costs, and it is the part with the worst return.
This method cannot prevent every failure: you still have to recognize the situation when it arrives. Semantic search can match your trigger sentence only if it occurs to you to ask. Treat someday saving as low-cost insurance: spend three seconds, expect a modest return, and appreciate the occasions when your past self left something useful where you would later look.
Save someday items together with the situation that will make them relevant—not with a fake deadline or a guessed folder. When that situation arrives, search by meaning will hold up its end.