GTD: Getting Things Done in Logseq

Getting Things Done (GTD) in Logseq works best when capture, clarification, and organization happen immediately—using tags, properties, and keyboard shortcuts—so tasks and reference material resurface with the right context later. The core move is to translate GTD’s “inbox → next actions → review” flow into Logseq’s block-level workflow, then standardize how metadata is added at the moment something enters the system.

Instead of waiting to clean things up later, the workflow starts by funneling everything into a single capture tag (for example, an “inbox” hashtag). From there, Logseq blocks can be pulled together under chosen tags or backlinks, letting users defer decisions like “someday” or “reference” without losing the ability to find the item quickly. The transcript emphasizes upfront thinking about what context will be needed when information is revisited—comparing it to searching WhatsApp chat history or using a couple of keywords in Google. In practice, that means choosing tag keywords that match how the user would actually search.

Calendar and time-based actions get handled through Logseq’s slash commands and built-in properties. Typing “/scheduled” or “/deadline” opens a menu to attach calendar-based information to a block. The “to do” property can be inserted via Control + Enter, while waiting states can be added by typing “waiting” (or selecting it from the “/” menu). For reference items, the approach leans on metadata: set a “type” property to “reference,” then add tags that reflect likely search terms—such as whether the item is about a project, a person, or a topic. “Someday” items use a consistent tag (the transcript mentions “somday” and notes that namespaces are created but the key is using them consistently).

For reminders, the transcript contrasts Logseq’s space repetition feature with a simpler navigation-based method: using “/read” and “/watch” commands to create quick routes to items, then relying on hierarchy to find them fast. Items that no longer matter can be removed by tagging “trash” or deleting the block.

The workflow then maps GTD’s “who/where/what” thinking into metadata triggers. “Who” can be captured with an “@” mention so queries can quickly pull up all blocks tied to a person. “Where” can be captured with “@” or “$”-style context tags (e.g., “home,” “work,” “shops”) so the same note can be retrieved based on location rather than forcing it into a single project category. “What” becomes the action itself: email, call, buy, or other next steps. The transcript suggests using a “next” tag for actionable items, then removing it once the action is done.

Finally, the system supports running agendas and reviews by filtering blocks by inbox, person, and project namespaces. Reference and action items can be organized into project hierarchies so users can collapse and navigate quickly. Dashboards—built with Logseq queries and potentially advanced queries later—are positioned as the next step for higher-level review, with examples like a home page that aggregates projects, reminders, and “to do” lists through queries and namespace navigation.