How to Create a Clean Final PDF From a Negotiated Contract (Free)

You have negotiated the contract. Both sides have said "this looks fine," and now someone needs to turn the marked-up Word file into one clean PDF that gets signed. This sounds like a five-minute task. It is actually where the most embarrassing mistakes in contract execution happen, because "clean" means more than "no more red text on screen." It means no tracked changes left un-accepted, no comments left in the file, and no hidden metadata sitting in the document properties nobody remembered to check. (Adira, which publishes this guide, sells contract review and CLM software, so we have a commercial interest in you trusting how contracts get built. This guide works whether or not you ever use Adira.)

Below: a step-by-step guide to a genuinely clean execution copy across the tools most people actually use, the specific privacy risk that catches people out, a runnable test before sending the file, and where finalisation sits legally under Indian contract law.

Why "final" is a legal question, not just a filename

Renaming a file "Contract_FINAL_v7.docx" does not make it final. What makes a document the contract is that both sides agreed to a fixed set of words and signed off on exactly that text, and that text is what a court, if it comes to that, will treat as the whole story. Section 91 of the Indian Evidence Act, 1872 states the rule directly:

"When the terms of a contract, or of a grant, or of any other disposition of property, have been reduced to the form of a document... no evidence shall be given in proof of the terms of such contract, grant or other disposition of property... except the document itself, or secondary evidence of its contents in cases in which secondary evidence is admissible." Source: Section 91, Indian Evidence Act, 1872 (Indian Kanoon)

In plain terms: once your terms are in a signed document, that document proves the terms, not the email thread, not the marked-up draft, not what someone remembers from a call. A "final" PDF that still visibly carries unresolved comments, an unaccepted change, or a stray draft's page numbers muddies the very thing Section 91 asks a court to rely on: one clean document that says what was actually agreed. It does not usually change what the contract legally means (a resolved comment is not a term of the contract), but it creates exactly the "wait, which version did we sign" argument a five-minute checklist prevents entirely.

What "clean" actually means: five things, not one

A genuinely clean execution copy has all five true at once. Missing any one is a real, common failure mode:

1. Every tracked change is accepted or rejected. No pending insertions, deletions, or formatting changes remain.
2. Every comment is deleted, not just resolved. A "resolved" comment (Word or Google Docs) is hidden from the default view, not gone from the file.
3. Hidden metadata is scrubbed. Author names, document statistics, custom XML data, and the list of recent editors are stored in the file whether or not they show up on the page.
4. Page and exhibit numbering is checked, not assumed. Accepting changes can shift paragraph numbering and page breaks; an "Exhibit A" reference written against an old page count can point to the wrong page in the final file.
5. The file is flattened to a real PDF, not a Word document renamed with a .pdf extension, and not a "print to PDF" that quietly drops some annotations while keeping others.

Skipping step 2 causes actual damage; steps 1, 4, and 5 mostly cause confusion. Step 2 can hand the other side your internal negotiation notes.

Step by step: Microsoft Word

1. Accept all tracked changes. Review tab, small arrow under Accept, "Accept All Changes." Do this even if the document looks clean; a change can be tracked and simply not displayed if your markup view is set to "Simple Markup" or "No Markup."
2. Delete every comment, not just resolve it. Review tab, arrow under Delete, "Delete All Comments in Document." Word's "Resolve" button greys a thread out; it does not remove it from the file.
3. Run Document Inspector. File, then Info, "Check for Issues," "Inspect Document." Tick every box, Comments, Revisions and Versions, Document Properties and Personal Information, Hidden Text, Custom XML Data, then Remove All wherever flagged. This catches things accepting changes and deleting comments alone do not, such as author names embedded in document properties.
4. Recheck numbering. Confirm exhibit letters, clause cross-references, and any table of contents still match after accepted changes shifted the layout.
5. Save as PDF, not print to PDF from a printer driver: File, Export, "Create PDF/XPS," or Save As, choosing PDF. This flattens the text into a real PDF instead of an editable Word file wearing a PDF extension.

Step by step: LibreOffice Writer

1. Accept all changes. Edit, Track Changes, Manage, select all, Accept.
2. Delete comments. Right-click any comment, "Delete All Comments," or clear them in bulk from the Comments sidebar.
3. Strip personal data. Tools, Options, LibreOffice, Security, Security Options and Warnings, tick "Remove personal information on saving." For a file already saved without this, use File, Properties, Reset Properties on that specific file.
4. Export as PDF, without comments. File, Export As, "Export as PDF," and on the General tab confirm "Comments" is unticked, so nothing leftover gets baked into the PDF by accident.

Step by step: Google Docs

Google Docs behaves differently from Word, in both directions.

1. Accept all suggestions. Tools, "Review suggested edits," Accept All.
2. Delete comments, do not just resolve them. Clicking the checkmark marks a comment "Resolved" and hides it from the default view, but it is not deleted: anyone with access to the document can still see it, since resolving only removes it from the active thread. To actually remove one, open its three-dot menu and choose Delete. Check the comment history pane if you inherited someone else's document; old resolved threads are still sitting there.
3. Download as PDF. File, Download, "PDF Document." A direct export generally does not render comment bubbles into the PDF at all, since Docs' PDF engine does not print the comment sidebar. The risk sits in the source file, not the export: share the Doc's link or export to Word instead, and every undeleted comment and the full version history come along.

Method 4: Weave, for one free pass that catches most of this

If you would rather not juggle three tools' menus from memory, open the file in Weave, Adira's free, no-login browser contract tool, and run a final pass clause by clause, checking nothing marked-up got left behind. It does not replace Document Inspector or LibreOffice's metadata option, but it is a fast way to confirm the document reads clean before you flatten it.

The privacy catch: what a leftover comment can actually cost you

This is the part most "how to save as PDF" guides skip, and it is the actual reason this step deserves five minutes of care rather than none.

A negotiation comment thread often holds things nobody meant for the other side to read: "push back hard on this, legal says we can concede it if they push," "client will not notice if we widen this," "this is our floor, do not go below it." None of it is secret internally. All of it is a real problem if it survives into the file you send.

You do not need a contract dispute to see the shape of the risk. In January 2019, lawyers for Paul Manafort filed a redacted court document in the Mueller investigation where the redaction bars were drawn over the text visually, without removing the underlying text. Reporters simply selected the "blacked-out" passages and pasted them elsewhere, revealing the contents in full, including that Manafort had shared campaign polling data with a Russian-linked associate. The lesson is not about redaction specifically: content people assume is hidden because it is not visible on screen is often still sitting in the file underneath, recoverable with a copy-paste or a comment-panel click. A comment thread hidden by "Resolve," or a tracked change never accepted, is the same failure mode in a contract negotiation.

The runnable test: do this before you send the "final" PDF

Do not trust that the document looks clean. Test it every time, in under two minutes:

1. Open the final PDF itself (not the source file) in a plain PDF reader.
2. Press Ctrl+F (Cmd+F on Mac) and search for "comment." Also try a distinctive word from an internal comment, if you remember one.
3. Check the file's properties panel (Acrobat Reader: File, then Properties) and look at the Author field. A person's name or template metadata that should not still be there means it was not scrubbed.
4. Select the whole page with Ctrl+A and paste into a plain text editor. A leftover comment marker or tracked-change artefact usually shows up there even when it is not visually rendered.
5. Confirm every exhibit reference and page number matches where that exhibit actually lands in this final file.

If any of these turn up something, fix it in the source document, then re-export. Patching a PDF directly usually leaves the original text recoverable underneath, the same problem as the redaction failure above.

Bad clause → better clause: the "this is the final document" clause

Most contracts already carry a clause meant to say the signed document is the whole deal. Weak drafting here compounds a messy finalisation; strong drafting limits the fallout even if some marks slip through.

Bad: "This Agreement constitutes the entire agreement between the parties."

What is wrong: it says nothing about prior drafts, comments, or correspondence, or which version governs if a stray earlier draft circulates after signing.

Better: "This Agreement, together with its Schedules and Exhibits, constitutes the entire agreement between the Parties regarding its subject matter, and supersedes all prior and contemporaneous drafts, negotiations, comments, markups, and correspondence between the Parties, whether written or oral. In the event of any conflict between this executed Agreement and any earlier draft or communication, this executed Agreement shall prevail."

What changed and why: it names drafts, comments, and correspondence as superseded, and adds a conflict rule putting the signed text above anything before it. This does not make it safe to send a sloppy file, but if an old comment or draft resurfaces, the contract itself already tells a court which version controls, reinforcing Section 91 rather than leaving it to be argued from scratch.

Where execution goes next: numbering, then signature

Once the file is genuinely clean, confirm the page count and exhibit letters one more time in the actual PDF you are about to send, since export can occasionally reflow a page. Then decide how it gets signed: a clean PDF is not automatically an executed contract, that depends on a valid signature. See Is an Electronic Signature Legally Valid in India for what the IT Act, 2000 requires, including the difference between a signature that is merely valid and one that carries the law's evidentiary presumption.

This checklist assumes a proper redline exchange already happened. If you are still at the markup stage, see How to Negotiate a Contract for Free: The Redline Email Workflow for getting from a first draft to an agreed one without losing track of what changed and why.

Red flags to check before you send a "final" PDF

Normal	Red flag	Why it matters
Every comment shows deleted in the Review pane or comment sidebar	Comment shows "Resolved" but is still present when you look	Resolved is not deleted; anyone with the source file or a Docs link can still read it
Document Inspector (Word) or Reset Properties (LibreOffice) run fresh, shows "no items found"	Metadata check never run, or run once before later edits added new comments	New edits after your last cleanup pass can reintroduce what you removed
File exported through a genuine "Save/Export as PDF" function	File just renamed from .docx to .pdf, or "printed" to PDF	A renamed file may still be fully editable; a careless print-to-PDF can drop visible marks while metadata survives
Exhibit letters and page numbers checked against the actual final PDF	Numbering only checked in the draft before the last "Accept All Changes"	Accepting changes shifts page breaks and paragraph numbers
Ctrl+F, select-all, and metadata check all run on the exported PDF itself	Only the source document was checked; the exported PDF never opened separately	The export step is exactly where things get missed
Signature method confirmed valid for this document type before sending	File sent for signature with no thought to whether e-sign is even usable for it	Some documents, certain property transactions among them, cannot be validly e-signed under Indian law at all

US and global contrast

The mechanics are near identical in the US, since it is the same software. What differs is emphasis. US legal practice has treated "metadata scrubbing" as a standard professional-responsibility item for close to two decades; several state bar ethics opinions discuss a lawyer's duty to avoid transmitting metadata revealing a client's confidential information, and many firms run a metadata-cleaning plugin automatically. In India this is still mostly manual and mostly missed, exactly why a checklist earns its place rather than assuming habit covers it.

FAQ

Does deleting a comment in Word actually remove it, or just hide it? A genuine delete (Review, then Delete, then "Delete All Comments in Document") removes it. Marking a comment resolved only hides it from the default view; run Document Inspector afterward to confirm nothing remains.

Is a resolved comment in Google Docs actually gone? No. Anyone with access to the document can still see it. Only the comment's Delete option removes it, which matters most if you later share the Doc's link or export to Word rather than PDF.

Do I need Adobe Acrobat Pro to flatten a contract to a clean PDF? No. Word's "Save As PDF," LibreOffice's "Export as PDF," and Google Docs' "Download as PDF" all produce a genuine flattened PDF for free. Acrobat Pro adds redaction and advanced metadata editing, not required for a standard finalisation pass.

Why does exhibit and page numbering matter if the wording is correct? Because "see Exhibit B at page 14" pointing to the wrong page creates real ambiguity about what was agreed. Recheck numbering in the exported PDF, not just the source draft, since accepted changes shift page breaks.

Can hidden metadata in a contract actually hurt me legally, or is it just embarrassing? Both, depending what it reveals. Metadata exposing your negotiating floor is usually a commercial problem, not a separate legal claim, unless it breaches a confidentiality obligation you owe someone else. The bigger legal point is Section 91: the signed document is what a court looks to, so a messy final file mainly creates dispute risk about which version is real.

This guide covers how to produce a genuinely clean, final execution copy of a negotiated contract, and what commonly goes wrong at that step. It does not tell you whether your contract's underlying terms are fair or enforceable, nor cover every jurisdiction's formatting or stamping requirements for a specific document type. For that, and before you rely on any clause in a live negotiation, talk to a lawyer; this is not legal advice.