# How to use a Righthand with Todoist

Prepare a Todoist weekly planning queue that preserves task identity, date semantics, recurring intent, and owner review.

By Righthand Team · 2026-10-09

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-todoist

## Use Todoist to prepare decisions about the week

Righthand can help review a selected Todoist project before weekly planning. The useful output separates tasks with unclear dates, unfinished prerequisites, and work the owner may want to reschedule. It should not mark tasks complete or move deadlines just to make the list shorter.

Todoist's [API reference](https://developer.todoist.com/api/v1/) distinguishes task operations and scheduling information. Keep each task's identity, project context, and actual supplied due information. A date-only task and a task scheduled at a precise time should not be treated as the same kind of commitment.

## Define a personal planning boundary

Choose the project or approved filter, reporting week, time zone, and labels relevant to planning. For an illustrative freelance project, include deliverables and their subtasks while excluding the owner's unrelated personal errands. Give the criteria for deciding which tasks need review.

Inspect Todoist's available reads through [integrations](/integrations). If due information or completed-history reads are absent, supply an approved export or authorize a browser review. Do not promise automatic recurring-task handling without checking the actual supported action and its behavior.

## A worked planning brief

> At 4 PM America/Los_Angeles on Sunday, review the approved client-delivery project for the coming week. Produce a private planning queue with task ID, task link, parent relationship, due information as supplied, relevant labels, and questions about missing dates or prerequisites. Keep recurring intent visible when the source provides it. Do not complete, reopen, move, or reschedule tasks. Send to me for owner review and reconcile the included tasks with the selected project and subtask scope.

This example is illustrative. The assistant should ask about uncertain priorities rather than invent a ranking from task order or wording.

## Make the proposal useful

An example entry could say: “Send draft; due Tuesday; prerequisite review task still open; owner should confirm sequencing.” Another might show an undated task and ask whether it belongs in this week's plan. It should not describe an undated item as overdue.

Keep recurring work distinct from one-time deliverables. Completing a recurring task can affect its next occurrence, so an owner-approved planning proposal should specify the exact intended action. A suggestion to postpone this week's task is not permission to alter the entire recurring responsibility.

## Reconcile the next run

Match task IDs and compare scheduling information. A changed title or moved project should not produce a second copy of the same item. If the source only contains currently active tasks, avoid claims about whether a missing task was completed or deleted without additional evidence.

Permission failures, stale exports, and filter changes should be visible coverage notes. If supported updates are approved later, apply the specified changes and retrieve the resulting task state. Verify the due information and recurring intent rather than assuming an accepted update produced the desired schedule.

Use [Righthand's workflow guide](https://docs.righthand.ai/guides/responsibilities-and-workflows) to define recurring planning preparation. Check [plans](/pricing) for the responsibility you want to maintain.