To compare two PDF contract versions safely, use two separate passes. First, compare the actual clauses, numbers, schedules, and signature blocks with a text or visual redline. Second, compare the PDFs’ file properties to catch changes in page count, PDF version, authoring software, dates, encryption, fonts, images, and embedded JavaScript.
The second pass is where the PDFCheck PDF Comparer helps. It compares selected metadata and structural properties side by side. It does not compare contract wording, images, or graphics, and it does not provide a legal conclusion. A “no property differences” result therefore does not prove that the visible terms are identical.
Contract comparison in six steps
- Freeze and label the baseline and revised files.
- Compare source documents when editable originals are available.
- Run a text and visual comparison of the two PDFs.
- Compare PDF metadata and structural properties.
- Validate any digital signatures separately.
- Record every resolved change before approval.
Why One Comparison Is Not Enough
| Review layer | What it can reveal | What it cannot settle alone |
|---|---|---|
| Source-document redline | Inserted, deleted, moved, or reformatted wording | Whether the delivered PDF matches the reviewed export |
| PDF text/visual comparison | Changed text, images, graphics, annotations, or layout | Why the file was regenerated or which properties changed |
| PDF property comparison | Page count, metadata, software, dates, security, and structural differences | Whether clauses or rendered pages contain the same content |
| Digital-signature validation | Signature status, certificate details, and post-signing integrity | Whether an unsigned revision was commercially or legally acceptable |
Use the layers together. Microsoft’s current legal blackline workflow compares two Word documents and shows the changes in a third document without changing the source files. Adobe’s Acrobat PDF comparison overview describes comparison of text, images, graphics, formatting, annotations, and backgrounds. PDFCheck adds a focused property-level check; it is not a substitute for either content method.
Step 1: Lock the Correct Baseline
- Name the files clearly. Use labels such as
contract-v07-approved-draft.pdfandcontract-v08-counterparty.pdf, not two files both calledfinal.pdf. - Keep the received copies unchanged. Compare duplicates, and preserve the original email, portal download, or document-management record.
- Confirm the direction. Decide which file is the baseline and which is revised before interpreting additions or deletions.
- Collect the editable sources. If both Word versions exist, compare those before relying on PDF extraction.
Step 2: Redline the Contract Content
When Word originals are available, use a source-document comparison first. Review changes at word or character level and keep the generated blackline as evidence of what was checked. If only PDFs are available, use a PDF comparison product that explicitly compares text and visual content.
Do not accept a summary count as the review. Open each reported change in context and check the high-consequence fields below.
| Contract area | Examples to verify | Common hiding place |
|---|---|---|
| Parties and dates | Legal names, effective date, notice period | Header, definitions, signature page |
| Money and quantities | Price, currency, tax, payment days, volume | Tables, annexes, footnotes |
| Scope and deliverables | Included work, acceptance, service levels | Schedules and statements of work |
| Risk terms | Liability, indemnity, warranty, insurance | Defined terms and cross-references |
| Exit and renewal | Termination rights, auto-renewal, survival | End of main terms or order form |
| Signatures and attachments | Signer, capacity, exhibits, page order | Final pages and appended schedules |
Scanned contracts need OCR first
If the contract is an image-only scan, a text comparison may find little or nothing. Follow the scanned PDF and OCR workflow, then visually confirm the OCR result against the page images. OCR errors in names, decimal points, or clause numbers can look like real revisions.
Step 3: Compare the PDF Properties
- 1. Open the PDFCheck PDF Comparer.
- 2. Upload the baseline as PDF A and the revised file as PDF B. Use the same copies you just reviewed.
- 3. Review every highlighted property. The report checks page count, file size, PDF version, title, author, subject, creator, producer, creation and modification dates, encryption, tagged status, font count, image count, and embedded JavaScript.
- 4. Explain each difference. A new producer may be a normal re-export; a changed page count may reflect an accepted schedule. The comparison identifies differences, not intent.
- 5. Escalate unexplained changes. Return to the source and visual comparison instead of treating metadata as proof of tampering.
Property differences are clues. Creation and modification dates can be missing, overwritten, or affected by export software. Font and image counts do not tell you which clause changed. For a deeper authenticity review, combine the comparison with the PDF edit-checking workflow and keep the business context.
Step 4: Validate Signatures Separately
If either version is digitally signed, do not edit, print, or re-save it before validation. Use the PDF Signature Checker for a signature-focused report, and confirm important signatures in the organization’s trusted validation workflow.
Adobe’s current digital-signature validation guide separates signature status, signer certificate, and timestamp review. A visual signature image is not the same as a cryptographic digital signature, and a property comparison does not validate either one.
Step 5: Record the Approval Decision
- Record the exact filenames and version labels reviewed.
- List every substantive change and its owner: accepted, rejected, or awaiting clarification.
- Note the content-comparison method, PDF property check, and signature result.
- Resolve missing pages, attachments, OCR uncertainty, and unexplained property differences.
- Approve only the exact final file, then preserve that approved copy in the controlled system.
What PDFCheck does not prove
PDFCheck compares selected metadata and structural properties. It does not redline contract wording, compare rendered pages, determine whether a change is authorized, verify legal effect, certify an audit trail, or replace professional review. “No differences” means no differences were found in the compared property fields—not that the contracts are identical.
Final Pre-Approval Checklist
- The baseline and revised files are correctly labeled and preserved.
- All wording, number, table, annotation, and layout changes were reviewed in context.
- Every page, exhibit, schedule, and signature block is present and ordered correctly.
- PDF property differences were reviewed and explained.
- Scanned pages were OCR-checked and visually confirmed.
- Digital signatures were validated separately when present.
- The approval record identifies the exact final PDF.
Start with a content redline, then run the exact two files through the PDFCheck PDF Comparer. If either file is damaged or incomplete, use the PDF Validator before approving the workflow.