Tag time-sensitive information with explicit expiration…
Assign explicit expiration dates to time-sensitive information at the moment of capture using the format 'expires:YYYY-MM-DD' or equivalent, rather than attempting to remember which items are time-bound.
When This Fires
- When saving any information that has a known or estimated shelf life
- When your reference system contains a mix of current and outdated information
- When you've acted on stale information because it wasn't marked as time-sensitive
- Complements Title reference items with the words your future self… (search-oriented naming) with the temporal dimension of reference management
Common Failure Mode
Undifferentiated storage: all reference items treated as equally valid regardless of age. A system with 1,000 reference items where 200 are expired but unmarked means 20% of your retrievals return outdated information. Without expiration metadata, you can't distinguish current from stale without manually checking each item.
The Protocol
(1) At the moment of capturing time-sensitive information, assess its lifespan: "How long will this remain valid?" (2) Add an explicit expiration tag: expires:YYYY-MM-DD. Use whatever format your system supports — the key is that it's searchable and filterable. (3) Common expiration heuristics: Pricing/quotes → expire at the stated validity date or 90 days. Meeting decisions → expire at the next relevant meeting or review cycle. Technical references → expire at the next version release. Regulatory/policy → expire at the next annual review date. (4) Set a monthly or quarterly reminder to search for expires: dates that have passed. Review expired items: delete, archive, or update with current information. (5) When uncertain about lifespan, err toward shorter expiration (When uncertain about lifespan, expire at 3 months not 1…) — it's easier to renew a still-valid item than to catch a silently expired one.