005THE HINGE
Cheap to Make, Expensive to Check
A quarterly report arrives before the analyst has opened its source files. The draft is finished; the evidence still needs checking. That review belongs in the cost estimate.
THE GATE
Price a check that can reject the output.
- Compare the check with remaking the work
- Include generation, building and running checks, and likely repair
- Include normal review in the manual baseline too
The analyst compares a report row with its source and finds a mismatch. This check can stop that error; one caught example does not establish its reliability across other failures. Saad-Falcon and colleagues, §3, define a different generation-verification gap: a correct candidate exists among the responses, but the verifier fails to select it. That selection metric does not establish a business-cost inequality. Here the operator must test whether a relevant check catches consequential errors, then compare the whole offload with a manual baseline that includes its own review at the same required quality.
THE LAST THIRTY
The quick draft leaves finishing work.
In The 70% Problem, dated December 4, 2024, Addy Osmani describes a fast first pass followed by difficult integration and production work. Finishing the job can still require expert diagnosis. The curve sketches rising cumulative effort; its unnumbered axes do not assign percentages to work, cost, or staffing.
- Scaffolding can arrive before correctness, security, and edge cases are resolved
- The 70/30 split is a heuristic, not a measured ratio
Include review in the cost estimate.
For a claim in the quarterly report, the analyst may need to reconstruct the calculation and read the underlying records. That work counts even when the draft took seconds. If checking already costs as much as remaking, generation and repair cannot be treated as a saving.
WHERE ORACLES LIVE
A useful check has a bounded question.
- AlphaEvolve: run proposed programs and score specified objectives
- GNoME: calculate predicted crystal stability
- AlphaProteo: measure binding to specified targets
AlphaEvolve uses automated program evaluators. GNoME uses density-functional calculations in its crystal discovery pipeline; computational stability alone does not establish that a material can be synthesized or will be useful. AlphaProteo tests designed binders in the laboratory; binding alone does not establish a medicine. These are different kinds of verifiable space, with different costs. The operator must match the tested property to the decision.
TWO STUDIES, TWO SETTINGS
Measure the workflow you intend to change.
- Support: about 15% more issues resolved per hour
- Developers: 19% more completion time in a historical trial
The published Generative AI at Work, QJE (2025), studied 5,172 support agents at one firm during a staggered assistant rollout. Its adjusted estimate was about 15% more issues resolved per hour. METR's early-2025 randomized trial covered 16 experienced developers and 246 tasks in familiar repositories, primarily with Cursor and Claude 3.5/3.7 Sonnet. AI access increased estimated completion time by 19% (95% CI: +2% to +39%); developers' post-study estimate was a 20% reduction. The time result adjusts self-reported active implementation time before and after pull-request review for task difficulty. Neither study isolates verification cost or explains the other's result. METR's February 2026 update identified selection and timing problems that prevent a reliable current estimate from its later experiment. Its May 2026 survey measures reported perceptions separately. Felt speed needs a local baseline before it enters the cost estimate.
THE SHELF
A cheap tie-out cannot certify the whole report.
In the illustrative report, the analyst ties one balance to a bank statement. The agreement does not validate the explanation beside it. That claim may require several source files and a reconstructed calculation. The paths have different checking demands; their cost must be measured locally. The reverse-centaur problem also concerns authority: who may challenge the output, reopen a decision, and stop acceptance. Expensive review alone does not establish that the operator has lost those rights.
- A bank tie-out can test a stated balance
- A narrative claim may require rebuilding the evidence
- Estimate review cost for each consequential claim
BUILD THE CHECK
Set the criterion before inspecting the draft.
- 01Record the source, threshold, owner, and stop rule in advance
- 02Use model criticism to find questions worth testing
- 03Give reviewers the access and authority their role requires
Precommitment makes an acceptance rule harder to move after seeing a convenient result. Scheel, Schijen and Lakens (2021) found author-reported full or partial support for the first hypothesis in 146 of 152 standard reports (96%) and 31 of 71 Registered Reports (44%), using the first preregistered hypothesis for the latter. These were the study's own comparison groups, not a causal experiment; formats, hypotheses, authors, and unblinded coding could affect the difference. The operator's proposed adaptation is to seal the criterion, challenge the draft, and verify the resulting questions against evidence. A fresh prompt or model does not create independent assurance. Under the IIA's July 2026 position, an assurance role needs appropriate scope, access, reporting, resources, and safeguards against conflicts. Hiring an outsider alone is insufficient; the Three Lines Model keeps accountability with the organization.
DIRECTOR OR LIMB
Give the owner a reason to stop.
- Output: the quarterly report's stated balance
- Source: the bank statement for the same account and date
- Threshold: agreement to the declared reporting precision
- Owner: the analyst responsible for resolving discrepancies
- Stop rule: hold acceptance when the balance fails to reconcile
Test this check with plausible mismatches, including wrong dates and missing entries. In the example, the trial report fails the agreed comparison and the owner holds it. That demonstrates the stop rule; more failure testing is needed before relying on the check. Count a saving only with evidence of check reliability appropriate to the risk, and when generation, review, and likely repair together beat the manual baseline at the required quality. Otherwise improve the check, narrow the task, or retain the work.