The problem with “GTD-compatible” task managers

Most task managers treat GTD as a marketing label. Todoist adds a “Getting Things Done” template. Things 3 has an inbox and areas. Asana lets you tag items as “Next Action.” But none of them enforce the GTD workflow — they give you the vocabulary without the system.

This matters because GTD is not a set of labels. It is a decision-making process. When you drop something into your inbox, GTD requires you to later clarify it: Is this actionable? Does it require multiple steps? Does it belong on a calendar? Should it be deferred? Generic task managers skip this entirely. They let you create a task, assign it a due date, and move on. That unclarified “stuff” sits in your list as vague anxiety — exactly the mental overhead GTD was designed to eliminate.

The result is a task manager full of items you have never actually processed. You have lists, but not a trusted system. And a system you do not trust is a system you stop using.

Purpose-built for the methodology

Capture GTD takes a different approach. Every feature exists because the GTD methodology demands it, and no feature exists simply because other task managers have it. There is no Kanban board, no Gantt chart, no team collaboration layer. Those are fine tools for other purposes, but they are not GTD.

The clarification workflow is enforced, not optional

When you capture an item, it enters your inbox as “Stuff” — an unclarified thought. To move it out, you must walk through a clarification step that mirrors David Allen’s decision tree. You declare whether the item is actionable. If it is, you determine whether it is a single next action, a multi-step project, or a calendar item. If it is not, you file it as reference material or send it to Someday/Maybe. Each path requires the right metadata: actions need effort estimates and contexts, projects need defined outcomes, scheduled items need dates or recurrence rules.

This is not bureaucracy. It is the core of GTD. The act of deciding “what is this and what do I do with it” is what transforms a pile of inputs into a system you can trust. Capture GTD makes that decision unavoidable.

All six horizons are first-class citizens

GTD defines six horizons of focus, from ground-level actions up through projects, areas of focus, goals, visions, and life purpose. Most task managers implement the bottom two — actions and maybe projects — and ignore the rest. Capture GTD treats all six horizons as real entities in the system. You can connect next actions to projects, projects to areas of focus, and areas of focus to higher-level goals. This vertical alignment is how GTD practitioners ensure day-to-day work serves long-term priorities.

Reviews are built in, not afterthoughts

The weekly review is the linchpin of GTD. Without it, inboxes overflow, projects stall, and the system degrades. Capture GTD treats reviews as a core workflow, not a calendar reminder you ignore. Morning, nightly, weekly, monthly, and yearly review cadences are supported, each scoped to the appropriate horizon.

Impact scoring follows GTD principles

When you sit down to engage with your system, Capture GTD does not just show you a flat list sorted by due date. Its impact scoring algorithm weighs task importance, effort size, deadline urgency, age, and dependency status to surface the actions that matter most right now. Smaller tasks score higher when you need quick wins. Approaching deadlines escalate naturally. Blocked tasks stay out of your way. The algorithm encodes the intuition that experienced GTD practitioners develop over time.

Multi-platform native, not a web wrapper

Capture GTD runs as a native application on each platform. iOS uses SwiftUI and follows Apple’s Human Interface Guidelines. Android uses Jetpack Compose and Material Design 3. The web client is built with React and Material UI. Each platform feels like it belongs on that platform because it does. A shared Kotlin Multiplatform domain layer ensures the GTD logic is identical everywhere, while the interface adapts to the conventions of each operating system.

Offline-first architecture

Your trusted system must be available when you need it — on a plane, in a dead zone, in a meeting where you do not want to wait for a spinner. Capture GTD uses a local SQLite database on mobile devices, synchronizing with the server when connectivity is available. You can capture, clarify, organize, and engage entirely offline. When you reconnect, your changes merge automatically. A trusted system that depends on a network connection is not fully trusted.

AI-native via MCP

Capture GTD exposes its full workflow through the Model Context Protocol (MCP), which means AI assistants like Claude can manage your GTD system through natural conversation. Say “capture that I need to call the dentist” and it lands in your inbox. Say “clarify that as a next action, low effort, @phone context” and it is processed. This is not a chatbot bolted onto a task manager — the MCP server exposes the same domain commands that the native apps use, so every AI interaction follows the same GTD rules.

Event sourcing: your data tells its own story

Under the hood, Capture GTD uses event sourcing. Every change to every task is stored as an immutable event — TaskCaptured, TaskClarified, TaskCompleted — rather than overwriting rows in a database. This means you have a complete audit trail of your productivity system. You can see when you captured something, how you clarified it, when you reclassified it, and when you completed it. No data is ever silently overwritten or lost. For a system that asks you to externalize your entire cognitive load, that guarantee matters.

The design philosophy

Capture GTD is opinionated because GTD is opinionated. David Allen’s methodology works precisely because it prescribes a specific workflow for processing inputs, organizing commitments, and reviewing progress. A tool that makes those steps optional undermines the methodology it claims to support.

The goal is not to be the most flexible task manager on the market. The goal is to be the most faithful GTD implementation — one where using the app correctly and doing GTD correctly are the same thing.