Building an application packet: turning many files into one tidy PDF

Why portals want a single PDF

Application systems, grant schemes, visa submissions and tender portals increasingly ask for "one PDF, max N MB". It is not bureaucracy for its own sake: a single file cannot have missing attachments, is easy to archive, and prints as one document. The task, then, is assembling your letters, scans, forms and screenshots — usually a mix of PDFs, JPGs and maybe a Word export — into one ordered file.

The assembly workflow

A reliable order of operations:

• Convert non-PDF pieces first. Photos and scans that arrived as JPG or PNG become PDF pages (ToolDock's image-to-PDF tool does this in batches, one image per page in your chosen order).
• Merge everything. Combine the converted pieces with your existing PDFs into one file. Most merge tools let you drop files in the exact order you want them appended — check the order before running, because it is much easier to fix now.
• Reorder and prune. Open the merged file in an organize tool and drag pages into final order, delete the accidental blank scan on page 7, and drop the duplicate copy of your CV you forgot you had added.
• Rotate what the scanner turned. It is remarkably common for one page to come out sideways; rotate just that page, not the document.
• Compress last. Compressing before merging wastes effort, because merging does not re-compress. Do it once, at the end, against the portal's size cap.

Details reviewers notice

Three things separate a tidy packet from a messy one. Page numbering: if the portal expects signed pages in sequence, add visible page numbers after merging so a printed copy can be checked against an index. Consistent orientation: mixed portrait/landscape is fine when it is intentional, jarring when it is not. And a filename that says what it is: "Smith_application_2026.pdf" beats "merged(3).pdf" for anyone opening it downstream.