The screening desk closed thirty-one alerts on Tuesday; automation opened them and a human closed every single one. A tool that returns a list is not a decision and never has been, and the throughput number the vendor quotes is the arrival rate, not the resolution rate, which is the number the client is actually paying for.
This is where a hit becomes a decision. Is this the same person; if not, why not, in writing, on file, so the same question does not have to be re-answered the next quarter. If yes, at what tier, and what does that mean for the specific relationship in front of us.
Throughput is the trap; a tool can screen thousands of names an hour. A desk can honestly review a few dozen. Building a queue that respects our side's actual capacity, rather than the tool's marketing number, is most of the operational work.
A screening desk that runs alone eventually starts approving to keep the queue moving. The system is designed to make that failure mode visible early: unusually fast approval rates, dropping average review times, and thin file notes all trigger their own review before the client ever sees the output.
A tool that returns a list is not the same as a decision. Someone has to look at the list, understand what it means, and close the loop. The throughput of the screening layer is not set by the software; it is set by the human review capacity behind the software.
The general version is that automation moves the bottleneck rather than removing it. Anywhere you install a tool that returns candidates, the next scarce resource becomes the attention needed to sort them. Systems that don't budget for that attention fail without warning.