It is one of three tools in the negotiation-to-contract guide.
How to mark each check
Pass: the company does this consistently and can say from which year. Partial: it does this for some teams, some deal types or only recently. Fail: it does not, or nobody knows. Ask for the year a habit began; a pass from 2023 and a pass from 2017 describe very different histories.
Write who answered. The VP of Revenue Operations knows configuration; sales leadership knows habits; IT knows mailbox retention. When two people disagree, record both answers and mark partial.
The six checks
| Check | The question to ask | Pass | Partial | Fail |
|---|---|---|---|---|
| 1. Field history window | Is history tracked on the discount and term fields, and is Field Audit Trail on? | Tracked, with Field Audit Trail or regular snapshots | Tracked, standard window only | Not tracked |
| 2. Approval attachments | Are drafts attached to approval requests, or only described in a comment? | Attached as a rule | Attached for large deals only | Described only |
| 3. Redlines by email | Are customer redlines ever accepted in an email reply without resubmitting for approval? | Never; changed drafts go back for approval | Sometimes, and the company can estimate how often | Often, or unknown |
| 4. Envelope tagging | Are envelopes sent from the opportunity, or with its ID in a custom field? | Yes, from a known year | Some senders or some years | Sent from personal accounts with no ID |
| 5. Corrections after sending | Does anyone review certificates for Envelope Updated entries? | Corrections are visible and the team knows it | Visible but never reviewed | Envelopes voided and resent with no link |
| 6. Mailbox departures | When an account executive leaves, is the mailbox retained? | Retained or converted before deletion | Retained for a fixed period only | Deleted |
Three checks rest on documented behavior. Without Field Audit Trail, Salesforce retains field history for up to 18 months, and up to 24 months through the API, so check 1 decides whether original exception values survive on older deals; the field history retention answer covers the options. DocuSign envelopes can carry custom fields used for sorting, searching and tracking, which is where an opportunity ID goes for check 4. And DocuSign's Certificate of Completion logs an Envelope Updated entry when a sent document is corrected, which is the signal behind check 5.
Why check 3 carries the most weight
Checks 1, 2, 4, 5 and 6 decide whether records exist. Check 3 decides whether they agree. When a customer returns a changed draft by email and the account executive accepts it in a reply, the approval and the signed order can describe different deals. Salesforce's Approval History will still show the approval as Approved, with the actual approver named, against a version nobody signed.
That is why a fail on check 3 is not a reason to walk away. It means approval drift happened and may be traceable. What matters is whether checks 2 and 4 pass, because numbered, attached drafts and tagged envelopes are what let the drift be found later. The record chain page shows how draft numbers expose it, and the missing-context comparison reads one such deal.
The draft-match test
One question tests the joins between the checks. Ask the RevOps owner: "For the last deal with an approved discount, can you tell me the approved draft number and the signed draft number without opening either document?"
| Answer | What it shows |
|---|---|
| Both numbers, and they match | Drafts attached, envelopes tagged, no drift on this deal |
| Both numbers, and they differ | The chain is complete and it caught a late change |
| One number only | One hop relies on memory |
| Neither | Drafts are not numbered or not linked; check 2 or 4 is really a fail |
The second row is the strongest result, not a problem. It shows the records are complete enough to reveal what actually happened.
A completed checklist (Illustrative)
A fictional 280-person software reseller, answered by its VP of Revenue Operations and IT director.
| Check | Mark | Note from the call |
|---|---|---|
| 1. Field history window | Partial | Tracked on discount and term fields; Field Audit Trail off |
| 2. Approval attachments | Pass | Drafts attached since the approval process went live in 2020 |
| 3. Redlines by email | Fail | Accepted by reply on smaller deals; frequency unknown |
| 4. Envelope tagging | Pass | Sent from the opportunity since 2021 |
| 5. Corrections after sending | Partial | Envelope Updated entries exist; nobody reviews them |
| 6. Mailbox departures | Pass | Departed mailboxes kept for seven years |
| Draft-match test | Both numbers, differ | Approved draft 3, signed draft 4 |
Three passes, two partials and one fail, plus a draft-match result that proves drift is visible. That is a chain worth describing from 2021, with older exception values likely lost to the field history window.
Sponsor, eligibility and the unknowns
The RevOps owner answers; the CEO decides whether to explore licensing, and the general counsel reviews customer contracts, since signed orders carry customer terms. For how contract review records are viewed more generally, see contract review workflows; for how buyers approach this kind of data, see how AI labs buy data.
The company needs 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. Unknown until SourceX reviews it: what customer contracts allow, how many deals join on draft numbers and what history remains. Partners never ask for or handle raw records and sign the Channel Partner Agreement first. SourceX funds any reward separately and never deducts it from the company's payout; see rewards. The broader case is in negotiation data for AI training.
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 checklist shows a deal trail with attached drafts and tagged envelopes, gaps included, register as a partner, confirm the company against who qualifies and read the terms before you introduce its sponsor.