Preview: not announced. Search engines asked not to index.

Proposal pack · RO-LD03-07 v1

Is the time AI saves paid for with weaker checking?

To keep this as a PDF or print it, use your browser's Print command (Ctrl+P, or Cmd+P on a Mac) and choose "Save as PDF". Links print with their addresses. This pack gathers what the opportunity page already holds; nothing in it is new.

Read this first. This is a research hypothesis drafted by Claude (SocioLens Project Lead), AI-drafted from the LD-03, LD-05 and LD-04 debates on 16 October 2026, not a finding. Not yet reviewed. Every check so far was done by AI; no person or domain expert has checked it yet. The literature screen below was done by AI web search and can miss relevant work. Version v1, permanent address https://sociolens-web.pages.dev/opportunities/ro-ld03-07/v1/.

Causal mechanism not isolated Funded team project Needs a budget (medium or higher) No study found

Research question

Where public services and clinics turn the time saved by generative-AI drafting into higher caseloads (social-work case records, clinical notes), does the time spent checking each output fall and the share of errors that survive into the signed record rise, and how much of any rise comes from time pressure rather than from a decline in the checkers' own skill?

Why it matters

Three debates measure the same minutes from different sides. LD-03 finds that checking and repairing AI output absorbs part of the measured gain. LD-05 finds that a human reviewer does not by itself give meaningful oversight, and that AI transcription in social care moves checking work onto social workers. LD-04 reports one observational case, from AI-assisted colonoscopy, in which experienced endoscopists detected fewer adenomas without AI after its introduction; its authors list a near doubling of colonoscopy volume among the study's limitations, so workload and loss of skill cannot be told apart there. If organizations bank saved time as more cases per person, the check that is meant to make AI output safe gets less time, so the time saving and the safety of the record may trade off. No debate can say whether the trade-off is real, or whether it runs through workload or through skill.

The debate lists this among what we still do not know: How much of the measured gain is spent on checking and repairing AI output elsewhere in the organization?

Evidence that motivates it

  1. In a case study of three German organizations, generative AI was used mainly as a personal assistant rather than changing team processes, the effort of validating its output partly offset efficiency gains, and policies written in response to regulation without regard to actual use led to gaps between policy and practice and to shadow IT. (LD03-SL-C08 v1.0)
    In three German organizations, the effort of validating generative-AI output partly offset the efficiency gains.
    Cites: Neumann et al. (2026), “Between Policy and Practice…”
  2. On 18 real tasks from two open-source repositories, an AI agent's code passed the maintainers' tests 38% of the time, but none of the 15 pull requests METR reviewed by hand could be merged as is; METR roughly estimated 26 minutes of human repair even for those that passed, about a third of the original human time. (LD03-SL-C12 v1.0)
    Even agent-written code that passed tests needed about 26 minutes of human repair, a third of the original human time, on METR's rough estimate.
    Cites: Rein (2025), “Research Update: Algorithmic vs. Holistic…”
  3. Qualitative evidence from UK social care shows that generative-AI transcription and summarisation can introduce hallucinations, omissions and changes in wording into official records, shifting checking and accountability work onto social workers. (LD05-HQ-C16 v1.0)
    In UK social care, AI transcription and summarisation can put hallucinations, omissions and changed wording into official records and shift checking work onto social workers.
    Cites: Bruff & Groves. “Scribe and prejudice?” Ada Lovelace…
  4. The presence of a human reviewer does not establish meaningful oversight; effective discretion depends on what the human can see, whether they can depart, how often they do so, and the organisational cost of disagreement. (LD05-HQ-C01 v1.0)
    Whether a human reviewer gives real oversight depends on what they can see, whether they can depart and the organisational cost of doing so; treating time to check as one such condition is a SocioLens reading, not part of the claim.
    Cites: Cross-case synthesis of Poland; Allegheny; DWP; Austria…
  5. In an observational study at four Polish centres, experienced endoscopists’ adenoma detection in colonoscopies done without AI fell from 28.4% to 22.4% in the three months after an AI detection system was introduced; the study is observational, and its authors list differences between the cohorts and a near doubling of colonoscopy volume after AI was introduced among its limitations. (LD04-SL-C14 v1.0)
    The one observational case where workload and skill are confounded. Experienced endoscopists' unaided detection fell after a detection aid (not a time-saving tool) was introduced; the authors list a near doubling of volume among the limitations, and the claim does not license causal deskilling.
    Cites: Budzyń et al. (2025), “Endoscopist deskilling risk after…”

Claims are shown as they read on the day this pack was built; claim pages keep every earlier version.

A possible design

Use a staggered rollout of an AI drafting or detection tool across teams or sites (for example local authorities adopting AI transcription in social work). For each team, record caseload per worker before and after; measure checking time per output from edit logs; and audit a random sample of signed records against the recorded conversation (with consent) for invented content, omissions and changed meaning. To separate workload from skill, give the same checkers periodic standardized review tasks with planted errors under a fixed time allowance, so that a decline under fixed time indicates skill and a decline only at real caseloads indicates time pressure. Compare teams whose saved time was turned into more cases with teams where caseloads were held constant.

Data needed

Caseload and edit-log data from the deploying organizations; consented recordings or reference transcripts for an audit sample; a set of standardized review tasks with planted errors; ethics approval covering people who draw on care or patients.

Feasibility

Funded team project. Medium; record audits against recordings and repeated standardized tests need trained coders and organizational partners over at least a year. Access depends on councils or hospitals agreeing to share caseload and edit data and to hold some caseloads constant; a smaller version can run in one organization with a before-and-after comparison and the standardized tests alone.

Has this been done?

The search found no study that does the core design (first-pass screen of 16 October 2026; not yet checked in depth).

Error rates in AI-drafted records, time savings from AI scribes and transcription, and automation complacency under workload have each been studied, and one audit found that the error rate it measured moved sharply with the instruction given to its own reviewer. One council's adoption is presented by the vendor as growing caseloads without more workload. No study was found that measures, in the same deployment, whether saved time becomes caseload, whether checking time per output falls and whether more errors survive into signed records, or that separates time pressure from checkers' skill. The search was web-based and partial.

Where the search could not reach. Screened by three web searches and an arXiv record on the date shown; clinical and social-work databases were not searched, and the human-factors literature on complacency is large and was not reviewed. Absence of a hit is not proof that the work does not exist.

Before building a project on it, run your own search in a scholarly database such as Scopus, Web of Science, Google Scholar or SSRN.

Nearest work found

References

Sources behind the motivating claims:

BibTeX

The first entry cites this opportunity; then its nearest work; then the sources above. Nearest work and sources are recorded as reference strings, so each goes in whole as the title; add authors and year from the original before you cite it.

@misc{sociolens_ro_ld03_07_v1,
  author = {{SocioLens project}},
  title = {Is the time AI saves paid for with weaker checking?},
  year = {2026},
  date = {2026-10-16},
  howpublished = {\url{https://sociolens-web.pages.dev/opportunities/ro-ld03-07/v1/}},
  note = {Research opportunity RO-LD03-07, version v1}
}

@misc{ro_ld03_07_nearest_1,
  title = {Fox, Markham, Lail and Karotsieris, "One note in three: a verified census of three deployed AI scribes, and the instrument that counted it", arXiv:2608.31017 (2026)},
  url = {https://arxiv.org/abs/2608.31017},
  note = {Reference as recorded by SocioLens; authors, title and year are not separated; Judged from an abstract, summary or search listing only}
}

@misc{ro_ld03_07_nearest_2,
  title = {Local Government Association, "Kingston Council - Using AI in Adult Social Care administration" (case study)},
  url = {https://www.local.gov.uk/case-studies/kingston-council-using-ai-adult-social-care-administration},
  note = {Reference as recorded by SocioLens; authors, title and year are not separated; Judged from an abstract, summary or search listing only}
}

@misc{ro_ld03_07_nearest_3,
  title = {Beam, "How Kingston Council managed to grow caseloads without increasing workload" (vendor case study)},
  url = {https://beam.org/case-studies/kingston-and-beam-case-study},
  note = {Reference as recorded by SocioLens; authors, title and year are not separated; Judged from an abstract, summary or search listing only}
}

@misc{ro_ld03_07_nearest_4,
  title = {Parasuraman and Manzey, "Complacency and Bias in Human Use of Automation: An Attentional Integration", Human Factors 52(3), 2010},
  url = {https://doi.org/10.1177/0018720810376055},
  note = {Reference as recorded by SocioLens; authors, title and year are not separated; Judged from an abstract, summary or search listing only}
}

@misc{src_sl_neumann_et_al_xp_2026,
  title = {Neumann, Bischof, Hinz et al., “Between Policy and Practice: GenAI Adoption in Agile Software Development Teams,” XP 2026, LNBIP},
  url = {https://doi.org/10.1007/978-3-032-22375-3_18},
  note = {Reference as recorded by SocioLens; authors, title and year are not separated}
}

@misc{src_sl_rein_metr_algorithmic_holistic_2025_08_13,
  title = {Rein, “Research Update: Algorithmic vs. Holistic Evaluation,” METR, 13 August 2025},
  url = {https://metr.org/blog/2025-08-12-research-update-towards-reconciling-slowdown-with-time-horizons/},
  note = {Reference as recorded by SocioLens; authors, title and year are not separated}
}

@misc{src_ld05_bruff_groves_ada_2026,
  title = {Bruff \& Groves. “Scribe and prejudice?” Ada Lovelace Institute, 11 February 2026},
  url = {https://www.adalovelaceinstitute.org/report/scribe-and-prejudice/},
  note = {Reference as recorded by SocioLens; authors, title and year are not separated}
}

@misc{src_r04_hq_cross_case_oversight_synthesis,
  title = {Cross-case synthesis of Poland; Allegheny; DWP; Austria; Ada Lovelace social-care evidence},
  note = {Reference as recorded by SocioLens; authors, title and year are not separated}
}

@misc{src_sl_budzyn_et_al_lancet_gh_2025,
  title = {Budzyń et al., “Endoscopist deskilling risk after exposure to artificial intelligence in colonoscopy: a multicentre, observational study,” Lancet Gastroenterology \& Hepatology 10(10), 2025},
  url = {https://doi.org/10.1016/S2468-1253(25)00133-5},
  note = {Reference as recorded by SocioLens; authors, title and year are not separated}
}

Back to the opportunity · All research opportunities