How to compare draft and executed versions for Consulting Agreements

Compare the executed consulting agreement against the last client-approved draft, not simply the latest file in the folder. Identify the complete agreement set, generate a comparison, and verify changes against the signed pages, including statements of work, pricing tables, exhibits, signatures, and dates. Assess each verified difference against the approved position and the client’s project requirements. The resulting version comparison checklist should distinguish authorized deviations, unexplained changes, missing evidence, and assigned corrective actions, while preserving the signed record separately from proposed corrections.

When to use this workflow

Use this workflow when client-side counsel receives a signed consulting agreement, discovers inconsistent execution copies, or needs to confirm that the final package reflects negotiated terms. Legal operations and procurement teams can assemble the record; counsel should assess material deviations and the appropriate response.

The task is execution control, not a fresh negotiation of every provision. Review unchanged language where a changed definition, attachment, or cross-reference affects its meaning. Do not describe an unchanged but unfavorable provision as an execution discrepancy.

This guide uses a US commercial-contract perspective. Federal copyright requirements are identified below; other contractual consequences depend on the agreement, governing law, facts, and transaction. Classification, tax, privacy, and foreign intellectual-property questions require separate analysis when implicated.

What you need

Collect the last approved draft and evidence identifying exactly what was approved. An email approving fees alone does not establish approval of a later ownership revision. Obtain the signed agreement, available signature counterparts, and the execution transmission or completion record.

For consulting engagements, gather the statement of work, deliverable schedule, acceptance criteria, pricing tables, expense policy, background-technology schedule, and incorporated licenses. Include amendments and side letters. Record unavailable attachments as missing evidence rather than assuming they match earlier drafts.

Also collect the client’s negotiation checklist, deal-specific instructions, approved fallbacks, and escalation authorities. Identify the sponsor who can assess revised milestones, staffing, and handover obligations. Preserve original files and compare working copies. Confirm whether the approved file contains unresolved tracked changes or comments; do not silently choose their intended disposition.

Use the template

Use Consulting Agreements — Version comparison checklist as the comparison record. You can copy this table into your working document or spreadsheet. Assign stable document IDs, such as D1 for the approved agreement and E1 for the executed agreement; identify each attachment separately.

Give each material difference its own row. In “Topic / source,” include both document IDs and clause/page citations, or table row and cell references. Preserve short excerpts where wording matters; summaries can conceal conditions and exceptions.

“Difference / uncertainty” distinguishes changed text, language not present, unavailable documents, and unreadable text. “Client consequence” states the practical effect. “Action / owner” should include a target decision date when needed. “Status / proof” identifies the approval evidence, corrective instrument, or expressly accepted residual risk supporting closure. Keep related issues cross-referenced rather than duplicating the same finding across several rows.

Step by step

1. Establish the approved baseline and signed record

Identify the version the client authorized for signature. Match its contents, attachments, and approval message; a filename or timestamp is insufficient. If counsel and procurement approved different versions, resolve or expressly document that conflict before selecting a baseline.

Inventory the signed package by page count, attachment title, version date, signatory, and execution date where shown. Distinguish the stated effective date from signature dates. Determine whether the package contains the agreement or only detached signature pages. Preserve inconsistent signed copies without silently combining them.

Record: a control row identifying the baseline, signed document IDs, approval evidence, and unresolved package discrepancies.

2. Map attachments and document priority

Match each approved statement of work and schedule to its executed version. Check identifiers for incorporated expense policies and technology schedules. Compare priority provisions before deciding which conflicting language controls.

For example, the Neoleukin consulting agreement, § 8.9 gives its statement of work and specified Contingent Value Rights Agreement precedence over conflicting consulting-agreement terms. This is negotiated wording, not a universal hierarchy. An unchanged master agreement therefore does not establish unchanged obligations where a controlling attachment differs.

Record: attachment matches, priority changes, missing documents, and the person responsible for obtaining each missing source. Distinguish an attachment referenced but unavailable from one verified as absent from the received execution package.

3. Generate and verify the comparison

Generate a document comparison using appropriate tools and working copies. For scanned execution copies, check extracted text against page images. Visually inspect tables, footnotes, handwritten changes, headers, signature blocks, and exhibit boundaries.

Separate cosmetic differences from substantive changes, but check altered numbering for broken cross-references. Verify apparent deletions against the source page before reporting them. A blank extraction result does not establish that a clause was omitted. Likewise, a visually similar pricing table should not be cleared without checking amounts, units, and payment triggers.

Record: verified differences with paired citations and enough text to reproduce the finding. Flag unreadable passages separately and assign someone to obtain a clearer copy.

4. Test changes to the consulting bargain

Compare deliverables, acceptance tests, revision rounds, staffing commitments, substitution rights, milestones, fee triggers, and change-control authority. Ask whether payment moved from accepted output to delivery or elapsed time, or whether a defined deliverable became discretionary assistance. Trace consequential changes into the statement of work and pricing schedule.

For expenses, separate advance approval from reasonableness, receipts, caps, and policy compliance. The Castle Biosciences agreement, § 3 combines prior written approval with reasonable service-related expenses, policy compliance, and requested verification. These are distinct negotiated controls, not statutory reimbursement requirements.

Record: the changed trigger or condition, affected amount or project dependency where known, and commercial decision owner. Identify missing assumptions instead of inventing exposure figures.

5. Trace ownership and exit dependencies

Compare assignment language, background-material exceptions, third-party components, subcontractor obligations, and licenses needed to use or modify deliverables. Delivery alone does not establish copyright ownership: 17 U.S.C. §§ 202 and 204(a) distinguish ownership of a material object from copyright and require a signed writing evidencing a copyright ownership transfer, other than by operation of law, from the rights owner or authorized agent.

Do not treat retained work-made-for-hire wording as an automatic substitute for a deleted assignment. The Copyright Office’s Circular 30 explains the limited statutory categories and express signed-agreement requirement for specially commissioned works; employee-created work follows a separate scope-of-employment route.

Check changed termination provisions against notice methods, deemed delivery, unfinished-work delivery, and transition access. A revised notice period cannot be assessed independently of its delivery mechanics.

Record: ownership or exit deviations, affected dependencies, missing creator or subcontractor evidence, and questions requiring specialist review.

6. Reconcile deviations with approval authority

Classify verified changes as approved, unexplained, or requiring a new decision. Search correspondence for approval of the specific revision, not general enthusiasm about closing. Check the approver’s internal authority and any conditions attached to approval.

Assess confidentiality, indemnity, liability-limit, and survival changes in relation to the affected consulting services. Distinguish commercial disadvantage from uncertain legal effect. A broader background-material exclusion, for example, may require both a business assessment of usability and legal analysis of the remaining license.

Record: rationale, approver, evidence, residual uncertainty, and escalation priority. Internal approval establishes the client’s recorded decision; it does not by itself amend the signed agreement or resolve disputed legal consequences.

7. Prepare the exception report and correction package

Summarize material deviations for counsel and the business sponsor. Separate verified changes, missing evidence, and recommended responses. Identify whether each next step is obtaining documents, confirming existing approval, requesting an explanation, or proposing corrective language.

Do not edit the executed copy to resemble the approved draft. Preserve it and prepare proposed corrections separately. Check the actual amendment requirements: the Neoleukin example, § 8.9 requires signed writings for amendments, but another engagement may differ. Compare any corrective instrument with the identified deviations before closing them.

Record: disposition, owner, target decision date, and closure evidence. Give operational teams verified terms with unresolved issues clearly identified, not an unqualified clean-match statement.

Worked example

Fictional scenario: Alder Cove Manufacturing retains Juniper Process Consulting for an $84,000 production-planning engagement. All parties, documents, amounts, and clause details in this example are fictional. D1 is the approved agreement and D2 its approved statement of work; E1 and E2 are their respective executed versions.

D1 requires written preapproval for travel and assigns project deliverables subject to a scheduled background-tool exception. D2 makes the final $24,000 payable on written acceptance. E1 retains work-made-for-hire wording but omits the assignment paragraph and travel preapproval. E2 changes the final payment trigger to delivery. The execution email references a background-tool schedule that was not supplied. No approval evidence for these changes has been located.

The package cannot be reported as matching the approved terms. V01 requires the missing schedule and ownership analysis; retained work-made-for-hire wording does not justify clearance. V02 changes when the final fee becomes payable, although invoice timing and other payment conditions still need checking. V03 concerns spending authority rather than proof of expenditure. These distinctions support separate decisions instead of a single request to approve all deviations.

Common mistakes

• Using the newest draft: An unapproved revision becomes the baseline. Anchor the comparison to specific approval evidence.
• Checking only the master: A revised statement of work changes acceptance or payment. Compare incorporated components and priority provisions.
• Treating delivery as ownership: Handover language conceals a deleted assignment. Review those obligations separately.
• Dismissing table changes as formatting: A shifted milestone cell changes a fee trigger. Verify rows, columns, amounts, and conditions.
• Treating missing evidence as a deletion: An unavailable schedule is reported as omitted contractual protection. State exactly what was received and what remains unverified.
• Repairing the signed file: The received record becomes obscured. Preserve it and document corrections separately.

Final quality check

Before releasing the comparison, confirm that:

• The baseline is tied to specific approval evidence.
• Signed copies, signature dates, and referenced attachments are inventoried.
• Each material difference has paired clause, page, or cell references.
• Extracted findings have been checked against source pages.
• Acceptance, payment, expenses, ownership, and exit dependencies are traced.
• Approval decisions identify authority and supporting evidence.
• Open issues are resolved or expressly assigned with next actions.
• Closure evidence is retained and signed records remain unchanged.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. For contract review, choose the represented party or neither in Word 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 working draft for corrections and verify findings against the execution package. Tabular review supports review across multiple documents; legal judgment and approval decisions remain with the team. Book a demo to discuss this workflow.

Frequently asked questions

Which draft should be the baseline?

Use the version supported by client approval evidence. If approval covers only selected terms, record that limitation and resolve the remaining baseline question before reporting a clean match.

What if the executed statement of work is missing?

Mark it unavailable and request it. Qualify conclusions about deliverables, pricing, and priority. An approved draft is not evidence that the same statement of work was executed.

Does work-made-for-hire wording clear an assignment deletion?

Not automatically. Evaluate the deliverable, authorship facts, applicable ownership route, and remaining terms against the requirements explained in Circular 30. Escalate unresolved ownership questions rather than relying on the label.

Does every difference require an amendment?

No. Verify its effect and approval status first. Cosmetic or authorized differences may require only a documented disposition. Material discrepancies may require correction; counsel should select the response using the actual agreement and circumstances.

Sources

• U.S. Copyright Office: Copyright Act, Chapter 2, §§ 202 and 204.
• U.S. Copyright Office: Circular 30, Works Made for Hire.
• Castle Biosciences consulting agreement, § 3.
• Neoleukin Therapeutics consulting agreement, § 8.9.

Scope: General professional workflow guidance, not advice for a particular matter. The filed agreements illustrate negotiated wording, not market standards or enforceability conclusions.

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.