AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 20 November 2026

Can Landing AI add and remove members in a record?

Landing AI's review screen offered no way to add or remove a line item in an extracted invoice. An attempt to change the list drew the message 'Cannot edit in read-only editor', no add control appeared, and the list still held its original three line items afterwards.

1 of 1 test case failed

Every test case in this scenario has a result.

Pass rate0%0 of 1 gradable
Coverage1 of 1test case with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are with each test case below.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

The test case

Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.

Add one member and remove oneFailEvidence
What we sent

On the review screen of the saved extraction of the plant hire invoice, which listed three line items, we tried to remove the site fencing line and add a concrete mixer weekly hire line at 1 × £95.00. Nothing new was sent to the product.

InputDocument (PDF)
Input PDF: the two-page plant hire invoice with its three-line item table
Open the PDF ↗
Extraction schema
Every line item in the invoice table
The saved schema with line_items as an Array of Object with children description, quantity, unit_price and amount
What the tool returned

The tool's response has no text to quote: it is what the evidence under Proofs shows.

Proof 1 · Screenshot

Proof 2 · Screenshot

Proof 3 · Screenshot

Expected vs. Found
✗Expected: The added line item appears in the extracted list, the removed one is gone, and every other line item is left untouched.Found: Neither change reached the list. Editing the site fencing line drew 'Cannot edit in read-only editor', right-clicking it opened only the browser's menu, and the list still held three items.
Supporting proof
Proof 1Screenshot
Screenshot: the extracted list of three line items and the schema, before any attempt
Open original ↗
Proof 2Screenshot
Screenshot: right-clicking the site fencing line opens only the browser's own menu
Open original ↗
Proof 3Screenshot
Screenshot: the read-only editor message, with the list still holding three line items
Open original ↗
Why this result

It is a Fail, not Not gradable: the review screen is where the test asks for one line item to be added and one removed, and it answered each attempt but offers no control for either; its only row controls are thumbs-up and thumbs-down feedback icons.

Also observed in this test case

No field-level editing either. Values inside a line item cannot be edited on this screen either: an attempt to edit a value inside one drew the same read-only message.

Only the schema can grow. The only editable control in the view is '+ New Field' in the Schema pane, which adds a field to the extraction schema, not a line item to the extracted list.

Tested by Rugved Nichite · evidence dated 27 October 2026

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.

Software that produced the output
Landing AI
Build or version
DPT-3 Pro (parse model; app version not exposed)
Plan or tier
Explore (free credits, no subscription)
Surface
Web app
Set up before the run
A saved extraction of a plant hire invoice, with its line-item schema, listed the invoice's line items. On its review screen, the site fencing line was to be removed and a concrete mixer weekly hire line added, then the list read back.
Tested
27 October 2026 · Rugved Nichite

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

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.

The rules
  • 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 test case's result says which one 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 test case's result 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.

LevelNameScope
BenchmarkStructured Document Extraction →19 scenarios · 10 tools
CapabilityReview and Correction →
ScenarioRepair a record →
ToolLanding AI →

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.

from the publication record
21 November 2026First publishedStructured Document Extraction v1

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.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/structured-document-extraction/results/landing-ai/repair-a-record · 0 pass · 1 fail · coverage 1/1 · graded 2026-11-20

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.

Input · Document (PDF) ↗application/pdf · 78 KB
Proof 1 · Screenshot ↗image/png · 96 KB
Proof 2 · Screenshot ↗image/png · 80 KB
Proof 3 · Screenshot ↗image/png · 135 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)fdcf03ac5ee53b083da58166f17fd41e7c72de79a9f3a3f6b67daa1360ddbca9
Proof 1 · Screenshot9829fe038feb0b31039fd3753cf364f33e883964d9ea6f8cbf93df316b57cd38
Proof 2 · Screenshotac0e96f3872e4ba9e0532defd9aed1363dd4b9db75d96d7321474cc2e1b19a70
Proof 3 · Screenshot0626546837bf5ad9783ec2cad805d05659dc25229188d6e072d8ad154046ae87