Evaluating human and LLM screening workflows in a conceptually complex scoping review: Recall--workload trade-offs and run-to-run consistency
Organizations: Institute of Psychology, Julius-Maximilians-Universität Würzburg, Würzburg, Germany
Abstract
Background. Large language models (LLMs) are increasingly used for screening in evidence synthesis, where false negatives can remove relevant studies before full-text assessment. We compared human and LLM title-and-abstract screening workflows in a preregistered study embedded in a conceptually complex scoping review. Methods. After a conservative title-only screen, 1,131 records were screened by one review lead, four trained assistants screening non-overlapping subsets, and seven complete LLM runs using different models and processing configurations, including a nominally identical repeat run. We compared retained workload, operational recall against 316 verified eligible records, agreement, run-to-run consistency, and procedural burden. Because eligibility was verified only for records advanced and assessed in the parent review, recall estimates were operational. Results. No workflow recovered all verified eligible records. The human workflows and two GPT-5.4 file-batch runs retained 42.2-45.0% of records while achieving 82.3-82.9% recall. Gemini 3.1 file batches achieved the highest recall (83.9%) but retained 56.7% of records. All-at-once configurations recovered fewer eligible records than corresponding file-batch configurations. Two nominally identical GPT-5.4 file-batch runs agreed on 91.7% of records but differed on 94 records, including 29 verified eligible records retained by only one run. Discussion. LLM screening performance depended on the implemented workflow, not model identity alone. Processing configuration, workload, record-level variation, and human-LLM decision integration are therefore substantive properties of deployed systems. For high-recall tasks, LLMs are better suited to validated, auditable, human-supervised workflows than autonomous exclusion.
Figures & tables
| Model | Date | Processing configuration | Role in study |
|---|---|---|---|
| ChatGPT 5.4 Thinking | March 17, 2026 | Files of approx. 100 records | Advancement workflow |
| ChatGPT 5.4 Thinking | March 17, 2026 | All 1,131 records at once | Comparative run |
| ChatGPT 5.4 Thinking | March 18, 2026 | Files of approx. 100 records | Nominally identical repeat of the March 17 file-batch workflow |
| ChatGPT 5.4 Thinking | March 19–24, 2026 | Sequential groups of 10 records | Exploratory comparative run |
| Gemini 3 Thinking | March 17, 2026 | Files of approx. 100 records | Advancement workflow |
| Gemini 3 Thinking | March 17, 2026 | All 1,131 records at once | Comparative run |
| RQ | Evaluation dimension | Outcome measures | Analytical set |
|---|---|---|---|
| RQ1 | Recovery and retained workload | Operational recall and missed eligible records quantified recovery of verified eligible records. Retained workload quantified the number of benchmark records retained for possible full-text assessment. | 316 verified eligible records; all 1,131 benchmark records |
| RQ2 | Agreement between screening outputs | Overall agreement, Cohen’s , Gwet’s AC1, and positive and negative agreement compared binary retained/not-retained decisions. | All 1,131 benchmark records |
| RQ3 | Conditional classification performance | Precision, specificity, and described classification performance among records with verified full-text outcomes. | 859 full-text-assessed records |
| RQ4 | Run-to-run consistency | The two nominally identical GPT-5.4 file-batch runs were compared using record-level agreement, retained workload, operational recall, missed eligible records, and discordant decisions. | All 1,131 benchmark records, including 316 verified eligible records |
| RQ5 | Missed-record patterns and retrospective checks | Record-level analyses examined overlap in missed eligible records, unique recovery, and records that alternative procedures would have advanced. Thirteen non-advanced records retained by the later sequential run were reassessed post hoc. | All 1,131 benchmark records, including 316 verified eligible records; 13 reassessed records |
| Explor. | Pairwise workflow complementarity | A liberal union rule quantified recovery and retained workload when a record was retained if either member of a workflow pair retained it. | All 1,131 benchmark records, including 316 verified eligible records |
| Workflow | Retained workload, (%) | Eligible retained, (%) | Eligible missed, (%) | Operational recall (95% CI) |
|---|---|---|---|---|
| Single reviewer | 477 (42.2%) | 262 (82.9%) | 54 (17.1%) | 0.829 (0.785–0.870) |
| Distributed team | 509 (45.0%) | 260 (82.3%) | 56 (17.7%) | 0.823 (0.778–0.864) |
| Gemini 3: file batches | 714 (63.1%) | 244 (77.2%) | 72 (22.8%) | 0.772 (0.725–0.816) |
| Gemini 3: all at once | 667 (59.0%) | 209 (66.1%) | 107 (33.9%) | 0.661 (0.608–0.715) |
| GPT-5.4: file batches | 493 (43.6%) | 261 (82.6%) | 55 (17.4%) | 0.826 (0.785–0.867) |
| GPT-5.4: all at once | 391 (34.6%) | 211 (66.8%) | 105 (33.2%) | 0.668 (0.614–0.718) |
| Workflow pair | Agreement, % (95% CI) | Positive agreement (95% CI) | Negative agreement (95% CI) | Cohen’s (95% CI) | Gwet’s AC1 (95% CI) |
|---|---|---|---|---|---|
| Human–human | |||||
| Single reviewer vs distributed team | 72.8 (70.2–75.3) | 0.688 (0.653–0.720) | 0.759 (0.732–0.784) | 0.447 (0.393–0.499) | 0.464 (0.413–0.516) |
| Single reviewer vs LLM | |||||
| Single reviewer vs Gemini 3 file batches | 55.0 (52.1–57.8) | 0.573 (0.539–0.605) | 0.525 (0.488–0.560) | 0.135 (0.083–0.187) | 0.102 (0.045–0.160) |
| Single reviewer vs GPT-5.4 file batches | 71.2 (68.4–73.8) | 0.664 (0.629–0.698) | 0.748 (0.720–0.773) | 0.412 (0.356–0.465) | 0.435 (0.380–0.488) |
| Distributed team vs LLM | |||||
| Workflow | FP | TN | Precision (95% CI) | Specificity (95% CI) | (95% CI) |
|---|---|---|---|---|---|
| Single reviewer | 178 | 365 | 0.595 (0.565–0.627) | 0.672 (0.634–0.711) | 0.693 (0.662–0.723) |
| Distributed team | 208 | 335 | 0.556 (0.527–0.585) | 0.617 (0.575–0.657) | 0.663 (0.633–0.692) |
| Gemini 3: file batches | 427 | 116 | 0.364 (0.346–0.381) | 0.214 (0.179–0.250) | 0.494 (0.470–0.518) |
| Gemini 3: all at once | 335 | 208 | 0.384 (0.359–0.409) | 0.383 (0.343–0.424) | 0.486 (0.453–0.518) |
| GPT-5.4: file batches | 202 | 341 | 0.564 (0.535–0.594) | 0.628 (0.587–0.669) | 0.670 (0.640–0.699) |
| GPT-5.4: all at once | 153 | 390 | 0.580 (0.543–0.617) | 0.718 (0.681–0.755) | 0.621 (0.583–0.658) |
| Workflow or reviewer | Records screened | Time, min | Min per record | Records per hour |
| Single reviewer | 1,131 | 1,176 | 1.04 | 57.7 |
| Distributed team, total | 1,131 | 1,628 | 1.44 | 41.7 |
| Assistant 1 | 300 | 418 | 1.39 | 43.1 |
| Assistant 2 | 331 | 505 | 1.53 | 39.3 |
| Assistant 3 | 200 | 300 | 1.50 | 40.0 |
| Assistant 4 | 300 | 405 | 1.35 | 44.4 |
Evidence Selection
Evidence selection chooses the documents, passages, claims, or observations that best support an answer or decision.
See all 61 papers