Recipe-building worksheet
Use this when none of the ready recipes fits. Fill in the five boxes in order; each takes about two minutes. At the end you have a chain you can run and check.
1. Define the goal (one sentence)
Write: "At the end I want [what file] that [who] can [do what]."
- Bad: "Clean up my PDF."
- Good: "A single, searchable PDF under 10 MB that my accountant can open, with the receipts in date order."
Add three constraints: format (PDF, Word, CSV...), size or device limits, and sensitivity (may this go to a cloud service? see Privacy).
2. Identify the document's state
Answer each question about your input. Every "yes" is a step you might need.
| Question | If yes, think about |
|---|---|
| Is it protected with a password? | Unlock first (Merger, Converter and most extractors refuse locked files) |
| Is it a scan or photos (no selectable text)? | Deskew and Rotation, then Searchable |
| Does it open at all? | Recovery |
| Is it not a PDF (Word, images, ZIP)? | Converter or Merger |
| Are the pages many files, mixed sizes, wrong order? | Merger, Splitter, Delete Page, Resize |
| Does it have a form? | Extract Form Data before Flatten |
How to test: select a word (text or scan?); open it (damaged?); look at the page sizes and orientation; check for form fields.
3. Pick the apps
For the goal, list the verbs (merge, straighten, recognise, summarise, shrink, sign) and match each to one app. Use the family index pages: Organize, Add & Structure, Protect, Shrink & Repair, Extract, Convert & Create, AI understand. Check each app's "What it does not do" (for example TOC AI makes bookmarks only; Parser has no tables; Collage has one setting; there is no Redactor or Compare app).
Prefer the fewest steps: every step is a possible quality loss (compression, image conversion) and a possible extra cost against a daily allowance.
4. Order them by the rules
The app chapters give these rules; the ordering rules chapter collects them.
- Make it openable first: Unlock, Recovery.
- Fix pages next: Rotation, Deskew, Merge, Split, Delete, Resize. Anything that changes the number or order of pages comes before anything that points at pages (contents, tables, signatures).
- Give scans text before anything that reads text: Searchable before Extract Text, Ask PDF, PDF KB, Cheat Sheet, Checklist, TOC AI. (Deskew likely drops the text layer, so Deskew comes before Searchable, not after.)
- Add structure after the pages are final: Add Table, Add TOC, TOC AI, Illustrator.
- Forms: read the answers, then flatten, then sign.
- Shrink late, once: Compressor, after edits and OCR, before signing and protecting.
- Seal last: Sign, Protector, PDF/A conversion and validation. Compressing a signed file changes it.
- AI last, on the final text, and verify (Trust).
5. Verify
For every chain write down one check per step and run the chain on a two or three page copy first:
- Page count and order right?
- Text selectable where it should be?
- File size and fonts acceptable?
- Bookmarks and links land on the right page?
- AI output checked against the source?
If a step fails, fix that step before adding the next. Keep the original untouched; every Documentize app writes a new file.
Worked example 1: receipts to one searchable file
Goal: a single searchable PDF under a few MB, from 25 phone photos of receipts. State: images, no text, mixed orientation. Chain: Merger (images to one PDF, sequential, file order = date order) → Searchable (language, Deskew on) → Compressor (Medium). Why: photos must be a PDF before recognition; recognition adds file size, so shrink last. Verify: Ctrl+F for a shop name; size drop shown in the Compressor panel. Merger's limit is about 10 files and 30 MB per operation, so do three rounds and merge the results. Compare with the full photos-to-searchable recipe.
Worked example 2: a meeting pack that opens with a contents page
Goal: one PDF from three Word files and a budget workbook, with a contents page, protected. State: DOCX and XLSX. Chain: Merger (Word files in order) → Add Table (the xlsx, with Insert Page Before set to where it belongs) → Add TOC (page numbers from the final file) → Compressor → Protector. Why: pages first, then structure that depends on page numbers, then size, then the lock. Verify: click each contents entry. See also the submission-pack recipe.
Worked example 3: a 40-page English manual, French brief for the team
Goal: a short French summary and a one-page sheet from an English text PDF. State: text PDF, not scanned. Chain: Abstracts (Style Technical, Length Medium, Language French) → Cheat Sheet (Language French, Balanced) → spot check with Ask PDF. Why: no page changes are needed; AI goes last and gets a check by a French reader because AI can be fluent and wrong in another language. Verify: have a French speaker check numbers and names.
When your chain has no recipe
Post it in your team's notes in the same shape as the recipes: Goal, Starting state, Chain, Steps with option values, Check. Next step: Make it repeatable.