Building a PDF Package a Reviewer Can Navigate and a Portal Accepts

You finish the package at 4:40 on the day it is due. Three hundred pages, every datasheet marked, drawings current. The GC's portal rejects the upload for size. You compress it, and now the scanned UL certificate is unreadable. You get it under the limit, it goes through, and two weeks later the review comes back with a comment that has nothing to do with your equipment: "Provide bookmarks per Section 01 33 00." The content was right. The file was wrong.

This article is how to build the PDF itself: bookmarks, page labels, searchable text, file size, splitting, and the file name, so the package gets read instead of returned on format.

Why format gets packages returned

A reviewer opens your PDF with forty other submittals waiting. If they can jump to the PLC datasheet in one click, they review the PLC. If they have to scroll through two hundred pages looking for it, they write "package not organized per spec" and move on to the next one. Many Division 01 submittal sections spell out electronic submittal format: PDF, bookmarked, searchable, sometimes a maximum file size or a naming convention. Read that paragraph on every job; reading 01 33 00 covers where it lives and what else it says.

Bookmarks that mirror the table of contents

The bookmark panel is the reviewer's real table of contents. It is always visible, it does not scroll away, and one click lands on the page. Build it as an exact mirror of the printed table of contents, same titles, same order, same nesting.

Two levels is right for most packages:

Cover
Transmittal
Table of Contents
1  Equipment Schedule
2  Drawings
     E01  Cover and Drawing Index
     E02  Enclosure Elevation
     E03  Interior Layout
     ...
3  Product Data
     PLC-1  Controller, 1756-L83E
     PS-1   24 VDC Power Supply
     ...
4  UL 508A Certificate

Rules that keep it useful:

• Every section gets a top-level bookmark. Every drawing sheet and every product data item gets a child bookmark.
• Titles say what the item is. "PS-1 24 VDC Power Supply" beats "Document 14" or the vendor's file name, "ds_quint4_ps_en_rev07.pdf."
• Bookmarks land on the first page of the item, not the page before, and not a blank separator.
• No leftover vendor bookmarks. Merging a manufacturer's PDF often drags in its own bookmark tree: their chapters, their figures, their language variants. Strip them or nest them under your item, collapsed. A bookmark panel with nine hundred entries is as bad as none.
• Set the file to open with the bookmark panel showing. Most PDF editors let you set the initial view in document properties. It costs ten seconds and saves the reviewer from wondering whether bookmarks exist.

Page labels

PDF pages have two numbers: the physical index the viewer counts from one, and an optional page label you define. Without labels, the viewer says page 147 while the printed footer says "Section 3, page 12," and every comment that cites a page number is ambiguous.

You have two good options. Number the whole package sequentially, stamp that number on every page, and leave the physical index alone, so the two always agree. Or define page labels so the viewer's page box shows what the footer shows, such as roman numerals for front matter and section prefixes after that. The first is simpler and survives every tool. Whichever you pick, the table of contents should cite the same numbers the reviewer will type into the page box.

Searchable text, not scans

A reviewer who presses Ctrl+F and types your catalog number expects to find it. That works only if the pages carry real text.

• Use the manufacturer's original PDF. Downloaded datasheets are already searchable and usually small. A printed and rescanned datasheet is neither.
• Export drawings to PDF directly from your CAD or schematic tool. Text stays text and lines stay sharp at any zoom.
• Run OCR on anything that has to be scanned, such as a signed certificate or a test sheet with a wet signature. Check the result by searching for a word you can see on the page.
• Keep the file unsecured. A password, or permissions that block commenting, stops the reviewer from marking it up, and many specs forbid both. If the reviewer cannot put a cloud on your drawing, they will write the comment in an email instead, and you will lose it.

File size limits and splitting

Limits come from three places: the spec, the GC's or owner's portal, and email. Portals set their own upload caps, and they differ, so ask the GC for theirs at the kickoff meeting rather than at 4:40 on the due date. Many mail servers reject attachments somewhere in the 10 to 25 MB range, which is why emailing a full package is the least reliable way to send it.

Before you split, shrink:

1. Replace scans with original PDFs. This is usually the biggest win.
2. Downsample images to what a screen needs. Photos and scanned pages at 600 dpi are where the weight lives.
3. Watch drawing exports. A sheet with a raster logo or a photo embedded at full resolution can outweigh the rest of the set.
4. Remove duplicate pages. The same vendor manual included under three items is three times the weight.

Check the result at 200 percent zoom on a drawing sheet and a small-print datasheet before you send it. A package under the size limit that nobody can read has failed in a different way.

If it is still too big, split by section, never mid-section. Each volume gets:

• Its own cover marked "Volume 1 of 3," with the same submittal number on every volume.
• Its own bookmarks for what it contains.
• A full table of contents in Volume 1 that says which volume holds each section.

The transmittal lists every volume as an enclosure. Upload them in the same submission so the reviewer never sees half a package.

Naming the file

The file name is the first thing the GC's document controller reads, and often the only thing they file by. If the spec or the GC dictates a convention, follow it to the character. If not, a name built from the same identifiers as the transmittal works everywhere:

26-118_40 61 13-002_Rev0_LS-4 Control Panel.pdf
26-118_40 61 13-002_Rev1_LS-4 Control Panel.pdf
26-118_40 61 13-002_Rev1_LS-4 Control Panel_Vol 2 of 3.pdf

Project number, submittal number, revision, short title. The revision belongs in the name so two versions never sit in a folder looking identical. Avoid characters that portals and file systems choke on, such as slashes, colons, and ampersands, and keep it short enough that it is not truncated in a portal list view. Numbering and revision conventions in more depth are in submittal numbering and revision schemes.

A last check before you send

Open the final file fresh, as the reviewer will:

1. The bookmark panel opens, and every bookmark lands on the right page.
2. The table of contents page numbers match what the viewer shows.
3. Searching for one catalog number from each section finds it.
4. Nothing is rotated, cropped, or blank.
5. It is under the portal's limit, and the file name matches the transmittal.

Five minutes, and the review is about your equipment instead of your PDF.

How Submittal Kit handles this

Bookmarking three hundred pages by hand the afternoon a package is due is the job nobody wants. In Submittal Kit, compile turns the package into one bound PDF in your configured section order, with a table of contents and bookmarks for every section and item generated together, so they always match. The download is named by your file name format, with project number and revision filled in from the package. When a portal or a reviewer wants the pieces, Download source documents exports every source PDF in a ZIP with the bill of materials as a workbook. For a reviewer outside your company, sharing sends a link instead of an attachment. It does not split packages into volumes for you. More on the submittal package.

Disclosure: I build Submittal Kit. The bookmark, size, and naming checks above apply to any PDF, whatever made it.