Published · 6 min read

Does Google Tasks support task dependencies on iPhone?

If you have searched “Google Tasks dependencies,” “Google Tasks blocked by,” or “waiting on task Google Tasks,” you are asking whether one task can stay locked until another finishes. Stock Google Tasks does not offer that link type. This guide explains what it does have, how to approximate waiting work cleanly, and when a dedicated project tool is the better fit.

Short answer

No. Google Tasks on iPhone (and on Android and the web) has no task dependency, blocked-by, waiting-on, or predecessor field. You cannot mark Task B as blocked until Task A is complete, and the app will not hide or lock B automatically.

What you do get is a lightweight checklist model: titles, notes, an optional due date and time, completion, lists, and subtasks nested under a parent. That is enough for many personal projects. It is not a dependency graph.

What people mean by dependencies

In apps like Todoist, OmniFocus, or many project tools, a dependency means one of these:

  • Task B cannot start (or should not show as next) until Task A is done
  • A chain of blockers across a project
  • A visual “waiting” state tied to another task’s completion

Google Tasks stores each row as an independent item. Completing A does not unlock B. Leaving B open does not keep A open. There is no automatic next-action gate.

If you came from a GTD or PM suite looking for that behavior inside Gmail’s Tasks panel, the missing field is real. A simple project checklist still works when steps are ordered by you, not enforced by the app.

Practical workarounds that stay honest

Use these only when the project is small enough that you can remember the order yourself.

1. Put blockers above the work they unlock

Create the outcome as a parent task, then add the real steps as subtasks in the order you must finish them. Complete children from top to bottom. Nesting is hierarchy and checklist structure, not a lock. You can still complete rows out of order if you tap them.

2. Keep a short Waiting list

Make a dedicated list named Waiting or Blocked. Move (or copy the title of) anything you cannot advance until someone else replies. When the blocker clears, move the task back to your active list and give it a real due date only if there is a real deadline. This keeps undated parking-lot items from looking like overdue work.

3. Write the blocker in the notes

In the task details notes field, add a plain line such as “Blocked by: invoice from vendor” or “After: draft approved.” When you open the task, the context is visible on every device that syncs that task. Notes do not create a link, so update or clear the line when the wait ends.

4. Prefer order over fake due dates

Do not set every step to due today just to force a sequence. That pollutes Google Calendar’s Tasks layer and creates overdue noise. Keep most dependency stand-ins undated, and reserve due dates for true deadlines. For day planning without fake dues, see the companion guide on planning without fake due dates.

When Google Tasks is the wrong tool

Choose a project or GTD app instead when you need:

  • Hard gates (B stays locked until A completes)
  • Cross-project blockers or many parallel waiting links
  • Assignees, comments, boards, or portfolio folders as first-class fields
  • Automatic next-action views built from dependency status

Personal Google Tasks also lacks folders for lists, separate start dates, and comments on a task. Workspace surfaces such as Chat or Docs assignment are different products, not personal Tasks dependencies.

Stay with Google Tasks when the value is proximity to Gmail and Google Calendar, a free shared account surface, and a short checklist you drive manually. That tradeoff is intentional simplicity, not a hidden advanced mode.

What a better iPhone client can (and cannot) add

A native client can make nested steps easier to scan, show all lists together, and offer month, week, day, and agenda planners so you see the sequence without inventing due dates. ETasks is built for that: two-way Google Tasks sync, clearer checklists, and optional alarms when a true deadline needs attention.

ETasks does not invent a Google-side blocked-by field that appears in the official Tasks web or Android apps. Dependency graphs still belong in tools designed for them. If your work fits ordered subtasks and a Waiting list, a stronger iPhone shell around Google Tasks is often enough. If you need enforced unlock rules, pick a project app and keep Google Tasks for capture next to email.

Quick answers

Does Google Tasks have blocked-by or depends-on links? No. There is no dependency field on iPhone, Android, or web.

Are subtasks the same as dependencies? No. Subtasks nest steps under a parent. They do not lock or unlock other tasks automatically.

Can I approximate waiting work? Yes. Use ordered subtasks, a Waiting list, and a short notes line that names the blocker. Clear those when the wait ends.

Will completing one task auto-complete or unlock another? No. Each task’s completion state is independent.

Should I use due dates to force order? Usually no. Fake due dates create overdue clutter. Save dates for real deadlines.

← How to keep a someday/maybe list in Googl… Next: How to turn a Google Tasks list into a si… →

Clearer checklists for Google Tasks on iPhone

Download ETasks for nested checklists, planners, and two-way Google Tasks sync when your projects stay simple. Free and ad-free.