ON THIS PAGE
Use Merge PDF now
Upload Files

An application is rarely one document. A job application is a CV, a covering letter and a scan of a qualification. A planning submission is a form, drawings and a certificate. A legal exhibit bundle is whatever the schedule lists, in the order the schedule lists it. A client packet is a proposal, a pricing sheet and the terms. The workflow for combining them is the same every time: fix the order, combine the files into one PDF, then check the result page by page before it goes anywhere.
This guide follows that workflow end to end for a packet you are submitting to somebody else, where the order is specified and a missing page has consequences. The combining itself is one press of a button in Merge PDF. The care goes into what you do either side of it.
What the other side expects from one file
Submission instructions are usually explicit about the packet, and they are worth copying into a note before you start rather than reconstructing from memory at the end. Three requirements come up again and again:
- One file, in a stated order. Often numbered: form first, then evidence, then appendices. A reviewer working through a stack expects to find things where the instructions said they would be, and reordering to suit yourself costs you goodwill before anybody has read a word.
- A size ceiling. Upload forms and email gateways both have them. Finding out after you have assembled a hundred page bundle is a poor moment to discover the number.
- A file name format. Some portals specify one exactly, including the applicant reference. Where none is given, a name that identifies the packet and its date will still be read by a human filing it.
Underneath all three sits something simpler: the packet is going to be read in the order you send it. The order is not administrative tidiness, it is the document.
Build the packet order before you merge
Settle the order before you touch any files. Working it out while dragging rows around is how a page ends up in the wrong section. A short checklist is enough:
- List the required documents in the order the instructions give them. Use the instructions' own numbering, so a reviewer can follow along with the requirements beside them.
- Note each document's page count. The total is the number you will check the merged file against, and it is the single most useful thing to have written down.
- Name the files so they sort into that order. Prefixing them 01-, 02-, 03- means one pass of the Sort menu's file name option arranges the whole list correctly, with no dragging and nothing to misjudge.
- Decide where scans belong. Photographs of documents can go into a merge directly, one picture per page, so a phone photo of a signed form does not need converting first. Make sure it is the right way up and readable before it goes in.
- Mark anything that needs trimming. A bank statement where only two pages are relevant should be cut down before merging, not submitted whole.
Then add the files, confirm the list matches your note, and merge. The list reads top to bottom as the finished document.
Merge the packet and check every page
Checking the result is the step most often skipped, and on a submission it is the step that matters. Three checks catch almost everything.
Count the files that actually went in
A file that cannot be opened is skipped rather than silently dropped: the result screen names it, gives the reason, and reports how many of your files went into the document. A password protected scan is the usual culprit. The important habit is not reading a success message as "all of them" without looking at the count.
Count the pages
Compare the merged document's page count against the total you noted while ordering. These two numbers agreeing is the strongest single signal that the packet is complete. If they disagree, the file count above usually explains why.
Read the joins
Open the file and look at the first and last page of each section. Joins are where ordering mistakes become visible: an appendix that starts before the evidence it supports, a covering letter that ended up second, a blank final page that was in one of the originals and is now sitting in the middle of your bundle. The tool verifies that the PDF it produced is structurally complete before handing it over, so a merge that exhausted your device's memory reports an error rather than saving a file that will not open. That covers the mechanical failure. Only reading the document catches an ordering mistake.
If a page needs rotating or removing at this point, Organise PDF shows every page as a thumbnail and lets you fix it without rebuilding the packet from scratch.
Check the size before you upload
Check the finished file against the portal's ceiling before you go near the upload button, not after a failed submission at five to five.
Scans are almost always the reason a packet is heavy. A page of typed text is small; the same page photographed at full phone resolution can be several megabytes, and twenty of them make a bundle that no email gateway will take. If the merged file is over the limit, run it through Compress PDF and then check the compressed copy properly: open it and read the smallest print in it, which on a scanned bundle is where loss of quality shows up first. Signatures, reference numbers and figures in tables deserve a second look.
Keep the uncompressed merge as well. If the compressed version turns out to be too soft to read, you want to be adjusting from the full quality file rather than assembling the packet again.
Name the file and keep the originals
Give the file the name the instructions ask for. Where none is specified, something like Smith-J-Planning-Application-2026-03.pdf will make sense to a stranger filing it and to you a year later. Avoid "final", which is never true for long, and avoid spaces if the portal is old enough to mind.
Then keep everything you started with: the individual source documents, your note of the order and page counts, and the merged file you actually submitted. Resubmission is common. An assessor asks for one extra document, a page is illegible, a deadline moves and something needs updating. Rebuilding a packet from the originals takes a minute if you kept them and the order note, and is genuinely unpleasant if you kept neither.
Ready to assemble yours? Open Merge PDF, arrange the list to match your note, and merge.
Ready to try Merge PDF?
Combine multiple PDFs into one document in the order you choose.