The Verification Tax: How Much Time Checking AI Output Really Costs (And How to Cut It)

TL;DR. The time AI saves you is a gross figure. The verification tax is what you pay back: reviewing, correcting and redoing the output, the expected cost of errors that get past you, and the cleanup others do on what you hand on. Large surveys put self-reported savings at 5.4 percent of users’ work hours in the US and 2.8 percent in Denmark, and neither reports checking time as a separate cost. Where work was measured directly, the tax could erase the gain: in METR’s 2025 randomised trial, experienced developers believed AI had cut their task time by 20 percent, yet their tasks took 19 percent longer, and 9 percent of their time went on reviewing and cleaning AI output. A Workday vendor survey reports that nearly 40 percent of AI time savings are lost to rework. The CEO move: budget verification as a real cost, tier it by stakes, detectability and reversibility, and drop AI where the break-even test is negative. The student move: record which errors each tool makes on your work, so the tax falls over time.

This piece is about the economics of checking, not the craft of it. For the craft, see the evaluation skill. For where checkpoints belong when an agent runs a multi-step job, see human-in-the-loop by design. And for why individual gains so rarely reach company results, see the AI productivity paradox.

What is the verification tax, and why is it so easy to miss?

Every AI-assisted task has two ledgers. The visible one records the drafting time you did not spend. The hidden one records four costs that most time-saved figures leave out:

1. Review time. Reading the output, comparing it with sources, running the code, checking the numbers.
2. Correction and redo time. Fixing what is wrong, re-prompting, or abandoning the AI version and doing the work by hand.
3. Residual error cost. The expected cost of mistakes that survive your check and surface later, when they are more expensive to fix.
4. Exported tax. The time colleagues, reviewers or customers spend repairing what you passed on.

Standard measurement is not built to see these costs. A widely used US estimate, from Alexander Bick, Adam Blandin and David Deming, asks users, in the authors’ words, “how many additional hours they would have needed to complete the same amount of work in the previous week if they had not had access to genAI.” That single counterfactual guess bundles drafting saved with checking spent and cannot include errors not yet discovered. Its answer, 5.4 percent of users’ work hours, or 2.2 hours a week at 40 hours, is gross by construction.

Perception widens the gap. In the METR trial, the distance between what developers believed afterwards (20 percent less time) and what was measured (19 percent more time) was 39 percentage points. A Microsoft Research survey of 319 knowledge workers, presented at CHI 2025, found that “higher confidence in GenAI is associated with less critical thinking.” The people most likely to under-check are those who trust the tool most.

What happens when the studies are put side by side?

The verification tax ledger below puts one study in each row and separates the gross gain, what the study reports about checking or rework, and the net result. Figures are as printed. Where a study reports nothing, the cell says so; the only calculations are ones where a single study supplies every input.

Study and design	Task	Gross gain, as printed	Checking or rework cost, as printed	Net result, as printed
Noy and Zhang, Science, 2023. Preregistered online experiment, 453 college-educated professionals	Mid-level professional writing	Time taken down 40%, output quality up 18%	2023 working paper version: editing share of task time more than doubled from about 25%; 68% of treated participants submitted ChatGPT’s initial output without editing	Large net saving, achieved with very little checking
Brynjolfsson, Li and Raymond, Quarterly Journal of Economics, 2025. Staggered rollout, 5,172 agents	Customer support	Issues resolved per hour up 15% on average	Not reported separately	Positive on average; the most experienced and highest-skilled agents saw “small gains in speed and small declines in quality”
Dell’Acqua et al., Organization Science, 2026. Preregistered experiment with Boston Consulting Group, 758 knowledge workers	18 realistic knowledge tasks inside the AI frontier, one managerial task outside it	Inside the frontier: 12.2% more tasks completed, 25.1% faster	Outside the frontier: 19% less likely to produce correct solutions	The tax was paid in wrong answers, not minutes
METR (Becker, Rush, Barnes, Rein), preprint, 2025. Randomised trial, 16 developers, 246 tasks	Real issues in mature open-source repositories the developers knew well	Forecast: 24% less time. Belief after the study: 20% less time	About 9% of time on AI-allowed issues spent reviewing or cleaning AI output (44 issues with labelled screen recordings), 4% waiting for generations; under 44% of generations accepted	Tasks took 19% longer (confidence interval +2% to +39%)
METR research note, February 2026. Same design, late-2025 tools, 10 returning and 47 new developers	Open-source development	Not reported	Not reported	Returning developers -18% time (interval -38% to +9%); new developers -4% (interval -15% to +9%). METR calls the signal unreliable because of selection effects
Tai-Seale et al., JAMA Network Open, 2024. Randomised waiting-list quality improvement study, 52 physicians plus 70 controls	Replying to patient messages with AI drafts	Hypothesis was less reading and reply time	Message read time up 21.8% (95% CI 5.2% to 41.0%)	Reply time -5.9% (not significant, P = .33); replies 17.9% longer
Garcia et al., JAMA Network Open, 2024. Five-week single-group quality improvement study, 162 clinicians	AI draft replies to patient inbox messages	Drafts used in 20% of replies (mean utilisation)	No change in read, write or reply time	No time saved; task load and work exhaustion scores fell
Humlum and Vestergaard, Becker Friedman Institute working paper, 2025. Survey of about 25,000 workers linked to Danish registers	11 occupations highly exposed to AI chatbots	Time savings of 2.8% of users’ work hours	New workloads for 12% of users even without employer initiatives (appendix estimate); 59% of new AI-related tasks are implementation and oversight, including quality review	Precise null effects on earnings and recorded hours, ruling out effects larger than 2%
Bick, Blandin and Deming, NBER working paper, 2025. Nationally representative US survey	All work	5.4% of users’ work hours (2.2 hours a week at 40 hours)	Not asked separately	1.4% of all workers’ hours, including non-users
Workday, company survey of 3,200 full-time employees fielded by Hanover Research in November 2025, published January 2026 (commercial)	Active AI users at organisations with $100M+ revenue	85% report saving one to seven hours a week	“Nearly 40%” of AI time savings lost to rework	Only 14% “consistently get clear, positive net outcomes”; about 60% of the saving retained (CEOtudent calculation from the 40% figure)

CEOtudent analysis of the ten sources named in the rows. Figures as printed; “not reported” where a source gives no figure. The Noy and Zhang editing figures come from the authors’ March 2023 working paper, which preceded the Science version and reported 444 participants; the Science abstract does not report the time breakdown. Dell’Acqua et al. and Brynjolfsson et al. figures are from the published abstracts. Workday’s full report sits behind a registration form and was not opened, so its method for the 40 percent figure could not be checked.

Three readings follow from the ledger.

The tax is smallest where checking is cheap or skipped, and largest where the human already knows the answer. In the Noy and Zhang working paper, on tasks the control group finished in about 27 minutes, most treated participants submitted the first output as it was. The saving was large, and almost no verification was bought. METR is the opposite case: repositories averaging 1,100,000 lines of code, very high quality bars, and a finding that “developers slowed down more on issues they are more familiar with.” One developer “wasted at least an hour first trying to [solve a specific issue] with AI” before reverting everything. When your own judgment is fast and your standard is high, checking the AI draft is expensive.

Time is only one of the currencies. Outside the frontier, Dell’Acqua’s participants paid in correctness, not minutes. The most skilled support agents paid a small quality cost. The physicians’ drafts lengthened reading time without shortening reply time. A ledger that tracks only minutes understates the tax where it matters most.

The tax is moving, and measuring it is getting harder. METR’s February 2026 note reports a later round in which the point estimate for returning developers showed AI-allowed tasks taking less time. It also calls its new data only very weak evidence: more developers declined to take part because they did not want to work without AI, and 30 to 50 percent said they withheld some tasks they did not want to do without it. Treat the 2025 slowdown as a dated measurement of early-2025 tools, and the improvement as encouraging but unproven.

Who actually pays the verification tax?

A time-saved figure is reported by the person who used the tool. Much of the tax lands elsewhere: on attention, on the colleague who receives the output, on job design and on the systems the output feeds.

Who pays	Finding, as printed	Source
The user’s attention	Generative AI “shifts the nature of critical thinking toward information verification, response integration, and task stewardship”; 114 of 319 workers verified by cross-referencing external sources, and 56 of 319 reported more effort in retrieval because “AI response can be wrong and needs verification”	Lee et al., CHI 2025 (Microsoft Research and Carnegie Mellon)
The user’s time	66% of developers cite “AI solutions that are almost right, but not quite” as a frustration; 45.2% say debugging AI-generated code is more time-consuming	Stack Overflow Developer Survey 2025 (company survey, commercial)
The user’s review load	77% of daily AI users review AI-generated work “just as carefully as work done by humans, if not more”	Workday press release, January 2026 (commercial)
The colleague who receives the work	40% of US desk workers received “workslop” in the last month; each incident takes about 2 hours to resolve; estimated cost $186 per employee per month	BetterUp Labs with Stanford Social Media Lab, survey of 1,150 workers, September 2025 (commercial)
The organisation’s job design	59% of new AI-related tasks relate to “AI implementation and oversight”; 5% of non-users report new workloads resulting from AI chatbots	Humlum and Vestergaard, 2025
The delivery system	Per 25% increase in AI adoption: an estimated 7.2% reduction in delivery stability and 1.5% reduction in throughput (2024). In 2025, AI adoption “now improves software delivery throughput” but “still increases delivery instability”	Google DORA reports, 2024 and 2025 (Google research)

Figures as printed in each source. The shares 114 of 319 (35.7 percent) and 56 of 319 (17.6 percent) are CEOtudent calculations from Lee et al.’s counts. The commercial surveys are self-reported and their full methods are not all published.

For anyone who manages people, the pattern is the point. Low-effort AI output moves the cost onto the recipient, who never appears in the sender’s time-saved figure. A team can report rising AI savings while total time per deliverable stays flat, because the tax has moved from the author’s column into the reviewer’s. DORA’s data show the same shape at system level: more throughput, less stability.

Why does skipping the check not make the tax disappear?

The obvious way to cut the tax is to check less. Research on automation bias says this converts a visible time cost into an invisible error cost.

Raja Parasuraman and Dietrich Manzey’s 2010 review in Human Factors concluded that automation bias “results in making both omission and commission errors when decision aids are imperfect” and “occurs in both naive and expert participants.” Complacency, they found, appears “under conditions of multiple-task load,” which describes most knowledge work. A 2012 systematic review by Kate Goddard and colleagues, which included 74 of 13,821 screened papers, lists workload, task complexity and time constraint among the factors that push people toward over-reliance.

The choice to check is also partly economic. Helena Vasconcelos and colleagues ran five experiments with 731 participants and argue that “people strategically choose whether or not to engage with an AI explanation,” weighing the effort of verifying against simply agreeing. When the reward for accuracy rose, over-reliance fell. Lee and colleagues saw the same logic at work: 44 of 319 workers cited lack of time for not thinking critically about AI output, and 55 of 319 skipped it because the task seemed trivial.

Under-checking therefore does not lower the verification tax. It defers it, moving it from a cost visible on your calendar to a probability invisible until the error surfaces. That is why the framework below prices residual errors explicitly.

How much checking does each task deserve? A CEOtudent editorial framework

The framework has two parts: a break-even test for whether AI is worth using on a task at all, and a tiered protocol for how much checking to buy when it is. It is built from the evidence above, not measured.

The break-even test. For any task you are about to hand to AI, estimate:

Net time saved = (time to do it yourself – time to prompt and generate) – checking time – fixing time – (chance the output contains a material error x chance your check misses it x cost if it gets through)

If the result is negative, do the task yourself or redesign it so checking gets cheaper. The last term is the one most people leave out: small when errors are cheap or visible, dominant when one missed error is expensive.

The tiered protocol. Score the task from 1 to 3 on each of three dimensions, then add the scores.

Dimension	Score 1	Score 2	Score 3
Stakes: what does a wrong answer cost?	Private draft or note	Internal decision or shared team work	External, financial, legal, safety or reputational
Detectability: how visible are errors on a normal read?	Visible on reading (tone, structure, obvious nonsense)	Need a source check (facts, figures, names, dates)	Silent (subtle logic, code that runs but is wrong, plausible citations)
Reversibility: how hard is it to undo?	Trivially undone	Costly to undo	Irreversible once sent, filed, merged or published

Total score	Tier	Check method	Typical tasks
3-4	Tier 1: skim	One read for sense. No source checks.	Brainstorm lists, first-pass outlines, rewording your own text
5-6	Tier 2: spot-check	Check every number, name, date and quotation; sample the remaining claims; run code once against a known case.	Internal summaries of material you supplied, meeting notes, routine emails
7-8	Tier 3: full review	Line by line against the sources; open every cited source; tests for any code.	Client-facing documents, decision memos, code that ships
9	Tier 4: independent recompute or second source	Rebuild key figures from the primary data yourself, or obtain an independent second answer and reconcile the two. Never accept the AI’s own summary of its sources.	Anything filed, published, contractual or financial

CEOtudent editorial framework. Tier boundaries and check methods are editorial judgment informed by the sources cited in this article, not measured thresholds.

Two error-rate anchors show why the top tier exists. In a preregistered Stanford evaluation, retrieval-based legal research tools each hallucinated “between 17% and 33% of the time,” counting responses that “falsely assert a source supports a statement.” Matthew Dahl and colleagues found general-purpose models hallucinated between 58 and 88 percent of the time on verifiable questions about federal court cases. The rates belong to 2023 and 2024 systems, but the principle holds: in some domains a citation is the thing to check, not proof that checking happened. The mechanics of why models produce such errors show where to look.

A worked example. The numbers below are invented for illustration, not drawn from any study. A market brief takes 120 minutes by hand. With AI, prompting and generation take 10 minutes. Assume one draft in five contains a material error.

Scenario	Checking	Fixing	Chance the check misses the error	Cost if an error gets through	Expected cost of missed errors	Net minutes saved
A. Internal brief, Tier 2 spot-check	20 min	10 min	40%	240 min (4 hours of internal cleanup)	19.2 min	+60.8
B. Same draft sent to a client, still spot-checked	20 min	10 min	40%	2,400 min (40 hours of rework and relationship repair)	192 min	-112
C. Client brief, Tier 4 independent recompute	60 min	15 min	5%	2,400 min	24 min	+11

Illustrative CEOtudent calculation using assumed inputs; see the formula above. Every value can be recomputed from the row.

The same draft is worth an hour inside the team and costs almost two hours when it reaches a client with the same light check. A heavier check rescues it, but only just: in scenario C, break-even is 71 minutes of checking. If a proper recompute takes longer, write the brief yourself and use AI only where errors are visible.

How do you cut the verification tax?

Each move lowers the cost of a check or raises the chance it catches something, and each is tied to evidence or labelled as editorial judgment.

1. Make errors visible before you read. Ask for claim-by-claim output with the source and supporting passage beside each claim. Vasconcelos and colleagues found that “explanations that make the AI’s mistake more obvious reduce overreliance more.” A cited source is still not a checked source: open it.
2. Check the error-prone parts first. Numbers, names, dates, quotations and citations carry the most risk per word. Dahl and colleagues found that models “perform better on cases that are newer, more salient, and from more prominent legal jurisdictions,” which points the check at obscure items, and that they “struggle to predict their own hallucinations,” so asking the model where it is wrong is no substitute.
3. Keep a personal error record by task type. A short log of what each tool got wrong, on which task, turns vague distrust into a targeted checklist and lets a task move down a tier once it has earned it; the method is in how to learn from AI mistakes. That this lowers checking time is editorial judgment, not a measured effect.
4. Decide the stakes before you read. Over-reliance fell as the reward for accuracy rose in the Vasconcelos experiments, and the Goddard review counts user accountability among the mitigators of automation bias. Name an owner for every AI-assisted deliverable and score its tier before opening the draft.
5. Do not export the tax. Anything at Tier 2 or above gets its check before it leaves your hands. Otherwise the cost lands on a colleague, as the BetterUp survey describes, and vanishes from your ledger but not from the team’s.
6. Stop using AI where the test comes out negative. METR’s developers slowed down more on the issues they knew best, and the Tai-Seale physicians read longer without replying faster. Where your judgment is quick and your standard high, doing it yourself can be cheaper; where that line sits is editorial judgment until your log says otherwise.

What does this mean for the CEO and the student?

The CEO side is budgeting. A chief executive does not accept a cost saving without asking what it cost to achieve. Estimate the tax by task class, log checking time for two weeks, and compare it with what AI saved. Workday’s survey suggests the gap can be wide: 85 percent of respondents reported saving one to seven hours a week, yet only 14 percent consistently got clear, positive net outcomes. Humlum and Vestergaard found that 80 percent of chatbot users redirect saved time to other job tasks, so the saving is reallocated without anyone recording whether it survived checking. A CEO also decides where not to compete: task classes that fail the break-even test stay human.

The student side is learning the tool’s failure patterns until checking gets cheaper. METR saw no clear learning effect across the first 30 to 50 hours of tool use, then positive speedup for the one developer with more than 50 hours, a result the authors call underpowered. The learning curve may be longer than people expect, which argues for deliberate error logging rather than waiting for familiarity to do the work. Re-test after major model updates: METR’s point estimates moved from slowdown to speedup between early and late 2025.

The verification budget check: seven questions before you hand work to AI

Two or more “no” answers mean the task should be redesigned, checked at a higher tier, or done without AI.

1. Do you know roughly how long this task takes you by hand?
2. Have you scored its stakes, detectability and reversibility, and picked a tier?
3. Will the output arrive in a form you can check quickly, with sources beside the claims?
4. Do you know which parts of this kind of output a tool usually gets wrong?
5. Is the checking time for that tier clearly smaller than the time AI saves?
6. If an error gets through, can you name who pays for it and roughly how much?
7. Will you record what the check found, so the next check can be lighter?

What this does not mean

It does not mean AI fails to save time. The ledger includes large, well-measured gains in writing, customer support and knowledge tasks inside the frontier. The tax is the price of those gains, not evidence against them.

It does not mean checking is waste. Paid at the right tier, verification is what makes the saving safe to keep.

It does not settle how big the tax is today. Most measured studies used 2023 to 2025 tools on specific tasks, METR warns its latest estimate is unreliable, and the commercial surveys are self-reported with methods not fully published. This article is general information about workplace research, not legal, medical or financial advice; the clinical and legal studies are cited only for what they measured about time and error rates.

Frequently asked questions

What is the verification tax?
The time spent reviewing, correcting and redoing AI output, plus the expected cost of errors that slip through and the cleanup others do on work you pass on. Most time-saved figures report the saving before this tax.

How big is the verification tax in practice?
It varies by task. In the writing experiment it was small, because most participants submitted the first output unedited. In METR’s 2025 trial it outweighed the gain, with 9 percent of time spent reviewing and cleaning AI output. Workday’s vendor survey puts rework at nearly 40 percent of time saved.

Is it better to check everything AI produces?
No. Full review on low-stakes, easily reversible work wastes the saving. Score stakes, detectability and reversibility, and match the check to the tier.

Why do people overestimate the time AI saves them?
Self-reports measure a felt saving, and people who trust a tool more check it less. METR’s developers believed AI had cut their task time by 20 percent when their tasks actually took 19 percent longer.

Does the verification tax fall as models improve?
Probably, but the evidence is thin. METR’s later round pointed to speedups while warning that selection effects make the estimate unreliable. Your own error log is the best measure of whether the tax is falling on your work.

Who should pay for checking in a team?
The author, before hand-off. When unchecked output is passed on, the recipient pays, and the author’s time-saved figure overstates the team’s real gain.

Sources

1. Becker, J., Rush, N., Barnes, B., Rein, D. (METR). Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity. arXiv 2507.09089, version 2, July 2025. Preprint.
2. Becker, J., Rush, N., Cunningham, T., Rein, D., Mahamud, K. (METR). We are Changing our Developer Productivity Experiment Design. METR research note, 24 February 2026.
3. Noy, S., Zhang, W. Experimental evidence on the productivity effects of generative artificial intelligence. Science 381(6654), 187-192, 2023 (abstract only, via PubMed).
4. Noy, S., Zhang, W. Experimental Evidence on the Productivity Effects of Generative Artificial Intelligence. MIT working paper, 2 March 2023, not peer reviewed.
5. Brynjolfsson, E., Li, D., Raymond, L. Generative AI at Work. Quarterly Journal of Economics 140(2), 889-942, 2025 (abstract only).
6. Dell’Acqua, F., McFowland, E., Mollick, E., Lifshitz, H., Kellogg, K. C., Rajendran, S., Krayer, L., Candelon, F., Lakhani, K. R. Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of Artificial Intelligence on Knowledge Worker Productivity and Quality. Organization Science 37(2), 2026 (abstract only).
7. Humlum, A., Vestergaard, E. Large Language Models, Small Labor Market Effects. Becker Friedman Institute Working Paper 2025-56, updated September 2025.
8. Bick, A., Blandin, A., Deming, D. J. The Rapid Adoption of Generative AI. NBER Working Paper 32966, revised February 2025.
9. Tai-Seale, M., et al. AI-Generated Draft Replies Integrated Into Health Records and Physicians’ Electronic Communication. JAMA Network Open 7(4), e246565, 2024.
10. Garcia, P., Ma, S. P., et al. Artificial Intelligence-Generated Draft Replies to Patient Inbox Messages. JAMA Network Open 7(3), e243201, 2024.
11. Lee, H.-P., Sarkar, A., Tankelevitch, L., Drosos, I., Rintel, S., Banks, R., Wilson, N. The Impact of Generative AI on Critical Thinking: Self-Reported Reductions in Cognitive Effort and Confidence Effects From a Survey of Knowledge Workers. CHI 2025, Microsoft Research.
12. Vasconcelos, H., Jörke, M., Grunde-McLaughlin, M., Gerstenberg, T., Bernstein, M. S., Krishna, R. Explanations Can Reduce Overreliance on AI Systems During Decision-Making. Proceedings of the ACM on Human-Computer Interaction 7(CSCW1), Article 129, 2023.
13. Parasuraman, R., Manzey, D. H. Complacency and Bias in Human Use of Automation: An Attentional Integration. Human Factors 52(3), 381-410, 2010 (abstract only).
14. Goddard, K., Roudsari, A., Wyatt, J. C. Automation bias: a systematic review of frequency, effect mediators, and mitigators. Journal of the American Medical Informatics Association 19(1), 121-127, 2012 (abstract only).
15. Magesh, V., Surani, F., Dahl, M., Suzgun, M., Manning, C. D., Ho, D. E. Hallucination-Free? Assessing the Reliability of Leading AI Legal Research Tools. arXiv 2405.20362, 2024. Preprint.
16. Dahl, M., Magesh, V., Suzgun, M., Ho, D. E. Large Legal Fictions: Profiling Legal Hallucinations in Large Language Models. Journal of Legal Analysis 16(1), 64-93, 2024.
17. DORA (Google Cloud). Accelerate State of DevOps Report 2024. Google research.
18. DORA (Google Cloud). State of AI-assisted Software Development 2025. Google research.
19. Stack Overflow. 2025 Developer Survey, AI section. Company survey (commercial).
20. Workday. New Workday Research: Companies Are Leaving AI Gains on the Table. Press release, 14 January 2026, on the survey report Beyond Productivity: Measuring the Real Value of AI. Company-reported (commercial); full report not opened.
21. BetterUp Labs and Stanford Social Media Lab. Workslop: The Hidden Cost of AI-Generated Busywork. Survey of 1,150 US desk workers, September 2025. Company-reported (commercial).

CEOtudent analyses in this article: the verification tax ledger (first table) and the payer table (second table) are CEOtudent compilations of figures as printed; the shares 35.7 percent and 17.6 percent, the 39-point perception gap and the 60 percent retained share are CEOtudent calculations from single sources (the 2.2-hour weekly figure is printed by Bick and colleagues and was rechecked); the break-even test, the tiered protocol and the seven-question check are CEOtudent editorial frameworks, and the worked example uses assumed, illustrative inputs. Deliberately not used: the Upwork Research Institute 2024 figures on AI adding to workloads (the primary page returned an access error and was not opened by other means); the minute-level per-incident workslop figure circulated from the Harvard Business Review articles, which were not opened (the BetterUp page that was opened prints “2 hrs”); and the quality-gain percentage widely quoted from the Dell’Acqua working paper, because the published abstract opened here says only “significantly improved quality.”

---

This content was compiled with the support of AI following in-depth research, then written and prepared for publication by the CEOtudent editorial team.

This post is also available in: