← Latest papers
🤖 machine learning

Valid Per-Field Selective Risk Control for Document Extraction: Three Failure Modes, a Validity Ladder, and When Conditioning Pays

This paper diagnoses three critical failure modes that cause standard per-field selective risk control in document extraction to violate safety guarantees, proposing a "validity ladder" of increasingly rigorous fixes—including Mondrian Learn-then-Test and support-bin taxonomy—that ultimately demonstrate how conditioning on provenance can achieve valid risk control where pooled thresholds fail, a finding validated by human audits and released as open-source software.

Original authors: Bhaskar Gurram

Published 2026-08-18
📖 5 min read🧠 Deep dive

Original authors: Bhaskar Gurram

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine a world where computers can read a handwritten receipt, a medical form, or a shipping label and instantly turn the messy text into neat, organized data. This is the promise of modern document extraction, a technology that powers everything from automated accounting to digital record-keeping. For this system to be useful, it must be trustworthy. If a computer reads a dollar amount incorrectly, the consequences can be financial or legal. To manage this, engineers have developed a "trust contract": the system should not just output a number, but also a confidence score. If the system is unsure, it should flag the item for a human to review. The goal is to accept only the answers the computer is confident about, while keeping the error rate among those accepted answers below a specific, safe limit. This balance between accepting enough data to be useful and rejecting enough to stay accurate is the central challenge of the field.

A recent study by Bhaskar Gurram at Zasti AI investigates whether the standard methods used to enforce this trust contract actually work on real-world documents. The researchers tested their ideas on a massive collection of 13,859 data fields extracted from 800 real receipts using a powerful artificial intelligence model. They found that the common, widely accepted way of setting confidence thresholds was silently failing. In nearly half of the test scenarios, the system accepted too many errors, breaking the safety promise it was supposed to keep. The study identified three specific reasons for this failure. First, the data was not independent; errors tended to cluster together within the same document, making the test data look more reliable than it actually was. Second, the computer was essentially using the same data to both learn how to score its confidence and to set the safety limit, leading to an overly optimistic view of its own performance. Third, the scoring system sometimes produced too many identical scores, creating a gridlock where no safe threshold could be found at all.

To fix these problems, the researchers proposed a new, step-by-step framework they call a "validity ladder." At the bottom rung, they introduced a simple protocol that separates the data into two distinct groups: one for teaching the system how to score, and a completely untouched group for setting the safety limit. This simple separation stopped the overfitting and restored the system's ability to control the average error rate. However, the researchers knew that for high-stakes applications, an average guarantee is not enough; users need a certificate that proves the error rate will not exceed the limit in any specific instance. To achieve this, they moved up the ladder to more rigorous statistical methods. These methods group the data by specific characteristics, such as the type of field or the quality of the source information, and apply strict mathematical tests to each group. This ensures that even if the data is messy or clustered, the safety guarantee holds true for every group.

The study revealed a surprising insight about when these complex grouping methods are actually helpful. When the computer's confidence score is already very smart and has learned from the data, adding extra grouping rules often makes things worse by breaking the data into too-small pieces. But when the confidence score is weaker or frozen, grouping the data by its source or type becomes the key to success. In the hardest test case, where the AI was only correct about half the time, using a specific grouping method based on the "provenance" of the data—essentially, how well the computer could point to the exact spot on the page where it found the answer—allowed the system to certify its safety where it previously could not. This method worked so well that it outperformed all other approaches in the most difficult scenarios, though it did not provide the same advantage when the AI was already highly accurate.

The researchers also tested their new protocol on data from different AI models that they had never seen before. The system held up, maintaining its safety guarantees even when the underlying technology changed. To be absolutely sure, they had human experts review a sample of the computer's accepted answers. The humans found that the actual error rate was far lower than the system's safety budget allowed, confirming that the new methods were not just mathematically sound but practically robust. The study concludes that while the old methods were dangerously flawed on real documents, a combination of careful data separation and smart grouping can restore trust. It offers a clear path forward for developers: use simple separation for everyday reliability, and switch to rigorous, grouped certification when the stakes are high or the data is difficult. This work does not just point out a flaw; it provides a working, tested solution that allows machines to read documents with a level of honesty and reliability that was previously missing.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →