Start with a source inventory, not a blind merge
Collect the PDFs and images that actually belong in the submission and inspect them before combining. A supporting-document package is easier to review when every source has a clear section name and unnecessary pages are excluded before the final PDF is built.
- Keep the original source files until the destination confirms receipt.
- Use section titles that a reviewer can understand without opening the original filenames.
- Do not merge cryptographically signed source PDFs without understanding that the new combined file is a different document.
Choose file order and page order deliberately
Put documents in the order a reviewer is likely to need them: instructions or cover first when appropriate, then primary forms or evidence, then supporting exhibits. Within a PDF, exclude blank or irrelevant pages only when the destination permits it, and keep the remaining source-page order explicit.
- A simple source order is often better than interleaving pages from unrelated files.
- Keep document titles and page selections visible during review.
- Reset a PDF's page selection when you are unsure rather than silently losing pages.
Keep original sources and machine-readable evidence separately
A companion ZIP can preserve the original selected files without forcing them into the PDF representation. A CSV document index is useful when another person needs a source map, and a SHA-256 checksum manifest can later confirm whether the generated PDF or source files changed byte-for-byte.
- A checksum proves byte equality with the recorded digest; it does not prove who authored a document.
- The source ZIP is not a backup unless you store it safely after download.
- Do not include confidential sources in a companion ZIP unless the recipient actually needs them.
Measure the saved final PDF against the destination limits
The important byte count is the final saved PDF, not the sum of the inputs or an estimate shown before generation. Reopen and measure the actual package, compare the actual page count with the destination ceiling, and confirm the download filename is the one the portal expects.
- If the PDF is over a byte ceiling, use explicit PDF compression and inspect the resulting quality before submitting. The builder can stay open while Compress PDF runs in another tab, then recheck that compressed PDF against the same page geometry and final limits.
- If the page limit fails, remove optional generated pages or permitted source pages and rebuild.
- READY means the configured technical checks pass; it does not guarantee filing, application, legal, signature, or policy acceptance.