How to compare draft and executed versions for Vendor Supply Agreements

Compare the executed vendor supply agreement against the buyer’s last approved draft, not simply the newest file. Establish the complete document set, generate a comparison, verify substantive differences against the originals, and assess their effect on pricing, ordering, quality, remedies, and supply continuity. Record source locations, approval evidence, business consequences, and corrective actions in a version comparison checklist. The resulting deliverable is a source-linked exception report distinguishing approved concessions, unexplained deviations, missing materials, and decisions requiring legal or business review.

When to use this workflow

Use this workflow when procurement receives a signed supply agreement, legal discovers competing “final” versions, or an acquisition team reconciles signed supplier contracts with negotiation files. It serves buyer-side commercial counsel, contract managers, and in-house teams confirming whether the execution package reflects approved terms.

The scope is execution verification, not complete renegotiation or a supplier-performance audit. Review communications and performance records only when they explain a discrepancy or identify a separate legal question.

This is a general US commercial-contract workflow. Determine governing law, whether goods-sale rules apply, and any relevant effective-date issues; mixed goods-and-services arrangements require separate coverage analysis. Rights depend on the actual language, facts, and deal context.

What you need

Collect these inputs before treating the comparison as complete:

• Approved baseline: buyer-approved draft, schedules, approval correspondence, and authorized signing changes.
• Execution package: signed agreement, counterparts, attachments, signature records, and contemporaneous amendments or side letters.
• Supply documents: specifications, quality agreement, price list, tooling schedule, forecasts, purchase-order forms, and incorporated terms.
• Negotiation evidence: supplier markups, counsel correspondence, procurement concessions, and the buyer’s checklist of preferred positions and permitted fallbacks.
• Operating context: critical products, alternate-source availability, ordering model, pricing assumptions, and procurement, quality, and finance contacts.

Preserve source files unchanged. Assign stable document IDs and record filenames, version dates, provenance, and completeness. For incorporated online terms, seek the version relevant to execution rather than assuming the current webpage is identical.

Use the template

The companion template is Vendor Supply Agreements — Version comparison checklist. You can copy this table into your working document or spreadsheet. Use one row per substantive difference or unresolved document gap; link related rows where multiple changes affect the same protection.

Use document IDs, sections, and pages in both source columns. For spreadsheets, include sheet and cell references; for specifications, include revision numbers. Capture enough wording to substantiate the difference while preserving the underlying sources.

“Approval / uncertainty” identifies the decision record or precise evidence gap. Distinguish absent, ambiguous, missing attachment, redacted, and not reviewed. An unavailable attachment does not establish that its terms are absent.

“Action / owner” identifies the next decision or investigation and accountable person. “Status” distinguishes source verification from resolution: a verified difference may remain unresolved. Retain approved differences and closure evidence rather than deleting completed rows.

Step by step

1. Establish the approved draft and execution set

Confirm which draft received buyer approval and whether approval covered every schedule. A later supplier file may contain unexplained edits; an earlier legal draft may omit an authorized commercial concession.

Match the executed body to exhibits, counterpart signatures, dates, legal entity names, and revision references. Distinguish signing dates from the stated effective date. Identify amendments separately rather than silently merging them into the original execution comparison.

Record: baseline and execution IDs, approval evidence, missing components, and an owner for each completeness question. Do not describe a partial package as a verified match.

2. Generate the comparison and validate the text

Run a comparison using the team’s chosen software. For scans, use extracted text as an aid, then inspect source images. Check tables, footnotes, handwritten additions, decimal points, and signature-page substitutions visually.

Separate formatting changes from changes to obligations. Renumbering may break cross-references; moving a definition may change its scope. Verify apparent deletions against both originals. Review changed defined terms across their uses, not just where they appear in the comparison.

Preserve the executed source. Put proposed corrections in a separate working draft, not into the signed record.

Record: verified differences, source locations, and extraction uncertainty requiring visual review. Keep the comparison file linked to its two source versions.

3. Reconcile the supply package and document hierarchy

Compare incorporation language, exhibit titles, specification revisions, order provisions, and precedence clauses. A matching agreement body does not establish matching price lists or quality requirements.

One SEC-filed supply agreement, § 3.5, makes accepted purchase orders binding and gives the agreement priority over conflicting order terms. This illustrates negotiated wording, not a universal hierarchy rule.

Check whether a revision makes forecasts binding, expands minimum purchases, or changes the treatment of order acknowledgments. Where a schedule can be updated under the agreement, distinguish a signing discrepancy from a later update made through that mechanism.

Record: incorporation or hierarchy differences, affected documents, and uncertainty about the version incorporated or the authority for an update.

4. Test commercial differences against buyer operations

Compare unit prices, currency, freight allocation, payment triggers, minimum quantities, lead times, and adjustment mechanics. For changed formulas, calculate illustrative results using identified assumptions; never infer missing inputs.

A filed supply agreement, § 3.2, combines a stainless-steel index, thresholds, proportional cost weighting, written notice, and timing requirements, addressing decreases as well as increases. Its later-adjustment qualifications and internal cross-references also require attention. It is an example, not a market benchmark.

Test both upward and downward movements. Check whether revised prices affect existing orders and whether forecast commitments exceed operational needs. Finance validates arithmetic; counsel checks contractual conditions.

Record: changed inputs, illustrative consequences, assumptions, approval evidence, and finance or procurement decision owners.

5. Review quality, remedies, and continuity together

Trace changes across inspection, acceptance, latent defects, warranties, replacement rights, indemnities, liability limits, and termination. A preserved warranty may offer less practical protection if signed wording narrows defect notification or changes the cap applying to replacement costs.

The first SEC example, §§ 5.1–5.2, contains an initial inspection period, separate latent-defect reporting, deemed-acceptance language, and related rejection remedies. Those provisions must be read together; the inspection period is contractual, not a general statutory deadline.

For continuity, compare stock ownership, replenishment, allocation, alternate sourcing, exclusivity exceptions, tooling access, and transition assistance. Check whether changed ordering conditions restrict an otherwise preserved alternate-source right.

Record: linked clause references, combined buyer consequences, and quality or operations assessments needed. Do not treat interacting clauses as isolated deviations.

6. Reconcile deviations with approval and legal questions

Locate approval for each substantive change and determine its scope. Approval of base prices does not necessarily cover an escalation formula. Where evidence is missing, report “approval not located,” not “unauthorized.”

Separate execution discrepancies from later modification or waiver questions. Where the relevant New York Article 2 provisions apply, UCC § 2-209(1)–(4) permits modification without consideration, preserves applicable signed-record and statute-of-frauds requirements, and recognizes that an ineffective attempted modification can operate as a waiver. Subsection (2) includes a separate-signature qualification for certain merchant-supplied forms outside transactions between merchants.

A comparison cannot establish assent, authority, or the effect of later conduct. Do not assume an email either amended the agreement or had no effect.

Record: approval sources, unresolved communications or performance questions, and counsel’s assigned analysis.

7. Issue an exception report and correction instructions

Group results into verified matches, approved differences, unresolved deviations, and incomplete evidence. Prioritize by financial exposure, production impact, and operational urgency—not changed-word counts.

For each exception, identify the route: obtain evidence, seek internal acceptance, discuss correction with the supplier, or prepare a proposed amendment. Internal acceptance records a buyer decision; do not present it as a bilateral change.

If an order or shipment is imminent, identify the issue requiring an immediate decision and who can make it. Do not assume the comparison itself authorizes suspending performance.

Record: action, owner, decision status, and closure evidence. Circulate the checklist, preserved comparison, and concise exception summary rather than an unsupported assurance that the contract is “clean.”

Worked example

Fictional scenario. Alder Circuit Manufacturing buys custom sensor housings from Northbank Components. Legal approved D-17 for estimated annual purchases of $1.8 million. Procurement receives signed package E-01 before placing its next order. All parties, documents, amounts, and terms below are fictional.

The body largely matches, but pricing weighting changes, an alternate-source exception narrows, and an incorporated quality revision is unavailable. Approval email AP-04 covers base prices only. The fictional price formula applies index movement to the stated proportion of the base unit price, subject to conditions not yet tested.

V01 moves the package from routine filing to pricing review. On an assumed $100 unit price, a qualifying 10% index rise would produce $103 under draft weighting and $110 under signed weighting, assuming no other limits. This shows sensitivity, not an actual payable price or annual exposure.

V02 requires legal and operational review: removing consent would not establish that another supplier can produce qualified housings. V03 prevents a complete-match conclusion. Obtain revision 5; do not invent its contents or assume the reference is clerical. The next-order decision belongs with assigned decision-makers while these issues remain open.

Common mistakes

• Comparing the newest filename. Establish approval provenance; chronology is not approval evidence.
• Stopping after the body matches. Verify schedules, quality revisions, specifications, and incorporated terms separately.
• Reporting changes without consequences. Explain interactions with remedies, exclusivity, pricing, and purchase commitments.
• Treating missing approval as proof of misconduct. Describe the searched record and assign investigation without overstating conclusions.
• Correcting the signed file in place. Preserve it unchanged and prepare a separate proposed correction or amendment.

Final quality check

• The baseline is tied to approval covering relevant schedules.
• Execution documents have stable IDs and identified completeness gaps.
• Every reported substantive difference is verified against both originals.
• Price tables, specification revisions, and incorporated terms are compared or expressly unresolved.
• Cross-references and linked acceptance, remedy, cap, and continuity provisions are tested.
• Calculations separate contractual inputs from illustrative assumptions.
• Every open issue has an owner and required decision; closed issues retain evidence.
• Legal propositions are checked against their sources; textual matching is not presented as an enforceability, modification, or waiver conclusion.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review capabilities can support assessment of identified differences. In Word, choose the buyer as represented party and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. Lawyers can edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name, or dismiss findings with reasons. Use a separate correction draft and retain human verification of the executed record. Book a demo to discuss this workflow.

Frequently asked questions

What if the last approved draft cannot be found?

Use the best-supported candidate provisionally and label it unconfirmed. Seek approval correspondence and negotiation attachments. Identify differences without claiming they depart from an approved position.

Should we compare every purchase order?

Start with incorporation and priority language. Review orders relevant to execution or a specific discrepancy. A broader order audit is a separate assignment, not an automatic part of version verification.

Can an exact text match close the review?

Only after checking completeness and nontext elements. Missing exhibits, changed dates, handwritten additions, and unverified incorporated terms can prevent closure despite matching extracted text.

What if supply has begun under changed terms?

Preserve communications and performance records and assign counsel the modification or waiver analysis. Do not conclude from the comparison alone which terms govern or whether prior conduct can be reversed.

Sources

• New York UCC § 2-209 — Modification, Rescission and Waiver.
• SEC Exhibit 10.1 — Supply Agreement, §§ 3.5 and 5.1–5.2.
• SEC Exhibit 10.6 — Supply Agreement, § 3.2.

The SEC agreements illustrate negotiated wording, not market standards. Apply the New York provision only after determining coverage and applicable statutory version.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.