How to compare draft and executed versions for SaaS Subscription Agreements

Compare the complete signed SaaS package with the exact customer-approved signing version. Review text, commercial tables, incorporated terms, attachments, and execution details separately, then determine whether each difference changes the customer’s rights, costs, or operational assumptions. Record source locations, approval evidence, unresolved questions, and corrective actions in a version comparison checklist. The deliverable is a verified difference register distinguishing approved concessions, presentation changes, and unexplained deviations, with an explicit disposition for each issue before the package receives a fully verified repository designation.

When to use this workflow

Customer counsel and legal operations should use this workflow upon receiving a signed subscription agreement, renewal, expansion order, or amendment. It is especially useful when the supplier generates the signing PDF, combines negotiated documents with standard attachments, or replaces an order form immediately before signature.

The task is execution reconciliation, not renegotiation. Record newly identified substantive concerns separately so an approved compromise is not mislabeled an unauthorized change. Conversely, an internally unauthorized departure should not automatically be treated as legally ineffective.

This U.S.-oriented guide uses an October 13, 2026 research cutoff. Contract consequences depend on the language, governing law, facts, and deal context. California privacy requirements require a separate applicability assessment; flag cross-border requirements for the relevant specialist.

What you need

Collect the approved native draft, any approved signing PDF, and the authorization record identifying what could be signed. Include approved business exceptions and unresolved negotiation comments. A filename containing “final” is not approval evidence.

Obtain the executed package, signature pages, and available signing completion record. Assemble approved and signed versions of:

• Master agreements, orders, amendments, and product-specific terms.
• DPAs, processing descriptions, security schedules, SLAs, and acceptable-use policies.
• Pricing tables, usage entitlements, implementation scope, and support commitments.
• Incorporated online terms and dated copies retained during negotiation.

Also collect procurement’s approved entities, products, quantities, term, currency, billing frequency, and commencement assumptions. Identify the legal, commercial, privacy, and implementation decision-makers. These internal records establish the authorized baseline; they do not themselves override signed terms.

Use the template

Use the SaaS Subscription Agreements — Version comparison checklist below. Copy this table into your working document or spreadsheet. Create one row per material difference or evidence gap. Maintain package inventories alongside it; the checklist records findings rather than every unchanged clause.

Assign stable document IDs, such as APP-OF-01 and EXE-OF-01. Cite sections, PDF pages, and table rows; use sheet names and cell references for spreadsheets.

“Evidence / difference” captures short excerpts or exact values from both versions. “Customer effect” explains the consequence. Separate confidence from severity: an unavailable DPA may present a serious evidence gap even though no particular wording change is yet established.

Useful statuses include approved change, presentation only, unexplained deviation, and missing source. Close substantive rows with identified approval or corrective evidence, not merely a review date. Put an owner and target resolution date in the action field.

Step by step

1. Freeze the approved and executed packages

Preserve read-only originals and compare working copies. Inventory document IDs, filenames, dates, page counts, and attachments. Keep signing records with the package, but do not treat completion of signing as proof that every term received internal approval.

If competing drafts claim to be final, obtain a baseline decision from the approving lawyer. Do not select whichever version resembles the signed document most closely. Where approval covered a particular PDF, compare that PDF as well as its native source.

Record: package identifiers, baseline approval evidence, and a finding for each missing or disputed baseline document.

2. Map precedence and incorporation

Read the package’s actual precedence and incorporation provisions before evaluating changes. Determine whether an order, amendment, DPA, or product term displaces master-agreement language. Check document titles, version dates, and attachment references against what was delivered.

For example, § 12.3 of an SEC-filed Salesforce agreement ranks the applicable order form above the master agreement and Documentation, and rejects customer purchase-order terms. This is contractual wording, not a universal SaaS hierarchy.

Compare hyperlink destinations and version references, not merely visible labels. If historical content is unavailable, mark the signing-date wording unverified. A current webpage is not sufficient evidence of its earlier contents.

Record: changed document relationships, missing schedules, affected protections, and the person responsible for obtaining unavailable versions.

3. Compare text and verify the source images

Run comparisons between corresponding files using suitable document comparison tools. For scans, use extracted text to locate differences, then check material findings against page images. Separately inspect tables, footnotes, exhibits, headers, and handwritten additions.

Distinguish additions, deletions, substitutions, moved text, and presentation changes. Recheck definitions and cross-references after clause moves; unchanged reference text may point to a different provision after renumbering. A formatting change is not harmless if it obscures an exclusion or changes a table’s alignment.

A clean automated comparison does not establish completeness. Missing exhibits and image-based tables require independent inspection.

Record: exact source locations, verified wording, and whether verification used text comparison, visual inspection, or attachment review.

4. Reconcile subscription economics and dates

Compare products, service tiers, licensed entities, seats, pooled quantities, usage units, currency, discounts, billing frequency, and tax wording. Check individual cells, not just totals. Determine whether a quantity edit changes the unit rate, minimum commitment, or overage exposure.

Review signature, commencement, activation, billing, expiration, and renewal dates independently. Identify the controlling trigger for each. If commencement moves, check whether expiration moves too; otherwise the paid service period or renewal timetable may differ from approval.

The historical SEC-filed order form’s Utilization notice addresses no rollover, Central Standard Time measurement, monthly arrears billing, and contractual rather than technical usage limits. It illustrates why notes matter, not current pricing or customary practice.

Record: changed economic inputs, calculation assumptions, operational dependencies, and the commercial decision-maker.

5. Trace changed protections across documents

Read changed liability caps, exclusions, indemnities, suspension rights, SLA remedies, security commitments, and data-use permissions together. Check whether product terms narrow an unchanged master protection. Compare export access, retention, deletion, and transition support with the approved package without expanding the task into a complete exit-planning review.

For covered California service-provider or contractor relationships, 11 CCR § 7051(a)–(b) specifies contractual processing restrictions, purposes, oversight rights, inability-to-comply notification, remediation rights, and subcontractor requirements. A changed DPA therefore calls for targeted applicability and language review, not an assumption that every SaaS supplier is covered or that unrestricted audits are required.

Record: connected clauses, the verified consequence or evidence gap, and the legal, privacy, or technical reviewer assigned to resolve it.

6. Verify execution details and approval provenance

Compare legal names, signature blocks, capacities, dates, counterpart pages, and handwritten changes. Investigate mismatched pages and references to absent orders. Refer questions about authority or execution effect to counsel rather than inferring validity from a signature image.

Match substantive differences to specific approval evidence. Approval of a topic is not necessarily approval of the signed wording or commercial configuration. Distinguish authority to negotiate from authority to accept the final departure.

Record: approval source and scope, unexplained execution differences, and questions about authority or corrective documentation.

7. Resolve deviations and release the record

Separate clerical reconciliation from changes requiring counterparty agreement. Never silently alter the signed PDF to match the approved draft. Counsel should determine whether resolution needs clarification, an amendment, replacement execution, or documented acceptance of the departure. Internal acceptance alone does not rewrite signed language.

Preserve originals, comparison output, findings, approvals, and corrective instruments together. Update repository metadata from verified evidence. If operations must proceed before resolution, obtain a named decision-maker’s direction and communicate the uncertainty; a conditional repository status is not a conclusion about enforceability.

Record: disposition, owner, closure evidence, and whether the package is verified, conditionally released, or awaiting resolution.

Worked example

The following parties, documents, amounts, and provisions are entirely fictional.

Harborlight Analytics LLC approves a two-year subscription from Aldercloud Systems Inc. for $144,000 annually. The approved order provides 2.4 million API events pooled annually. Approved MSA § 8 incorporates negotiated Schedule D. The signed package instead contains quarterly limits, an earlier commencement date, and an online DPA reference in MSA § 8.

Counsel holds the approved package and approval email but no signing-date copy of the linked DPA. Procurement confirms that authorization assumed annual pooling. Implementation expected production access on January 1, 2027, and has not confirmed earlier readiness. Both order versions define the subscription term as 24 months from commencement, with no separate fixed expiration date.

The unchanged annual fee does not establish a match. Quarterly expiry removes annual flexibility, but no usage forecast or applicable overage calculation supports a dollar estimate. The commencement edit changes timing rather than the stated 24-month duration; readiness determines its practical impact.

The DPA issue is an incorporation change and evidence gap. Counsel cannot identify which protections differ without the referenced text. The package should remain short of fully verified status while the three assigned questions are resolved, without reopening unrelated approved compromises.

Common mistakes

• Comparing only the master. Include orders and product terms containing economics and overrides.
• Equating unchanged totals with unchanged economics. Compare measurement windows, expiry, minimums, and overage units.
• Using live terms as historical proof. Preserve them separately and seek signing-date evidence.
• Calling every difference unauthorized. Match each substantive change to its actual approval record.
• Repairing the signed file locally. Preserve the original and obtain an authorized, traceable correction.

Final quality check

• The baseline has identifiable approval evidence and a stable version ID.
• The package inventory identifies missing documents and historical online terms.
• Material comparison findings match their source pages.
• Tables, dates, signatures, and hyperlinks received separate checks.
• Affected precedence rules, definitions, and cross-references were tested.
• Substantive differences have approval evidence or an assigned resolution owner.
• Closure evidence and repository status accurately reflect remaining uncertainty.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review capabilities support represented-party selection and deal-specific instructions in Word. Findings quote and locate clauses, rank severity, and identify missing language as not present. Lawyers edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name and can dismiss findings with reasons. Tabular review supports work across documents; completeness checks, historical verification, and corrective decisions remain with the legal team. To discuss this workflow, book a demo.

Frequently asked questions

Which draft is the baseline?

Use the version authorized for signature. Resolve conflicting legal and procurement approvals first; do not construct a new baseline from preferred provisions across drafts.

Must unchanged renewal wording be checked?

Yes: changed dates or order overrides can alter its operation. Section 11.2 of the Salesforce example makes its default renewal mechanism subject to order-form variation. Its 30-day notice requirement is contractual, not a general statutory deadline.

What if the online DPA is unavailable?

Record the reference and request dated evidence. Until obtained, describe the wording as unverified rather than equivalent to the approved attachment or missing particular protections.

Can counsel redline the executed agreement?

Use a clearly labeled working redline to explain proposed corrections. Preserve the signed original, and have counsel select the corrective instrument and approval process.

Sources

• SEC Exhibit 10.12: Salesforce Master Subscription Agreement and Order Forms, §§ 11.2, 12.3 and Utilization notice; historical contractual examples only.
• California CCPA Regulations effective January 1, 2026, 11 CCR § 7051(a)–(b); apply only after assessing coverage.

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.