Open most to-do apps and you’ll find one long list, sorted by nothing in particular except the order tasks were typed in. “Call the dentist” sits next to “Refactor the onboarding flow” sits next to “Buy stamps.” Every time you glance at it, your brain has to re-sort the whole thing in real time, deciding what’s even possible right now.
GTD contexts fix this by tagging each task with where, what, or who you need to do it — so the list you see matches the situation you’re actually in. That’s the core idea behind David Allen’s Getting Things Done method, and it’s one of the most underused parts of task management. This post covers what contexts are, how to set up a set that actually fits your life, and how to use them without turning your task list into a filing system you dread maintaining.
What a Context Actually Is
A context is simply the condition required to do a task. Not a priority, not a deadline — a circumstance. Classic GTD contexts from the original book were tied to physical tools and locations, because that’s how most work happened at the time:
- @calls — anything you can only do with a phone in hand
- @computer — tasks that need a keyboard and screen
- @errands — things to knock out while you’re already out
- @home — tasks that require being physically at home
- @waiting for — things you’re blocked on, delegated to someone else
The point isn’t the specific labels. It’s that each one answers a single question: given where I am and what I have access to right now, which of these tasks are even possible? A list sorted by context turns “what should I do” into “what can I do,” which is a much smaller and easier question.
Contexts vs. Projects vs. Priority
People often blend these three ideas together, which is exactly what makes lists feel tangled. They answer different questions, and untangling them is most of the value:
| Concept | Question it answers | Example |
|---|---|---|
| Project | What am I trying to accomplish? | “Launch the new website” |
| Context | Where/how can I do this task? | “@computer” |
| Priority | How urgent or important is it? | “Do today” |
A single project like “Launch the new website” might contain a dozen tasks scattered across three different contexts — some @computer, some @calls, one @errands to pick up a printed sign. Contexts let you pull out just the actionable slice that fits your current situation, without losing track of which project it belongs to.
Designing a Context List That Fits Your Actual Life
The classic @calls/@computer/@errands set was designed for a world with landlines and desktop computers bolted to desks. Most people now carry a phone that handles calls, browsing, and messages in one device, so a context list copied straight from a 20-year-old book often doesn’t map to anyone’s real day. Build yours around your actual constraints instead:
- Location-based: @home, @office, @errands — useful if certain tasks truly require being somewhere specific
- Tool-based: @deep-focus, @quick-wins, @admin — useful if the limiting factor is your mental state or the block of time available, not where you’re standing
- People-based: @waiting-for, @agenda-[name] — useful for tracking delegated work or things to raise in your next 1:1
Most people end up with 4 to 7 contexts total. More than that and the overhead of tagging outweighs the benefit; fewer and you’re not really filtering anything. A useful test: if you can’t remember all your contexts without looking at the list, you probably have too many. The goal is a set small enough to hold in your head, so filtering by context becomes automatic rather than another decision.
It also helps to separate contexts from energy level, which is a related but distinct filter some people fold in as a bonus tag rather than a full context. A task might be @computer and also low-energy-friendly, meaning it’s a reasonable thing to do during an afternoon slump even though it technically requires being at a desk. You don’t need a formal system for this — just noticing the pattern is often enough to route the right task to the right moment.
A Practical Example: One Project Across Four Contexts
Abstract advice about contexts is easy to nod along to and hard to actually apply, so it helps to walk through one real project. Say you’re planning a small dinner party. As a single project, it might break down like this once you’ve captured everything into your inbox:
- Text three friends to confirm they’re coming — @calls
- Order flowers for the table online — @computer
- Pick up wine and a dessert on the way home — @errands
- Ask your neighbor if you can borrow extra chairs — @waiting-for
- Clean the dining room before guests arrive — @home
None of these tasks share a context, but they all belong to the same project. Without contexts, “Dinner Party” would be one clump of five unrelated actions, and you’d have to re-read the whole project every time you wanted to find something doable right now. With contexts, the two calls happen back-to-back while you’re waiting somewhere anyway, the errand happens on your actual errand run, and the home task waits until you’re actually home — each piece surfaces exactly when it’s usable.
Contexts and the Two-Minute Rule
Contexts work best alongside another core GTD habit: the two-minute rule. During your daily sort, anything you can finish in two minutes or less gets done immediately rather than filed into a context at all. It never needs a tag because it never sits on a list — it’s just gone. Everything that survives that filter is what actually needs a context, which keeps your @computer or @errands list from filling up with two-second replies and quick clicks that don’t deserve a slot.
This combination — quick wins handled instantly, everything else sorted by context — is exactly how Gratodo’s inbox is built: a fast lane for anything under two minutes, and contexts for the rest, so your list stays short enough to actually glance at and trust.
When Contexts Stop Working
Context systems tend to fail in one of two directions, and both are fixable once you notice the pattern. The first is over-engineering: a dozen hyper-specific contexts like @car, @gym-bag, @kitchen-counter that each hold one or two tasks and require more thought to file into than they save later. If you find yourself hesitating over which context a task belongs in, that’s a sign you have too many.
The second failure is the opposite — sticking with the default @calls/@computer/@errands set even though your actual week barely involves any calls or errands anymore. If most of your work happens at a single desk, location-based contexts add no filtering value at all, and you’re better off switching to energy- or focus-based contexts like @deep-focus and @quick-admin, which actually split your day into meaningful groups.
A quick monthly check is enough to catch either problem: look at how many tasks sit in each context. If one context is empty and another is overflowing, your contexts don’t match your real life anymore, and it’s worth spending five minutes redesigning them. Contexts are meant to serve the way you actually work, not the other way around — treat them as a living list, not a one-time setup you’re stuck with.
Getting Started
- List your last 20 completed tasks and notice what condition each one actually required — a phone, a computer, being at a specific place.
- Draft 4 to 6 contexts based on that pattern, not a template from a book — your contexts should match your actual week.
- Tag your current open tasks with one context each, running anything under two minutes through the fast lane instead.
- Filter by context the next time you sit down to work, and only look at the slice that matches where you are right now.
Contexts don’t make your task list shorter — they make it usable, by showing you only what’s possible in the moment instead of everything you’ve ever committed to. If you want contexts built into the same app that already handles your Pomodoro focus sessions and daily gratitude check-in, Gratodo keeps GTD-style capture, projects, and contexts in one calm, fully offline inbox — no subscription, one-time $4.99.
For more background on the broader method contexts come from, see the overview of Getting Things Done on Wikipedia.