Contract round-trip
Goal
Take a contract through its last negotiation round and out the door with confidence: you know exactly what changed, the final file is frozen, you sign it, and you prove the signature is intact.
The other side returns "the final version, just small tweaks". Before you sign anything you want to know whether it really is. Then you sign, and your counterparty must be able to check that nobody touched it afterwards.
Starting state
- Version A (what you sent) and version B (what came back) as PDFs with real text (if either is a scan, run Searchable first).
- A
.pfxcertificate you control and its password. - A text comparison tool outside Documentize (a code editor's diff, or a word processor's "compare documents").
Chain
Extract Text (A and B) → outside text diff → Flatten → (Compressor) → Sign → Verify Signature
two .txt files what changed freeze size last prove intact
Step by step
1. Extract Text, both versions
Run each version through Extract Text with the same mode (Pure, the default). If you upload both in one run you get a .txt per file plus a combined file. Different modes create false differences.
2. Compare outside Documentize
Compare PDFs does not exist as an app, so open the two .txt files in your diff tool. Read every difference, not just the ones the other party mentioned. A text diff misses changed images, signatures, layout and metadata; for those, compare the files side by side in your viewer and run Extract Metadata on both. Settle any difference before continuing.
3. Flatten
Upload the agreed PDF and press Flatten with options empty, so any form fields (dates, initials) become fixed. Flatten covers form fields; for comments or markup, test a copy. See Flatten.
4. Compressor (optional)
Only if the file must be smaller. Medium is enough. Do it now: any rewrite after signing breaks the signature. See Compressor.
5. Sign
Choose your .pfx, type its password, keep the mode on Sign, press Sign. There are no position or reason options: the app places a visible signature box on page 1 at the lower-left (400 x 200 units). Check that it does not cover text. Do not protect the file with a password first: Sign's quick path is for files without an open password. See Sign.
6. Verify Signature
On the same Sign page switch to Verify, upload the signed file, press the button. Green "All signatures are valid" lists the signature names. See Verify Signature.
Why this order
Compare while the document can still change; freeze while forms still hold values; shrink while the file can still be rewritten; then sign last because a signature only covers a file that never changes again. Verify immediately: it is the cheapest way to catch a step that rewrote the file.
Expected result
A signed PDF whose text you compared and agreed, and a green verification.
Check it worked
- The text diff showed only differences you accept.
- The verify panel is green and lists at least one signature name.
- The signature box on page 1 does not hide wording.
- Optional proof: run the signed file through Compressor and verify again; red proves the order rule (use a copy).
Variations
- Draft only: stop after the diff.
- Need confidentiality too: send the signed file over a protected channel, or protect a copy and tell the recipient the signed original travels separately. Protecting after signing is expected to break the signature (verify on the live app).
- Archival requirement: see Archive-ready (validate before signing).
What can go wrong
- "Valid" is not "trusted": Verify confirms only that the file is unchanged. It does not say who signed or whether the certificate is trusted; use your PDF viewer's signature panel for that. A self-made certificate shows as untrusted.
- Anyone, including you, who re-saves, compresses or unlocks the signed file breaks it.
- Wrong certificate password: error and no output.
- Several signers in turns: Sign handles one certificate per run.
- A scanned counter-signed page has no signature at all.