6 min read
By ScoutMyTool Editorial Team · Last updated: 2026-05-28
Introduction
I have watched perfectly competent permit packages bounce back from intake because the documents arrived as a dozen separate uploads in the wrong order, none of them bookmarked, and one of them too large for the portal. The submittal was complete; the assembly was not. That is the gap this guide closes. Whether you are a homeowner pulling a permit for a deck, a contractor submitting an addition, or an architect compiling a full review package, the goal of combining your permit PDFs is the same: produce one navigable file, in the order the inspector expects, signed where the regulator requires, sized for the portal, and searchable for the record. The technical content of the permit (the design, the calculations, the code compliance) is your responsibility; this is the assembly workflow that gets it through intake fast.
The documents in a typical permit submittal
| Document | Use | Combine note |
|---|---|---|
| Permit application form | Cover document, signed | First page; complete and signed |
| Plans / drawings | Approved design | Crisp, to scale, ordered by sheet |
| Calculations | Structural / energy / load | Per-section; clearly labelled |
| Specifications | Materials and methods | Searchable text; section bookmarks |
| Certificates / licences | Contractor + product | Current; legible; signed where required |
| Supporting reports | Geotech, energy, etc. | Stamped; dated; included in order |
| Index / cover sheet | Navigation for inspector | Built last; mirrors bookmark outline |
Step by step — combining the permit package
- Gather every required document. Use the jurisdiction’s permit checklist as a literal pick-list — application, plans, calcs, specs, certificates, supporting reports. Missing one item is the most common intake-rejection cause.
- Sign forms first, separately. Use Sign PDF on the application and any certificates before combining, so each signed page stays independently verifiable.
- OCR scanned pages. Run OCR over any scanned forms, certificates, or older reports so the whole package is searchable for the inspector and for your record.
- Merge in jurisdiction order. Combine with Merge PDF in the order the authority requires — see also combining construction PDFs.
- Add a bookmark per section. Use Add Bookmarks so the inspector can jump to application, plans, calcs, specs, certificates, reports from the bookmark panel.
- Number the pages, build the index. Apply page numbers and a cover/index sheet that mirrors the bookmark structure — the inspector should be able to navigate digitally or on paper.
- Compress to portal-size. Compress losslessly — see quality vs. size for keeping plan sheets crisp while still hitting the upload cap.
- Save versioned, keep an archive. Name the file
permit-<address>-<YYYY-MM-DD>.pdf, archive each submission under that name, and keep an uncompressed master locally.
Pitfalls that cause intake rejection or review delays
- Wrong order. The single fastest way to be sent back — match the jurisdiction’s required sequence exactly.
- Missing signature on the application form. Intake usually checks the front page first.
- Over portal-size cap. Compress first; split into volumes only if you still exceed.
- No bookmarks in a 200-page bundle. Functional but slow — review takes longer and minor issues become formal queries.
- Sideways-scanned pages. Rotate before combining; do not make the reviewer turn the screen.
- Stacked revision packs at the back. Replace the affected sheets in-place and re-issue; do not append.
- Image-only scans of text reports. OCR before combining so the bundle is searchable.
Related reading and tools
- Combine construction PDFs: the broader trade workflow this draws on.
- PDF for electricians: permit + load-calc package workflow.
- PDF for inspectors: the receiving side of this submittal.
- PDF for home inspectors: pre-purchase inspection report PDFs.
- Share PDFs without losing quality: compressing plans while keeping them crisp.
- Merge PDF: the core combine tool.
- Add Bookmarks: navigable per-section outlines.
- All ScoutMyTool PDF tools: the full toolkit.
FAQ
- What order should the combined permit PDF be in?
- Follow whatever order the jurisdiction (or the specific inspector) asks for if there is one — that is the single most important factor and saves everyone time at intake. If there is no published order, a workable default is application form first (signed and complete on the front), then plans/drawings in sheet order, then calculations, then specifications, then certificates and licences, then supporting reports, with an index/cover sheet built last so it mirrors the final document. Match the bookmark outline to that order so the inspector can jump straight to a section, and keep the order stable across revisions so anyone re-reviewing recognises the layout immediately. The order itself is administrative; the PDF craft is keeping it consistent, navigable, and matched to what the authority asked for.
- Do I need bookmarks, or is just merging enough?
- A merged file without navigation is functional but slow for the inspector, and slow is what causes minor issues to be raised as questions rather than resolved at a glance. Add a top-level bookmark per section (application, plans, calcs, specs, certificates, reports), and where useful, nested bookmarks per sheet or sub-section. The reviewer can then jump straight to any item from the bookmark panel rather than scrolling 200+ pages. Pair the bookmarks with a written index/cover sheet that mirrors the same structure, so both a digital reviewer and a printed-out reviewer can navigate. Bookmarks are essentially free to add once and pay back across every page of review — the standard professional submittal contains them.
- How do I keep the combined file under the portal upload limit?
- Most permit portals cap uploads at a fixed size (commonly 25, 50, or 100 MB), and exceeding it forces re-uploads or a phone call to intake. After combining, compress the file losslessly — image-heavy plan sheets are where size accumulates, so the priority is downsampling photos in supporting reports rather than the line-art plans (which should stay crisp). If you still exceed the cap, split the package into volumes (e.g. volume 1 plans, volume 2 calcs and reports) with a cover page in each that explains the split, rather than damaging plan legibility to fit. Keep an uncompressed master archive separately so the working file you upload stays small while the record copy stays high-fidelity.
- Should I combine before signing or sign before combining?
- Sign forms and certificates first, then combine the signed PDFs — this keeps every signed page independently verifiable and avoids re-signing the entire bundle if you later add or revise one supporting document. The cover application is typically signed in its original form and then placed at the front of the combined package; calculations and reports are signed/stamped by the responsible professional on their own document and dropped in. If the jurisdiction requires a single signature on the assembled package, sign the assembled file last, but keep the per-document signed originals as the authoritative record. Treat the combined PDF as the navigable submittal, not as the integrity boundary for signatures — the signatures live on the individual documents.
- What about plan revisions after the first submission?
- Revisions are normal during plan review, and the rule is: replace the affected sheets in the combined package rather than appending a separate revision pack at the back, which makes the inspector hunt across two locations for the current sheet. Use a clear revision marker (rev cloud, revision number, date) on each affected sheet, update the cover/index to reflect the revision, save the prior submission under a versioned filename so the history is preserved, and re-bookmark only if the section structure changed. Submit the new combined file as the document of record. Keeping one current combined file plus a versioned archive of every prior submission is far easier to navigate than a base file plus stacked addenda.
- How do I handle scanned paper documents in the combined file?
- Scanned documents (older certificates, hand-signed forms, paper reports) often come in as images, which makes them larger, unsearchable, and sometimes unreadable on a small screen. Before combining, run OCR over scanned pages so the inspector can search them and so they form part of the searchable record; rotate any pages scanned sideways so the bundle reads in one orientation; and check that text-heavy scans are crisp at the size they will be viewed. A bundle that mixes searchable born-digital pages with non-searchable scanned pages is worse than one where everything is searchable, so OCR is a quick win for both review speed and the long-term record.
- Is it safe to combine permit PDFs in a web tool?
- Permit packages contain property addresses, owner details, contractor licences, and sometimes commercially sensitive design information, so prefer a tool that processes files locally rather than uploading. ScoutMyTool merges, bookmarks, OCRs, and compresses entirely in your browser tab, so permit documents never leave your machine. For confidential or contractually-restricted work, confirm the tool does not upload before using it, and follow your jurisdiction’s upload requirements for the actual permit-portal submission.
Citations
- Wikipedia — “Building permit,” the regulatory submittal this assembly serves. en.wikipedia.org/wiki/Building_permit
- Wikipedia — “Construction document,” the document set that comprises a permit package. en.wikipedia.org/wiki/Construction_document
- Wikipedia — “Optical character recognition,” making scanned permit pages searchable. en.wikipedia.org/wiki/Optical_character_recognition
Combine your permit package without uploading it
Merge, bookmark, OCR, and compress your permit documents into one inspector-ready PDF entirely in your browser with ScoutMyTool — permit files never leave your machine.
Open Merge PDF →