How to assign a batch of work without sharing the whole list

Managers often keep the full list in a spreadsheet and then copy subsets into Slack, email, or another tab. That works until someone pastes the wrong range, a formula breaks a filter, or a teammate opens the master file and sees everyone else's work.

BatchBrief is built around a simpler rule: one batch goes in, private lists come out. The assigner keeps the full picture. Each receiver logs in and only sees the rows assigned to them.

Start from the batch, not the person

Write the work as a list first — one item per line. That might be leads to call, pages to review, applicants to screen, or follow-ups that need a human. Do not start by creating a separate board per person. The batch is the source of truth; assignment is a second step.

When the list is in one place, you can split it evenly, send everything to one teammate, or leave items unassigned until you are ready.

Keep the full list on the assigner side

The person who owns the workspace should still see every row: status, assignee, and notes. That is how you catch stalled work without asking the team to report in. Receivers should not need the master list to do their job.

If you currently share a filtered Google Sheet, the failure mode is familiar: filters get cleared, tabs proliferate, and privacy depends on everyone remembering the process. Server-side assignment avoids that.

Leave items unassigned when you are not ready

You do not have to pick an owner on day one. Unassigned items still belong to the workspace. They show up in All Items, count toward the total, and can be assigned later. Skipping assignment is not the same as skipping the work.

A concrete next step

If you split inbound leads across a sales team, start with a short batch of account names, assign them, and confirm each person only sees their own list. The weekly outreach template in Resources is a paste-ready example of that workflow.