Can Extend AI handle a document mixing digital and scanned pages?
Extend AI returned the requested values from a document mixing digital and scanned pages. The decision-relevant finding is that the image-only page was processed rather than skipped: the scanned-page values and the digital-page values both came back correct in one extraction call.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above counts this row.
Values on both digital and scanned pagesPassEvidence
{ "value": { "total_due": "£1,246.80", "received_by": "J. Whitlock", "vehicle_registration": "LR19 KVM", "line_item_description": "Dosing pump, 240V; Chemical feed tubing, 10m coil; Inline flow sensor" }, "metadata": { "total_due": {…}, "received_by": {…}, "vehicle_registration": {…}, "line_item_description": {…} } }
Transcribed from Proof 1 · Screenshot
These are scenario-level criteria. Each test case's Expected and Found are listed separately.
- Whether the scanned page inside a mixed document is processed rather than silently skipped.
- Whether page-by-page handling keeps content from both digital text pages and scanned image-only pages.
- Whether the system treats the document as mixed, not as a fully digital file with no special handling needed.
| ✓ | Found: All four requested values were returned correctly, with the digital-page and scanned-page values matching their sources. |
The extraction returned all four requested values correctly. The digital page supplied the invoice total and line items, and the image-only page supplied the recipient name and vehicle registration.
Three-page document mix. The file has three pages: digital, image-only, digital. That gives one scanned page and two digital pages for the split-value check.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the row says which and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the row says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | Structured Document Extraction → | 19 scenarios · 10 tools |
| Capability | OCR → | |
| Scenario | A document mixing digital and scanned pages → | |
| Tool | Extend AI → |
Global scenario definition → · Global capability definition → · Extend AI product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.