Abstention, in plain language
To abstain is to decline to answer or act because the available evidence is not enough. In AI research the idea has become a topic of its own: a 2025 survey in Transactions of the ACL reviews abstention methods, benchmarks and metrics for language models, and OpenAI has argued that accuracy-only scoring rewards guessing over admitting uncertainty, even though a confident error is worse than an abstention.
Businesses have recorded the human version for decades without calling it that. A contract administrator who refuses to route an incomplete package for signature, logs why, and sends it to legal has produced an abstention example: the input, the reason for stopping, the escalation and the outcome. Vendors such as Appen now market failure-mode taxonomies and rubric design for agent evaluation, but market interest does not mean every contract archive qualifies.
One stopped package, annotated (Illustrative)
The graphic shows a fictional renewal package of six documents. Four are in order. The insurance certificate is missing, and the data processing addendum attached is version 2, while the customer signed version 3. A completeness check finds 4 of 6 in order, so routing for signature is blocked. The administrator escalates to legal with both gaps named, and the renewal is signed on day 9 with matching versions.
| Moment | What a good record holds | Where it usually sits |
|---|---|---|
| Package arrives | The six documents as received, with versions | Contract tool upload history or intake email |
| Check fails | Which items failed and why | Status change with a reason field |
| Stop | Signature routing blocked | Workflow status history |
| Escalation | Recipient, time, gaps named | Legal intake queue or ticket |
| Resolution | Corrected documents and signature date | Executed contract record |
A history like this is useful only when all five moments can be tied to the same contract. That is what the discovery questions test.
What should an introducer ask about abstention examples?
Five questions, each answerable from memory by a contracts manager or general counsel, with nothing shared. Together they separate an archive that exists from an opportunity that only sounds plausible.
1. When a contract package is incomplete, where is the stop recorded? Real records sound like: "The package goes on hold in our contract tool with a reason." Theory sounds like: "Someone would notice and mention it."
2. Can you see what was in the package when it arrived? Real records: "Every upload is versioned, and the original email is attached." Theory: "We have the final signed version."
3. Who receives escalations, and is that written down? Real records: "Legal intake queue; the policy says what contract administrators can and cannot approve." Theory: "Whoever is around."
4. Do you keep the cases that went through cleanly as well as the ones that stopped? Real records: "Yes, every renewal since 2019 is in the same system." Theory: "We only kept the problem files."
5. Who could authorize a conversation about licensing these records? Real records: "The general counsel, with the CFO." Theory: "We would need to find out whether customer contracts allow it."
Reading the answers
Three or more answers that sound like the first version suggest a company worth introducing. Fewer is not a rejection; it is a list of things for the owner to check, and questions to ask before licensing company data is a good place to start. Record only system names, years, rough package counts and the owner. Never ask for a sample escalation, policy or contract, even redacted.
Two answers deserve a note. If the company kept only the problem files (question 4), the history shows stops without the ordinary cases they should be compared with. If the original package was overwritten by the final version (question 2), the stop can no longer be checked against what the administrator actually saw. Both are common and both are worth stating plainly. For background on what makes records an asset at all, see what is a data asset and what is proprietary data.
Who owns these records, and what stays unknown?
Contract packages usually belong to legal or a contracts team, with executed copies sometimes held by finance or sales operations. Authority to discuss a license normally sits with the general counsel, CFO, CEO or owner. Customer contracts may restrict reuse of their terms, so the owner should expect a rights review.
The company itself must have 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. The who qualifies page has the full criteria.
What nobody knows until SourceX reviews it: whether there is SourceX's current data needs for these specific records, the rights review result, what redaction is needed, the company's offer, and therefore any reward. Contract review records are described under contract review workflows, and a related behavior is covered in clarification behavior. More record families are listed under data types.
Go deeper on abstention examples
- Which record gaps make abstention examples hard to assess: a question page on the missing fields that weaken a history of stops.
- Abstention examples review packet: a resource listing what belongs in an evidence packet for SourceX's review.
- Abstention examples in an ordinary business workflow: a worked example that follows one escalation from start to finish.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a client's contracts team answers at least three of the five questions with real records, register as a partner, check who qualifies, and read the program terms before you introduce the decision-maker.