← All postsPerson using Document Assembler on a laptop for a real client delivery task

Assemble Seven Mixed Files Into One Client Onboarding Packet

Combine PDFs, Word files and images into one PDF with a cover, contents page and bookmarks, in the order your client should read it.

document assemblerclient onboardingcombine PDF and Wordtable of contentsmixed file packetpdf toolsbrowser tools
4 min readPDF Tools

A new client signs on and expects one tidy file, but your onboarding material lives in seven places: a welcome letter in Word, a 12-page contract PDF, a one-page payment schedule, a brand guide PDF, a kickoff agenda saved as text, a logo PNG and a JPEG of the project site. Document Assembler turns that pile into one PDF with a cover page, a table of contents and a bookmark per section.

Unlike a plain merge, it accepts PDF, Word (.docx), plain text and PNG or JPEG images together, gives every file a section title, and fits every page to one page size.

Combine PDF, Word and images

Combine PDF, Word and images

The onboarding packet, in order

Decide the reading order before you upload anything. For a client who will read top to bottom, a sensible sequence is: welcome letter, kickoff agenda, brand guide, payment schedule, contract, logo, site photo. Putting the contract last in the packet is a choice, not a rule. Some teams lead with it. What matters is that you pick the order on purpose.

Say the sources are 2 pages (welcome letter), 1 (agenda), 9 (brand guide), 1 (payment schedule), 12 (contract), 1 (logo) and 1 (photo), 27 pages in all. The finished file will be longer than 27, because it adds a cover and a contents page. The download button shows the real total, such as "Download Document (30 pages)", so you can check it against what you expect before sending.

Steps in the tool

  1. Type a Document Title, such as "Harbour Studio Onboarding Packet". It is required while the cover page is on.
  2. Optionally fill Author / Prepared By.
  3. Choose a Page Size. US Letter and A4 are there, plus a range of book trim sizes. For a client packet choose the paper they will print on.
  4. Drop the files in. Each appears in a list; drag to reorder or remove a file.
  5. Edit the title next to each number. That text becomes the line in the Table of Contents, so use "Payment schedule" instead of pay_sched_final_v3.
  6. Tick or untick Cover Page, Table of Contents (auto-generated) and List of Images.
  7. Press Assemble Document, check the preview, then Download.

How pages are treated

Each page is scaled to fit inside the page size you chose, keeping its proportions, and rotated pages are turned upright first. A landscape logo on a portrait Letter page ends up with white space above and below, which looks fine. Judge each image page in the preview, since a low-resolution photo can look soft on a full page.

The tool adds one bookmark per section and nests a file's own bookmarks beneath it. Web and email links on source pages move to where their text now sits. Links that point from one page to another inside the original file should be tested before you rely on them.

The List of Images option adds a page listing pictures found in the document with page numbers. It is off by default and worth turning on only for packets where figures matter, such as a report. Full-page scans count as pages rather than figures.

Choosing titles that read well

The contents page is only as good as the titles you type. Aim for two to five words in the client's vocabulary: "Welcome and next steps", "Brand guide", "Payment schedule", "Master services agreement". Avoid version numbers and initials, because the client will see this page first. If two sections share a topic, distinguish them: "Contract, signed copy" and "Contract, working notes" tell the reader which to open. When you rebuild the packet next month, the titles are a quick checklist of what changed.

Also decide whether you want the cover at all. For an internal pack that only your team reads, switching the cover off removes the title requirement and saves a page. For anything a client will print, keep it, since it carries the name, the author line and a clear starting point.

Mistakes that embarrass you in front of a client

  • Leaving the signature page first because the files sorted alphabetically. Check the list order, not just the file names.
  • Keeping default titles from the file names. The contents page will show whatever you leave in each title box.
  • Uploading a Word file that depends on fonts you do not have. Convert-heavy layouts can shift, so skim every Word-origin page in the preview.
  • Forgetting a draft watermark inside one source file. Open each source briefly before you build.
  • Sending a 40 MB packet by email. Run the result through Compress PDF if the mail limit is tight, then check the images still look sharp.

Plain merge versus assembly

If everything is already PDF and you want no cover and no contents page, Merge PDF is the quicker path. If one file in the pile is a 200-page master and the client needs only part of it, extract those pages first with Split PDF and bring the smaller piece into the assembler. A different view of this chain is in the guide on assembling a magazine or newsletter PDF with a table of contents.

Keeping the originals safe

The assembled packet is a new PDF built in memory and offered as a download. Your source PDFs, Word files and images are read, not changed. The PDF is built in your browser and the files are not uploaded for assembly. Name the result with the client and the date, for example harbour-studio-onboarding-2026-10-17.pdf, and keep the sources in the same folder so version 2 takes five minutes.

Each assembly counts toward your 2 trial usages for the day, so settle the order and titles first. More tools for the same kind of document work sit in the PDF tools category.

Which packets do you assemble most, onboarding, proposals or reports? Tell us on the contact page.

Open Document AssemblerOpen Merge PDFOpen Split PDFOpen Compress PDF