Submittal package guide

Build a submittal package, not another folder of files.

By PM4Subs Published

To build a construction submittal package, verify the project requirements, collect the relevant documents, select what belongs in the package and arrange it in a clear order. Add the required identifying information, review the finished PDF and submit it through the project's required process.

CHECK 01

Verify what this project needs.

Start with the project specifications and submission instructions. A specification-review tool can help you locate relevant sections, but your team still checks the source documents. Do not assume every product or every job requires the same information.

  • Identify the relevant specification sections and required documents.
  • Confirm the proposed products and scope covered by this package.
  • Check the required recipient, format and submission process.
  • Assign an owner for missing information before assembling the package.

CHECK 02

Select documents, not the entire project folder.

A project may hold files for several materials or scopes. Select the documents that belong in this submission and leave unrelated or superseded files out. Separate named packages can help keep different submissions organized.

  • Collect the required product data, reports and supporting documents.
  • Check that the documents describe the products you intend to submit.
  • Exclude irrelevant or outdated files from this package.
  • Use a clear package name so the next person can identify its purpose.

CHECK 03

Make the package easy to navigate.

Arrange the selected files in a useful order. Use section names that explain what the reviewer is looking at. The cover and contents should describe the finished package rather than a previous version of it.

  • Check company and project information on the cover.
  • Give documents clear display names.
  • Arrange the documents and add named section dividers where useful.
  • Make sure the table of contents agrees with the selected files and order.

CHECK 04

Review the assembled PDF.

Building a PDF does not verify the technical suitability of its contents. Open the combined file and check both its organization and the underlying product information before sending it to the project reviewer.

  • Inspect the cover, table of contents, dividers and document pages.
  • Check that the intended files appear and excluded files do not.
  • Confirm the package is readable and supporting documents are complete.
  • Resolve missing or conflicting information with the responsible team member.

CHECK 05

Send it and preserve what was sent.

Follow the general contractor's or project team's required submission process. Emailing a package is not the same as having it approved. Keep the sent package for reference, and track requests for revision separately from the original submission.

  • Confirm the recipient and required delivery method.
  • Keep a record of the package actually submitted.
  • Record the submission status without treating it as approval.
  • If revision is requested, update the relevant documents, rebuild and review before resubmitting.

How PM4Subs helps

Your documents. Your order. One finished submittal package.

The PM4Subs package builder lets your team select individual documents, arrange them with named dividers and save multiple named packages. It generates a company-branded cover, table of contents and combined PDF. After review, email the package link from the project and retain the sent package for reference or resend. Outbound email requires a configured sending account.

Explore submittals

This is a workflow checklist, not a complete list of requirements for every project. Follow the applicable project documents and submission instructions.

KEEP READINGProposal checklist

A few good questions

Before you bring
the team on board.

What is the difference between a submittal log and a package builder?

A log tracks submission items and their status. A package builder assembles the documents the reviewer will receive. PM4Subs includes package assembly and can connect sent packages to submission tracking; these are related but different jobs.

Does every submittal package need the same documents?

No. The contents depend on the project requirements and the products or scope being submitted. Verify the specifications and submission instructions rather than copying the contents of a previous job.

Does generating or emailing the PDF mean it is approved?

No. Your team reviews the contents before submission, and the appropriate project reviewers make approval decisions. A generated PDF or sent email is not an approval.

Your next job is a good place to start

Bring your workflow.
We'll show you where it fits.

$200/month for 4 seats during beta. Request access for a conversation about your company and your jobs.

Prefer email? [email protected]

Let's get your team connected.

$200/month for 4 seats during beta.
Tell us about your team. We'll follow up personally.

We'll use these details to respond to your request. Privacy policy