Workflows - Task Batching & Approval Gates

    Last updated: March 19, 2026

    1. What Is Task Batching?

    Summary

    Task batching groups related tasks into a single Cole workflow, reducing agent spin-ups and saving credits.

    Task batching is a workflow strategy where you combine multiple related tasks into one Cole session instead of running them individually. When tasks share context - such as the same data source, brand voice, or objective - Cole can process them together far more efficiently.

    Example: Instead of creating three separate tasks - "Write a LinkedIn post," "Draft an email newsletter," and "Create an Instagram caption" - you create one task: "Create social content for our product launch." Cole plans all three as subtasks within the same workflow.

    Learn more about Cole's auto-planning →

    2. How Batching Saves Credits

    Summary

    Batching can save up to 40% on credits by sharing context, reducing agent spin-ups, and eliminating redundant processing.

    Every time an agent starts a new task, it consumes credits for initialization, context loading, and execution. Batching reduces this overhead in three ways:

    1. Shared context - Agents load your data, brand guidelines, and preferences once instead of repeating it for every task.
    2. Fewer spin-ups - Instead of initializing the same agent three times, Cole assigns it once and feeds it multiple subtasks sequentially.
    3. Coherent output - Batched tasks produce consistent results because agents retain context across subtasks, which also means fewer revision cycles.

    💡 Pro Tip

    Group tasks by shared inputs - same data source, same audience, or same campaign. The more context overlap, the greater your savings.

    View your credit balance and usage →

    3. What Are Approval Gates?

    Summary

    Approval gates are human-in-the-loop checkpoints that let you review, edit, or reject agent work before it's finalized.

    Approval gates are checkpoints that pause a workflow and ask for your input before continuing. When Cole creates a plan or an agent produces output, an approval banner appears on the task card. You can:

    • Approve - Accept the output and let the workflow continue
    • Edit - Modify the output or plan and then approve the updated version
    • Reject - Send the task back for the agent to retry with your feedback

    Approval gates ensure that credits aren't wasted on redundant retries or incorrect outputs. By catching issues early, you prevent agents from continuing down the wrong path.

    See Cole's approval flow in detail →

    4. Configuring Approval Levels

    Summary

    Set approval requirements by risk level - auto-approve low-risk actions and require manual review for high-risk ones.

    Not every action needs manual approval. You can configure approval levels based on the risk and impact of each action:

    • Auto-approve (low risk) - Routine actions like generating draft content, formatting data, or running research queries. These proceed without pausing.
    • Notify + auto-approve (medium risk) - Actions like sending internal summaries or updating spreadsheets. You get a notification but the workflow continues.
    • Require approval (high risk) - Actions like publishing content, sending emails to customers, or making API calls to external services. These always pause for your review.

    💡 Pro Tip

    Start with all actions requiring approval. As you build trust with specific agents, gradually auto-approve their low-risk actions to speed up workflows.

    Learn more about agent configuration →

    5. Batching + Approvals Together

    Summary

    Combine task batching with strategic approval gates for maximum efficiency and control over your AI workflows.

    The most efficient workflows combine batching with approval gates. Here's how it works in practice:

    1. You create a batched task with multiple related subtasks
    2. Cole plans the workflow and assigns agents
    3. You approve the plan (one approval for all subtasks)
    4. Agents execute low-risk subtasks automatically
    5. High-risk subtasks pause for your approval
    6. You review and approve final outputs

    This approach gives you the credit savings of batching with the safety net of approval gates - you stay in control without micromanaging every step.

    Best Practices Checklist

    • Group tasks by shared context (same campaign, data source, or audience)
    • Auto-approve drafts and internal content generation
    • Require approval for anything customer-facing or externally published
    • Review your approval settings monthly as you learn which agents you trust
    • Monitor your credit usage weekly to spot optimization opportunities

    Learn about multi-agent team workflows →

    Questions about this policy? Email us at support@pocodot.ai