Monthly expiration sweep
Conduct monthly expiration sweeps reviewing all items whose expiration dates have passed and either archive/delete if expired or renew with new expiration date if still relevant.
Why This Is a Rule
Expiration dates (Tag time-sensitive information with explicit expiration…) are only useful if someone checks them. Without a regular sweep, expired items accumulate silently — the expiration metadata exists but nobody reads it, and the system gradually fills with items that are flagged as expired but still present and retrievable. The expiration system has the data; the sweep is the process that acts on it.
Monthly sweeps balance thoroughness against overhead. Weekly sweeps would catch expired items faster but create excessive maintenance burden. Quarterly sweeps would miss items that expired 2 months ago and were used as if current during that window. Monthly hits the sweet spot: items are caught within one month of expiration, limiting the stale-information exposure window while requiring only 15-20 minutes of review per month.
The binary decision at each item — archive/delete (genuinely expired) or renew (still valid, set new expiration) — prevents the "review without action" failure where you look at expired items, think "I should deal with this," and move on. Every item must leave the expired state in one of two directions: out of the system or renewed with a fresh date.
When This Fires
- On a scheduled monthly cadence (first Monday of the month, or similar recurring slot)
- When your reference system feels cluttered and you suspect stale items
- When you retrieve an item and discover it's outdated — sign that sweeps aren't frequent enough
- Complements Tag time-sensitive information with explicit expiration… (assign expiration) and When uncertain about lifespan, expire at 3 months not 1… (conservative defaults) as the maintenance loop
Common Failure Mode
Sweep without action: reviewing expired items but deferring the archive/renew decision. "I'll deal with these later." The items remain expired but present, and next month's sweep finds the same items plus new expirations. The backlog grows until the sweep feels overwhelming and gets skipped entirely.
The Protocol
(1) Schedule a recurring monthly reminder: "Expiration sweep — 15 minutes." (2) Search your system for all items with expiration dates that have passed. (3) For each expired item, make one of two decisions: Archive/Delete — the information is genuinely outdated. Remove from active system. Renew — the information is still valid. Set a new expiration date (When uncertain about lifespan, expire at 3 months not 1…'s 3-month default if uncertain). (4) Do not skip items or defer decisions. Each item must exit the expired state during this sweep. (5) Track sweep metrics: how many items expired vs. renewed? If most items are renewed, your expiration defaults may be too aggressive — extend them. If most are archived, your defaults are well-calibrated.