How to Compare Two Contract Versions with AI

A revised contract lands in your inbox and the other party says the changes are minor. Reading both versions line by line to verify that claim can take the better part of a morning, and it is easy to miss something on page 14 while your attention drifts. AI can identify what actually changed between two contract versions in seconds, covering every clause, and tell you which differences carry risk.

AI will not tell you whether to accept the changes. That decision depends on your negotiating position, your relationship with the other party, and sometimes on legal advice. But it can show you exactly what moved, what disappeared, and what was added, so you are making that decision with full information. This tutorial shows you how.

What you will learn

• Identify every meaningful change between two contract versions without reading both documents in full
• Spot added obligations and removed protections before they become your problem
• Compare payment terms, termination rights, IP ownership, and liability clauses side by side
• Understand why a change was made, based on what the revised language actually says
• Build a clear list of changes to accept, reject, or push back on before replying to the other party
• Know when the changes are significant enough to involve a lawyer

In this guide

• Who is this for
• How AI compares contract versions
• Before you compare contracts with AI
• Step 1: Upload both versions
• Step 2: Get a high-level summary of changes
• Step 3: Identify added obligations
• Step 4: Identify removed obligations and protections
• Step 5: Compare payment and pricing terms
• Step 6: Compare termination clauses
• Step 7: Compare intellectual property clauses
• Step 8: Compare confidentiality and liability clauses
• Step 9: Ask for a risk summary of changes
• Step 10: Decide what to do next
• Worked example
• Common mistakes
• When AI is enough and when it is not
• Privacy and document security
• Before you compare: checklist
• Prompts you can copy
• What you learned
• Next step
• Related tutorials

Who is this for

This tutorial is for people who receive a revised version of a contract and need to understand what changed. That includes:

• Freelancers and contractors who receive client revisions to an agreement they have already reviewed
• Business owners comparing a vendor's updated terms against the version they originally signed
• Procurement and operations staff reviewing amended service contracts
• Startup founders comparing term sheets or SaaS agreements after a round of negotiation
• Anyone who has been told "the changes are minor" and wants to verify that independently

If you have not yet reviewed the original contract, start with How to Review a Contract with AI first. That tutorial covers single-document review. This one assumes you already understand the original agreement.

How AI compares contract versions

Before getting into steps, it helps to understand what happens when you upload two contracts for comparison.

LearnByAI uses Retrieval-Augmented Generation (RAG). When you upload both versions and ask about differences, the AI reads both documents in full and answers based on what is actually written in each. It does not rely on tracked changes or redline formatting, which means it can identify differences even in clean PDFs where no changes have been marked. You can read more about how AI document chat works.

The AI treats each version as a complete document. It can find clauses that appear in one version but not the other, compare the language of matching clauses, and flag where phrasing has shifted in ways that change meaning.

AI handles this well	A human lawyer is still needed
Identifying which clauses changed between versions	Advising whether a change is acceptable in your jurisdiction
Explaining what revised language means in plain English	Assessing the negotiating implications of a change
Spotting added or removed obligations	Interpreting how a change interacts with other contracts you hold
Comparing payment, termination, IP, and confidentiality terms	Advising on enforceability of specific clauses
Flagging changes that shift risk from one party to the other	Recommending negotiation strategy

Keep that distinction in mind throughout this tutorial.

Before you compare contracts with AI

Label your files clearly before uploading. Name your files something like contract-v1.pdf and contract-v2.pdf before you upload them. Clear filenames help you refer to each version precisely in your prompts and make the AI's responses easier to follow.

Use text-based PDFs or DOCX files. If either version was scanned as an image rather than saved as a text-based PDF, the AI may not read it correctly. If the AI says it cannot find a clause you know is there, copy the text into a Word document and upload that instead.

Upload both versions before asking any questions. Start the comparison session by uploading both files. Uploading them together means the AI can reference both throughout the session without you needing to re-upload.

One comparison per session. If you are comparing more than two documents, run separate sessions for each pair. Mixing three or more versions in one session tends to produce confused references.

Step 1: Upload both versions

Go to the AI Legal Document Review page. Upload both versions of the contract before typing your first question. Once both documents are processed, you are ready to start.

Step 2: Get a high-level summary of changes

The first question to ask is not about a specific clause. Ask for the big picture. This tells you which areas changed and how significant the revision is overall.

Prompt to use:

I have uploaded two versions of the same contract. Please compare them and give me a high-level summary of what changed. Which sections were modified, what was added, and what was removed?

What a good response looks like:

Comparing the two versions, I can identify changes in four areas. First, the payment section has been revised: the original specified payment within 30 days of invoice, while the revised version extends this to 45 days. Second, the liability clause has changed: the original included a mutual liability cap of £50,000, but the revised version removes the cap entirely. Third, the termination notice period has been shortened from 30 days to 14 days in the revised version. Fourth, a new clause has been added in Section 11 covering data processing obligations that did not appear in the original.

This summary is your map. It tells you where the real differences are and lets you prioritise which areas to investigate in detail. If the summary mentions more changes than you expected, that is a signal to slow down before responding to the other party.

Step 3: Identify added obligations

New obligations are the changes most likely to affect what you are committing to. This step surfaces every new requirement that appears in the revised version but not the original.

Prompt to use:

What obligations appear in the revised version that were not present in the original? List each new obligation, which party it applies to, and where it appears in the document.

What a good response looks like:

Three obligations appear in the revised version that were not in the original. First, Section 4.3 now requires the service provider to submit a monthly progress report by the fifth business day of each month. This obligation did not exist in the original. Second, Section 8.1 has been expanded to require the service provider to maintain professional indemnity insurance of at least £500,000, specifying a minimum coverage amount not previously stated. Third, Section 11 is entirely new and requires both parties to enter into a Data Processing Agreement within 30 days of signing. No equivalent clause appeared in the original.

Read each new obligation carefully. Some will be routine. Others, like new insurance requirements or reporting commitments, have real operational costs. The goal at this step is not to reject changes automatically, but to know exactly what you are accepting.

Step 4: Identify removed obligations and protections

Removals are harder to spot than additions, because something missing does not draw your eye the way new text does. This step finds what the other party quietly took out.

Prompt to use:

What was present in the original version that has been removed or significantly weakened in the revised version? Focus on obligations, protections, and rights that applied to me.

What a good response looks like:

Two provisions from the original have been removed or weakened. First, the original included a mutual liability cap of £50,000 in Section 9. This cap has been removed entirely in the revised version, leaving both parties with uncapped liability exposure. Second, Section 12 in the original gave both parties the right to terminate for convenience with 30 days' notice. In the revised version, this right has been removed for the service provider but retained for the client. The client can now terminate at any time with 30 days' notice, while the service provider can only terminate for cause.

Asymmetric changes are the ones that tend to matter most. A change that removes your right to terminate while preserving the other party's right is not a minor revision. Ask yourself whether the original document was negotiated that way, and whether the removal is acceptable.

Step 5: Compare payment and pricing terms

Payment terms are among the most commonly revised clauses in amended contracts. Small changes in payment timing, milestone definitions, or late payment conditions can have meaningful cash flow implications.

Prompt to use:

Compare the payment terms in both versions. What changed in the payment schedule, amounts, due dates, milestone conditions, or late payment provisions?

What a good response looks like:

The original version required payment within 30 days of invoice, with a late payment interest rate of 8% per annum on overdue amounts. The revised version extends the payment period to 45 days and removes the late payment interest clause entirely. The milestone structure is unchanged: three equal payments on signing, delivery of draft, and final acceptance. However, Section 5.2 in the revised version adds a new condition requiring written sign-off from the client's procurement department before each payment is released, a condition not present in the original.

That last addition, a sign-off requirement from a specific department, changes a straightforward payment schedule into one that depends on an internal process at the other party's organisation. That kind of operational dependency is worth flagging before you accept it.

Step 6: Compare termination clauses

Termination clauses determine how and when either party can exit the agreement. Changes here often shift the balance of power significantly, and they are not always obvious from the summary level.

Prompt to use:

Compare the termination clauses in both versions. What changed in the notice period, grounds for termination, consequences of early termination, and any rights each party has on exit?

What a good response looks like:

In the original, either party could terminate for convenience with 30 days' written notice. The revised version removes the service provider's right to terminate for convenience entirely. The service provider can now only terminate if the client is in material breach and fails to remedy it within 14 days of written notice. The client retains the right to terminate for any reason with 14 days' notice, reduced from 30 days in the original. On termination, the original required the client to pay for all work completed to date. The revised version limits this to work completed and formally accepted in writing, which may exclude work in progress at the point of termination.

A shorter notice period gives you less time to wind down work and find alternative clients. Losing the right to terminate for convenience while the other party keeps it is a significant imbalance. Both changes warrant a direct conversation before you accept them.

Step 7: Compare intellectual property clauses

IP clauses are among the most commercially significant parts of any service contract. Revisions here can affect what you retain, what you assign away, and whether you can use your own work elsewhere.

Prompt to use:

Compare the intellectual property clauses in both versions. What changed in who owns the work product, when ownership transfers, whether background IP is covered, and whether any licence rights were added or removed?

What a good response looks like:

The original assigned ownership of final deliverables to the client upon receipt of full payment. The revised version extends this to all work product created during the engagement, including drafts, working files, and preliminary concepts, and moves the transfer of ownership to the point of creation rather than payment. Section 6.3 in the revised version also adds an assignment of background intellectual property if it is incorporated into the deliverables, which was not present in the original. A new clause in Section 6.4 prohibits the service provider from using any portion of the work in their portfolio without prior written consent.

The shift from "final deliverables on payment" to "all work product on creation" is a substantial change. It means you no longer own your working files even if the project is abandoned before payment. Paired with the portfolio restriction, this version significantly limits what the service provider retains.

Step 8: Compare confidentiality and liability clauses

Confidentiality and liability clauses often attract less attention than payment or IP terms, but they can carry significant risk if revised in the wrong direction.

Prompt to use:

Compare the confidentiality and liability clauses in both versions. What changed in the scope of confidential information, how long confidentiality obligations last, liability caps, exclusions, and indemnification obligations?

What a good response looks like:

On confidentiality: the original set a two-year confidentiality obligation after termination. The revised version extends this to five years. The definition of confidential information is broader in the revised version, now including pricing information and internal processes that were not listed in the original. On liability: the original included a mutual liability cap equal to the total contract value. The revised version removes the mutual cap and replaces it with an uncapped indemnification obligation on the service provider for any losses arising from errors in the deliverables, while the client's liability remains capped at the contract value. The indemnification obligation in the revised version does not require the client to mitigate their losses before making a claim.

A confidentiality period that doubles in length has operational implications, particularly if you work with clients in the same industry. The asymmetric liability change, uncapped for the service provider, capped for the client, is the kind of change that warrants legal advice before acceptance.

Step 9: Ask for a risk summary of changes

After working through each area, ask the AI to consolidate what it found into a practical summary. This is the most useful output for making a decision or preparing a response to the other party.

Prompt to use:

Based on your comparison of both versions, what are the three to five most significant changes from my perspective as the service provider? Focus on changes that increase my risk, reduce my protections, or add obligations I should consider carefully.

What a good response looks like:

Five changes stand out as significant from the service provider's perspective. First, the liability cap has been removed and replaced with an uncapped indemnification obligation, which is the highest-risk change in the revised version. Second, the service provider has lost the right to terminate for convenience, while the client's termination rights remain broad. Third, IP ownership now transfers at the point of creation rather than on payment, affecting leverage if a payment dispute arises. Fourth, the confidentiality period has more than doubled, which may restrict your ability to discuss the engagement for years after it ends. Fifth, the new procurement sign-off requirement in the payment clause introduces a dependency that could delay every payment without triggering a late payment claim.

This summary is the foundation for your response to the other party. Each point is specific, tied to a clause, and actionable.

Step 10: Decide what to do next

After Step 9, you have a clear picture of what changed. The question is what to do with it.

• The changes are acceptable. Nothing material shifted, or the changes are ones you anticipated and can live with. Confirm your acceptance and move forward.
• Some changes need to go back. You have specific points to push back on. Use the AI's clause-by-clause comparisons to draft precise redlines rather than general objections.
• The changes require a lawyer. The liability cap removal, the IP ownership change, or the termination asymmetry are substantial enough that you want legal advice before accepting. Take your session summary into that meeting. You will get more from the hour.

Worked example

Here is a complete walkthrough.

Situation: A software developer receives a revised version of a development services agreement from a client. The client's email says the changes are "mostly administrative." She uploads both versions to LearnByAI.

Initial comparison prompt:

I have uploaded two versions of a software development agreement. Compare them and give me a high-level summary of what changed, which sections were modified, and anything that was added or removed.

AI response:

Comparing the two versions, I can identify changes in five areas. The payment schedule has been revised: the original split payment across three milestones with a 30-day payment window, while the revised version adds a fourth milestone and extends payment terms to 45 days. The liability clause has changed: the original included a mutual liability cap of £30,000, but the revised version removes the cap for the service provider while retaining it for the client. The termination notice period has been shortened from 30 to 14 days. The IP ownership clause has been rewritten to transfer ownership at the point of creation rather than on final payment. A new confidentiality clause extends the post-termination confidentiality period from two to five years.

What this tells her: Five changes across the most commercially sensitive areas of the contract. Nothing about this is "mostly administrative." She continues with targeted follow-up questions.

Follow-up prompt:

The original contract had a mutual liability cap of £30,000. What exactly does the revised version say about liability and what happened to the cap?

AI response:

The original Section 8 stated: "Neither party's total liability under this Agreement shall exceed £30,000." The revised Section 8 removes this mutual cap. In its place, Section 8.1 states that the service provider shall indemnify the client against all losses, claims, damages, and expenses arising from errors, omissions, or delays in the deliverables. Section 8.2 retains a £30,000 liability cap for the client only. There is no corresponding cap on the service provider's indemnification obligation, and no requirement for the client to mitigate losses before making a claim.

What this tells her: She had a mutual £30,000 cap. The revised version removes her cap entirely while keeping the client's cap in place. If a deliverable causes the client any loss, her exposure is now unlimited. This is not an administrative change.

Follow-up prompt:

What does the revised IP clause say compared to the original? When does ownership transfer, and does it cover work in progress?

AI response:

The original Section 6 stated that all intellectual property in the final deliverables would vest in the client upon receipt of full and final payment. The revised Section 6 states that ownership of all work product, including code, documentation, design assets, working files, and preliminary versions, vests in the client at the point of creation. There is no longer a payment condition attached to the transfer. Section 6.3 in the revised version also adds that background intellectual property belonging to the service provider, if incorporated into the deliverables, is licensed to the client on a perpetual, royalty-free basis, rather than remaining the property of the service provider.

What this tells her: Under the original, she owned her work until she was paid. If the client stopped paying, she could stop delivery. Under the revised version, the client owns everything as soon as she writes it, regardless of whether they have paid. Her leverage in a payment dispute has been significantly reduced.

What to verify with a lawyer: She should get legal advice on the liability cap removal and the IP transfer timing before responding. Both are substantial changes that shift financial and commercial risk in her direction. The "mostly administrative" framing was not accurate.

---

Common mistakes

Asking the AI to compare before uploading both files. The AI can only compare what it has access to. Upload both versions before typing your first question. If you forget and upload the second version mid-session, ask the AI to confirm it can see both documents before continuing.

Accepting the high-level summary as the full picture. The summary in Step 2 is the map, not the territory. It tells you where to look. Always follow up with specific questions on each changed area. Summaries can miss wording changes that alter meaning without removing whole clauses.

Treating identical section numbers as identical clauses. A clause in Section 6 in version one may not correspond to Section 6 in version two if sections were added or renumbered. Ask about the subject matter of the clause, not its number: "What does the revised version say about intellectual property ownership?" is more reliable than "What changed in Section 6?"

Focusing only on additions and ignoring removals. Removed protections are harder to notice than new obligations. Step 4 exists specifically to catch what the other party quietly deleted. Do not skip it.

Confusing stylistic changes with substantive ones. A clause rewritten in cleaner language is not the same as a clause unchanged in substance. If the AI flags a change in wording, ask whether the substantive meaning also changed: "Does the revised wording change what either party is actually required to do?"

Responding to the other party before completing the full comparison. It is tempting to reply as soon as you spot the first problem. Finish the full comparison first. Changes in one clause sometimes offset or interact with changes in another, and an incomplete review can lead to a poorly targeted response.

When AI is enough and when it is not

For most contract revisions, AI gives you a fast, complete picture of what changed. You know which clauses were affected, whether the change shifted risk in your direction, and which points to push back on.

A human lawyer is worth the time when:

• The liability cap was removed or reduced. Uncapped liability exposure is the single change most likely to justify legal advice before acceptance.
• The IP ownership clause was significantly rewritten. Changes that affect when ownership transfers, what background IP is covered, or what rights you retain after termination can have long-term commercial consequences.
• The governing law or jurisdiction changed. If the revised version adds or changes a governing law clause, your rights under the contract may be different from what you assumed.
• The changes are asymmetric. A revision that removes your rights while preserving or expanding the other party's rights is a deliberate negotiating move, not an administrative update.
• The financial exposure is significant. Use AI to identify the changes and prepare your questions, then take those specific questions to a lawyer. You will get more from the meeting.

For AI-assisted legal document comparison, see the AI Legal Document Review page.

Privacy and document security

Before uploading contract versions for comparison, consider what they contain.

LearnByAI processes documents in session-isolated storage. Your files are not shared with other users and are not used to train AI models. Even so:

• Both versions may contain confidential commercial terms, personal details, or third-party information. Review what each document contains before uploading.
• Check your organisation's confidentiality policy before uploading contracts that include the other party's confidential information. Most NDAs govern how you may share their terms.
• For contracts in active negotiation, consider whether sharing either version with any third-party platform, including AI tools, is consistent with the confidentiality obligations already in place.
• For signed agreements in active disputes or litigation, consult your legal team before uploading either version.

Read the Security page and Privacy Policy for a full explanation of how documents are stored and processed.

Before you compare: checklist

• Both versions uploaded before asking the first question
• Files clearly named so you can refer to each version precisely
• Confirmed both documents are text-based PDFs or DOCX files, not scanned images
• Requested a high-level summary of changes before asking about specific clauses
• Reviewed added obligations and confirmed each one is acceptable
• Reviewed removed protections and confirmed none were material to your original position
• Compared payment terms, including any new conditions or changed timing
• Compared termination rights and confirmed the balance is acceptable
• Compared IP ownership, including transfer timing and background IP
• Compared confidentiality duration and liability caps
• Requested a consolidated risk summary before forming a response
• Noted any changes that require legal advice before acceptance

Prompts you can copy

Use these in order for any contract comparison session. Copy the prompt, paste it into the chat, and adjust any details to match your specific documents.

1. I have uploaded two versions of the same contract. Please compare them and give me a high-level summary of what changed, which sections were modified, what was added, and what was removed.
2. What obligations appear in the revised version that were not present in the original? List each new obligation, which party it applies to, and where it appears in the document.
3. What was present in the original version that has been removed or significantly weakened in the revised version? Focus on obligations, protections, and rights that applied to me.
4. Compare the payment terms in both versions. What changed in the payment schedule, amounts, due dates, milestone conditions, or late payment provisions?
5. Compare the termination clauses in both versions. What changed in the notice period, grounds for termination, consequences of early termination, and rights on exit?
6. Compare the intellectual property clauses in both versions. What changed in who owns the work product, when ownership transfers, and whether background IP or licences are affected?
7. Compare the confidentiality clauses in both versions. What changed in the scope of confidential information, how long the obligations last, and any exceptions?
8. Compare the liability and indemnification clauses in both versions. What changed in liability caps, indemnification obligations, and exclusions?
9. Does the revised wording in [clause name or section] change what either party is actually required to do, or is this a stylistic change only?
10. Are there any changes in the revised version that appear in one clause but interact with or affect another clause in the document?
11. Based on your comparison of both versions, what are the three to five most significant changes from my perspective as the [party role]? Focus on changes that increase my risk, reduce my protections, or add obligations I should consider carefully.
12. Which changes in the revised version would you recommend I push back on before accepting, and why?

What you learned

• Upload both versions before asking any questions so the AI can reference both throughout the session.
• Start with a high-level summary to understand the scope of changes before investigating individual clauses.
• Added obligations require active acceptance. Removed protections require active identification.
• Payment terms, termination rights, IP ownership, confidentiality duration, and liability caps are the five areas most commonly revised in ways that shift commercial risk.
• Clause numbers are not reliable identifiers in a revised contract. Ask about subject matter, not section numbers.
• A stylistic rewrite is not the same as a substantive change. Always verify whether revised wording changes what either party is actually required to do.
• The consolidated risk summary in Step 9 is the most useful output for deciding how to respond to the other party.
• AI identifies what changed and what it means. A lawyer tells you whether to accept it.

Next step

Once you have identified the changes you want to push back on, the next step is understanding how to communicate them clearly. The following tutorial covers how to extract and summarise specific clauses for negotiation.

How to Summarise a Legal Document with AI (coming soon)

Related tutorials

These tutorials cover related tasks you may want to run alongside or after completing your contract comparison.

• How to Review a Contract with AI
• How to Summarise a Legal Document with AI (coming soon)
• How to Extract Key Dates and Deadlines from a Contract (coming soon)