# Clarification behavior evidence gaps | SourceX

Canonical: https://refer.sourcex.si/questions/clarification-behavior-evidence-gaps
Last updated: 2026-11-04

Four gaps make clarification behavior hard to assess: lost context (a conflicting instruction lived in a mailbox that was later deleted), missing authority (nobody documented who could sign off which levels), overwritten versions (the system kept only the last value), and no recorded outcome (billing cannot be tied back to the case). Each breaks the evidence chain at a different link. One or two gaps narrow what can be licensed without ruling a company out.

This gap analysis belongs to the guide to [clarification behavior in an ordinary workflow](/guides/concept-clarification-behavior), whose worked example is a renewal with two incompatible discount sign-offs that someone paused to resolve. Here that example becomes the yardstick. The job of this page is different: list what a review would need to reconstruct such a case, set it against what archives usually retain, and give introducers honest language for the shortfall.

## What a reviewer expects to trace in one case

A clarification record earns its value only when the whole arc survives, from contradiction to consequence. Research shows why the arc matters: the CLAMBER benchmark reports that today's language models struggle to produce good clarifying questions, partly for lack of conflict resolution, and OpenAI's Model Spec treats asking as the right move when a mistaken guess would be expensive. A reviewer therefore needs proof of three things: a genuine contradiction existed, the person who paused consulted someone entitled to settle it, and pausing produced a better result than pressing on.

Broken into evidence, that means seven links:

1. **Request**: what was asked for and why, usually in the CRM.
2. **First sign-off**: one approver's figure, with name and timestamp.
3. **Second sign-off**: a different figure for the same customer and period.
4. **Pause**: a status change showing work stopped, ideally with a reason.
5. **Question**: the written query that names both figures.
6. **Authorized answer**: a reply from someone whose role covers the final figure.
7. **Outcome**: what was billed and paid, or disputed and credited.

## The gap table for a discount conflict

Approval archives tend to keep the steps that live in the main system of record and lose the ones that live around it. The table is a pattern, not a measurement.

| Gap | Link it breaks | What the record looks like with the gap | Question to ask (metadata only) |
|---|---|---|---|
| Lost context | Link 3 absent, so link 4 looks unexplained | Work paused for no visible reason | "Do approval emails stay with the deal after staff leave?" |
| Missing authority | Link 6 cannot be checked | A decision by someone whose authority is unknown | "Is the discount approval matrix documented, and for which years?" |
| Overwritten versions | Links 2 and 3 collapse into one value | A routine case with no visible conflict | "Does the quoting tool keep field history or an audit log?" |
| No outcome | Link 7 absent | A decision with no consequence | "Can invoices and credits be tied back to the quote number?" |

Links 1, 4 and 5 are usually the safest. Requests sit in the CRM, pauses are status changes, and questions survive if they were asked on the case rather than on a call.

## How each gap changes what can be licensed

A gap rarely ends the discussion. It changes which cases are usable and what they can show.

**Lost context.** If the 8% finance approval lived in a personal inbox deleted when the analyst left, the clerk's pause looks like simple delay. Cases from before the company kept approval emails on the deal may be usable only as examples of holds, not of conflicts. The fix is a date: "approval emails attached to deals since 2022."

**Missing authority.** If the archive does not show who could approve which discount levels, a reviewer cannot judge whether the clerk asked the right person. A documented approval matrix for each year, even a spreadsheet, closes much of this gap. Without one, cases can still show that a question was asked, but not that it went to the right place.

**Overwritten versions.** Many quoting tools keep only the current value of a discount field. If 12% was overwritten by 10%, the conflict vanishes and the case looks routine. This is the gap that cannot be repaired later. Field history or an audit log either existed at the time or it did not. Quote history in manufacturing has the same problem; see [RFQ and quote history](/data-types/rfq-quote-history-manufacturing).

**No outcome.** Without the invoice, payment or credit note, nobody can tell a case where asking prevented a dispute from one where it did not. Outcomes often exist in the ERP but are not tied to the quote. If a quote number or customer ID appears on both, the link can usually be made in review.

## Describing gaps in your introduction note

An introduction note should let SourceX start from an accurate picture. Name each gap, its scope and who told you. Illustrative wording, all fictional:

| Gap | Note that helps | Note that misleads |
|---|---|---|
| Lost context | "Approval emails kept on deals since a 2022 policy change; earlier ones may be gone" | "All approvals are recorded" |
| Missing authority | "CFO says an approval matrix exists for 2023 onward; earlier years unknown" | "Approvals follow policy" |
| Overwritten versions | "Ops lead unsure whether the quoting tool keeps field history" | "Quote history is complete" |
| No outcome | "Invoices carry the quote number; credits sometimes do not" | "Finance has everything" |

"Unsure" and "unknown" are acceptable. A note that admits a gap is more useful than one that guesses it away.

## Questions to leave for SourceX's review

Some gaps can only be measured by looking at records, which partners never do. How many cases show a full chain, whether field history survived a system change, whether customer contracts allow use of deal data, and how personal data will be handled are all decided in SourceX's review under an agreement with the company. So is buyer interest. Vendors such as Appen market (on a page checked October 18, 2026) agent training work built around CRM and ERP systems, and evidence exists that [AI companies pay for data](/proof/ai-companies-pay-for-data), but neither says anything about one company's approval archive.

Sales operations, finance and IT usually share ownership of these records; the CEO, or the owner in an owner-run company, authorizes a licensing discussion. The company needs 50 or more full-time employees at peak (contractors excluded), documented operating history, rights to license, 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.

To rate a company before describing its gaps, use the [clarification behavior qualification scorecard](/questions/does-clarification-behavior-data-qualify). After an introduction, the company assembles the [clarification behavior review packet](/resources/clarification-behavior-review-packet). For the broader record family, see [deal desk approval data](/data-types/deal-desk-approval-process), and for reading vague client requests, [how to understand a request for more information](/guides/how-to-understand-a-request-for-more-information).

## 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 the gaps you found narrow the archive rather than empty it, [register as a partner](/register), confirm the basics on [who qualifies](/who-qualifies), and read the [terms](/terms) before you introduce the CFO with your gap notes attached.

## Sources

- https://aclanthology.org/2024.acl-long.578/
- https://model-spec.openai.com/2026-08-18.html
- https://www.appen.com/agentic-ai
- https://refer.sourcex.si/terms
