Docsumo in Structured Document Extraction
Scenario-level performance from current published Results.
6 of 20 scenarios published
Docsumo passed every graded scenario it has a published Result for.
How Docsumo performed
Open a capability to explore its scenarios. Each row reports the test set in its published Result.
Field Extraction1 pass4 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The field is absent | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedDocsumo passed this scenario: it returned an honest null for an absent field instead of inventing a value, and the empty field had no source pointer. In the same run, the receipt number, subtotal, tax, and total stayed correct. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The same field across layouts | No published result | ||
| The value is directly available | No published result | ||
| The value must be derived | No published result | ||
| The value needs a supplied definition | No published result | ||
Nested & Repeated Fields2 pass2 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A repeated set of records | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedDocsumo extracted the invoice’s three line items with the right values attached to each item. It excluded the subtotal, VAT and total rows from the extracted set. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The set is legitimately empty | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedDocsumo passed this empty-set extraction case. The page said no damage or exceptions were reported, and the extracted table came back with zero rows in both the saved JSON and the Results panel. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| The set contains a non-record | No published result | ||
| The set continues across a page break | No published result | ||
Review and Correction2 pass1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Corrected data goes downstream | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedDocsumo kept the correction in the delivery path for this case. The spreadsheet and JSON export both show the corrected receipt number and matching money fields, while the source receipt shows the earlier number. One observation notes the spreadsheet stores total_due as a float. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Repair a record | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedDocsumo repaired the record by adding one line item and removing another. After saving, reloading, and reopening, the stored set and the export matched on the new Concrete mixer row, the missing Site fencing row, and the unchanged header and totals. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Correct a field value | No published result | ||
Source Grounding1 pass1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| The field is absent | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedDocsumo passed this scenario: it returned an honest null for an absent field instead of inventing a value, and the empty field had no source pointer. In the same run, the receipt number, subtotal, tax, and total stayed correct. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Trace a value to its location | No published result | ||
OCR2 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A cleanly scanned document | No published result | ||
| A document mixing digital and scanned pages | No published result | ||
Querying3 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Aggregate across documents | No published result | ||
| Filter records across documents | No published result | ||
| The answer was never in the schema | No published result | ||
Training1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A field the tool can only get right from examples | No published result | ||
Reading these Results
Published evidence and test coverage answer different questions.
Which scenarios have a Result?
A published Result is public evidence for this tool on one scenario. “No published result” does not say whether testing has taken place.
What does each Result cover?
Assessed includes Pass, Fail and Not gradable. Gradable includes Pass and Fail. Both use the pinned test count in that published Result.
Out of 19 scenarios
The summary counts each of the 19 scenarios once. A scenario fails when any of its published test cases failed. “No published Result yet” means nothing is public for that scenario; it does not say whether Docsumo was tested on it.