Skip to content
Back to blog
Article

Getting Things Done with Todoist and Todolytics: A Practical GTD Guide

Build a practical GTD system in Todoist and discover how Todolytics’ Classic Reviews and Work Cycles help you learn from your tasks and plan your next week.

Getting Things Done with Todoist and Todolytics: A Practical GTD Guide

Getting Things Done with Todoist and Todolytics: A Practical GTD Guide

Getting Things Done (GTD) is David Allen’s productivity method for capturing commitments, defining next actions, and regularly reviewing your system. Todoist gives those tasks and projects a place to live, while Todolytics adds structured reflection to help you learn from your work. Together, they support a practical workflow: capture what needs your attention, decide what to do next, carry out the work, and use your weekly review to improve your decisions. For people who already organize their work in Todoist, this combination connects daily task management with a regular opportunity to examine what helped, what caused friction, and what should change in the coming week.

What is the Getting Things Done method?

The Getting Things Done methodology starts with moving commitments into a trusted external system. Instead of remembering every task, idea, and unfinished obligation, you capture them somewhere you will reliably revisit. The David Allen Company’s introduction to GTD describes five stages that form the foundation of the method:

  1. Capture: Collect tasks, ideas, and commitments that have your attention.
  2. Clarify: Decide what each item means and whether it requires action.
  3. Organize: Put actions and supporting information where they belong.
  4. Reflect: Review your system to keep it accurate and useful.
  5. Engage: Choose and carry out the appropriate action.

Their practical value becomes clear with an everyday example: “Website” is something you might capture, but “Publish an updated services page” defines an outcome, and “Draft the opening paragraph” gives you a next action you can actually start. Clarifying that action is an essential part of building a useful GTD system. Similarly, “Prepare workshop” leaves several decisions unresolved, while “Email the organizer to confirm the audience and workshop length” tells you how to begin. During inbox processing, GTD also uses the two-minute rule: if an actionable item takes less than two minutes, complete it immediately; longer actions can be organized for later or delegated. Todoist’s Getting Things Done guide explains this decision process.

How to set up GTD in Todoist

A practical Todoist GTD setup gives incoming items, active projects, next actions, dependencies, and future ideas a clear home. Use the Todoist Inbox to capture new tasks and ideas, then process those items into an appropriate structure. Start with a system you can maintain easily and add detail when it solves a recurring problem. The following setup builds on the use of projects and labels described in Todoist’s GTD guide:

GTD element Suggested Todoist setup Purpose
Capture inbox Todoist Inbox Collect incoming tasks and ideas
Projects A project for each active outcome requiring multiple actions Keep related work together
Next actions @next label Identify actions you can take now
Waiting For @waiting_for label Track dependencies and delegated work
Someday/Maybe A separate project Preserve possibilities for later consideration
Contexts Labels such as @calls, @home, or @computer Find actions suited to your circumstances
Reference material Links in relevant task or project comments Keep supporting information accessible

Contexts and filters make this structure easier to use during the day. A context should help you decide what you can do with your current tools, location, or circumstances. With Todoist filters, you can combine labels to create useful views using the documented label queries and filter operators:

  • @next shows tasks labeled as next actions.
  • @next & @calls shows next actions requiring a call.
  • @next & @computer shows next actions requiring a computer.
  • @waiting_for shows your tracked dependencies.

Consistent naming matters: if you choose @next, keep that spelling throughout your setup. Each label should earn its place by making your task management system easier to use. If you rarely consult a context or filter, consider whether you need it. A smaller set of useful views is easier to maintain and gives you a clearer starting point when you sit down to work.

Why the GTD Weekly Review matters

The GTD Weekly Review keeps your system aligned with your actual commitments. Over a week, projects change, new information arrives, completed work creates follow-up actions, and some priorities become less relevant. Reviewing your system gives you an opportunity to update those details before they become difficult to track. The David Allen Company groups the review into Get Clear, Get Current, and Get Creative. Its official GTD Weekly Review checklist includes processing inboxes, reviewing next action lists, checking past and upcoming calendars, examining Waiting For items, updating projects, and revisiting Someday/Maybe.

A weekly review is also a useful moment to examine your experience of doing the work. Updating a project might show that a report is complete, while reflecting on the process could reveal that gathering information took much longer than writing it. Those observations lead to different improvements: one confirms progress, and the other suggests a better preparation step for the next report. Combining system maintenance with task reflection lets you answer two useful questions: “Are my commitments accurately represented?” and “What have I learned about how I work?” The first keeps your GTD system trustworthy; the second gives you concrete material for better project planning and personal productivity.

How Todolytics complements GTD

Todolytics fits naturally around the Reflect stage of Getting Things Done. Todoist holds your tasks and projects, while Todolytics provides a structured way to examine the work behind them. A sensible approach is to add this reflection to your existing GTD Weekly Review, alongside checking your inboxes, calendar, open projects, and Waiting For list. For example, your project review might confirm that a research brief is finished, but a closer look could reveal that the first work session was spent deciding what the brief should cover. That experience suggests a practical improvement: agree on the research questions before beginning the next brief. The insight can then become a clear Todoist action, such as “Send proposed research questions to the project lead.”

Todolytics offers two review formats with different starting points:

Review format Starting point Main focus
Classic Review Completed Todoist tasks from a chosen period Understand completed work and capture lessons
Work Cycle Todoist tasks selected before the work begins Compare expectations with what happened

A Todolytics Classic Review loads completed tasks from a chosen period, optionally narrowed by a saved label filter. You answer questions for individual tasks and then write your own summary using summary questions. You can use your own questions or AI-generated task questions. Available retrospective history depends on your Todoist plan. For a GTD workflow, useful prompts might include:

  • Was the next action clear enough when I started?
  • What information did I need earlier?
  • Which part of the process would I repeat?
  • Did completing this task create another commitment?

A Todolytics Work Cycle begins with existing Todoist tasks selected through your configured label or the Todolytics extension. Customizable pre-review questions record expectations before you work. You complete tasks in Todoist, then close the cycle at the end of your chosen period, even if some work remains unfinished. Reasons for open tasks and an AI reflection chat help you examine the outcome. A cycle usually lasts a week, although another rhythm is possible. This approach is useful when you want to investigate planning assumptions, such as whether a task was sufficiently clear or whether a dependency needed attention earlier.

A practical GTD Weekly Review checklist with Todolytics

Use the following sequence as a weekly review template, combining the core GTD review with an additional reflection step. Keep the checklist somewhere you regularly revisit, such as a recurring Todoist task. The first three steps adapt the structure of the official Weekly Review checklist; the final two connect that review with learning and future action.

  1. Get Clear. Collect loose notes and incoming information, capture uncaptured commitments through a brain dump or mind sweep, and process your inboxes.
  2. Get Current. Review next actions, past and upcoming calendars, Waiting For items, active projects, and relevant checklists. Confirm that projects have an appropriate next action.
  3. Get Creative. Revisit Someday/Maybe, reconsider commitments, and record new ideas or possibilities.
  4. Reflect with Todolytics. Use a Classic Review or close your Work Cycle to examine what helped, what caused friction, and which assumptions need changing.
  5. Bring the lesson back into Todoist. Turn a useful insight into an action, a project note, a reusable checklist, or a different planning choice.

Inbox zero, in this context, means that incoming items have been clarified and placed appropriately; the underlying work may still be open. Once your system is current, focus your reflection on a question that could influence your next decision. If research repeatedly starts before the scope is agreed, create an action to request approval. If a dependency surfaces late, add an earlier availability check. If a task feels difficult to start, rewrite it as a smaller, visible step. This connection between reflection and next actions makes the weekly review part of your ongoing work.

An example: improving a recurring reporting project

Imagine that you produce a monthly customer report. In Todoist, you capture the commitment, clarify the outcome, and identify the first action: request the latest customer data from the account team. During your GTD Weekly Review, you check whether the data arrived, update the Waiting For item, and confirm the next action. Once the report is complete, reflection reveals that you rebuild the same structure and search for the same supporting information every month. That observation suggests a change to the process, which you can translate into concrete actions:

  • Create a reusable report outline.
  • Add a preparation checklist covering the required data sources.
  • Use the outline and checklist in the next reporting project.

GTD keeps the commitment moving, while additional reflection helps improve the process around it. Entering those actions in Todoist gives your insight a practical effect on the next project. Over time, you can use the same approach to examine recurring client work, content production, administrative tasks, or personal projects. The most useful lesson is often a specific adjustment: request information earlier, define the outcome more clearly, or preserve a successful approach for reuse.

Common questions about GTD, Todoist, and weekly reviews

  • Can you use Todoist for Getting Things Done? Yes. Its projects, labels, and filters can support next actions, contexts, Waiting For items, and Someday/Maybe lists, as explained in Todoist’s GTD guide.
  • What is the difference between a GTD Weekly Review and task reflection? The GTD review updates your commitments and system. Task reflection examines your experience of carrying out the work.
  • Do you need AI for a Todolytics Classic Review? No. You can use your own reflection questions, with AI-generated task questions available as another option on the Classic Review page.
  • How long should a weekly review take? Allow enough time to make your system current, with additional reflection scoped to the questions that matter. The time required depends on your inboxes, projects, and commitments.

A common mistake is to judge the week mainly by the number of completed tasks. Task completion provides useful evidence, but tasks differ in size and importance: resolving a critical project dependency can have a greater effect than finishing several routine items. Ask which actions moved meaningful outcomes forward, and consider the circumstances behind unfinished work before deciding what to change. Missing information, a changed priority, or an unrealistic assumption can each require a different response. Keep the review manageable, focus on observations that could influence your decisions, and give useful lessons a place in your working system.

Explore Classic Reviews for Todoist or Work Cycles for planning and reflection, then start with one question about your work and one concrete change to carry into the next week.ö