A counterparty who uses LLMs to generate changes, documents, and requests has a throughput you cannot match by hand. If they then forbid you from using LLMs to review that same work, they have not raised the quality bar; they have rigged the queue. You will fall behind, and the falling behind is the point.
The Setup #
The pattern is specific. On their side, a model drafts the pricing changes, the proposals, the redlines, the spec revisions, the follow-up questions, faster and in greater volume than any human would produce alone. On your side, the same work arrives as items to read, reconcile, and answer. And somewhere in the engagement letter, the process doc, or the spoken rule, there is a line: review must be human, no AI.
The asymmetry is not accidental. One side of the pipeline is unbounded. The other is capped at the speed of a single person reading.
The rigged pipeline looks like this:
The Math Is the Problem #
Review is a queue. Items arrive at the producer’s production rate and leave at your review rate. If production rate exceeds review rate, which it must when one side uses a model and the other does not, the queue grows without bound.
The only tool that could lift your review rate to match is the one being banned. A model can triage a hundred documents, flag the three that matter, and summarize the rest in the time it takes you to open the first one. That is exactly the capacity the rule removes from your side. Forbid the reviewer’s LLM and you have not protected quality; you have guaranteed the reviewer loses the race.
This is not a question of effort or discipline. No amount of reading faster, staying later, or caring more will close a gap between a human’s reading speed and a machine’s generation speed. The two rates are different categories.
The Rule Is Never Applied to Production #
Every time I ask what justifies the rule, I get the same reasons. Quality. Confidentiality. “I want a real human looking at this.” Trust.
None of those reasons are applied to the producer. If quality required a human, the producer’s output would be human-written too. If confidentiality forbade a model, it would forbid the model on both sides. A rule that binds only the reviewer is not a rule about quality; it is a rule about leverage.
The tell is the asymmetry itself. A counterparty who genuinely believed human attention was the safeguard would insist on it for the work they send you, not only for the work you send back. When the standard runs in one direction, the standard is a tactic.
Flood Is an Old Tactic; LLMs Made It Cheap #
Overwhelming a reviewer with volume is one of the oldest leverage moves in negotiation and review. Bury the clause, exhaust the reader, let fatigue do the accepting. It used to cost real effort to produce that volume, which capped the abuse.
LLMs removed the cap.
Producing fifty variations, fifty justifications, and fifty follow-up questions now costs minutes and cents.
The producer can flood at marginal cost while demanding the reviewer meet each item with marginal human effort.
That is not a process; it is a denial-of-service on your attention, presented as a quality standard.
What Review Becomes on a Flood #
Once the queue exceeds what a human can read carefully, the review degrades in one of two directions, and both favor the producer.
You triage, skimming for flags, and the unflagged majority passes unread. Or you tire, and you rubber-stamp. Either way, the work ships with less scrutiny than a smaller, human-paced batch would have received. The flood does not get reviewed more rigorously for being human-reviewed; it gets reviewed less, because humans have a finite attention budget and the producer is spending it for them.
The irony is precise. The rule meant to guarantee careful human review is the rule that guarantees there is not enough human attention to go around.
Push Back on the Symmetry #
The fix is not to read faster. It is to refuse the asymmetric pipeline.
If they produce with a model, you triage with one, or the queue is illegitimate. Say it out loud, early, before the volume arrives. A review process is only fair when both sides have comparable tools on the queue.
Make the producer carry the cost of their own volume. Require a summary with every batch, written by them, stating what changed and what it means. Require structured, machine-checkable submissions instead of free-form documents. Cap the intake per day the way you would cap any rate-limited service. If the volume is genuine, the producer can absorb the cost of making it reviewable; if it is tactical, the requirement exposes the tactic.
And if the rule forbidding your LLM is non-negotiable, name it for what it is. It is a one-sided throttle, and agreeing to it is agreeing to lose on the schedule.
The Principle #
Review is not a virtue test. It is a throughput match between two sides of a pipeline. Whoever sets the tooling asymmetry sets the outcome, and a reviewer forbidden the only tool that matches the production rate has already lost.
See also #
- Keeping Up With AI Is a Losing Strategy - the same production-versus-consumption asymmetry, applied to reading the field; this piece applies it to a single adversarial counterparty
- Rethinking Code Review in the Age of LLMs - why line-by-line review of machine-generated work is low-leverage, the exact assumption the flood-and-forbid tactic exploits
- The Acceptance Gap - why “produced” is not “accepted”; the gap is precisely where a flood-and-forbid tactic hides items you never truly reviewed
- The Shifting Bottleneck - the constraint-moving pattern; here the bottleneck is deliberately pinned on the reviewer and frozen there
References #
Information overload - the long-standing name for the underlying problem, here weaponized rather than accidental