GTD for Multiple Jobs: Exact System to Separate Contexts, Prioritize, and Execute Without Overwhelm

GTD (Getting Things Done) solves the core problem of managing multiple jobs: context-switching overload. When you juggle three clients, two side projects, and personal tasks, your brain can’t track everything. GTD’s five-step workflow—capture, clarify, organize, reflect, engage—creates a system where tasks are out of your head and into a trusted structure, so you can focus on execution, not memory. Here’s how to adapt it for multi-job environments with concrete examples.

1. Capture: Empty Your Head Into One Place (No Exceptions)

Rule: If it’s on your mind, capture it immediately. Multi-job environments generate tasks from emails, Slack messages, meetings, and random ideas. Use a single inbox (app, notebook, or voice memo) to collect everything. Examples of what to capture:

• Client work: "Draft API spec for Client X by EOD Thursday" (from a Slack message), "Review pull request #42 in GitHub" (from an email notification).
• Internal projects: "Update onboarding docs for new hires" (from a team meeting), "Research Figma plugins for design system" (from a brainstorm).
• Personal tasks: "Call insurance provider to confirm coverage for Client Y’s contract" (from a reminder), "Buy groceries for team lunch next Tuesday" (from a calendar event).
• Follow-ups: "Ask Client Z for feedback on the wireframes" (from a previous conversation), "Check if the server migration is complete" (from a status update).

Pro tip: Use voice capture for speed. Dictate tasks while walking or between meetings. For example, say: "Review Client A’s contract changes, urgent, due Friday at 3 PM. Schedule a call with the designer to align on the new mockups." The app transcribes it and extracts the deadline, priority, and project automatically.

2. Clarify: Turn Captured Items Into Actionable Tasks (The Critical Step Most People Skip)

Clarifying means processing each captured item to decide: Is this actionable? If not, trash it, archive it, or file it as reference. If yes, define the next physical action—a specific, doable step. Examples:

• Vague item: "Work on Client B’s report." → Actionable task: "Draft the introduction section of Client B’s Q2 report in Google Docs (context: @office, @with-internet)."
• Non-actionable item: "Team meeting notes." → Archive as reference or create tasks from it: "Follow up with Sarah on the budget approval," "Update the project timeline in Notion."
• Multi-step item: "Launch Client C’s marketing campaign." → Project: Break it into tasks: "Write ad copy for LinkedIn," "Review designer’s mockups," "Schedule posts for next week."

Key question: Can this be done in under 2 minutes? If yes, do it now. If no, organize it by context (e.g., "@calls," "@clientA"). For example, "Email Client D about the delay" takes 2 minutes—do it immediately. "Write the quarterly report" takes hours—schedule it.

3. Organize: Structure Tasks by Projects, Contexts, and Deadlines (No Overlaps)

Organizing means placing tasks where they belong so you can find them when needed. For multiple jobs, use these categories:

Projects: Group Tasks by Outcome

Each job or client should be a project with its own list of tasks. Example:

• Project: "Client A’s Website Redesign."
• Tasks: "Review client feedback on wireframes (context: @office),"; "Update homepage copy (context: @with-internet),"; "Schedule call with developer to discuss API changes (context: @calls)."

Contexts: Filter Tasks by Where/How You Can Do Them

Contexts let you filter tasks based on your current situation. Examples:

• @office: Tasks requiring a computer or specific tools (e.g., "Design logo for Client B").
• @mobile: Tasks you can do on your phone (e.g., "Approve invoice for Client C").
• @calls: Tasks needing a phone or quiet space (e.g., "Call supplier about delivery delay").
• @clientA: Tasks specific to Client A (e.g., "Review contract changes").
• @with-internet: Tasks needing online access (e.g., "Research competitors for Client D").

Calendar: Only for Fixed Deadlines

Put only time-specific tasks in your calendar, like meetings or immovable deadlines. Example:

• Calendar: "Client A’s feedback call – 05/15 2:00 PM,"; "Submit tax documents – 05/20 5:00 PM."
• Next Actions list: "Draft blog post for Client B,"; "Review pull request #42."

Someday/Maybe: Park Non-Urgent Ideas

Use this list for tasks you might do later. Review it weekly to move items to active projects. Example:

• Someday/Maybe: "Learn React for future projects,"; "Attend a UX design workshop,"; "Pitch a new service to Client A."

4. Reflect: The Weekly Review That Prevents Multi-Job Chaos

Without a weekly review, your system collapses. Dedicate 60–90 minutes to:

• Empty your inbox: Process all captured items (emails, notes, messages) into tasks, projects, or reference material.
• Review projects: For each project, ask: What’s the next action? Are there blocked tasks? Do I need to delegate? Example: For "Client A’s Website Redesign," the next action might be "Email developer about API changes."
• Update contexts: Remove obsolete tasks or add new ones. Example: If you’re traveling next week, add a context "@travel" for tasks you can do on the go.
• Check deadlines: Flag tasks due in the next 7 days. Example: "Client B’s report is due Friday—schedule time to draft it."
• Plan the week: Assign time blocks for critical tasks. Use time blocking for multiple clients to avoid double-booking.

Pro tip: Use a checklist for your review. Example:

• Have I captured everything from the past week?
• Are all projects moving forward (each has a next action)?
• Are there tasks I can delegate or delete?
• Do I need to adjust priorities based on new deadlines?
• Have I scheduled time for critical tasks?

5. Engage: Choose What to Do in the Moment (Without Guesswork)

GTD’s engage step uses four criteria to decide what to do now:

• Context: What can I do based on where I am or what tools I have? Example: If you’re on your phone, filter tasks with "@mobile."
• Time available: How much time do I have? Example: 10 minutes? Reply to an email. 2 hours? Draft a report.
• Energy: How do I feel? Example: Tired? Organize files. Fresh? Design wireframes.
• Priority: What’s most important now? Use the Eisenhower Matrix to categorize tasks as urgent/important, not urgent/important, etc. Example: "Send invoice to Client A" (urgent/important) vs. "Research new tools" (not urgent/important).

Example: You’re at the office with 45 minutes before a meeting. Filter tasks by:

• Context: "@office" and "@with-internet."
• Time: 45 minutes or less.
• Energy: Medium (you just had lunch).
• Priority: Urgent or important.

The chosen task might be: "Review and approve Client C’s pull request" (urgent, fits your context, and requires moderate focus).

Common Mistakes (and How to Fix Them)

• Mistake: Mixing tasks from different projects in one list. → Fix: Use separate projects and filter by tags (e.g., "@clientA").
• Mistake: Vague contexts like "@work." → Fix: Be specific (e.g., "@clientA," "@calls," "@with-server-access").
• Mistake: Skipping the weekly review. → Fix: Block it in your calendar as an unmovable meeting. Use a checklist to stay on track.
• Mistake: Overloading the calendar with non-time-specific tasks. → Fix: Use the calendar only for fixed deadlines (meetings, deliveries). Keep the rest in "Next Actions" lists.
• Mistake: Not delegating. → Fix: Identify tasks others can do (e.g., "Ask the designer to review mockups"). Use tools with collaboration features to assign tasks.

Tools for GTD with Multiple Jobs (What to Look For)

Your tool should:

• Centralize all jobs: See tasks from clients, projects, and personal life in one place.
• Support flexible tagging: Organize by projects, contexts, and priorities (e.g., "@clientA," "urgent").
• Offer multiple views: List (for GTD workflows), kanban (for project statuses), and calendar (for deadlines).
• Sync across devices: Capture tasks on mobile and access them on desktop.

Examples:

• Foco: Designed for multiple jobs. Each job is a container with its own color. Use Focus mode to see tasks for one job at a time. Supports voice capture, time blocking, and integrations with GitHub/Notion. Learn how to unify tasks from multiple apps without migrating data.
• Todoist/Notion: Flexible but require manual GTD setup. Good for generic use cases.
• OmniFocus/Things: GTD-specialized but may lack multi-job features like project separation.

How to Apply GTD with Foco (Step-by-Step)

Foco aligns with GTD’s principles while solving multi-job challenges:

1. Set Up Jobs as Projects

Create a job for each client or project (e.g., "Client A," "GitHub Issues," "Home"). Assign a color to each job so tasks appear in that color across all views. Example:

• "Client A" (blue) → Tasks: "Draft report," "Review contract."
• "GitHub" (green) → Tasks: "Fix bug #42," "Review pull request #101."

2. Capture Tasks Fast

Use voice capture to dictate tasks. Foco transcribes the audio and extracts details like deadlines, priorities, and projects. Example:

• Dictate: "Review Client A’s contract changes, urgent, due Friday at 3 PM." → Foco creates a task with "urgent" priority, a due date of Friday, and the audio attached.
• Use Rapid to dictate multiple tasks at once. Example: "Email Client B about the delay. Schedule a call with the designer. Buy Figma licenses." Foco separates them into three tasks for review before saving.

3. Organize with GTD Fields

Use Foco’s fields to implement GTD:

• Date of realization: When you’ll work on the task (e.g., "Tomorrow 9–11 AM"). This appears in your calendar.
• Due date: The deadline (e.g., "Friday 5 PM").
• Priority: Urgent, important, or normal.
• Tags: For contexts (e.g., "@calls," "@clientA").
• Notes: Attach files, voice memos, or transcribed audio.

4. Use Views for Different Workflows

Switch between views with one tap:

• List view: Group tasks by date (Today, This Week, Later). Ideal for GTD’s "Next Actions" lists.
• Kanban view: Columns for statuses (e.g., "To Do," "In Progress," "Done"). Useful for project tracking.
• Calendar view: See tasks with realization dates alongside meetings. Avoid overlaps with time blocking for multiple clients.

5. Simplify the Weekly Review

Filter tasks by job, date, or priority. Example:

• Open the list view and filter by "This Week" to see pending tasks.
• Use the kanban view to move tasks between columns (e.g., from "To Do" to "In Progress").
• Check the calendar view for upcoming deadlines.

6. Automate Task Capture

Connect Foco to tools like GitHub, Notion, or Jira. Assigned tasks appear automatically in Foco. Example:

• A GitHub issue assigned to you appears in Foco as: "Review pull request #101 (GitHub job)."
• Mark it as done in Foco, and it updates in GitHub (if enabled).

For emails, forward them to your personal Foco email (e.g., u-xxxx@in.heyfoco.com). Foco extracts the task and attaches the email as a note.

A productivity system for multiple jobs isn’t about doing more—it’s about remembering less. GTD gives you the framework; the right tool removes the friction.

FAQ

How do I apply GTD if I have 10+ active projects?

GTD scales to any number of projects. The key is clarifying next actions for each project and using contexts to filter tasks. For example, tag tasks with "@clientA" or "@office" to see only what’s relevant now. Use a tool like Foco to group tasks by job and avoid visual clutter.

What if a task belongs to two projects (e.g., a contract for Client A and Client B)?

In GTD, a task can only belong to one project. Solutions: 1) Duplicate the task in both projects (e.g., "Review contract for Client A" and "Review contract for Client B"). 2) Create a new project for shared tasks (e.g., "Q2 Contract Reviews").

How do I avoid mixing personal and work tasks in GTD?

Use separate projects (e.g., "Work," "Home") and contexts (e.g., "@personal," "@work"). In your tool, filter by project to focus on one area at a time. For example, use Foco’s Focus mode to see only work tasks during office hours.

Can I use GTD with paper, or do I need an app?

You can use paper, but apps are more practical for multiple jobs. They let you filter, search, and sync tasks across devices. If you prefer paper, use a notebook per project and an index to locate tasks. Example: A bullet journal with separate collections for each job.

How do I apply GTD if I work with teams on multiple projects?

Use a tool with collaboration features (e.g., Foco, Asana). 1) Create shared projects for team tasks. 2) Assign tasks to team members. 3) During your weekly review, check for blocked tasks and communicate dependencies. For developers, sync tools like GitHub or Jira to avoid duplicate entries.