# Clarification behavior data fit scorecard | SourceX

Canonical: https://refer.sourcex.si/questions/does-clarification-behavior-data-qualify
Last updated: 2026-11-04

Ask an operations or finance lead eight things and rate each answer green, amber or red: headcount, operating history, rights, whether questions about conflicting instructions are written on the case, whether the case links to a customer or deal number, whether the final decision names who made it, whether outcomes such as invoices and credits are kept, and who can authorize a licensing discussion. English share is a ninth row outside the U.S., Canada and the EU.

This scorecard sits under the guide to [clarification behavior in an ordinary workflow](/guides/concept-clarification-behavior), which follows two conflicting discount approvals for one customer through to a clean invoice. That guide explains why the pause to ask is the valuable part of the record. This page turns it into a rating an introducer can fill in during one conversation, with nothing shared but answers.

## The scorecard at a glance

Green means the answer points to records that exist. Amber means they may exist but nobody has confirmed it. Red means the opportunity is theoretical for now.

| Criterion | Green | Amber | Red |
|---|---|---|---|
| Company size | Clearly 50+ full-time employees at peak | Near 50; needs confirming | Under 50, or mostly contractors |
| Operating history | Several years of approvals in one CRM or ERP | History split by a system change | A recent start or rebuilt records |
| Rights | Company owns its records; customer contracts allow internal analytics use | Some customer or parent-company terms unreviewed | A parent, client or vendor controls the records |
| Question recorded | Questions about conflicts sit in ticket or CRM comments on the case | Sometimes written, sometimes settled by phone | "People sort it out on a call" |
| Linkage | Thread linked to the opportunity, quote or customer ID | Findable only by date and customer name | "Only if you know who handled it" |
| Decision and decider | Final reply and system update both name the approver | Decision recorded, approver unclear | "The quote just changes" |
| Outcome kept | Signed quotes, invoices and credit notes retained for years | Kept, but in a system not tied to the quote | "Finance would have to dig" |
| Authority to discuss | The CEO, or the owner-CEO, named | Senior contact, authority unconfirmed | "We would need to ask the parent company" |

Outside the U.S., Canada and the EU, add a ninth row for English share. The rule in full: 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.

**How to read it.** Six or more green with no red is a strong fit. Any red on size, rights or authority stops the introduction until it is resolved. Otherwise, three to five green with at most one red is borderline: introduce with the open rows named. Fewer than three green is a weak fit for now.

## Five discovery questions that fill in the middle rows

The record rows are the hardest to rate, and five questions settle them. Each can be answered from memory, with no file shared.

| Question | Green answer | Red answer |
|---|---|---|
| 1. When two approvals or instructions conflict, where does someone record the question? | "In the ticket or CRM comment on the deal itself" | "People sort it out on a call" |
| 2. Can you find the case afterward from the customer or deal number? | "Yes, the thread is linked to the opportunity ID" | "Only if you know who handled it" |
| 3. Is the final decision written down with who made it? | "The director's reply and the CRM update both show it" | "The quote just changes" |
| 4. Is the outcome kept: signed quote, invoice, dispute or credit? | "Invoices and credit notes are in the ERP for seven years" | "Finance would have to dig" |
| 5. Who could authorize a conversation about licensing these records? | "The CEO, and our customer contracts allow internal analytics use" | "We would need to ask the parent company" |

Anything between the two columns is amber. Write the answer down in the person's own words; it is more useful to SourceX than your rating.

Why these questions and not others: researchers behind the CLAMBER benchmark found that current language models are weak at spotting ambiguity and asking good clarifying questions, partly for lack of conflict resolution. OpenAI's published Model Spec says asking is appropriate when a wrong guess is costly. A discount on a signed quote is costly. Records that show a person noticing a conflict, asking the right person and getting a clean outcome are the human version of what models struggle with.

## Three fits, described (Illustrative)

All three companies are fictional.

**Strong: a 300-person industrial parts distributor.** Quote holds carry a reason code, clerks ask questions in CRM comments on the opportunity, and the deal desk's replies name the approver. Invoices and credit notes stay in the ERP for seven years and carry the quote number. The CFO owns the records and says customer contracts allow internal analytics. Two rows are amber: a CRM change four years ago, and an unreviewed reseller agreement. Six green, two amber, no red.

**Borderline: a 120-person software reseller.** Discount conflicts are common and usually raised in a shared chat channel rather than on the deal. The final price is in the CRM, invoices are in accounting software, and both carry the customer ID. Question recorded and decision-and-decider are amber, and so are rights, because a vendor agreement may restrict use of deal data. Size, history, linkage, outcome kept and authority are green. Five green, three amber. Worth introducing with the chat-channel question stated.

**Weak: a 65-person marketing agency in Singapore.** Scope changes are agreed by phone, the agency's clients own much of the work, and about a quarter of records are in languages other than English, which misses the 70% English rule for a Singapore company. Two green, three red, including rights. Not ready, however willing the founder.

## Signals that look green but are not

Some answers sound strong and turn out to be amber or red on a second question.

- **"We approve everything in the CRM."** An approval field that is overwritten each time keeps only the last value, so the conflict disappears. Ask whether the field keeps history.
- **"We have an approval workflow tool."** A tool that routes approvals does not mean questions about conflicts are recorded. Ask where people write when two approvals disagree.
- **"Our customers rarely dispute invoices."** Good news for the business, but the outcome row is about whether invoices and credits are kept and linked, not how few disputes there are.
- **"Everything is in email."** Email can hold the question and the answer, but it often leaves with the employee. Ask whether approval emails stay attached to the deal.

For help reading what a client means by a vague request, the guide to [understanding a request for more information](/guides/how-to-understand-a-request-for-more-information) is a useful companion.

## Who decides, and what stays unknown

Sales operations usually owns CRM and quoting records, finance owns approvals and invoices, and IT or revenue operations runs the systems. 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.

The scorecard cannot show how many cases pass a reviewer's acceptance check, what de-identification is needed, whether any buyer wants these records, or what the company might be paid. Vendors such as Appen market (on a page checked October 18, 2026) agent training and evaluation work built around CRM and ERP systems, but competitor interest in agent data does not mean every approval archive qualifies. Discovery stays at metadata level; partners never ask for threads, quotes or invoices. Before introducing, read how to [document client consent for a referral](/resources/how-to-document-client-consent-for-a-referral) and point the owner to [questions to ask before licensing company data](/resources/questions-to-ask-before-licensing-company-data). The amber rows can then be phrased using [clarification behavior evidence gaps](/questions/clarification-behavior-evidence-gaps), and the company later prepares the [clarification behavior review packet](/resources/clarification-behavior-review-packet). The wider record family is covered under [deal desk approval data](/data-types/deal-desk-approval-process).

## 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 company has no red on size, rights or authority and at least three green rows overall, [register as a partner](/register), confirm the basics on [who qualifies](/who-qualifies), and read the [terms](/terms) before you introduce the CEO.

## 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
