Batching for freelancers with multiple clients: how to group similar tasks and reclaim hours each week

Batching for freelancers with multiple clients isn’t just another productivity hack—it’s a lifeline when you’re juggling projects, deadlines, and competing priorities every hour. Every time you switch from reviewing a client’s design to answering an email from another, you lose up to 23 minutes regaining focus, according to University of California research. If you manage three or four jobs at once, those minutes add up to hours wasted each week. The solution isn’t working harder; it’s grouping similar tasks to execute them in dedicated blocks. In this guide, we’ll show you how to apply batching in practice using Foco to organize your tasks by type, client, or energy level, turning your day into a sequence of productive blocks (without the mental overload of remembering what’s next).

What is batching, and why does it fail when you have multiple clients?

Batching involves grouping tasks that require the same type of effort, tools, or context, and executing them consecutively in a time block. For example: replying to all your clients’ emails in one session instead of jumping between them throughout the day. The problem for freelancers with multiple clients is that traditional batching assumes you work on a single project or role. When you’re alternating between graphic design for an e-commerce client, meetings with a development team, and invoicing for a local business, grouping by task type (e.g., "all emails") doesn’t always work: an email from Client A might require research, while one from Client B only needs a quick reply.

Effective batching for multiple clients isn’t about grouping by format, but by shared context: energy, tools, and deadlines.

The 3 mistakes that break your batching (and how to avoid them)

• Grouping only by task type (e.g., 'all emails'): If one email requires research and another just a two-line reply, the mental depth switch still exists. Solution: subdivide blocks by effort level (e.g., 'quick emails' vs. 'emails requiring research').
• Ignoring your energy levels: Making calls first thing when you’re most creative is a waste. Solution: assign batching blocks based on your energy cycle (e.g., analytical tasks in the morning, creative ones in the afternoon).
• Not syncing with client deadlines: If Client A needs a delivery today and Client B next week, grouping their tasks in the same block will lead to poor prioritization. Solution: use due dates to separate urgent from important tasks, even within the same task type.

How to apply batching in Foco: step-by-step

1. Create 'jobs' by client or task type (not by project)

In Foco, each job is a container with a name and a color. For batching, the key lies in how you define them. If you create a job per project (e.g., "Client X Website"), you’ll end up with dozens of tabs and lose the big picture. Instead, group by client (e.g., "Client A - Design") or by task type (e.g., "Invoicing and Payments"). This way, when you enter Focus mode (which filters tasks for a single job), you’ll only see what’s relevant for that block. For example:

• Job: Client A - Development (blue). Tasks: "Review pull request #42", "Document authentication API".
• Job: Client B - Content (green). Tasks: "Write batching post", "Edit social media images".
• Job: Administration (gray). Tasks: "Send invoice to Client A", "Update contract template".

This structure lets you switch contexts with one click: when you finish a development block for Client A, you close their tab and open the administration one, without distractions.

2. Use views to plan batching blocks

Foco offers three views to organize your tasks: List, Kanban, and Calendar. Each serves a different batching purpose:

• List view: Ideal for batching by deadlines. Group pending tasks into "Today", "This Week", or "Later". For example, if today’s block is "emails", filter by the #emails tag and sort by due date to see only those due today.
• Kanban view: Perfect for batching by status. Create columns like "To Do", "In Progress", and "Review", and drag tasks according to their phase. For example, in a "design" block, move all "To Do" tasks to "In Progress" and work only on those.
• Calendar view: Use it for batching by time blocks. Assign a due date with time and duration to each task (e.g., "Review Client B wireframes" from 10:00 to 12:00). This way, in the calendar, your batching blocks will appear as events, alongside your external meetings (if you sync Google Calendar or Outlook).

3. Tag tasks to filter by context (not just by client)

Tags in Foco are unlimited and color-coded. Use them to mark the context of each task, not just the client. For example:

• #emails: For tasks requiring email responses or sends.
• #calls: For meetings or phone calls.
• #research: For tasks needing information gathering.
• #creative: For design, writing, or brainstorming.
• #urgent: For tasks with tight deadlines (combine with the "Urgent" priority in Foco).

This way, when you want to do an email batching block, filter by the #emails tag and see only those tasks, regardless of the client. This is especially useful if you work with tools like Notion or GitHub: with Foco’s Copilot (Plus plan), tasks assigned to you in those platforms are automatically imported with tags like #github or #notion, ready to group.

4. Schedule batching blocks with due dates

In Foco, each task has two dates: due date (when you’ll work on it) and deadline (the final due date). For batching, the due date is key: it lets you assign a specific time block to a group of tasks. For example:

• Monday 9:00-11:00: #emails block (due date: today at 9:00).
• Monday 11:30-13:00: #calls block (due date: today at 11:30).
• Tuesday 14:00-16:00: #creative block for Client B (due date: tomorrow at 14:00).

In the Calendar view, these blocks will appear as events, alongside your meetings. If you sync with Google Calendar or Outlook, you’ll see everything in one place, without overlaps. Pro tip: use the task’s duration to adjust the block. If an email task usually takes 20 minutes, assign it that time to avoid overloading the block.

5. Automate capture to avoid breaking your flow

Batching breaks when you have to stop to jot down a new task in the middle of a block. Foco solves this with voice capture and Rapid Fire (for dictating multiple tasks at once). For example, if you’re in a design block and remember you need to send an invoice, you dictate: "Send invoice to Client A, due date tomorrow at 10:00, tag #administration." Foco transcribes the audio, extracts the date and tag, and creates the task automatically. This way, you don’t lose the rhythm of the current block. For tasks that arrive via email, use email capture (Plus plan): forward the email to your personal address u-xxxx@in.heyfoco.com, and Foco will create a task with the email attached as a note.

Batching vs. the typical alternative: why Foco wins for freelancers

Most freelancers with multiple clients turn to one of these options to organize their tasks:

• Spreadsheets: One tab per client, with columns for task, deadline, and status. Problem: there’s no way to group tasks by context (e.g., "all emails"), and switching tabs is as slow as switching clients in your head.
• Generic note-taking apps: One note per project, with task lists. Problem: no due dates, priorities, or views like Kanban or Calendar. Batching becomes a memory exercise.
• Traditional project managers: Like Asana or Trello, designed for teams. Problem: they’re optimized for a single project. If you create a board per client, you end up with 10 open tabs and no big picture. If you use one board, tasks from different clients mix, making batching impossible.

Foco is designed for multiple jobs at once, not a single project. Its advantages for batching are:

• Color-coded jobs: Each task shows its job’s color, so you instantly identify which client it belongs to, even in Panorama mode (which shows all tasks together).
• Flexible views: Switch between List, Kanban, and Calendar based on the batching type you need, without losing data.
• Due dates: Schedule specific time blocks for each task group, something apps like Notion or Trello don’t allow without complex workarounds.
• Work tool integrations: With Copilot (Plus plan), tasks from Notion, GitHub, Jira, or Asana are automatically imported into Foco, with tags and dates. This way, your batching includes everything assigned to you, not just what you manually note.

If you manage multiple projects and want to reduce stress, also check out GTD for stress and multiple projects: how to maintain mental clarity under pressure.

Real example: a day of batching with Foco

Imagine you’re a freelance designer with three clients: a startup (Client A), an agency (Client B), and a personal project. Here’s how you’d apply batching in Foco:

• 8:30 - 9:30: #emails block (tag). Filter by #emails in List view and reply to all pending emails, regardless of client. Use voice capture to note new tasks that come up (e.g., "Review Client B feedback, due date tomorrow").
• 9:30 - 11:30: #creative block for Client A (job: "Client A - Design"). Enter Focus mode to see only their tasks and use Kanban view to move them from "To Do" to "In Progress".
• 11:30 - 12:00: #calls block (tag). Filter by #calls in Calendar view and have all meetings back-to-back, using listen mode to record and transcribe the call as a task note.
• 12:00 - 13:00: #administration block (job: "Administration"). Send invoices, update contracts, and review payments, using List view to see only what’s due today.
• 14:00 - 16:00: #research block for Client B (job: "Client B - Content"). Use List view to see tasks with today’s due date and the #research tag.

Batching isn’t about doing more in less time, but doing the same with fewer context switches and more focus.

Conclusion: batching as a lifestyle (not a trick)

Batching for freelancers with multiple clients isn’t a technique you apply one day and forget the next. It’s a mindset shift: from reacting to urgent tasks to designing your day in productive blocks. Foco gives you the tools to make it real: jobs by context, flexible views, due dates, and automation. But the real power lies in how you use it. Start with one type of batching (e.g., emails or calls) and add more as you gain confidence. Over time, you’ll notice that context switches no longer drain you, because each block has a clear purpose. And most importantly: you’ll reclaim those lost hours each week, not to work more, but to work better.

If you’re looking for alternatives to Asana’s free plan limits for managing multiple projects, check out our detailed comparison with Foco.

FAQ

Does batching work for all types of freelancers?

Yes, but the key is adapting it to your workflow. For example, a developer might group tasks by programming language (e.g., "Python block"), while a writer groups by content type (e.g., "blog post block"). The important thing is that tasks in the same block require a similar context.

How do I prevent one client from monopolizing my batching blocks?

Use due dates to distribute each client’s tasks across different days. For example, assign Client A’s design blocks on Mondays and Wednesdays, and Client B’s on Tuesdays and Thursdays. In Foco, filter by job and date to see only what’s relevant each day.

What if a task doesn’t fit into any batching block?

If a task is unique (e.g., "set up a domain"), assign it a tag like #miscellaneous and do it in a "miscellaneous tasks" block at the end of the day. In Foco, use List view to group all tasks with that tag and execute them consecutively.

Is batching useful for creative tasks or just administrative ones?

It works for both, but requires adjustments. For creative tasks, group by energy level (e.g., "brainstorming block in the morning") and use Kanban view to move tasks by phase. For administrative tasks, group by task type (e.g., "invoicing block") and use List view to see deadlines.

How do I apply batching if my clients assign me tasks in Notion or GitHub?

With Foco’s Copilot (Plus plan), connect your Notion, GitHub, and other tool accounts. Tasks assigned to you will be automatically imported into Foco with tags like #github or #notion, ready to group into your batching blocks. Learn more about how to sync tasks from Notion, Linear, and GitHub in one list.