How to use contexts or @tags as separate Google Tasks lists on iPhone
If you have searched “Google Tasks contexts,” “Google Tasks @home,” or “GTD contexts in Google Tasks on iPhone,” you want a way to see work by where or how you can do it. Stock Google Tasks has no tags. Ordinary lists can still carry that job if you keep them few and undated.
Short answer
Google Tasks does not ship labels, tags, or GTD-style contexts on iPhone. There is no @Calls filter that pulls matching rows from every list. Create a small set of ordinary lists named for contexts you actually use (Calls, Errands, Computer, Home), keep those tasks undated until you have a real deadline, and open the matching list when you are in that place or mode. Do not treat contexts as a second Inbox, and do not sprinkle fake due dates to fake a context view.
Contexts versus lists, Waiting, and Inbox
A context answers: where or how can I do this next action? Classic GTD examples are @Calls, @Errands, @Computer, or @Home. A tag would let one task wear several markers at once. Google Tasks only gives you lists as containers. For why tags are missing, see labels and tags in Google Tasks.
Keep roles distinct so context lists stay scannable:
- Inbox (or Capture): unprocessed dump. Process it daily. See the Inbox or Capture list guide.
- Waiting: committed work blocked on someone else. See the Waiting For list pattern.
- Someday / Maybe: uncommitted ideas, kept undated. See the someday/maybe parking lot.
- Work / Home / Project lists: outcomes or life areas you own.
- Context lists: next actions you can do yourself when the place, tool, or energy matches.
A grocery checklist can be a context list; see grocery or errands lists. Contexts are not dependencies. Waiting covers blockers; Google Tasks has no blocked-by field.
How to set up context lists in stock Google Tasks
- In Google Tasks on iPhone, create only the contexts you open weekly. Common starters: Calls, Errands, Computer, Home. Skip @ prefixes in the list name if they clutter the switcher; the meaning matters more than the symbol.
- Cap the set. Five or fewer context lists beat fifteen micro-tags you never open. Merge rare contexts into notes (“needs printer”) instead of a new list.
- When you process Inbox, move doable next actions into the one context that best fits. If two contexts both fit, pick the one you will open first when you have ten minutes. Do not duplicate the task onto two lists.
- Keep context rows undated by default. Add a due date only when the deadline is real. Fake “due Today” to simulate a context view pollutes Calendar and overdue. See planning a day without fake due dates.
- Place context lists near each other in the list switcher so review is one swipe path. List order syncs with Google Tasks. For broader list hygiene, see how to organize Google Tasks lists.
Write titles for the moment you open the list
When you open Calls, you want dialable rows, not vague projects. Prefer short next-action titles:
- “Call Jordan about lease renewal”
- “Pharmacy pickup: refill #8821”
- “Email vendor for revised quote”
Put secondary cues in notes: phone number, address, tab URL, or what “done” looks like. Avoid stuffing every context under one mega-parent with subtasks. Subtasks are project steps inside one list, not a tag filter across your day.
Do not park blocked work in Calls hoping someone else will finish it. Move that to Waiting with a title that names the blocker. Do not leave untriaged capture in Errands; that belongs in Inbox until you decide the next action.
When to open each context
Contexts earn their keep when you batch. Standing in a store: open Errands. Ten minutes between meetings: open Calls. At your desk with focus time: open Computer. At home after dinner: open Home.
Fold a quick context pass into weekly review: delete zombies, move finished-looking rows out, and clear past due dates without fake-completing them. See clearing overdue without completing.
If you need one screen that shows Calls beside Work without flipping lists constantly, a native shell helps. ETasks syncs two-way with Google Tasks and adds all-lists and planner views on iPhone. It does not invent Google-side tags or context filters for web or Android.
Limits to accept
Stock Google Tasks will not let one task sit in Calls and Work at once, filter “everything tagged errand” across lists, or auto-suggest a context from your location. Keywords in titles (`#call`) are brittle search crutches, not a tag system.
If you need true multi-tag filters and Google proximity is optional, a tags-first app may fit better. If Gmail and Calendar already hold your tasks, stay on lists, keep contexts few, and batch by place.
Quick answers
Does Google Tasks have contexts or @tags? No. There is no context or tag field. Use ordinary lists named for the contexts you actually open.
Should every task live on a context list? No. Capture starts in Inbox. Blocked work goes to Waiting. Only clear next actions belong on context lists.
Can one task have two contexts? Not as two list memberships. Pick the primary context, or note the second cue in the title or notes.
Do context tasks need due dates? Usually no. Date only real deadlines so contexts stay a place-based batching tool, not an overdue pile.
Is Errands the same as a grocery list? It can be. Keep one simple undated checklist and open it when you shop.
← How to use Areas of Focus or life-area li… Next: How to keep a Waiting For list in Google… →