GTD for Multiple Projects: Exact Workflow, Examples, and Tools to Implement It Without Overwhelm

GTD (Getting Things Done) for multiple projects is a five-step workflow designed to handle complexity without losing control. Unlike generic to-do lists, GTD structures tasks by contexts (where/when you can do them), horizons of focus (from daily actions to long-term goals), and real-time decision-making—critical when juggling freelance clients, side projects, and personal responsibilities. Below is the exact system, with concrete examples for each step.

Step 1: Capture Everything (The ‘Inbox Zero’ for Your Mind)

Capture every task, idea, or pending item—no filtering. The goal is to empty your mind so you can process information, not store it. Use tools that are always accessible (e.g., a notes app, voice recorder, or email to yourself).

• What to capture: Tasks (e.g., ‘Send invoice to Client X’), ideas (e.g., ‘Redesign portfolio’), deadlines (e.g., ‘Contract due 10/15’), and even vague concerns (e.g., ‘Check tax deadline’).
• How to capture: Add project context and deadlines upfront (e.g., ‘Project Y - Client Z: Draft proposal by 10/10’). This saves time later.
• External sources: Unanswered emails, Slack messages, sticky notes, or calendar reminders. Example: If you have 3 unread emails from clients, capture them as ‘Respond to Client A’s feedback’ and ‘Clarify scope with Client B.’

Example for a freelancer with 3 clients + 1 personal project:

• Client A: Send wireframes (deadline: 3 days).
• Client B: Review feedback (urgent, no deadline).
• Client C: Call supplier for print specs (requires phone).
• Personal: Buy domain for online course (requires computer).
• Vague: ‘Update portfolio’ (no action yet).

Step 2: Clarify (Turn ‘Stuff’ into Actionable Tasks)

For each captured item, ask: ‘Is this actionable?’ If not, trash it or file it under ‘Someday/Maybe.’ If yes, decide the next physical action (e.g., ‘Call Juan’ vs. ‘Organize meeting’). Use this decision tree:

• Single-step task? Do it now if it takes <2 minutes (e.g., ‘Reply to Client A’s email’). Otherwise, add it to your Next Actions list.
• Multi-step task? It’s a project (e.g., ‘Launch online course’). Break it into next actions (e.g., ‘Research domain providers,’ ‘Draft course outline’).
• Depends on someone else? Add it to your ‘Waiting For’ list (e.g., ‘Waiting for Client B’s feedback’).

Example: Clarifying the freelancer’s captured tasks:

• ‘Send wireframes to Client A’: Single action → ‘Draft email with wireframes’ (Next Actions list, @Computer context).
• ‘Review feedback from Client B’: Project → Next actions: ‘Read feedback’ and ‘List required changes’ (both @Computer).
• ‘Buy domain’: Single action → ‘Search for available domains’ (@Computer).
• ‘Update portfolio’: Project → Next actions: ‘Select 3 recent projects’ and ‘Edit images’ (@Computer).

Step 3: Organize (Structure Tasks for Real-World Execution)

The 5 Essential GTD Lists for Multiple Projects

• Next Actions: Tasks you can do now, grouped by context (e.g., @Computer, @Calls, @Errands). Example: ‘Call supplier’ goes under @Calls, ‘Edit images’ under @Computer.
• Projects: A master list of all active projects (e.g., ‘Client A - Website Redesign,’ ‘Personal - Online Course’). Each must have at least one next action.
• Waiting For: Tasks delegated or pending others’ input (e.g., ‘Waiting for Client B’s feedback - sent 10/5’). Include dates for follow-up.
• Someday/Maybe: Non-urgent ideas (e.g., ‘Learn Figma,’ ‘Travel to Portugal’). Review weekly.
• Calendar: Only for time-specific actions (e.g., meetings, deadlines). Avoid adding flexible tasks here.

How Contexts Work with Multiple Projects (With Examples)

Contexts let you filter tasks by what you can do right now, not by project. This is critical when managing multiple responsibilities. Example contexts:

• @Computer: Edit images, send emails, research domains.
• @Calls: Call supplier, confirm meeting with Client C.
• @Errands: Buy domain, mail package to Client A.
• @Low Energy: File documents, respond to simple messages.
• @High Energy: Design wireframes, write course outline.

Scenario: You’re at home with 30 minutes and low energy. Instead of scrolling through all projects, check your @Low Energy list and pick ‘File invoices’ (Client A) or ‘Respond to Slack messages’ (Client B).

Step 4: Reflect (The Weekly Review - Your GTD ‘Reset Button’)

The weekly review prevents GTD from becoming a graveyard of outdated tasks. Dedicate 60-90 minutes to:

• Capture again: Add anything new since the last review.
• Review Projects list: Ensure each has at least one next action. If not, archive or discard it.
• Update Next Actions and Waiting For lists: Remove completed tasks, add new actions, and follow up on delegated items (e.g., ‘Has Client B sent feedback?’).
• Check your calendar: Look 2-3 months ahead for deadlines or key events (e.g., ‘Client A’s launch on 11/1’).
• Prioritize for the next week: Choose 3-5 tasks or projects to focus on. Example: ‘Finish Client A’s wireframes’ and ‘Draft course outline.’

The weekly review isn’t optional—it’s the difference between GTD as a system and GTD as a to-do list that grows stale.

Step 5: Execute (How to Choose What to Do Right Now)

With multiple projects, decision fatigue is the enemy. GTD uses four criteria to pick tasks:

• Context: What can you do right now? (e.g., @Computer tasks if you’re at your desk).
• Time available: 5 minutes? Do a quick task (e.g., ‘Reply to email’). 2 hours? Tackle a bigger task (e.g., ‘Design wireframes’).
• Energy: High energy? Do creative work (e.g., ‘Write course outline’). Low energy? Do administrative tasks (e.g., ‘File invoices’).
• Priority: Urgent (imminent deadline) or important (high impact)? Example: ‘Client B’s feedback is urgent; Client A’s wireframes are important but not urgent.’

Example: It’s 10 a.m., you’re at the office with 1 hour before a meeting. Your options:

• Context: @Computer.
• Time available: 1 hour (medium task).
• Energy: High (fresh start).
• Priority: Client B’s feedback is urgent; Client A’s wireframes are due tomorrow.

Decision: Do ‘Make changes to Client B’s design’ (urgent + high energy) instead of ‘Send wireframes to Client A’ (can wait or be delegated).

Common Mistakes (And How to Fix Them)

• Mistake 1: Not capturing everything. Solution: Use voice capture (e.g., dictate tasks while commuting) or a ‘capture inbox’ (e.g., a notes app widget).
• Mistake 2: Projects without next actions. Solution: During the weekly review, ask: ‘What’s the next physical action?’ for each project.
• Mistake 3: Overloaded Next Actions lists. Solution: Limit lists to 20-30 items max. Split by context (e.g., @Computer, @Calls) and prioritize 3-5 tasks per week.
• Mistake 4: Skipping the weekly review. Solution: Block a fixed time (e.g., Friday 4 p.m.) and treat it like a client meeting.
• Mistake 5: Ignoring contexts. Solution: Use contexts to filter by availability. Example: If you’re on your phone, check @Calls or @Mobile tasks.

Tools to Implement GTD for Multiple Projects

GTD works with any tool, but these features help manage multiple projects:

• Separate containers for each project: Color-code tasks by project (e.g., blue for Client A, green for personal).
• Context-based filtering: View tasks by @Computer, @Calls, etc. Example: Bullet Journal for Multiple Jobs: Exact System to Separate Contexts Without Losing the Big Picture explains how to do this analogically.
• Calendar integration: Sync deadlines and time-block tasks. Example: Time blocking for freelancers with multiple clients shows how to avoid overlaps.
• Voice capture: Dictate tasks and let the tool transcribe them. Example: Foco’s voice capture detects dates, priorities, and recurrences from your speech and creates tasks automatically. Its Ráfaga feature lets you dictate multiple tasks in one go (e.g., ‘Send invoice to Client A by Friday, call supplier for Client B, buy domain for course’), which it splits into separate tasks for review before saving.
• Unified task view: See all projects at once or filter by one. Example: Foco’s Panorama mode shows tasks from all projects (each with its project’s color), while Focus mode filters to one project. This mirrors GTD’s horizons of focus—seeing the big picture or zooming into details. You can also group tasks by due date or start date, add reminders, and attach notes (e.g., audio recordings, emails). For freelancers, this is useful to unify tasks from multiple apps (e.g., Notion, GitHub, Jira) without migrating data.

FAQ: GTD for Multiple Projects

FAQ

What’s the first step to implement GTD for multiple projects?

Start with capture. Spend 10 minutes writing down every task, idea, or pending item from all your projects. Use a tool that’s always accessible (e.g., a notes app or voice recorder). Example: A freelancer might capture ‘Send invoice to Client X,’ ‘Review feedback from Client Y,’ and ‘Buy domain for course.’ Don’t organize yet—just get it all out of your head.

How do I prioritize tasks when everything feels urgent?

Use GTD’s four criteria: context, time available, energy, and priority. Example: If you have 30 minutes at home with low energy, check your @Low Energy list and pick a task like ‘File invoices’ instead of ‘Design wireframes.’ For urgent vs. important, ask: ‘What’s the deadline?’ and ‘What’s the impact?’ Example: ‘Client B’s feedback is urgent (due today); Client A’s wireframes are important (due tomorrow).’

How often should I do the GTD weekly review with multiple projects?

Do the weekly review once a week, without fail. Block 60-90 minutes (e.g., Friday afternoon or Monday morning). The review includes: capturing new items, updating projects and next actions, checking the calendar, and prioritizing 3-5 tasks for the next week. Without it, your GTD system will become outdated and overwhelming.

Can I use GTD with tools like Notion or Todoist for multiple projects?

Yes. GTD works with any tool that lets you: create lists by context (e.g., @Computer, @Calls), group tasks by project, and filter by availability. Example: In Todoist, use labels for contexts (e.g., @computer) and projects for each client/personal task. In Notion, create a database for Next Actions with properties for context, project, and priority. For a deeper dive, see Critical Power List: How to Identify, Prioritize, and Execute Critical Tasks.

How do I handle tasks that depend on others when using GTD for multiple projects?

Add them to your ‘Waiting For’ list. Include the date you delegated them and follow-up details. Example: ‘Waiting for Client B’s feedback - sent 10/5.’ During the weekly review, check this list and follow up if needed. This keeps your Next Actions list clean and ensures nothing slips through the cracks.