Chapter lab: prepare a contract for external sharing
Scenario
You must send a contract to a partner. It contains an internal pricing annex that they must not see, it is large, and the partner must be able to confirm later that the file is the one you sent. You will cut, tidy, shrink, sign and verify it.
What you will learn
Why order matters in this family: edit first, sign last, and the one-minute check that proves it. You will also see exactly what Protector and Verify Signature do and do not promise.
Files you need
- A multi-page contract PDF (any sample; the last pages will play the "internal annex").
- A
.pfxsigning certificate you control, and its password. A self-made one is fine for the lab; your viewer will call it untrusted, which is expected.
Steps
- Delete Page: remove the internal annex pages, for example
7-9. See Delete Page. - Extract Metadata: look at author, title and producer in Extract Metadata. Write down anything you do not want the partner to see (the book cannot clean it for you here).
- Flatten: Flatten, so forms and annotations cannot change later.
- Compressor: Compressor, so it is email-friendly.
- Sign: Sign with your
.pfxand its password. Download the signed PDF. - Verify: switch the Sign page to Verify and check the result. See Verify Signature.
- Break it on purpose: run the signed file through Compressor again, then verify it. Read the red message.
- Optional password: Protector on a copy of the signed file, then try verifying that copy as well. Observe and note the result; the order rule says protect before signing (verify on the live app).
- Keep the signed, verified file from step 6 as your deliverable.
Result and checkpoints
- The page count is the original minus the annex.
- Step 6 shows "All signatures are valid" and lists at least one signature name.
- Step 7 shows that the same file is no longer valid after re-compression: proof that signing must be last.
- You can state in one sentence what "valid" means: unchanged since signing, not "trusted signer".
- The unredacted original is still stored separately.
Going further
- Add a PDF/A Validator run on the file before signing if the partner demands archive-grade PDF.
- For partial-page secrets, read PDF Redactor and use its verification step.
- Compare the draft and final versions with the method in Compare PDFs before step 5.
- See the full recipe: Contract round-trip.