Route actionable items to your task system and reference…

Why This Is a Rule

Actionable items and reference items have opposite access patterns and opposite failure modes when stored together. Actionable items need to be visible, time-sensitive, and easy to scan quickly ("What do I need to do?"). They're consumed by being completed and then archived or deleted. Reference items need to be searchable, persistent, and out of the way until needed ("Where's that document?"). They're consumed by being looked up, used, and put back.

When actionable and reference items occupy the same space, both fail: tasks get buried under reference items and are missed ("I forgot to call Sarah because the task was hidden among 50 bookmarked articles"). Reference items get lost in a sea of completed/stale tasks and can't be found ("I know I saved that article somewhere in my task list"). The mixed system serves neither function because it's optimized for neither access pattern.

This is David Allen's GTD insight operationalized as a routing rule: during processing (Process inboxes sequentially top-to-bottom, never…), every item must be classified as actionable or reference, and each classification determines the destination system. The classification is binary and should be made immediately during processing, not deferred.

When This Fires

• During inbox processing (Process inboxes sequentially top-to-bottom, never…) when deciding where each item goes
• When your task system is cluttered with non-actionable reference items
• When your reference system contains stale to-do items you keep stumbling over
• Complements Separate reference material (static lookup) from working… (reference vs. working notes) with the parallel actionable vs. reference routing

Common Failure Mode

The overloaded task list: mixing "Buy groceries" (actionable) with "Tax deadline reference sheet" (reference) with "Interesting article about productivity" (reference). The task list grows to 200+ items, most of which aren't tasks at all, and you can't see the actual actions through the noise.

The Protocol

(1) During inbox processing, classify each item: "Does this require action from me, or is it information for future reference?" (2) Actionable → route to your task management system (to-do app, project board, action list). Capture with a specific next action (Capture actions as specific next physical steps…). (3) Reference → route to your reference system (notes app, file system, bookmarks). Title for future search (Title reference items with the words your future self…). (4) If an item is both (an email containing a task and useful reference information) → split it: action goes to task system, reference information goes to reference system. (5) The inbox itself should contain neither — it's a temporary staging area, not a storage system. After processing, the inbox should be empty, with items routed to their proper destinations.