A GTD next action is the single physical action you can take right now to move a project or commitment forward. In David Allen’s Getting Things Done system, a next action is never a vague label like “sort out the proposal” — it is always a concrete, physical step with a clear starting point, such as “open the proposal document and draft the three key terms in section two.” This specificity is what separates a task list you act on from one that keeps growing without shrinking.

If you are trying to choose between GTD and other knowledge management approaches, see GTD vs Building a Second Brain for how these frameworks treat capture and action differently.

Why GTD Treats Next Actions as the Unit of Work

Most to-do lists are filled with projects disguised as tasks. “Follow up with the accountant” sounds like a task. In GTD terms, it is a multi-step commitment — a project — and it will stay on your list until you identify the very next physical action: “Call Sarah at the accountancy firm and ask when the draft accounts will be ready.”

The distinction matters because your brain cannot act on a project. It can only act on a physical step. When you have fifteen minutes before a meeting and scan your list, “accountant” does nothing. “Call Sarah” tells you exactly what to do.

David Allen argues that the failure to identify next actions is the single biggest reason tasks stall. The project stays open in your head as an unresolved commitment — what Allen calls an open loop — draining background mental energy without producing any progress. Closing that loop requires identifying one concrete next step.

This is not a minor distinction. A study by Gloria Mark found that it takes an average of 23 minutes to return to a task after a distraction. Vague task items force a micro-decision every time you read them — “can I act on this right now?” — and the answer is almost always no, because the action is not clear. That micro-decision is a distraction in itself.

The Anatomy of a Well-Formed Next Action

A clear next action has three components.

A verb that specifies the physical action. Not “think about” or “consider” — those are mental states, not physical steps. The verb should describe what you would actually see someone doing: call, write, email, open, print, visit, buy, send, review.

A clear object or outcome. What exactly are you doing? “Write the executive summary for the Smith proposal” is clear. “Work on the proposal” is not — it could mean anything from reading it again to sending the final draft.

A context or location if relevant. Some next actions belong in specific environments: at your computer, on the phone, at the office, waiting on someone else’s response. This context label feeds directly into your GTD context lists, which organise next actions by where or how they can be taken.

A well-formed next action looks like: “Call James to confirm the project kickoff date — @calls” or “Open the March invoice and check the consulting hours line item against the SOW — @computer.” Both are physical, specific, and ready to act on without further thinking.

Here is a quick comparison of vague tasks versus clear next actions:

Vague task	GTD next action
Sort client files	Create a Google Drive folder for the Smith account and move the three March invoices from Downloads into it — @computer
Follow up with James	Email James asking for an update on the contract review — @computer
Deal with the insurance renewal	Call the broker on 020 7777 8888 to get a renewal quote for the business liability policy — @calls
Prep for Thursday’s board meeting	Open last quarter’s board pack and write three bullet points for the trading update slide — @computer

How Next Actions Connect to GTD Projects

In GTD, a project is any outcome that requires more than one physical step to complete. A next action is the single visible step currently in front of you for any given project.

Your GTD projects list holds all open commitments. For every project on that list, you need at least one next action in your system — otherwise the project has no forward motion. The weekly review is specifically designed to catch projects without a visible next action and surface what that step should be.

The relationship works like this: the projects list holds the destination; the next actions list holds the next move. You do not manage projects day to day. You manage next actions, and the actions accumulate into completed projects.

This is a meaningful shift for most business owners. The temptation is to plan the entire project before taking any action. GTD argues that you only need to plan as far as the next physical step. The GTD natural planning model gives you the full planning sequence for complex projects — but even complex projects reduce to a single next action at the execution stage.

Why Vague Tasks Stay on Your List

There is a specific reason some items sit on your list for weeks without moving. The item is not a next action — it is a reminder that something exists, without the clarity of what to do about it.

“Sort the client files” is a common example. It is not clear what “sort” means, which files, or where to start. Every time you read it, your brain engages briefly, concludes there is no clear starting point, and moves on. The item accrues a small amount of anxiety each time without producing any action.

Converting it to a next action requires a moment of deliberate thinking: what is the very next physical step? “Create a folder in Google Drive for the Smith account and move the three invoices from the downloads folder into it.” That is a ten-minute task you can do immediately. “Sort client files” might stay on your list for six months.

The brain dump method surfaces these stalled items by externalising everything in your head at once. The processing step — converting each item to either a project with a next action, or a someday/maybe entry — is where GTD’s real value lands.

Filing Next Actions into Context Lists

Once you have a next action, it goes into the right context. GTD organises next actions by where or how they can be done, so you can scan the right list for the moment you are in.

The four core contexts for a business owner are:

• @Computer — digital tasks that require a screen and an internet connection.
• @Calls — phone conversations to initiate or return, with the number or name noted.
• @Waiting — items you have delegated or sent, where you are waiting on a response. These are not things you can do — they are things to track and chase if they go quiet.
• @Anywhere — actions you can take regardless of location: a short conversation, a quick physical task, a decision that needs making.

When you have a free block at your desk, you scan @computer and pick the most important item. When you have thirty minutes between meetings, you work @calls. The context system stops you from re-reading every item on the list to find what fits the current moment — which is one of the main ways an unorganised task list becomes a source of friction rather than clarity.

See GTD context lists for the full setup process, including how to build a context map that reflects your actual working life rather than a generic GTD template.

Capturing Next Actions in the Weekly Review

Next actions do not only get created during processing. New ones surface as you think through the week ahead, review your commitments, and scan your projects list for anything that has stalled.

The GTD weekly review includes a dedicated step for reviewing every open project and confirming that at least one next action exists for each. Projects without a visible next action get one assigned before the week starts. This is the maintenance habit that keeps the system from breaking down.

Without the weekly review, projects accumulate without next actions, and the system becomes unreliable. Once the system is unreliable, you stop trusting it, and you are back to keeping things in your head — which is the exact problem GTD is designed to solve.

The GTD capture habit feeds the weekly review by ensuring nothing falls through the cracks in the first place. Every new commitment — a promise made in a meeting, an idea that arrived during the school run, a task mentioned in an email — enters one trusted inbox, where it gets processed into a project and a next action during the next review cycle.

For anything that is not ready to become a next action — a project you might do in the future, an idea worth revisiting — the GTD Someday/Maybe list holds it without cluttering your active system.

Using Claude to Clarify Stalled Next Actions

One of the practical places Claude fits in a GTD-based system is at the processing stage — specifically, converting vague items into concrete next actions.

The prompt is straightforward: paste a list of stalled tasks and ask Claude to rewrite each as a single physical action with a verb, an object, and a context label. For longer project items, ask it to identify the very next physical step and explain why that specific step would unblock the project.

This is particularly useful for items that have been on your list for more than two weeks without moving. Something is blocking them — either the outcome is unclear, the action requires a decision you have been avoiding, or it belongs to someone else and is sitting in your inbox as a vague reminder. Claude can surface the ambiguity and name the step.

You can also set up a context file in Claude that includes your project list and current context structure. When you sit down for your weekly review, load the file and ask Claude to flag any project without a visible next action. It will run the check in a few minutes across every open commitment.

The same logic applies to prioritising tasks — when every item is expressed as a concrete next action, ranking them by urgency and impact becomes far simpler because you are comparing like-for-like physical steps rather than vague project labels.

Four Common Next Action Mistakes

Writing next actions at project level. “Redesign the website” is a project with dozens of next actions. Writing it as a single item means you will never start, because there is no clear physical step. Break it down: “Open the current site on mobile and note the three pages with the longest load time — @computer.”

Using vague verbs. “Discuss the contract with Sarah” is not a next action — it is a meeting agenda item. The next action is “Email Sarah to schedule a 20-minute call about the contract renewal terms — @computer.” Vague verbs (“look into”, “deal with”, “handle”) are reliable signs that the item has not been properly processed.

Confusing waiting-for items with active next actions. If you are waiting on someone else’s response, the action sits in @waiting, not in your active list. The only time a waiting-for item generates a next action is when you need to chase it: “Email James to follow up on the March invoice if no response by Friday — @computer.”

Keeping too many active next actions. GTD does not ask you to do everything at once. Your next action list should be scannable at a glance. If reviewing it takes more than two minutes, it has outgrown its useful size. Most experienced GTD practitioners keep between thirty and sixty active next actions across all contexts, with the majority in @waiting and @computer.

What Changes When You Get This Right

The clearest sign that a GTD system is working is the absence of mental noise around what to do next. Every project is moving because every project has a visible next step. The weekly review catches anything that has stalled and assigns it a new step before it becomes a source of background anxiety.

The business owner who runs on a next-action list does not spend mental energy deciding what to work on. The system holds those decisions. Each session starts with a clear physical step, and the work becomes simpler — not because there is less of it, but because the path through it is visible.

The Nerd Productivity System builds this structure across every area of your work: capture, process, plan, and execute, with next actions as the fundamental unit at the execution stage. The free course walks through all four phases and how they connect: start with the free NP System course.

Frequently Asked Questions

What is a GTD next action? A GTD next action is the single physical action you can take right now to move a project or commitment forward. It is always specific and physical — “email James to book a call” rather than “follow up with James.”

How is a next action different from a task? A task is often vague or multi-step. A next action is the single physical step that requires no further thinking before you start. In GTD, you convert tasks into next actions during the processing step.

How many next actions should you have? Most GTD practitioners keep between thirty and sixty active next actions across all contexts. More than that and the list becomes unmanageable; fewer suggests projects are not being properly tracked.

What do you do if a next action is blocked? Move the project outcome to @waiting if it is blocked by someone else, or to your Someday/Maybe list if it is blocked by a decision you are not ready to make. Remove it from your active next actions until it is genuinely actionable.

How do you write a next action for a complex project? Use the GTD natural planning model to clarify the project’s outcome and desired state, then identify the single next physical action that moves it forward. You do not need to plan every step — only the next one.