Per-action approval feels safe. At seven actions it already isn't.
I run approval-gated agent work in production: every consequential send stops for a human decision. At one or two items, that is a safety mechanism. At 37 items — the real batch this pattern was built on — it becomes something else: a person tapping approve, approve, approve, attention thinning with every card, until the lock that was supposed to catch mistakes is rubber-stamping them.
The approval did not fail. The unit of approval did.
The batch is the unit
Batch approval changes what the human decides. Instead of 37 separate yes/no calls on items they cannot hold in their head at once, they get one review decision on a prepared queue:
- Compose everything first, approval-free. Drafts, posts, sends — built in full, sent nowhere.
- Suppress before anyone reviews. Dead addresses, duplicates, anyone who already replied or opted out — removed before the queue is shown, so human attention is never spent on items that should not exist.
- Present the queue as one decision. Every item listed with an honest one-line summary, the risk line stated up front, and the count exact.
- Verify before executing — the Dive. A sample drawn by rule, not by choice, read in full. A failed dive pauses the whole queue, not just the item.
- Execute exactly what was approved. Approved 30 of 37? Send exactly 30. Partial approval is a normal outcome, not an error.
- Reconcile against ground truth. Sent folder, not memory. Numbers first in the report, or it didn't happen.
What batching does not do
Batching does not remove the human. It moves the human to the one place their judgment actually scales: reviewing a prepared, suppressed, sampled queue — instead of interrupting them 37 times and calling the interruptions safety.
And batching without verification is just a faster rubber stamp. The Dive is not optional decoration on this pattern; it is the step that keeps the batch honest.
The payoff, stated plainly
37 interruptions became 1 review decision. The cost was preparation: composing in full, suppressing first, and spending about twelve minutes on dives for a 30-item batch. Price one wrong send — to the wrong stranger, with the wrong fact, under your name — and preparation is the cheapest stage in the system.
I'm Veronica Stewart. I run approval-gated agent operations and write up the patterns that survive production. This piece is the written sibling of my Short "Stop Approving One by One. Batch It." on my channel: https://www.youtube.com/channel/UCKUmmgexgrWNK18i32eE0GA — watch the Short here: https://www.youtube.com/shorts/tartUWmzUMw — the pattern's verification step is a 43-second video here: https://www.youtube.com/shorts/YnqrBoIpgKs
The full pattern — compose, suppress, present, dive, execute, reconcile, plus templates and an audit checklist — is in my guide Approval-Locked. Chapters 1 and 3 are free: https://veronique2320.gumroad.com/l/sffdfk — and the full book ($19) is here: https://veronique2320.gumroad.com/l/approval-locked
Field notes like this, as they land: https://operatorfieldnotes.beehiiv.com
Start here for the whole set: https://dev.to/veronicstewart/start-here-agent-operations-that-survive-production-4hm6
