Golden rules of ordering
Summary
Eight rules cover nearly every chain. They all come from one idea: do the work that changes content first, and the work that freezes content last. Below, each rule has its reason (taken from the app chapters), then a catalogue of anti-patterns, the quiet mistakes that destroy signatures, text layers and bookmarks without any error message.
Details
The rules
| # | Rule | The reason |
|---|---|---|
| 1 | Repair before you analyse | Recovery comes first; Compressor, Flatten and others fail or misbehave on damaged files. Recovery itself rejects locked files, so Unlock before it if both problems exist |
| 2 | Unlock first | Merger refuses encrypted files; Searchable, Compressor, TOC AI, Flatten, Converter and the extractors expect an open file. Unlock is "usually step one" |
| 3 | Fix orientation before recognition | Searchable and OCR Image read sideways pages poorly; the Searchable chapter calls orientation errors the worst offender. Rotation first |
| 4 | Straighten before recognising, then recognise after Deskew | Deskew rebuilds pages as images and likely drops the text layer, so the order is Deskew then Searchable |
| 5 | Settle pages, then number them | Add TOC, Add Table and TOC AI store page numbers. Merge, split, delete and reorder first; Delete Page warns that an old contents page may be wrong afterwards |
| 6 | Recognise before you ask | Everything that reads text (Search, Extract Text, TOC AI, all of AI: understand) needs a text layer. Searchable once, then reuse the result |
| 7 | Compress after editing, once | A second pass makes already-softened pictures worse for little gain; Searchable enlarges the file, so shrink after it. Compressor is near last |
| 8 | Protect late, sign last | Protector locks the file (and you should not edit afterwards); a signature certifies "unchanged since signing", so Sign is the final rewrite. Verify Signature straight after |
The canonical order, compressed
Unlock → Recovery → Rotation → Deskew → Merger / Splitter / Delete Page / Resize
→ Searchable → Add TOC / TOC AI / Add Table → Flatten
→ Compressor → Protector → Sign → Verify Signature
You will rarely need every step. Skip what does not apply but keep the relative order of the steps you use.
The protect-then-sign sequence in the last line follows the Protect & Prove chapter's rule, but see the honest caveat in the dependency matrix: Sign works on a file without an open-password, and Protector rewrites the file. If you must do both, test the pair on a copy.
Edit order for specific goals
| Goal | Order | Why |
|---|---|---|
| Archive a paper pile | Rotation → Deskew → Searchable → Compressor | Orientation, then straightness, then text layer, then size |
| Make a final contract | Flatten → Compressor → Sign → Verify Signature | Freeze form content, shrink, certify, check |
| Send a confidential file | Delete Page → Compressor → Protector | Edit and shrink while open, lock last |
| Change an existing password | Unlock → Protector | The quick path will not re-encrypt an encrypted file |
| Contents for a merged pack | Merger → Add TOC | Numbers can only be right after pages are final |
| PDF/A delivery | Flatten → Optimize → PDF/A Validator | Validate the file you will actually deliver; validate again after any later rewrite, such as Compressor |
| Forms data and archive copy | Extract Form Data → Flatten | Flattened fields come back empty |
Anti-patterns: quiet destroyers
These are the mistakes that produce a file that looks fine and is not.
Destroying signatures
A digital signature certifies that nothing changed since signing. Any app that writes a new file is a threat; the chapters name these explicitly:
| Anti-pattern | What happens |
|---|---|
| Sign, then Compressor | "Compress before signing, never after: it would change a signed file" |
| Sign, then Protector | The signature is expected to break; check with Verify Signature |
| Sign, then Unlock | Unlocking can invalidate the signature; re-sign afterwards (verify on the live app for your file) |
| Sign, then re-save or print-to-PDF | Destroys the thing you are testing |
| Sign, then any other rewriting app: Merger, Splitter, Delete Page, Rotation, Resize, Add TOC, Flatten, Optimize, Searchable | Expected, not tested individually. Any change after signing breaks the signature; assume it does |
| Run Verify Signature on a copy you already processed | It will say invalid, or "not signed", and you will blame the sender. Test the file as received |
The reading-only apps are safe after signing: Verify Signature, PDF/A Validator, the extractors (Extract Text, Extract Metadata, Parser and friends) and the AI-understand apps, because they leave your PDF alone and produce something else.
Destroying text layers
| Anti-pattern | What happens |
|---|---|
| Searchable then Deskew | Deskew re-assembles each page from its image; do not count on the text layer surviving (verify on the live app). Run Searchable after |
| Resize in tile mode after Searchable | Tile mode converts pages to images; text is searchable again only if you tick OCR |
| Converter: PDF to image formats, then back to PDF | You have made pictures; run Searchable again |
| Unwatermark on a PDF you wanted to keep as is | The PDF comes back as plain re-typeset text: layout, images, links gone |
| Rotation Auto Skew on a searchable scan | It resamples content; whether the text layer survives is expected, not tested |
| Searchable "AI correction" on exact wording | It can change words; do not use for names, numbers or legal text without checking |
| Searchable to Word/Excel/PowerPoint output when you wanted the scan's look | The page picture is dropped and text is reflowed; looks different |
Destroying bookmarks and contents
| Anti-pattern | What happens |
|---|---|
| Add TOC or TOC AI, then Delete Page or Merger | Entries point to the wrong pages |
| TOC, then Add Table | The inserted table shifts later pages by its page count |
| TOC, then Abstracts | An Abstract page is added; add the TOC after, so it is listed |
| Bookmarked file, then Splitter | Bookmarks and links that pointed outside a piece cannot follow it |
| TOC, then Unwatermark | The PDF is re-typeset as plain text, so structure is gone (expected, not tested for bookmarks specifically) |
| Recovery with default "Full" cleaning | Strips metadata, attachments, history and hidden content; whether outlines are kept is not documented, so check |
| Search on a bookmarked file | The marked copy adds a "Search results" bookmark tree; how it sits beside your outline is not documented |
Other quiet costs
| Anti-pattern | What happens |
|---|---|
| Flatten before Extract Form Data | Fields become static content; the CSV comes back empty. Flatten is also irreversible on that copy |
| Compressor twice | Softer pictures for little gain |
| Compressor after PDF/A Validator | Any rewrite can change validity; validate again |
| Protecting a file before editing it | Most apps cannot read the result; unlock first |
| Forgetting the Protector password | There is no way to read it back; Documentize does not keep it |
| Collage on scanned documents | It crops around the AI's chosen subject; use Merger to keep pages whole |
| Checking Verify Signature on several files at once | Only the first file is reported (verify on the live app) |
What is safe in any order
- Reading apps: Extract Metadata, Extract Text, Extract Image, Parser, Ask PDF and the other AI-understand apps (with the text-layer caveat).
- PDF/A Validator and Verify Signature, which produce verdicts only.
- Anything on a copy: apps never alter your original, so a failed experiment costs only a download.