How to Manage Interdependent Tasks Across Multiple Clients (Exact Workflow)

When Client A’s deliverable depends on Client B’s approval, or Client C’s report can’t start until Client D’s feedback arrives, you need a system that shows these connections without manual cross-checking. Foco structures each client as a separate work (with its own color) and lets you visualize all tasks together in Panorama mode. Dependencies become visible in three ways: (1) color-coding (each task shows its client’s color), (2) filters (tag tasks as ‘Blocked’ or ‘Waiting’), and (3) calendar drag-and-drop (adjust deadlines while seeing overlaps).

Step 1: Set up works for each client (and shared coordination)

• Create a work for each client: tap +, name it (e.g., ‘Client A - Website Redesign’), and assign a color. Tasks inherit this color, so you’ll recognize them instantly in Panorama mode.
• For shared dependencies (e.g., a meeting between Client A and Client B), create a third work named ‘Client Coordination’ with a neutral color. Assign the meeting task here to avoid duplicating it.
• Example: An architect managing two construction projects (Client A and Client B) creates three works: ‘Client A - Permits’, ‘Client B - Structural Review’, and ‘Coordination - Site Visits’.

Step 2: Add tasks with dependency details (fields that matter)

• Due date: Set the final deadline (e.g., ‘Client A’s homepage due June 10’). For tasks blocked by others, leave it blank or use a broad estimate (e.g., ‘This week’).
• Priority: Mark as ‘Urgent’ if it blocks another task (e.g., ‘Client B’s feedback is Urgent because Client A’s design depends on it’).
• Tags: Use ‘Blocked’, ‘Waiting’, or ‘Dependency’ to filter later. Example: A developer tags a task as ‘Blocked’ until Client B approves the API specs.
• Notes: Add context like ‘Depends on Client B’s task #123 (API approval)’ or ‘Do not start until Client C sends assets’. Voice capture transcribes this automatically: say ‘Task for Client A: draft proposal, depends on Client B’s budget approval, due Friday’, and Foco fills the fields.

Example: A freelance marketer’s interdependent tasks

• Client A (Social Media): ‘Post campaign assets’ (due June 12, depends on Client B’s approval).
• Client B (Branding): ‘Approve campaign assets’ (due June 10, Urgent priority).
• Client C (Analytics): ‘Send monthly report’ (due June 15, depends on Client A’s campaign data).

Step 3: Visualize dependencies in Panorama mode (avoid blind spots)

• Filter by ‘Blocked’ or ‘Dependency’ tags to see stalled tasks. Example: A designer filters for ‘Blocked’ and sees that Client A’s task is waiting on Client B’s feedback.
• List view: Group tasks by date (‘Today’, ‘This Week’, ‘Later’). If Client A’s task is in ‘This Week’ but its dependency (Client B’s task) is ‘No Date’, you’ll spot the risk immediately.
• Kanban view: Create columns like ‘To Do’, ‘Waiting (Dependencies)’, and ‘Done’. Drag tasks between them. Example: Move Client A’s task to ‘Waiting’ if Client B misses the deadline. Learn how to [organize Kanban boards for multiple projects without mixing deadlines](p/kanban-method-for-multiple-jobs-how-to-organize-projects-on-one-visual-board-without-overwhelm).

Step 4: Adjust deadlines in Calendar view (see overlaps)

• Switch to Calendar view to see tasks and external events (via Google Calendar/Outlook sync). Example: A consultant sees that Client A’s deadline (June 12) overlaps with a 3-hour meeting for Client B (June 11) and reschedules the task to June 13.
• Drag tasks to new dates to adjust deadlines. Example: If Client B’s feedback is delayed from June 10 to June 12, drag Client A’s task from June 13 to June 15.
• Use the ‘Due date’ or ‘Do date’ filters to group tasks by delivery or work dates. Example: Filter by ‘Due date’ to see all deadlines for the week, or by ‘Do date’ to plan your workload.

Step 5: Automate follow-ups and recurring dependencies

• Set reminders for critical tasks. Example: Schedule a reminder for June 9 to ‘Follow up with Client B on pending approval (blocks Client A’s task)’.
• Use recurrence for repetitive dependencies. Example: A monthly report for Client A depends on data from Client B. Create a recurring task (monthly) with the note ‘Depends on Client B’s data (task #456)’.
• Ráfaga (Plus plan): Dictate multiple interdependent tasks at once. Example: Say ‘Task 1: Review brief for Client B, due June 5, Urgent. Task 2: Design banner for Client A, depends on Client B’s review, due June 10.’ Foco splits them into two tasks with dates and dependencies pre-filled.

Step 6: Collaborate without losing context

• Invite clients to their work. Example: Add Client B to the ‘Brief Review’ work so they can see their task and upload files directly in Foco.
• Assign tasks to team members or clients. Example: Assign ‘Send feedback’ to Client B with a deadline. They’ll see it in their Foco dashboard without accessing other works.
• Share a task via public link. Example: Send Client B a link to the ‘Brief Review’ task so they can upload feedback without seeing Client A’s tasks.

Why Foco handles dependencies better than alternatives

• Spreadsheets: Manually update dates and cross-reference tabs. Example: A spreadsheet with tabs for Client A and Client B requires constant scrolling to check if Task 1 (Client A) depends on Task 2 (Client B). In Foco, both tasks appear in Panorama mode with their client’s color, and filters show dependencies instantly.
• Single-project apps (e.g., Trello, Asana): Designed for one workflow. Example: In Trello, you’d need separate boards for Client A and Client B, making it impossible to see dependencies between them. Foco’s Panorama mode shows all works together while keeping them separate.
• Note-taking apps: Dependencies get buried in text. Example: In Notion, you’d write ‘Client A’s task depends on Client B’s feedback’ in a long page, but you can’t filter or visualize it. Foco’s tags and color-coding make dependencies visible at a glance.
• Traditional calendars: Only show events, not tasks or dependencies. Example: Google Calendar shows Client A’s deadline but not that it’s blocked by Client B’s feedback. Foco’s calendar integrates tasks and external events, and you can drag dates to adjust deadlines while seeing the impact.

Real example: An architect’s interdependent tasks

• Client A (Permits): ‘Submit zoning application’ (due June 20, depends on Client B’s structural review).
• Client B (Structural Review): ‘Approve plans’ (due June 15, Urgent priority).
• Coordination (Site Visits): ‘Inspect Client A’s site’ (due June 18, depends on Client B’s approval).
• Steps taken: (1) Created three works (Client A, Client B, Coordination) with distinct colors. (2) Added tasks with due dates, priorities, and dependency notes. (3) Filtered by ‘Blocked’ in Panorama mode to see that Client A’s task was waiting on Client B. (4) Adjusted deadlines in Calendar view after Client B’s review was delayed by 2 days. (5) Assigned the ‘Approve plans’ task to Client B and set a reminder for June 14.

The bottleneck isn’t the dependency itself—it’s not seeing it until it’s too late. Foco’s color-coding and filters turn invisible risks into visible tasks you can act on.

Key decisions when managing interdependent tasks

• When to leave a task’s date blank: If it’s blocked by another task, set a broad estimate (e.g., ‘This week’) or leave it blank to avoid false urgency.
• When to use ‘Urgent’ priority: Only for tasks that block others. Example: Client B’s feedback is Urgent because Client A’s deliverable depends on it, but Client C’s non-critical request isn’t.
• When to create a shared work: For tasks involving multiple clients (e.g., a meeting between Client A and Client B). Assign it to the ‘Coordination’ work to avoid duplication.
• When to adjust deadlines: In Calendar view, drag tasks to new dates only after confirming the dependency is resolved. Example: Don’t move Client A’s task to June 15 if Client B’s feedback is still pending.

For a step-by-step guide on organizing tasks by client without mixing deadlines, see [this exact workflow](p/step-by-step-guide-to-organizing-tasks-by-client-in-a-task-app-without-mixing-deadlines). To avoid common mistakes when managing multiple jobs, check [these fixes](p/common-mistakes-when-managing-multiple-jobs-and-how-to-avoid-them).

FAQ

How do I track tasks that depend on external teams (not just clients)?

Use the same system: create a work for the external team (e.g., ‘Vendor - Printing’), assign tasks with due dates, and tag them as ‘Blocked’ or ‘Waiting’ if they depend on others. Example: A designer tags a task as ‘Blocked’ until the printer sends proofs.

What if a task depends on multiple clients?

Create a separate task for each dependency and link them in the notes. Example: ‘Task 1: Draft proposal (depends on Client A’s brief). Task 2: Finalize proposal (depends on Client B’s feedback).’ Use the ‘Blocked’ tag for both until all dependencies are resolved.

How do I handle last-minute changes to dependencies?

In Calendar view, drag the dependent task to a new date. Example: If Client B’s feedback is delayed by 3 days, move Client A’s task from June 13 to June 16. Use reminders to follow up with Client B.

Can I automate task creation for dependencies?

Yes, with Ráfaga (Plus plan). Dictate multiple tasks at once, and Foco will split them and set dependencies. Example: Say ‘Task 1: Review Client B’s brief, due June 5. Task 2: Design Client A’s banner, depends on Client B’s review, due June 10.’ Foco creates both tasks with the dependency pre-filled.

How do I avoid mixing up deadlines for different clients?

Use color-coding (each client’s tasks have a unique color) and filters. In Panorama mode, filter by client or tag (e.g., ‘Urgent’) to focus on one workflow at a time. For a detailed guide, see [how to organize tasks by client without mixing deadlines](p/step-by-step-guide-to-organizing-tasks-by-client-in-a-task-app-without-mixing-deadlines).