Negotiation-to-contract completeness checklist: six RevOps checks with pass, partial and fail guides

Short answer

A negotiation-to-contract evidence trail breaks wherever the deal changes outside the system that approved it. The six checks below find those places: how long Salesforce keeps field history, whether drafts are attached to approvals, whether customer redlines are accepted by email, whether envelopes carry the opportunity ID, whether corrections after sending are logged, and what happens to a departing account executive's mailbox. Each is a question for the RevOps owner about configuration and habit, never about content.

Visual briefFull-size diagram
Six check tiles in a grid tick one by one, field history window, approval attachments, redlines by email, envelope tagging, corrections after sending and mailbox departures, while a ring meter draws to three passes, two partials and one fail.
Illustrative score for a fictional software reseller: three passes, two partials, one fail on redlines by email.

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

CheckThe question to askPassPartialFail
1. Field history windowIs history tracked on the discount and term fields, and is Field Audit Trail on?Tracked, with Field Audit Trail or regular snapshotsTracked, standard window onlyNot tracked
2. Approval attachmentsAre drafts attached to approval requests, or only described in a comment?Attached as a ruleAttached for large deals onlyDescribed only
3. Redlines by emailAre customer redlines ever accepted in an email reply without resubmitting for approval?Never; changed drafts go back for approvalSometimes, and the company can estimate how oftenOften, or unknown
4. Envelope taggingAre envelopes sent from the opportunity, or with its ID in a custom field?Yes, from a known yearSome senders or some yearsSent from personal accounts with no ID
5. Corrections after sendingDoes anyone review certificates for Envelope Updated entries?Corrections are visible and the team knows itVisible but never reviewedEnvelopes voided and resent with no link
6. Mailbox departuresWhen an account executive leaves, is the mailbox retained?Retained or converted before deletionRetained for a fixed period onlyDeleted

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?"

AnswerWhat it shows
Both numbers, and they matchDrafts attached, envelopes tagged, no drift on this deal
Both numbers, and they differThe chain is complete and it caught a late change
One number onlyOne hop relies on memory
NeitherDrafts 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.

CheckMarkNote from the call
1. Field history windowPartialTracked on discount and term fields; Field Audit Trail off
2. Approval attachmentsPassDrafts attached since the approval process went live in 2020
3. Redlines by emailFailAccepted by reply on smaller deals; frequency unknown
4. Envelope taggingPassSent from the opportunity since 2021
5. Corrections after sendingPartialEnvelope Updated entries exist; nobody reviews them
6. Mailbox departuresPassDeparted mailboxes kept for seven years
Draft-match testBoth numbers, differApproved 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.

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.

  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

Why is a fail on redlines by email not a reason to drop the company?

Because the habit itself is informative. A company that accepts some redlines by email and can say roughly how often holds a record of approval drift, which is one of the more useful patterns in negotiation history. The fail describes a gap to state, not a disqualification.

Who should answer these checks?

The VP of Revenue Operations or Salesforce administrator for checks 1, 2 and 4, the DocuSign administrator for check 5, sales leadership for check 3 and IT for check 6. Each is a question about configuration or habit.

Can I share the completed checklist with SourceX?

Yes. It holds systems, years and pass, partial or fail marks, with no customer names, prices or contract language, so it can travel with your registration.

Sources

  1. help.salesforce.com/s/articleView
  2. help.salesforce.com/s/articleView
  3. support.docusign.com/s/document-item
  4. developers.docusign.com/docs/esign-rest-api/reference/envelopes/enve…
  5. refer.sourcex.si/terms
  6. refer.sourcex.si/rewards

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