A task dependency means one task must be completed before another becomes actionable. In Chorsu, blocked work stays out of Today. When its final prerequisite is completed, an otherwise active task becomes ready and returns in Today’s Just unblocked section. You do not have to keep checking a task you cannot do yet.

Start with the work that must happen first

Suppose you need to send a report, but its budget must be approved first. Create a task named Budget approval. That is the prerequisite. Send the report is the task that depends on it.

  1. Capture the dependent task. Open Quick Capture and write send the report after Budget approval.
  2. Resolve its project. Chorsu chooses a clear match or asks you to choose a project in the panel.
  3. Check the prerequisite. A uniquely matching task title can be linked automatically. If the match is unclear, choose the right task in the dependency picker. You can also type a title to create the prerequisite.
  4. Finish capture. Check that the confirmation shows the expected prerequisite. The report task remains blocked while that prerequisite is unfinished.
  5. Complete Budget approval when it is actually done. Once the report’s prerequisites are satisfied, it becomes actionable. With notifications enabled, Chorsu can notify you of the transition.
Chorsu confirmation showing Send the report blocked by Budget approval with a reminder for tomorrow at 9
This example combines a prerequisite with a time reminder. The dependency records what must be finished; the reminder records when you want a nudge.
Chorsu Today list showing Send the report under Just unblocked
Ready work appears in Chorsu after the blocking prerequisite is completed.

Use the picker when wording is not enough

You can add a relationship with + Dependency in Quick Capture. Search existing tasks, select the intended prerequisite, or create one in the chosen project. If two tasks have similar names, make the choice yourself rather than relying on an approximate match.

A completed prerequisite no longer blocks the task. If you add several prerequisites, completing only one is not enough: the task must no longer have an unfinished prerequisite before it is unblocked. Its project and task must also remain active; an archived task or one deliberately put in Waiting or Someday is not made actionable by a dependency alone.

Dependencies, subtasks, and reminders solve different problems

A dependency describes readiness.
“Send the report” cannot happen until “Budget approval” is complete.
A subtask describes a smaller piece of work.
A checklist inside “Prepare the report” can break the work into steps. A nested item, by itself, does not establish a completion-triggered dependency.
A reminder describes time.
“Tomorrow at 9 am” gives you a scheduled nudge. It does not establish that another task has been finished.

Use a prerequisite for real blockers and a reminder for time-sensitive work. Keeping those meanings separate helps you avoid using arbitrary dates as a substitute for readiness.

What Chorsu does not know

Chorsu does not watch your email, a teammate’s project tool, or an approval system. If someone approves the budget elsewhere, mark the prerequisite complete in Chorsu yourself. Its local task state is what drives the dependency.

The workflow is for your tasks on this Mac. It is not a shared project-management system or a promise that macOS will always display a notification banner. Check Chorsu’s lists for the current state of your work.

For setup help, see notifications and task support. For work shared with other people or devices, read the Chorsu and Todoist comparison.