How to Use GTD for Multiple Jobs: A Practical Guide to Organizing Projects, Contexts, and Next Actions

Managing multiple jobs—whether as a freelancer, entrepreneur, or employee juggling several projects—can quickly become mental chaos if you don’t have a clear system. How to use GTD for multiple jobs isn’t just a common question; it’s a real need for anyone looking to maintain control without drowning in endless to-do lists. GTD (Getting Things Done), David Allen’s methodology, is one of the most effective systems for organizing tasks, but implementing it in environments with multiple responsibilities requires specific adjustments. In this guide, we’ll explain how to adapt GTD to multiple jobs, with concrete examples of projects, contexts, and next actions so you can apply it starting today.

Why GTD Is Ideal for Managing Multiple Jobs

GTD is based on two key principles: capturing everything that occupies your mind and processing it into a reliable external system. This is especially useful when managing multiple jobs because it allows you to mentally separate responsibilities without losing sight of what’s important. Unlike other methods, GTD doesn’t just prioritize tasks; it helps you define what’s actionable and what context you need to execute it. This prevents mental overload, as you don’t have to constantly remember what you need to do in each area of your professional life.

When you work on multiple fronts, it’s easy to mix tasks from one project with another or procrastinate on urgent matters due to lack of clarity. GTD solves this with a structured workflow: capture, process, organize, review, and do. Each step is designed so nothing gets lost in limbo, which is crucial when you have deadlines, clients, or different teams demanding your attention.

The 5 Steps of GTD Adapted for Multiple Jobs

1. Capture: Gather Everything in One Place

The first step of GTD is to empty your mind into an external system. When managing multiple jobs, this means recording all tasks, ideas, emails, or pending meetings, regardless of which project they come from. Use a tool that allows you to group them by job but without losing the big picture. For example:

• Write down in a temporary list everything you have pending: from "send proposal to client X" to "review invoices for project Y."
• Include ideas or reminders that come up during the day, like "research tool to automate reports."
• If you use email, forward messages that require action to your capture system (we’ll see how later).

If you don’t capture it, your mind will remember it at the least opportune moment, stealing your focus.

2. Process: Define What’s Actionable and What’s Not

Once everything is captured, the next step is to process each item. This is where GTD shines for multiple jobs because it forces you to ask: Does this require action? If the answer is no, archive it, delete it, or save it as reference. If yes, define the next physical action needed to move forward. For example:

• If the task is "prepare presentation for client A," the next action might be "review client A’s brief and list 3 key ideas."
• If it’s "pay invoice to supplier B," the next action would be "log into the payment platform and schedule the transfer."
• If it’s an unclear email, like "I need feedback on the design," the next action would be "send a message to [name] asking for specific feedback points."

This step is crucial to avoid analysis paralysis. When you have multiple jobs, it’s easy to procrastinate on tasks because you don’t know where to start. Defining the next concrete action eliminates that ambiguity.

3. Organize: Projects, Contexts, and Next Actions

This is where GTD adapts to managing multiple jobs. You need a system that allows you to group by projects, filter by contexts, and see only what’s relevant at any given moment. Let’s break it down:

In GTD, a project is any outcome that requires more than one action to complete. When managing multiple jobs, it’s helpful to group projects by area. For example:

• Job 1 (Client X): Project "Campaign Launch," Project "Monthly Meetings."
• Job 2 (Personal Project): Project "MVP Development," Project "Investor Search."
• Job 3 (Administration): Project "Quarterly Invoicing," Project "Contract Updates."

Each project should have at least one next action associated with it. If a project doesn’t have a clear action, it’s not well-defined.

Contexts are labels that tell you where or with what resources you can complete a task. When working on multiple fronts, contexts help you focus on what you can do at any given moment. Some useful examples:

• @office: Tasks that require being in your workspace (e.g., "review contracts").
• @computer: Tasks that need a device (e.g., "edit video for client Y").
• @calls: Tasks that require a phone (e.g., "call supplier to confirm delivery").
• @home: Personal or administrative tasks (e.g., "pay electricity bill").
• @time: Tasks that require a specific block of time (e.g., "2 hours to write report").

Contexts are especially useful when you have downtime (like waiting in a meeting) and want to take advantage of it to make progress on quick tasks, like replying to emails or reviewing documents on your phone.

Once tasks are organized by projects and contexts, create a next actions list that includes only what you can do now. This list should be dynamic and constantly updated. For example:

• If you’re in the office with your computer, filter actions by the contexts @office and @computer.
• If you have 15 minutes free, look for actions with the context @calls or @quick.
• If it’s the end of the month, prioritize actions from the Quarterly Invoicing project.

4. Review: The Habit That Keeps the System Alive

The weekly review is the heart of GTD, and it’s even more critical when managing multiple jobs. Dedicate 30-60 minutes each week to:

• Review all projects and ensure each has at least one next action defined.
• Update contexts if your circumstances have changed (e.g., if you’re now working more from home, adjust the labels).
• Delete or archive completed or irrelevant tasks.
• Plan the following week, assigning time blocks to priority projects.

Without this review, your system will fill up with obsolete or irrelevant tasks, and you’ll lose the clarity GTD provides. The review is what turns a to-do list into a reliable system.

5. Do: Focus on What Matters Now

The final step is execution. GTD doesn’t tell you what to do at every moment, but it gives you the tools to decide with clarity. When working on multiple fronts, this means:

• Use contexts to filter what you can do at that moment.
• Prioritize based on energy and available time: if you’re tired, choose mechanical tasks; if you’re fresh, focus on strategic ones.
• Avoid multitasking: GTD helps you concentrate on one action at a time, which is key to maintaining productivity in environments with multiple responsibilities.

Practical Example: How to Use GTD for Multiple Jobs in a Week

Let’s look at a concrete example of how to apply GTD when managing three different jobs: Client A (digital marketing), personal project (app development), and administrative tasks (invoicing and contracts). Here’s what a typical week might look like:

Monday: Capture and Processing

• You review your inbox and capture everything: emails from Client A, ideas for the app, pending invoices, and a meeting with a potential investor.
• You process each item: define next actions like "draft brief for Client A’s campaign," "research libraries for app login," and "schedule transfer for supplier invoice."
• You organize by projects: assign each action to its corresponding project and add contexts (@computer, @calls, etc.).

Tuesday: Focus on One Job

• You filter your next actions list by the Client A project and the @computer context.
• You spend 2 hours drafting the brief and sending it to the client.
• You take advantage of a 15-minute gap to call the supplier (@calls) and confirm the invoice.

Wednesday: Review and Adjustments

• You do a quick review of your projects: Client A has responded to the brief, so you add the next action "review Client A’s feedback."
• You update contexts: since you’re working from home today, you add the @home context to administrative tasks.
• You delete completed tasks, like "schedule transfer for invoice."

Thursday: Time Block for the Personal Project

• You filter by the App Development project and the @computer context.
• You spend 3 hours researching libraries and prototyping the login.
• You take the opportunity to email the potential investor (@computer), adding the next action "prepare pitch for Friday’s meeting."

Friday: Weekly Review and Wrap-Up

• You do the weekly review: archive completed tasks, update projects, and plan the next week.
• You prioritize the most important actions: the investor meeting and Client A’s feedback.
• You adjust contexts and projects based on what’s changed during the week.

Common Mistakes When Using GTD for Multiple Jobs (and How to Avoid Them)

Implementing GTD for multiple jobs isn’t foolproof. These are the most common mistakes and how to fix them:

• Mixing projects in one list: If you don’t group tasks by project, you’ll lose the big picture. Solution: Use a system that lets you see each project separately but also the master next actions list.
• Not defining next actions: If you only write "work on project X," you won’t know where to start. Solution: Break down each task into concrete physical actions (e.g., "open Figma and design the login button").
• Ignoring contexts: If you don’t filter by contexts, you’ll miss opportunities to make progress on quick tasks. Solution: Add contexts to all actions and review them based on your location or available resources.
• Skipping the weekly review: Without it, your system will fill up with obsolete tasks. Solution: Block 30-60 minutes each week to review and update your system.
• Overloading the next actions list: If you include tasks you can’t do now, the list will become overwhelming. Solution: Keep only the actions you can execute in the next few days and archive the rest.

How to Apply GTD for Multiple Jobs with a Tool Like Foco

Implementing GTD for multiple jobs requires a tool that lets you organize by projects, filter by contexts, and maintain a clear view without overloading your mind. Foco, for example, is designed to manage multiple responsibilities in one place. Each job (like "Client A," "Personal Project," or "Administration") acts as a container for projects and tasks, with a distinctive color to help you identify them instantly. You can see all your tasks in Panorama mode, where each appears with its job’s color, or enter Focus mode to concentrate on just one area.

To apply GTD in Foco, you can use tags as contexts (e.g., @office, @calls, @computer) and group tasks by due date or projects. The Kanban view lets you organize columns by task status (e.g., "To Do," "Doing," "Done"), while the calendar helps you assign time blocks to next actions. Additionally, voice capture and the Rapid mode (for dictating multiple tasks at once) make it easy to record everything that comes up during the day without missing anything. If you work with teams, you can invite collaborators to a specific job and assign them tasks, keeping everything organized without mixing responsibilities.

The most important thing is that Foco lets you filter and prioritize based on what you need at any given moment. For example, if you’re in the office today, you can see only tasks with the @office context and the Client A project, avoiding distractions from other jobs. This way, GTD becomes a living, adaptable system, not a static list.