Does clarification behavior data qualify? A green, amber and red scorecard for approval conflicts

Short answer

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.

Visual briefFull-size diagram
A semicircle dial divided into red, amber and green; eight criteria are checked one by one beneath it and the needle swings, then settles in green with six green, two amber and no red for a fictional 300-person parts distributor.
Illustrative rating for a fictional company. A green rating sorts an introduction; it does not predict acceptance or a payout.

This scorecard sits under the guide to clarification behavior in an ordinary workflow, 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.

CriterionGreenAmberRed
Company sizeClearly 50+ full-time employees at peakNear 50; needs confirmingUnder 50, or mostly contractors
Operating historySeveral years of approvals in one CRM or ERPHistory split by a system changeA recent start or rebuilt records
RightsCompany owns its records; customer contracts allow internal analytics useSome customer or parent-company terms unreviewedA parent, client or vendor controls the records
Question recordedQuestions about conflicts sit in ticket or CRM comments on the caseSometimes written, sometimes settled by phone"People sort it out on a call"
LinkageThread linked to the opportunity, quote or customer IDFindable only by date and customer name"Only if you know who handled it"
Decision and deciderFinal reply and system update both name the approverDecision recorded, approver unclear"The quote just changes"
Outcome keptSigned quotes, invoices and credit notes retained for yearsKept, but in a system not tied to the quote"Finance would have to dig"
Authority to discussThe CEO, or the owner-CEO, namedSenior 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.

QuestionGreen answerRed 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 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 and point the owner to questions to ask before licensing company data. The amber rows can then be phrased using clarification behavior evidence gaps, and the company later prepares the clarification behavior review packet. The wider record family is covered under deal desk approval data.

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, confirm the basics on who qualifies, and read the terms before you introduce the CEO.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Who in the company should I ask?

An operations or finance lead who handles approvals day to day can answer most rows from memory. The owner, CEO or CFO answers the rows on headcount, rights and authority.

What if most answers are amber?

Amber means the records may exist but nobody has checked. If no row is red, you can introduce the company and list the amber rows as open questions. If two or more rows are red, wait until the owner has looked into them.

Is a company that approves thousands of discounts automatically green?

No. Volume alone does not show clarification. What counts is whether conflicts led to a recorded question, an answer from someone with authority, and a kept outcome.

Sources

  1. aclanthology.org/2024.acl-long.578
  2. model-spec.openai.com/2026-08-18.html
  3. appen.com/agentic-ai
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment