# Call-to-contract trail completeness scorecard | SourceX

Canonical: https://refer.sourcex.si/resources/promise-to-obligation-completeness-checklist
Last updated: 2026-11-04

A promise-to-obligation trail breaks wherever a commitment changes form without a record: a call linked to the account but not to the opportunity, stage history that has aged out, redlines traded by email outside the contract workflow, an executed copy stored somewhere else, and above all a spoken promise that never reaches the contract. The seven checks below each take one metadata question and a pass, partial or fail mark, so you can describe the trail without hearing a call or reading a clause.

The scorecard belongs to the [promise-to-obligation records guide](/guides/chain-promise-to-obligation). If you need the facts the checks rest on, fill in the [metadata packet](/resources/promise-to-obligation-metadata-packet) first; the scorecard then takes ten minutes.

## How to mark each check

- **Pass:** the link or fact is recorded by a system for most years the company wants to describe.
- **Partial:** recorded for some years, some deal types or some teams, or dependent on someone correcting it by hand.
- **Fail:** not recorded, or nobody can say. Unknown is a fail until confirmed.

Report the result as a count and a sentence, for example "four pass, two partial, one fail; calls and contracts join from 2022; no routine check of spoken promises." Two checks act as gates. If check 2 (call to opportunity) or check 3 (contract to opportunity) fails, describe the trail as two separate archives, not a chain, whatever the other marks say.

## The seven checks for a call-to-contract trail

| # | Check | Metadata question | Pass | Partial | Fail |
|---|---|---|---|---|---|
| 1 | Coverage | Since which year do CRM, call and contract records overlap? | Three or more years in all three | Shorter overlap, or contracts split across tools | One or two systems only |
| 2 | Call to opportunity (gate) | Roughly how often are calls associated to an opportunity, not just an account? | Nearly always, with corrections made | Often, but multi-deal accounts drift | Calls linked to accounts only |
| 3 | Contract to opportunity (gate) | Are contract workflows launched from the opportunity, and since when? | Yes, for all years described | From a given year only | Contracts started separately |
| 4 | Event order | Is field history tracked on stage and amount, and is retention extended? | Tracked, with extended retention | Tracked, default retention | Not tracked |
| 5 | Redlines inside the workflow | What share of negotiation happens in the contract system rather than by email? | Nearly all | Most, with email for some customers | Mostly by email |
| 6 | Executed copy | Where does the signed version live? | In the workflow, synced back to the CRM | In the workflow, not synced | Elsewhere, or unknown |
| 7 | Spoken-promise review | Does anyone compare calls with the contract before signature? | Routine review that leaves a record | Checked when a customer raises it | Not checked |

The documented behavior behind several marks:

- **Check 2.** The call recorder guesses the deal from participant emails and the account's open deals, and a person can override a wrong guess. Accounts with several open deals are where guesses go wrong, so ask who fixes them and how often.
- **Check 3.** The contract tool can start a workflow from the deal record. Ask for the year that integration was switched on; before it, contracts and deals usually share no key.
- **Check 4.** Default field history covers 18 months in the interface and 24 months through the API, for up to 20 tracked fields per object. Older stage and amount changes lose their order unless retention was extended; see [Salesforce field history retention](/questions/salesforce-field-history-tracking-retention).
- **Check 5.** In Ironclad's editor, saving a change asks for a comment, which lands in the workflow's Activity Feed beside a link to the new version. Negotiation inside the workflow leaves reasons behind; negotiation by email does not.

## Check 7, the silent gap

Check 7 is different from the others. Every other check asks whether a record exists. Check 7 asks whether anyone looks for a record that, by definition, does not exist in the contract system: a commitment spoken on a call and never drafted.

Ask: "If a customer says 'you promised us this on a call', how do you check?" Mark the answer:

1. **Pass.** "Legal or deal desk reviews call highlights against the draft before signature, and notes the review in the workflow." Worth stating with its start year.
2. **Partial.** "We pull the call when a customer raises it." The gap is known and recoverable, provided checks 2 and 4 hold.
3. **Fail.** "We rely on the account executive's memory." The spoken promise sits outside the record entirely.

A company that marks partial and can say roughly how often such disputes come up is describing a known, labeled exception. For AI training and evaluation, that disagreement between spoken and written records is exactly what makes a chain valuable, so an honest partial is a strong line in an introduction. For one deal where this happened, read the [before-and-after reading of one renewal](/guides/promise-to-obligation-missing-context).

## A scored sales organization (Illustrative)

A fictional 620-person logistics software company, scored with its revenue operations lead and legal operations manager. Every answer is invented.

| # | Check | Answer heard | Mark |
|---|---|---|---|
| 1 | Coverage | CRM since 2015, calls since 2019, contract system since 2021 | Pass |
| 2 | Call to opportunity | Automatic; revenue operations corrects multi-deal accounts weekly | Pass |
| 3 | Contract to opportunity | Launched from the opportunity since 2022 | Partial |
| 4 | Event order | Stage and amount tracked; default retention | Partial |
| 5 | Redlines inside the workflow | Nearly all negotiation in the contract system | Pass |
| 6 | Executed copy | In the workflow and synced back | Pass |
| 7 | Spoken-promise review | No routine review | Fail |

Result: four pass, two partial, one fail. Gates: check 2 pass, check 3 partial, so the chain holds from 2022. How a partner would put it: "Calls, opportunities and contracts join from 2022; event order limited to default history retention; no routine check of spoken promises against contracts." If the company is mid-way through a CRM change, the [CRM migration handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-a-crm-migration) helps time the conversation before history is lost.

## Owners, the officer who can authorize, and what remains open

Revenue operations answers checks 2 and 4; legal operations answers checks 3, 5 and 6; check 7 usually needs a sales or legal leader. None of them typically authorizes a licensing discussion. That is the CEO, usually with the CFO, COO or general counsel involved, because calls include customers' voices and contracts carry confidentiality terms. Consultants already working on a Salesforce project will find the moment to raise it described in [how CRM and RevOps consultants spot referral opportunities](/guides/how-crm-and-revops-consultants-spot-referral-opportunities-during-salesforce-projects).

Check the baseline: 50+ 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. The [company fit checker](/tools/company-fit-checker) covers the same basics.

What stays unknown until SourceX reviews it: what call consent and customer contracts allow, what must be removed, how many deals have a complete chain, and what the company would be paid. Partners never ask for or handle calls, notes or contracts, and sign the Channel Partner Agreement before submitting introductions.

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

When the seven marks give you one honest sentence about how far a company's promises can be traced, [register as a partner](/register), confirm it on [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing the officer.

## Sources

- https://help.gong.io/docs/associating-salesforce-accounts-and-leads-to-calls
- https://help.gong.io/docs/manage-call-associations
- https://help.salesforce.com/s/articleView?id=xcloud.tracking_field_history.htm&language=en_US&type=5
- https://support.ironcladapp.com/hc/en-us/articles/12274871100055-Use-Ironclad-Editor
- https://support.ironcladapp.com/hc/en-us/articles/12285599508119-Get-Started-with-the-Ironclad-Salesforce-Integration
- https://refer.sourcex.si/terms
