Why You Should Compare Two Versions of the Same Contract

You negotiated for two weeks. Email says “attached final for execution.” You sign at the broker’s office. Later, a dispute arises and your lawyer opens the PDF — and finds a indemnity clause, a longer lock-in, or a wider IP assignment that was not in the draft you marked up in Word. It happens in leases, employment, vendor deals, and builder agreements with uncomfortable regularity.

Verbal assurances do not override the signed PDF. Indian courts start with the document’s plain meaning unless fraud or misrepresentation is proved — and that is hard. Comparison before signature is cheap insurance.

When comparison matters most

Registry-ready lease vs your last redline. Employment offer letter vs the full agreement HR sends on day one. Builder’s “RERA draft” vs the document actually stamped. Translated fard vs the Punjabi original — area or name changes between versions have blocked sales.

Renewals: year-two lease renewal that quietly adds a 10% rent bump clause or removes a cap. Auto-renewed SaaS contracts with changed liability caps in the “updated terms” PDF.

Family settlements and partition deeds where one sibling’s copy includes an extra schedule. Even pagination and “minor wording cleanup” can hide material shifts.

What Doc Compare shows

Upload two PDFs — labeled old and new, or draft vs final. The tool highlights additions, deletions, and changed language, with AI summaries of material risk shifts, not only raw text diff. For land records and dense tables, it helps spot row-level changes that eyeballing misses.

Use the summary to build a written list of objections before you pay stamp duty, earnest money, or join a employer. Send email: “Clause 14(b) in the execution copy differs from our agreed draft dated X — please confirm revert or explain.” Paper trail matters.

Combine with Doc Bias on the new version alone if the diff is huge — understand overall tilt after you know what changed.

Land records and registries

Punjab and Haryana land records often exist in both Punjabi and English portal exports — differences in transliteration of names cause registry mismatches. Compare before you book the sub-registrar slot.

Registry drafts for sale deeds sometimes change area or khasra references from the fard the buyer verified. Treat deed comparison against fard as mandatory, not optional, for agricultural plots.

Commercial contracts with exhibits and schedules benefit from comparing exhibit versions too — not just the main body. Exhibits often carry pricing and SLAs that change silently.

If you use track-changes in Word but receive a “clean” PDF for signing, compare the clean PDF against your last exported Word PDF — not against the Word file with markup hidden. Hidden accept-all changes have burned teams before.

Treat comparison as part of closing checklist, alongside stamp duty, KYC, and signatures.

Workflow tips

Always keep the last agreed draft with date in filename. Never sign the same day you first see “final” if the deal is large — sleep on it, compare, lawyer glance.

For scanned PDFs, ensure both versions are readable; OCR quality affects diff accuracy. Re-scan if pages are crooked or low resolution.

Doc Compare consumes credits based on document size. For high-stakes deals, the credit cost is trivial next to one month’s wrongful lock-in or a widened indemnity.

In land deals, compare the seller’s fard from last year with the one issued this month before registry. Patwari updates, family partitions, or correction entries can change names or shares without the broker mentioning it. A diff takes minutes; discovering the change at the sub-registrar takes hours and may cancel the appointment.

Version control discipline helps: filename with date, person who sent it, and “draft / execution” in the name. When opposing counsel sends “clean” PDFs, compare against your last marked version, not against memory of a meeting six weeks ago.