Getting Things Done (GTD) in Obsidian: A Complete Setup Guide

Getting Things Done (GTD) is David Allen's productivity method built on one simple promise: your mind is for having ideas, not holding them. When every task, idea, and commitment lives in a trusted system outside your head, you stop worrying about what you're forgetting and start focusing on what's in front of you. The problem is that most GTD apps are rigid, cloud-locked, and subscription-bound. Obsidian is the opposite: local-first, plain-text, endlessly flexible, and yours forever.

This guide walks you through a complete GTD setup in Obsidian, from a frictionless capture inbox to a weekly review that actually sticks. You'll learn how to wire up the Tasks and Dataview plugins to surface your next actions by context and due date, how to handle multi-step projects, and how to layer the Eisenhower matrix on top so you always know what to do next, not just what's on the list.

By the end, you'll have a system that captures everything, clarifies what each item means, organizes it where it belongs, and resurfaces it exactly when you need it. Whether you build it piece by piece or start from a ready-made template, the principles here are the same ones GTD practitioners have trusted for two decades, now running entirely on your own machine.

What are the five steps of GTD?

GTD breaks productivity into five distinct stages, and the genius of the method is that you never do more than one at a time. Mixing them, like trying to organize while you capture, is what makes most to-do lists collapse.

1. Capture — Collect everything that has your attention into trusted inboxes. Ideas, tasks, errands, half-formed thoughts. Get them out of your head fast.
2. Clarify — Process what each item means. Is it actionable? If not, trash it, file it as reference, or park it on a someday list. If it is, decide the very next physical action.
3. Organize — Put each clarified item where it belongs: a next-actions list, a project, a context, or a calendar date.
4. Reflect — Review your system regularly, most importantly in a weekly review, so you trust it and keep it current.
5. Engage — Do the work. With a clear, trusted system, you can confidently choose what to tackle right now.

Obsidian maps onto these five steps beautifully because each one is just a note, a tag, or a query away. Let's build them.

How do you build a quick-capture inbox in Obsidian?

Build your capture inbox as a single Inbox.md note (or a dedicated 00 Inbox folder) that you can reach in one keystroke, so nothing ever slips through the cracks. The whole point of capture is speed: if adding a thought takes more than a couple of seconds, you'll stop doing it.

Here's a reliable setup:

• Create a note called Inbox.md at the root of your vault.
• Open Settings, then Hotkeys, search for "Open quick switcher" or assign a custom hotkey to a Templater command that jumps straight to the inbox.
• On mobile, add a shortcut or widget that opens Obsidian directly to this note so you can dump thoughts on the go.
• Optionally, use the core Templater plugin or a simple QuickAdd-style capture command to append a timestamped line without even opening the file.

Every captured item starts life as a raw bullet. Don't clarify yet, just collect:

• Call dentist about appointment
• Idea: blog post on plain-text productivity
• Buy birthday gift for Sam

Tip: Resist the urge to organize during capture. The inbox is allowed to be messy. You'll process it during Clarify, and a messy inbox you trust beats a tidy one you abandon.

If you want to go deeper on frictionless input, the patterns in mastering Obsidian daily notes pair perfectly with a capture inbox, since your daily note becomes a natural landing pad for anything you jot down through the day.

How do you clarify and organize tasks with the Tasks plugin?

Use the Tasks plugin to turn raw inbox bullets into structured, queryable actions with due dates, priorities, and contexts, then let it move them out of the inbox and into your system. Tasks is the backbone of GTD in Obsidian because it understands checkbox syntax natively and adds rich metadata through emoji shorthands.

When you clarify an inbox item, you decide the next action and tag it accordingly. A clarified task looks like this:

• Call dentist to book cleaning #context/calls 📅 2026-06-12 🔼

Here's what each piece does:

• #context/calls — a GTD context tag, so you can batch all your phone calls together.
• 📅 2026-06-12 — a due date the Tasks plugin recognizes and sorts on.
• 🔼 — a priority marker (medium here; ⏫ is high, 🔽 is low).

Common GTD contexts map cleanly onto tags: #context/calls, #context/computer, #context/errands, #context/home, #context/waiting. The waiting context is especially powerful for tracking things you've delegated and are waiting to hear back on.

Note: The Tasks plugin works on plain checkboxes, so your data stays as readable Markdown. Nothing is locked into a proprietary format, which is exactly the privacy-first promise that makes Obsidian worth using.

For a thorough walkthrough of every field, recurrence rule, and filter the plugin supports, see the ultimate guide to using the Obsidian Tasks plugin. It covers the metadata syntax in far more depth than we can here.

How do you surface next actions with Tasks and Dataview?

Surface your next actions by writing a query that pulls every incomplete, dated, prioritized task from across your vault into one live list, so you never have to hunt through notes. This is where GTD in Obsidian goes from a pile of bullets to a real engagement engine.

The Tasks plugin has its own query language. Drop a fenced code block labelled tasks into any note, and it renders a live, filterable list. Here's a focused query that shows high-priority work due before year end:

not done
due before 2026-12-31
priority is high

Each line is a filter, and they stack with AND logic: this returns tasks that are incomplete, and due before the date, and marked high priority. You can build dozens of these dashboards, one per context, one for "due today," one for "waiting on others," and pin them to a single Next Actions.md note.

If you prefer the flexibility of querying frontmatter and inline fields, the Dataview plugin complements Tasks nicely. Dataview can build tables of projects with their status, count open actions per area, or list every note tagged #waiting. A simple Dataview list of pending calls might filter on your #context/calls tag and group by project.

A practical division of labor:

• Use Tasks for anything checkbox-shaped: next actions, due dates, recurrence, priority.
• Use Dataview for higher-level rollups: project dashboards, area overviews, and reports that pull from note metadata.

If you're new to either plugin, the broader task management in Obsidian guide lays out how the two fit together across a full workflow. And once your dashboards are humming, a ready-made system like Obsibrain ships these GTD queries, contexts, and Eisenhower views preconfigured, so you skip the setup and start engaging on day one.

How do you handle projects in GTD inside Obsidian?

Handle projects by giving each one its own note that holds the outcome, the next action, and a live list of all related tasks, because in GTD a "project" is anything that takes more than one action to finish. A note titled "Launch newsletter" or "Plan Q3 offsite" is a project, even if it only has two steps.

A solid project note contains:

• A clear outcome statement at the top: what "done" actually looks like.
• The current next action, clearly marked so you always know your entry point.
• A task list of remaining steps, each a Tasks-plugin checkbox.
• Reference material and links to supporting notes.

Because every task carries its project context, you can write a Tasks query inside the project note that shows only its open actions, and another in your global dashboard that flags any project missing a next action, the single most common reason projects stall.

Tip: A project without a defined next action is a stuck project. Run a query for projects that have no #context/ task and you'll instantly spot what's blocked.

This is exactly where Obsidian's linking shines: projects connect to areas, resources, and meeting notes through wiki-links, building a web of context around each commitment. For a deeper treatment of structuring multi-step work, the guide on Obsidian project management covers outcomes, milestones, and review cadences in detail.

What does an effective weekly review look like?

An effective weekly review is a recurring 30-to-60-minute session where you empty your inboxes, update every project, and get your whole system current and trusted again. This is the Reflect step, and it's the habit that separates people who do GTD from people who merely tried it.

Run through this checklist every week, ideally the same day and time:

1. Clear the inbox. Process every captured item to zero. Clarify and organize each one.
2. Review next-action lists. Mark off what's done, delete what's stale, add what's missing.
3. Review project list. Confirm each project has a clear next action. Add one to any that don't.
4. Review waiting-for list. Follow up on anything you've delegated.
5. Review the calendar. Look back at the past week and ahead at the next two.
6. Review someday/maybe. Pull anything that's now actionable into your active system.

In Obsidian, your weekly review can live in a dedicated periodic note. The Periodic Notes plugin (or Obsidian's core daily notes with a weekly template) gives you a fresh review note each week, pre-filled with the Tasks and Dataview queries that surface exactly what needs attention. You check the boxes, and the dashboards update themselves.

Note: The weekly review is non-negotiable. A GTD system you don't review degrades into a graveyard of stale tasks within a month. Block the time on your calendar and treat it as a real appointment.

How do you layer the Eisenhower matrix on top of GTD?

Layer the Eisenhower matrix by sorting your next actions along two axes, urgent versus not urgent and important versus not important, so you decide what to do rather than just what exists. GTD tells you what your options are; Eisenhower helps you choose among them.

The matrix has four quadrants:

• Quadrant 1 — Urgent + Important: Do it now. Crises, hard deadlines.
• Quadrant 2 — Not Urgent + Important: Schedule it. This is where deep, high-value work lives.
• Quadrant 3 — Urgent + Not Important: Delegate it, or batch it. Many interruptions land here.
• Quadrant 4 — Not Urgent + Not Important: Eliminate it. Be honest.

In Obsidian, you can encode the matrix with tags or priorities. Map "important" to the Tasks plugin's priority field (⏫ high, 🔼 medium) and "urgent" to due dates, then write four Tasks queries, one per quadrant, on a single dashboard. A Quadrant 2 query, for instance, filters for high priority and no near-term due date, surfacing the meaningful work that's easy to neglect.

The real payoff is focus: instead of staring at fifty next actions, you look at your Quadrant 1 and 2 lists and know precisely where your attention belongs today.

Should you build this yourself or start from a template?

Build it yourself if you enjoy tinkering and want to understand every moving part; start from a template if you'd rather be productive this afternoon. Both are valid, and the GTD principles are identical either way.

Rolling your own teaches you the system intimately and lets you shape every query to your exact taste. The trade-off is time: contexts, dashboards, project templates, and a polished weekly-review note take hours to build and refine. Many people start enthusiastically and stall before the system is complete.

A ready-made template removes that friction. Obsibrain ships a complete GTD-and-Eisenhower workflow on top of PARA folders, with quick capture, next-action dashboards, project templates, habit tracking, and daily-through-yearly periodic planning already wired up. You get the trusted system on day one and spend your energy doing the work instead of configuring it.

If you're weighing your options, it helps to see how GTD compares with other approaches before committing, so the rundown in the best note-taking system is a useful companion read.

Frequently Asked Questions

Do I need both the Tasks and Dataview plugins for GTD? No, you can run a solid GTD setup with just the Tasks plugin, which handles capture, contexts, due dates, priorities, and queries on its own. Dataview is an optional upgrade for higher-level rollups like project dashboards and area reports that pull from note metadata rather than checkboxes.

Where should my GTD contexts live, in tags or folders? Use tags for contexts, like #context/calls or #context/errands, because a single task often belongs to one context but moves between projects and notes. Tags let you query across your whole vault, while folders lock an item into one location. Reserve folders for broad PARA-style structure.

How is GTD different from the Eisenhower matrix? GTD is a complete workflow for capturing, clarifying, and organizing everything that has your attention, while the Eisenhower matrix is a single prioritization tool for deciding what to do next. They work best together: GTD builds the trusted list, and Eisenhower helps you choose from it.

Can I do GTD in Obsidian on mobile? Yes. Obsidian's mobile apps sync your vault and run the Tasks and Dataview plugins, so you can capture on the go, check off next actions, and even view your dashboards. Set up a home-screen shortcut straight to your inbox note to keep capture frictionless.

Conclusion

GTD works because it moves everything out of your head and into a system you trust, and Obsidian gives you that system in plain text you fully control. Start with a fast capture inbox, clarify each item into a next action with the Tasks plugin, organize by context and project, and protect the weekly review like an appointment. Layer the Eisenhower matrix on top, and you'll always know not just what's on your plate, but what deserves your attention right now.

Build it from scratch to learn every detail, or start from a preconfigured template and get moving today. Either way, the payoff is the same: a clear mind, a trusted system, and the quiet confidence that nothing is falling through the cracks.